Integrating the Healthcare Enterprise

 

 IHE/MESA Content Creator Tests

 

Electronic Radiology Laboratory
Mallinckrodt Institute of Radiology
510 South Kingshighway Blvd.
St. Louis, MO  63110
314.362.6965 (Voice)
314.362.6971 (Fax)

 

Revision 10.12.0
29-January-2007


Content Creator (an Abstract Actor)

  1. Introduction
  2. Patient Identification
  3. Configuration
  4. Starting the MESA Servers
  5. Installation Test
  6. Loading Test Data

XDS-SD Tests

  1. 14101: XDS-SD - Sample XDS-SD Documents
  2. 14110: XDS-SD - Wrapper Format - HL7 CDA R2

General Test Cases for Content Profiles

  1. 40001: CDA R2 Valid Schema
  2. 40002: PCC Valid Schema
  3. 40003: PCC Schematron Patient Randolph
  4. 40004: PCC Schematron Patient Wilson
  5. 40050: PCC Schematron Structure
  6. 40051: PCC Schematron CRS
  7. 40100: PCC Schematron XPHR
  8. 40101: PCC Schematron EDR
  9. 40102: PCC Schematron BPPC
  10. 40103: PCC Schematron PPHP
  11. 40104: PCC Schematron - XDS-MS Discharge Summary
  12. 40105: PCC Schematron - XDS-MS: Referral
  13. 40106: PCC Schematron - XD-Lab
  14. 40150: XPHR Sample
  15. 40151: EDR Sample
  16. 40152: BPPC Sample
  17. 40153: PPHP Sample
  18. 40154: XDS-MS Discharge Summary Sample
  19. 40155: XDS-MS Referral Sample
  20. 40156: XD-Lab Sample
  21. 40157: XPHR Sample Extract
  22. 40158: XPHR Sample Update
  23. 40200: PCC XPHR Aortic Dissection
  24. 40201: PCC XPHR Cardiac Referral
  25. 40300: PCC EDR Aortic Dissection
  26. 40301: PCC EDR Cardiac Referral
  27. 40400: PCC BPPC Aortic Dissection
  28. 40401: PCC BPPC Cardiac Referral
  29. 40500: PCC PPHP Aortic Dissection
  30. 40501: PCC PPHP Cardiac Referral
  31. 40600: PCC XDS-MS Referral Aortic Dissection
  32. 40601: PCC XDS-MS Referral Cardiac Referral
  33. 40700: PCC XDS-MS Discharge Summary Aortic Dissection
  34. 40701: PCC XDS-MS Discharge Summary Cardiac Referral

Appendix A: Aortic Dissection

Appendix B: Cardiac Referral


 

Content Creator (an Abstract Actor)

Introduction

This Content Creator test document describes test cases in two broad categories:

In general, if you are testing the XDS-SD profile, you have a short number of tests and have some latitude on content.

If you are testing PCC Content Profiles, make sure you read the introductory material in that section of this document. If you just start running tests in numerical sequence, you will find that you are creating extra work that you do not need to do.

Patient Identification

Configuration

The MESA scripts are run from the directory $MESA_TARGET/mesa_tests/pcc/actors/ccrt.

Starting the MESA Servers

There are no MESA servers to start for this test.

Installation Test

Loading Test Data

General Test Cases for Content Profiles

This section contains test cases that are general to Content Creator actors in the PCC and other domains. The Content Creator under test should be reading this introduction and this section if it creates content for one or more of the following profiles:

  1. XDS-MS: Discharge Summary
  2. XDS-MS: Referral
  3. XPHR
  4. EDR
  5. BPPC
  6. PPHP
  7. XDS-SD

The tests in this section are based on two medical scenarios:

  1. Aortic Dissection
  2. Cardiac Referral

The Content Creator under test will create documents for one or both of the medical scenarios. Your system is not given an option. The test instructions will indicate if you have to create content for only one or forboth of the scenarios. Your content creator should create content documents according to the profiles that are supported. For example, if you create an XPHR document, you will be required to run test 40100.

Some of the tests require special attention.

Read all of the tests in this section before starting any one test. You will find that you need to create very few documents to complete these tests. Each test is examining a different aspect of your document.

40001: CDA R2 Valid Schema

In test 40001, the Content Creator determines that a document consists of well formed XML and is valid according to the CDA R2 schema definition.

References

Copyright Notice

The HL7 CDA documents are copyrighted material and are not distributed as part of the MESA release package. You will need to obtain the documentation from HL7 (as a member) or from the IHE Project Manager.

Instructions

This test requires you to use one of the available XML tools that can perform schema validation. We use XML Spy for this purpose, but do not take that as an endorsement of that product. We assume that different organizations will adopt different tools for visually examining and modifying documents for test purposes.

  • Obtain the CDA Schema definitions. These are available to HL7 members. Non members may have rights under IHE agreements. Look for a copy of these files in the MESA software release web page. From HL7, you are looking for “CDA Normative Edition zip package”. The MESA release page will have that zip package and a separate zip file with just the schema definitions.
  • The CDA definition files that you will need are:
    • CDA.xsd
    • POCD_MT000040.xsd
    • datatypes-base.xsd
    • datatypes.xsd
    • NarrativeBlock.xsd
    • voc.xsd
  • Use the XML tool of your choice to open and validate your CDA document using the CDA.xsd schema definition.
  • Capture the output of the schema definition. This may be a log file or screen capture, depending on the tool.
  • Name the file SYSTEM_NAME_40001.<extension> where <extension> is the appropriate file extension (txt, doc, jpg, bmp). SYSTEM_NAME is the name of the system as registered for testing.
  • Submit that file to the Project Manager for evaluation.

Evaluation

  • Submit the schama validation file created above to the Project Manager. You will know from your tool if the CDA document you produced is valid.

Administrative Notes

The schema definitions distributed by HL7 in the CDA Normative Edition are found in different folder and have references that include that folder structure. If you use their files directly, you will need to maintain that directory structure. The xsd files found on the MESA distribution web page will have all of the files in a common directory and the internal references will reflect that structure.

40002: PCC Valid Schema

This test is a placeholder in the event that a schema is defined for content profiles.

There is nothing to do for this test.

40003: PCC Schematron Patient Randolph

40003 tests Patient Demographics stored in most PCC (and some ITI) content documents using Schematron. This includes proper formatting and proper values, including the OIDs on the patient identifiers.

The table below shows the demographics that are required for this test.

Patient
Given Name Frederick
Family Name Randolph
birthTime 19590203
administrative gender code system 2.16.840.1.113883.5.1
administrative gender code M

Patient ID (extension)

40003

Patient ID root/OID

1.3.6.1.4.1.21367.2005.1.1

 

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

  1. Create your PCC or ITI Content Profile Document using the demographics listed above.
  2. Copy the file to the MESA test system where it can be accessed by the test scripts.
  3. Set the current directory to $MESA_TARGET/mesa_tests/pcc/actors/ccrt.
  4. Evaluate the XML file to test demographic values using the steps below.

Evaluation

  1. Run the evaluation script on the file of your choice (FILE) as described below:
    perl  40003/eval_40003.pl <log level> FILE
  2. The result file is found in 40003/grade_40003.txt. The test is successful when the grade file indicates 0 errors.
  3. Submit the grade to the Project Manager for evaluation.

Supplemental Information

  1. To conserve time, create a Content Profile Document that is specific to one or more content profiles (XPHR, XDS-MS, XDS-SD etc.). Use that same document in this test and other tests.
  2. If your system provides more detail in the "birthTime" field, the schematron test will fail your submission. Merely submit a note with the results and indicate those differences.

40004: PCC Schematron Patient Wilson

40004 tests Patient Demographics stored in most PCC (and some ITI) content documents using Schematron. This includes proper formatting and proper values, including the OIDs on the patient identifiers.

The table below shows the demographics that are required for this test.

Patient
Given Name Margaret
Family Name Wilson
birthTime 19480503
administrative gender code system 2.16.840.1.113883.5.1
administrative gender code F

Patient ID (extension)

40004

Patient ID root/OID

1.3.6.1.4.1.21367.2005.1.1

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

  1. Create a PCC or ITI Content Profile Document using the demographics listed above.
  2. Copy the file to the MESA test system where it can be accessed by the test scripts.
  3. Set the current directory to $MESA_TARGET/mesa_tests/pcc/actors/ccrt.
  4. Evaluate the XML file to test demographic values using the steps below.

Evaluation

  1. Run the evaluation script on the file of your choice (FILE) as described below:
    perl 40004/eval_40004.pl <log level> FILE
  2. The result file is found in 40004/grade_40004.txt. The test is successful when the grade file indicates 0 errors.
  3. Submit the grade to the Project Manager for evaluation.

Supplemental Information

  1. To conserve time, create a Content Profile Document that is specific to one or more content profiles (XPHR, XDS-MS, XDS-SD etc.). Use that same document in this test and other tests.
  2. If your system provides more detail in the "birthTime" field, the schematron test will fail your submission. Merely submit a note with the results and indicate those differences.

40050: PCC Schematron

40050 tests general structure and content of any PCC content profile document.

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

  1. Create a PCC Content Profile Document that satisfies one of the PCC content profiles:
    • XDS-MS: Referral
    • XDS-MS: Discharge Summary
    • EDR
    • XPHR
    • PPHP
  2. Copy the file to the MESA test system where it can be accessed by the test scripts.
  3. Set the current directory to $MESA_TARGET/mesa_tests/pcc/actors/ccrt.
  4. Evaluate the XML file using the steps below.

Evaluation

  1. Run the evaluation script on the file of your choice (FILE) as described below:
    perl 40050/eval_40050.pl <log level> FILE
  2. The result file is found in 40050/grade_40050.txt. The test is successful when the grade file indicates 0 errors.
  3. Submit the grade to the Project Manager for evaluation.

Supplemental Information

Test 40050 is looking for these features in the Content Profile Document:

40051: PCC Schematron CRS

40051 tests general structure of PCC documents that are defined according to the HL7 CRS

References

Copyright Notice

The HL7 CRS documents are copyrighted material and are not distributed as part of the MESA release package. You will need to obtain the documentation from HL7 (as a member) or from the IHE Project Manager.

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

  1. Obtain the HL7 Care Record Summary documents (Levels 1 and 2), Release 1.0, Informative Ballot 02, August 11, 2005.
  2. Extract the files schema.sch and voc.xml from that documentation.
  3. Create a PCC Content Profile Document that satisfies one of the PCC content profiles:
    • XDS-MS: Referral
    • XDS-MS: Discharge Summary
    • EDR
    • XPHR
    • PPHP
  4. Validate the document you created using your favorite XML tool and the schematron file listed above, or
  5. Validate your document using these further steps:
    • Copy the file schema.sch into the folder $MESA_TARGET/mesa_tests/pcc/actors/ccrt/40051
    • Copy the file to the MESA test system where it can be accessed by the test scripts.
    • Set the current directory to $MESA_TARGET/mesa_tests/pcc/actors/ccrt.
    • Evaluate the XML file using the steps below.

Evaluation

  1. Run the evaluation script on the file of your choice (FILE) as described below:
    perl 40051/eval_40051.pl <log level> FILE
  2. The result file is found in 40051/grade_40051.txt. The test is successful when the grade file indicates 0 errors.
  3. Submit the grade to the Project Manager for evaluation.

Supplemental Information

Test 40051 is looking for these features in the Content Profile Document:

40052: PCC Placeholder

40052 is a placeholder for a future test.

References

Instructions

40100: PCC Schematron XPHR

40100 tests general structure and content of an XPHR content profile document.

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

  1. Create a PCC Content Profile Document that satisfies the XPHR PCC content profile.
  2. Copy the file to the MESA test system where it can be accessed by the test scripts.
  3. Set the current directory to $MESA_TARGET/mesa_tests/pcc/actors/ccrt.
  4. Evaluate the XML file using the steps below.

Evaluation

  1. Run the evaluation script on the file of your choice (FILE) as described below:
    perl 40100/eval_40100.pl <log level> FILE
  2. The result file is found in 40100/grade_40100.txt. The test is successful when the grade file indicates 0 errors.
  3. Submit the grade to the Project Manager for evaluation.
  4. <

Supplemental Information

You are welcome to reuse the document you tested in 40001, 40002, 40003, 40004, 40050.

Test 40100 is looking for these features in the XPHR Content Profile Document:

  1. Document template ID: 1.3.6.1.4.1.19376.1.5.3.1.1.2
  2. Document template ID: 1.3.6.1.4.1.19376.1.5.3.1.1.5
  3. Vital Signs section wth proper template ID (1.3.6.1.4.1.19376.1.5.3.1.1.5.3.2) and LOINC code (8716-3).
  4. Medications section with proper template ID (1.3.6.1.4.1.19376.1.5.3.1.3.19) and LOINC code (10160-0).
  5. Medications Entry section with proper template ID (1.3.6.1.4.1.19376.1.5.3.1.4.7).
  6. Conditions section with proper template ID ( 1.3.6.1.4.1.19376.1.5.3.1.1.5.3.3) and LOINC code (46240-8)
  7. Encounter Entry section with proper template ID (1.3.6.1.4.1.19376.1.5.3.1.4.14)
  8. Allergies section with proper template ID ( 1.3.6.1.4.1.19376.1.5.3.1.3.13) and LOINC code (10155-0).
  9. Allergies Entry section with proper template ID (1.3.6.1.4.1.19376.1.5.3.1.4.5)
  10. Other tests for singular entries and expected coded values.

40101: PCC Schematron EDR

40101 tests general structure and content of an EDR content profile document.

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

  1. Create a PCC Content Profile Document that satisfies the EDR PCC content profile.
  2. Copy the file to the MESA test system where it can be accessed by the test scripts.
  3. Set the current directory to $MESA_TARGET/mesa_tests/pcc/actors/ccrt.
  4. Evaluate the XML file using the steps below.

Evaluation

  1. Run the evaluation script on the file of your choice (FILE) as described below:
    perl 40101/eval_40101.pl <log level> FILE
  2. The result file is found in 40101/grade_40101.txt. The test is successful when the grade file indicates 0 errors.
  3. Submit the grade to the Project Manager for evaluation.

Supplemental Information

You are welcome to reuse the document you tested in 40001, 40002, 40003, 40004, 40050.

Test 40101 is looking for these features in the EDR Content Profile Document:

  1. Document template ID: 1.3.6.1.4.1.19376.1.5.3.1.1.10
  2. Document template ID: 1.3.6.1.4.1.19376.1.5.3.1.1.3
  3. REASON FOR REFERRAL section wth proper template ID (1.3.6.1.4.1.19376.1.5.3.1.3.1) and LOINC code (42349-1).
  4. HISTORY OF PRESENT ILLNESS section (1.3.6.1.4.1.19376.1.5.3.1.3.4 : 10164-2).
  5. PROBLEM LIST section (1.3.6.1.4.1.19376.1.5.3.1.3.6 : 11450-4).
  6. HISTORY OF ALLERGIES section (1.3.6.1.4.1.19376.1.5.3.1.3.13 : 10155-0).
  7. TRANSPORT MODE section (1.3.6.1.4.1.19376.1.5.3.1.1.10.3.2 : 11459-5).
  8. HISTORY OF MEDICATION USE section (1.3.6.1.4.1.19376.1.5.3.1.3.19 : 10160-0)
  9. Advance Directions section (1.3.6.1.4.1.19376.1.5.3.1.3.34 : 42348-3)

40102: PCC Schematron BPPC

40102 tests general structure and content of a BPPC content profile document.

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

  1. Create a PCC Content Profile Document that satisfies the BPPC PCC content profile.
  2. Copy the file to the MESA test system where it can be accessed by the test scripts.
  3. Set the current directory to $MESA_TARGET/mesa_tests/pcc/actors/ccrt.
  4. Evaluate the XML file using the steps below.

Evaluation

  1. Run the evaluation script on the file of your choice (FILE) as described below:
    perl 40102/eval_40102.pl <log level> FILE
  2. The result file is found in 40102/grade_40102.txt. The test is successful when the grade file indicates 0 errors.
  3. Submit the grade to the Project Manager for evaluation.

Supplemental Information

You are welcome to reuse the document you tested in 40001, 40002, 40003, 40004, 40050.

Test 40102 is looking for these features in the BPPC Content Profile Document:

40103: PCC Schematron PPHP

40103 tests general structure and content of a PPHP content profile document.

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

  1. Create a PCC Content Profile Document that satisfies the PPHP PCC content profile.
  2. Copy the file to the MESA test system where it can be accessed by the test scripts.
  3. Set the current directory to $MESA_TARGET/mesa_tests/pcc/actors/ccrt.
  4. Evaluate the XML file using the steps below.

Evaluation

  1. Run the evaluation script on the file of your choice (FILE) as described below:
    perl 40103/eval_40103.pl <log level> FILE
  2. The result file is found in 40103/grade_40103.txt. The test is successful when the grade file indicates 0 errors.
  3. Submit the grade to the Project Manager for evaluation.

Supplemental Information

You are welcome to reuse the document you tested in 40001, 40002, 40003, 40004, 40050.

Test 40103 is looking for these features in the PPHP Content Profile Document:

40104: PCC Schematron XDS-MS Discharge Summary

40104 tests general structure and content of a XDS-MS Discharge Summary content profile document.

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

  1. Create a PCC Content Profile Document that satisfies the XDS-MS Discharge Summary PCC content profile.
  2. Copy the file to the MESA test system where it can be accessed by the test scripts.
  3. Set the current directory to $MESA_TARGET/mesa_tests/pcc/actors/ccrt.
  4. Evaluate the XML file using the steps below.

Evaluation

  1. Run the evaluation script on the file of your choice (FILE) as described below:
    perl 40104/eval_40104.pl <log level> FILE
  2. The result file is found in 40104/grade_40104.txt. The test is successful when the grade file indicates 0 errors.
  3. Submit the grade to the Project Manager for evaluation.

Supplemental Information

You are welcome to reuse the document you tested in 40001, 40002, 40003, 40004, 40050.

Test 40104 is looking for these features in the XDS-MS Discharge Summary Content Profile Document:

  1. Document template ID: 1.3.6.1.4.1.19376.1.5.3.1.1.2
  2. Document template ID: 1.3.6.1.4.1.19376.1.5.3.1.1.4
  3. PROBLEM LIST section wth proper template ID (1.3.6.1.4.1.19376.1.5.3.1.3.6) and LOINC code (11450-4).
  4. HISTORY OF PAST ILLNESS section (1.3.6.1.4.1.19376.1.5.3.1.3.8 : 11348-0).
  5. HOSPITAL DISCHARGE DX section (1.3.6.1.4.1.19376.1.5.3.1.3.7 : 11535-2)
  6. HOSPITAL ADMISSION DX section (1.3.6.1.4.1.19376.1.5.3.1.3.3 : 46241-6)
  7. HOSPITAL DISCHARGE MEDICATIONS section (1.3.6.1.4.1.19376.1.5.3.1.3.13 : 10183-2)
  8. HISTORY OF ALLERGIES section (1.3.6.1.4.1.19376.1.5.3.1.3.22 : 10155-0)
  9. HOSPITAL COURSE section (1.3.6.1.4.1.19376.1.5.3.1.3.5 : 8648-8)
  10. PLAN OF CARE section (1.3.6.1.4.1.19376.1.5.3.1.3.31 : 18776-5)

40105: PCC XDS-MS Referral

40105 tests general structure and content of an XDS-MS Referral content profile document.

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

  1. Create an XDS-MS Referral Content Profile Document that satisfies the XDS-MS Referral PCC content profile.
  2. Copy the file to the MESA test system where it can be accessed by the test scripts.
  3. Set the current directory to $MESA_TARGET/mesa_tests/pcc/actors/ccrt.
  4. Evaluate the XML file using the steps below.

Evaluation

  1. Run the evaluation script on the file of your choice (FILE) as described below:
    perl 40105/eval_40105.pl <log level> FILE
  2. The result file is found in 40105/grade_40105.txt. The test is successful when the grade file indicates 0 errors.
  3. Submit the grade to the Project Manager for evaluation.

Supplemental Information

You are welcome to reuse the document you tested in 40001, 40002, 40003, 40004, 40050.

Test 40105 is looking for these features in the XDS-MS Referral Content Profile Document:

  1. Document template ID: 1.3.6.1.4.1.19376.1.5.3.1.1.2
  2. Document template ID: 1.3.6.1.4.1.19376.1.5.3.1.1.3
  3. REASON FOR REFERRAL section wth proper template ID (1.3.6.1.4.1.19376.1.5.3.1.3.1) and LOINC code (42349-1).
  4. HISTORY OF PRESENT ILLNESS section (1.3.6.1.4.1.19376.1.5.3.1.3.4 : 10164-2).
  5. PROBLEM LIST section (1.3.6.1.4.1.19376.1.5.3.1.3.6 : 11450-4).
  6. HISTORY OF ALLERGIES section (1.3.6.1.4.1.19376.1.5.3.1.3.13 : 10155-0).
  7. HISTORY OF MEDICATION USE section (1.3.6.1.4.1.19376.1.5.3.1.3.19 : 10160-0)

40106: PCC Schematron XD-Lab

40106 tests general structure and content of an XD-Lab content profile document.

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

  1. Create a PCC Content Profile Document that satisfies the XD-Lab content profile.
  2. Copy the file to the MESA test system where it can be accessed by the test scripts.
  3. Set the current directory to $MESA_TARGET/mesa_tests/pcc/actors/ccrt.
  4. Evaluate the XML file using the steps below.

Evaluation

  1. Run the evaluation script on the file of your choice (FILE) as described below:
    perl 40106/eval_40106.pl <log level> FILE
  2. The result file is found in 40106/grade_40106.txt. The test is successful when the grade file indicates 0 errors.
  3. Submit the grade to the Project Manager for evaluation.

Supplemental Information

You are welcome to reuse the document you tested in 40001, 40002, 40003, 40004, 40050.

Test 40106 is looking for these features in the XD-Lab Content Profile Document:

40150: XPHR Sample

This test is now deprecated in favor or 40157 and 40158.

This test is due 2 weeks before the normal deadlines. Submit a document (even if your work is not complete) so the other participants can review your sample.

In test 40150, you submit a sample of an XPHR document that your system will produce. The purpose of this test is to allow the Project Manager to post this sample to consumers so they can read/test/render the documents in advance of face to face testing.

References

Instructions

To run this test, follow these steps:

  1. Create one XPHR document that satisfies the XPHR profile.
  2. For the patient name, construct a name that is:
    • Last Name: The name of your system as registered in Kudu
    • First Name: A short mnemonic/abbreviation for your company that is recognizable
  3. Name the file using this convention: XPHR_KuduName.xml
  4. Before submitting, place the file in a zip file: XPHR_KuduName.zip
  5. After you submit the document into Kudu, send an email to the Project Manager to wake him up.

Evaluation

The evaluation for this test is performed by the other participants. As they review your document, there will be conversation about items in the document.

Supplemental Information

40151: EDR Sample

This test is due 2 weeks before the normal deadlines. Submit a document (even if your work is not complete) so the other participants can review your sample.

In test 40151, you submit a sample of an EDR document that your system will produce. The purpose of this test is to allow the Project Manager to post this sample to consumers so they can read/test/render the documents in advance of face to face testing.

References

Instructions

To run this test, follow these steps:

  1. Create one EDR document that satisfies the EDR profile.
  2. For the patient name, construct a name that is:
    • Last Name: The name of your system as registered in Kudu
    • First Name: A short mnemonic/abbreviation for your company that is recognizable
  3. Name this file: <your_system_name_40151.xml
  4. If possible, render the document and perform a screen capture (JPEG or other common format).
  5. Place the XML file and screen capture in a zip file: <your_system_name_40151.zip>
  6. Upload the zip file into the Connectathon Wiki: http://ihewiki.wustl.edu/wiki.
  7. Find the entry for your Connectathon and test 40151. There should be an existing link you can click that will allow you to upload the file.
  8. Go to the Kudu tool and enter a note indicating you have uploaded your sample.
  9. As Content Consumer actors render your data, you may receive a request for interpretation or directives from the Project Manager to repair attributes. This may prove to be an iterative process.

Evaluation

The evaluation for this test is performed by the other participants. As they review your document, there will be conversation about items in the document.

Supplemental Information

40152: BPPC Sample

This test is due 2 weeks before the normal deadlines. Submit a document (even if your work is not complete) so the other participants can review your sample.

In test 40152, you submit a sample of a BPPC document that your system will produce. The purpose of this test is to allow the Project Manager to post this sample to consumers so they can read/test/render the documents in advance of face to face testing.

References

Instructions

To run this test, follow these steps:

  1. Create one BPPC document that satisfies the BPPC profile.
  2. For the patient name, construct a name that is:
    • Last Name: The name of your system as registered in Kudu
    • First Name: A short mnemonic/abbreviation for your company that is recognizable
  3. Name this file: <your_system_name_40152.xml
  4. If possible, render the document and perform a screen capture (JPEG or other common format).
  5. Place the XML file and screen capture in a zip file: <your_system_name_40151.zip>
  6. Upload the zip file into the Connectathon Wiki: http://ihewiki.wustl.edu/wiki.
  7. Find the entry for your Connectathon and test 40152. There should be an existing link you can click that will allow you to upload the file.
  8. Go to the Kudu tool and enter a note indicating you have uploaded your sample.
  9. As Content Consumer actors render your data, you may receive a request for interpretation or directives from the Project Manager to repair attributes. This may prove to be an iterative process.

Evaluation

The evaluation for this test is performed by the other participants. As they review your document, there will be conversation about items in the document.

Supplemental Information

40153: PPHP Sample

This test is due 2 weeks before the normal deadlines. Submit a document (even if your work is not complete) so the other participants can review your sample.

In test 40153, you submit a sample of a BPPC document that your system will produce. The purpose of this test is to allow the Project Manager to post this sample to consumers so they can read/test/render the documents in advance of face to face testing.

References

Instructions

To run this test, follow these steps:

  1. Create one PPHP document that satisfies the PPHP profile.
  2. For the patient name, construct a name that is:
    • Last Name: The name of your system as registered in Kudu
    • First Name: A short mnemonic/abbreviation for your company that is recognizable
  3. Name this file: <your_system_name_40153.xml
  4. If possible, render the document and perform a screen capture (JPEG or other common format).
  5. Place the XML file and screen capture in a zip file: <your_system_name_40153.zip>
  6. Upload the zip file into the Connectathon Wiki: http://ihewiki.wustl.edu/wiki.
  7. Find the entry for your Connectathon and test 40153. There should be an existing link you can click that will allow you to upload the file.
  8. Go to the Kudu tool and enter a note indicating you have uploaded your sample.
  9. As Content Consumer actors render your data, you may receive a request for interpretation or directives from the Project Manager to repair attributes. This may prove to be an iterative process.

Evaluation

The evaluation for this test is performed by the other participants. As they review your document, there will be conversation about items in the document.

Supplemental Information

40154: XDS-MS Discharge Summary Sample

This test is due 2 weeks before the normal deadlines. Submit a document (even if your work is not complete) so the other participants can review your sample.

In test 40154, you submit a sample of an XDS-MS Discharge Summary document that your system will produce. The purpose of this test is to allow the Project Manager to post this sample to consumers so they can read/test/render the documents in advance of face to face testing.

References

Instructions

To run this test, follow these steps:

  1. Create one XDS-MS Discharge Summary document that satisfies the XDS-MS profile (Discharge Summary option).
  2. For the patient name, construct a name that is:
    • Last Name: The name of your system as registered in Kudu
    • First Name: A short mnemonic/abbreviation for your company that is recognizable
  3. Name this file: <your_system_name_40154.xml
  4. If possible, render the document and perform a screen capture (JPEG or other common format).
  5. Place the XML file and screen capture in a zip file: <your_system_name_40154.zip>
  6. Upload the zip file into the Connectathon Wiki: http://ihewiki.wustl.edu/wiki.
  7. Find the entry for your Connectathon and test 40154. There should be an existing link you can click that will allow you to upload the file.
  8. Go to the Kudu tool and enter a note indicating you have uploaded your sample.
  9. As Content Consumer actors render your data, you may receive a request for interpretation or directives from the Project Manager to repair attributes. This may prove to be an iterative process.

Evaluation

The evaluation for this test is performed by the other participants. As they review your document, there will be conversation about items in the document.

Supplemental Information

40155: XDS-MS Referral Sample

This test is due 2 weeks before the normal deadlines. Submit a document (even if your work is not complete) so the other participants can review your sample.

In test 40155, you submit a sample of an XDS-MS Referral document that your system will produce. The purpose of this test is to allow the Project Manager to post this sample to consumers so they can read/test/render the documents in advance of face to face testing.

References

Instructions

To run this test, follow these steps:

  1. Create one XDS-MS Referral document that satisfies the XDS-MS profile (Referral option).
  2. For the patient name, construct a name that is:
    • Last Name: The name of your system as registered in Kudu
    • First Name: A short mnemonic/abbreviation for your company that is recognizable
  3. Name this file: <your_system_name_40155.xml
  4. If possible, render the document and perform a screen capture (JPEG or other common format).
  5. Place the XML file and screen capture in a zip file: <your_system_name_40155.zip>
  6. Upload the zip file into the Connectathon Wiki: http://ihewiki.wustl.edu/wiki.
  7. Find the entry for your Connectathon and test 40155. There should be an existing link you can click that will allow you to upload the file.
  8. Go to the Kudu tool and enter a note indicating you have uploaded your sample.
  9. As Content Consumer actors render your data, you may receive a request for interpretation or directives from the Project Manager to repair attributes. This may prove to be an iterative process.

Evaluation

The evaluation for this test is performed by the other participants. As they review your document, there will be conversation about items in the document.

Supplemental Information

40156: XD-Lab Sample

This test is due 2 weeks before the normal deadlines. Submit a document (even if your work is not complete) so the other participants can review your sample.

In test 40156, you submit a sample of an XD-Lab document that your system will produce. The purpose of this test is to allow the Project Manager to post this sample to consumers so they can read/test/render the documents in advance of face to face testing.

References

Instructions

To run this test, follow these steps:

  1. Create one XD-Lab document that satisfies the XD-Lab profile
  2. For the patient name, construct a name that is:
    • Last Name: The name of your system as registered in Kudu
    • First Name: A short mnemonic/abbreviation for your company that is recognizable
  3. Name this file: <your_system_name_40156.xml
  4. If possible, render the document and perform a screen capture (JPEG or other common format).
  5. Place the XML file and screen capture in a zip file: <your_system_name_40156.zip>
  6. Upload the zip file into the Connectathon Wiki: http://ihewiki.wustl.edu/wiki.
  7. Find the entry for your Connectathon and test 40156. There should be an existing link you can click that will allow you to upload the file.
  8. Go to the Kudu tool and enter a note indicating you have uploaded your sample.
  9. As Content Consumer actors render your data, you may receive a request for interpretation or directives from the Project Manager to repair attributes. This may prove to be an iterative process.

Evaluation

The evaluation for this test is performed by the other participants. As they review your document, there will be conversation about items in the document.

Supplemental Information

40157: XPHR Extract Sample

This test is due 2 weeks before the normal deadlines. Submit a document (even if your work is not complete) so the other participants can review your sample.

In test 40157, you submit a sample of an XPHR Extract document that your system will produce. The purpose of this test is to allow the Project Manager to post this sample to consumers so they can read/test/render the documents in advance of face to face testing.

References

Instructions

To run this test, follow these steps:

  1. Create one XPHR document that satisfies the XPHR profile (PHR Manager / Extract).
  2. For the patient name, construct a name that is:
    • Last Name: The name of your system as registered in Kudu
    • First Name: A short mnemonic/abbreviation for your company that is recognizable
  3. Name this file: <your_system_name_40157.xml
  4. If possible, render the document and perform a screen capture (JPEG or other common format).
  5. Place the XML file and screen capture in a zip file: <your_system_name_40157.zip>
  6. Upload the zip file into the Connectathon Wiki: http://ihewiki.wustl.edu/wiki.
  7. Find the entry for your Connectathon and test 40157. There should be an existing link you can click that will allow you to upload the file.
  8. Go to the Kudu tool and enter a note indicating you have uploaded your sample.
  9. As Content Consumer actors render your data, you may receive a request for interpretation or directives from the Project Manager to repair attributes. This may prove to be an iterative process.

Evaluation

The evaluation for this test is performed by the other participants. As they review your document, there will be conversation about items in the document.

Supplemental Information

40158: XPHR Update Sample

This test is due 2 weeks before the normal deadlines. Submit a document (even if your work is not complete) so the other participants can review your sample.

In test 40158, you submit a sample of an XPHR Update document that your system will produce. The purpose of this test is to allow the Project Manager to post this sample to consumers so they can read/test/render the documents in advance of face to face testing.

References

Instructions

To run this test, follow these steps:

  1. Create one XD-Lab document that satisfies the XD-Lab profile
  2. For the patient name, construct a name that is:
    • Last Name: The name of your system as registered in Kudu
    • First Name: A short mnemonic/abbreviation for your company that is recognizable
  3. Name this file: <your_system_name_40158.xml
  4. If possible, render the document and perform a screen capture (JPEG or other common format).
  5. Place the XML file and screen capture in a zip file: <your_system_name_40158.zip>
  6. Upload the zip file into the Connectathon Wiki: http://ihewiki.wustl.edu/wiki.
  7. Find the entry for your Connectathon and test 40158. There should be an existing link you can click that will allow you to upload the file.
  8. Go to the Kudu tool and enter a note indicating you have uploaded your sample.
  9. As Content Consumer actors render your data, you may receive a request for interpretation or directives from the Project Manager to repair attributes. This may prove to be an iterative process.

Evaluation

The evaluation for this test is performed by the other participants. As they review your document, there will be conversation about items in the document.

Supplemental Information

40200: PCC XPHR Aortic Dissection

Not available in the 10.10.0 release.

40200 is a test of an XPHR extract in the Aortic Dissection case. In this test, the Content Creator creates an XPHR extract that matches patient history entered into a PHR. You are required to enter the data specified by this test. The XPHR document may contain other data. If so, the test system should ignore that other data.

40200 and 40201 are similar tests. 40201 is for the Cardiac Referral case.

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

  1. Create a patient record in your system that matches the history/data specifed for the Aortic Dissection case (see Appendix A).
  2. Perform an extract and create an XPHR document that matches that history/data.
  3. Copy the file to the MESA test system where it can be accessed by the test scripts.
  4. Set the current directory to $MESA_TARGET/mesa_tests/pcc/actors/ccrt.
  5. Evaluate the XML file using the steps below.

Evaluation

  1. Run the evaluation script on the file of your choice (FILE) as described below:
    perl 40200/eval_40200.pl <log level> FILE
  2. The result file is found in 40200/grade_40200.txt. The test is successful when the grade file indicates 0 errors.
  3. Submit the grade to the Project Manager for evaluation.

Supplemental Information

You are welcome to reuse the document you tested in 40001, 40002, 40003, 40004, 40050.

Test 40200 is looking for these features in the XPHR Content Profile Document:

  1. Allergy to Iodinated Contrast
  2. Current medication: Amoxicillin

40201: PCC XPHR Cardiac Referral

Not available in the 10.10.0 release.

40201 is a test of an XPHR extract in the Cardiac Referral case. In this test, the Content Creator creates an XPHR extract that matches patient history entered into a PHR. You are required to enter the data specified by this test. The XPHR document may contain other data. If so, the test system should ignore that other data.

40200 and 40201 are similar tests. 40200 is for the Aortic Dissection case.

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

  1. Create a patient record in your system that matches the history/data specifed for the Cardiac Referral case.
  2. Perform an extract and create an XPHR document that matches that history/data.
  3. Copy the file to the MESA test system where it can be accessed by the test scripts.
  4. Set the current directory to $MESA_TARGET/mesa_tests/pcc/actors/ccrt.
  5. Evaluate the XML file using the steps below.

Evaluation

  1. Run the evaluation script on the file of your choice (FILE) as described below:
    perl 40201/eval_40201.pl <log level> FILE
  2. The result file is found in 40201/grade_40201.txt. The test is successful when the grade file indicates 0 errors.
  3. Submit the grade to the Project Manager for evaluation.

Supplemental Information

You are welcome to reuse the document you tested in 40001, 40002, 40003, 40004, 40050.

Test 40201 is looking for these features in the XPHR Content Profile Document:

40300: PCC EDR Aortic Dissection

Not available in the 10.10.0 release.

40300 is a test of an EDR document in the Aortic Dissection case. In this test, the Content Creator creates an EDR that matches patient history. You are required to enter the data specified by this test. The EDR document may contain other data. If so, the test system should ignore that other data.

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

  1. Create a record in your system that matches the history/data specifed for the Aortic Dissection case (see Appendix A).
  2. Create an EDR document that matches that history/data/referral location.
  3. Copy the file to the MESA test system where it can be accessed by the test scripts.
  4. Set the current directory to $MESA_TARGET/mesa_tests/pcc/actors/ccrt.
  5. Evaluate the XML file using the steps below.

Evaluation

  1. Run the evaluation script on the file of your choice (FILE) as described below:
    perl 40300/eval_40300.pl <log level> FILE
  2. The result file is found in 40300/grade_40300.txt. The test is successful when the grade file indicates 0 errors.
  3. Submit the grade to the Project Manager for evaluation.

Supplemental Information

You are welcome to reuse the document you tested in 40001, 40002, 40003, 40004, 40050.

Test 40300 is looking for these features in the EDR Content Profile Document:

  1. Allergy to Iodinated Contrast
  2. Current medication: Amoxicillin

40301: PCC EDR Cardiac Referral

There is no test 40301 for the EDR/Cardiac Referral Case. The numbering system would imply there should be such a test case, but this was not designed in the medical scenario for the test patient.

40400: PCC BPPC Aortic Dissection

Not available in the 10.10.0 release.

40400 is a test of a BPPC document in the Aortic Dissection case. In this test, the Content Creator creates a BPPC document that matches patient demographics and one consent policy. You are required to enter the data specified by this test. The BPPC document may contain other data. If so, the test system should ignore that other data.

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

  1. Create a BPPC document that matches that patient demographics/consent policy described for the Aortic Dissection case (Appendix A).
  2. Copy the file to the MESA test system where it can be accessed by the test scripts.
  3. Set the current directory to $MESA_TARGET/mesa_tests/pcc/actors/ccrt.
  4. Evaluate the XML file using the steps below.

Evaluation

  1. Run the evaluation script on the file of your choice (FILE) as described below:
    perl 40400/eval_40400.pl <log level> FILE
  2. The result file is found in 40400/grade_40400.txt. The test is successful when the grade file indicates 0 errors.
  3. Submit the grade to the Project Manager for evaluation.

Supplemental Information

Test 40400 is looking for these features in the BPPC Content Profile Document:

40401: PCC BPPC Cardiac Referral

Not available in the 10.10.0 release.

40401 is a test of a BPPC document in the Cardiac Referral case. In this test, the Content Creator creates a BPPC document that matches patient demographics and one consent policy. You are required to enter the data specified by this test. The BPPC document may contain other data. If so, the test system should ignore that other data.

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

  1. Create a BPPC document that matches that patient demographics/consent policy described for the Cardiac Referral case (Appendix B).
  2. Copy the file to the MESA test system where it can be accessed by the test scripts.
  3. Set the current directory to $MESA_TARGET/mesa_tests/pcc/actors/ccrt.
  4. Evaluate the XML file using the steps below.

Evaluation

  1. Run the evaluation script on the file of your choice (FILE) as described below:
    perl 40401/eval_40401.pl <log level> FILE
  2. The result file is found in 40401/grade_40401.txt. The test is successful when the grade file indicates 0 errors.
  3. Submit the grade to the Project Manager for evaluation.

Supplemental Information

Test 40401 is looking for these features in the BPPC Content Profile Document:

40500: PCC PPHP Aortic Dissection

Not available in the 10.10.0 release.

40500 is a test of one PPHP document in the Aortic Dissection case. In this test, the Content Creator creates one PPHP document that matches patient history. You are required to enter the data specified by this test. The PPHP document may contain other data. If so, the test system should ignore that other data.

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

  1. Create one PPHP document that matches that history/data for the Aortic Dissection case (Appendix A).
  2. Copy the file to the MESA test system where it can be accessed by the test scripts.
  3. Set the current directory to $MESA_TARGET/mesa_tests/pcc/actors/ccrt.
  4. Evaluate the XML file using the steps below.

Evaluation

  1. Run the evaluation script on the file of your choice (FILE) as described below:
    perl 40500/eval_40500.pl <log level> FILE
  2. The result file is found in 40500/grade_40500.txt. The test is successful when the grade file indicates 0 errors.
  3. Submit the grade to the Project Manager for evaluation.

Supplemental Information

You are welcome to reuse the document you tested in 40001, 40002, 40003, 40004, 40050.

Test 40500 is looking for these features in the PPHP Content Profile Document:

  1. Allergy to Iodinated Contrast
  2. Current medication: Amoxicillin
  3. TBD

40501: PCC PPHP Cardiac Referral

Not available in the 10.10.0 release.

40501 is a test of one PPHP document in the Cardiac Referral case. In this test, the Content Creator creates one PPHP document that matches patient history. You are required to enter the data specified by this test. The PPHP document may contain other data. If so, the test system should ignore that other data.

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

  1. Create one PPHP document that matches that history/data for the Cardiac Referral case (Appendix B).
  2. Copy the file to the MESA test system where it can be accessed by the test scripts.
  3. Set the current directory to $MESA_TARGET/mesa_tests/pcc/actors/ccrt.
  4. Evaluate the XML file using the steps below.

Evaluation

  1. Run the evaluation script on the file of your choice (FILE) as described below:
    perl 40501/eval_40501.pl <log level> FILE
  2. The result file is found in 40501/grade_40501.txt. The test is successful when the grade file indicates 0 errors.
  3. Submit the grade to the Project Manager for evaluation.

Supplemental Information

You are welcome to reuse the document you tested in 40001, 40002, 40003, 40004, 40050.

Test 40501 is looking for these features in the PPHP Content Profile Document:

  1. Allergy to Iodinated Contrast
  2. Current medication: Amoxicillin
  3. TBD

40600: PCC XDS-MS Referral Aortic Dissection

Do not run this test; it is a placeholder for a future year.

40500 is a test of one XDS-MS Referral document in the Aortic Dissection case. In this test, the Content Creator creates one XDS-MS Referral document that matches patient history. You are required to enter the data specified by this test. The XDS-MS Referral document may contain other data. If so, the test system should ignore that other data.

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

  1. Create one XDS-MS Referral document that matches that history/data for the Aortic Dissection case (Appendix A).
  2. Copy the file to the MESA test system where it can be accessed by the test scripts.
  3. Set the current directory to $MESA_TARGET/mesa_tests/pcc/actors/ccrt.
  4. Evaluate the XML file using the steps below.

Evaluation

  1. Run the evaluation script on the file of your choice (FILE) as described below:
    perl 40600/eval_40600.pl <log level> FILE
  2. The result file is found in 40600/grade_40600.txt. The test is successful when the grade file indicates 0 errors.
  3. Submit the grade to the Project Manager for evaluation.

Supplemental Information

You are welcome to reuse the document you tested in 40001, 40002, 40003, 40004, 40050.

Test 40600 is looking for these features in the XDS-MS Referral Content Profile Document:

  1. Allergy to Iodinated Contrast
  2. Current medication: Amoxicillin
  3. TBD

40601: PCC XDS-MS Referral Cardiac Referral

Not available in the 10.10.0 release.

40601 is a test of one XDS-MS Referral document in the Cardiac Referral case. In this test, the Content Creator creates one XDS-MS Referral document that matches patient history. You are required to enter the data specified by this test. The PPHP document may contain other data. If so, the test system should ignore that other data.

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

  1. Create one XDS-MS Referral document that matches that history/data for the Cardiac Referral case (Appendix B).
  2. Copy the file to the MESA test system where it can be accessed by the test scripts.
  3. Set the current directory to $MESA_TARGET/mesa_tests/pcc/actors/ccrt.
  4. Evaluate the XML file using the steps below.

Evaluation

  1. Run the evaluation script on the file of your choice (FILE) as described below:
    perl 40601/eval_40601.pl <log level> FILE
  2. The result file is found in 40601/grade_40601.txt. The test is successful when the grade file indicates 0 errors.
  3. Submit the grade to the Project Manager for evaluation.

Supplemental Information

You are welcome to reuse the document you tested in 40001, 40002, 40003, 40004, 40050.

Test 40601 is looking for these features in the XDS-MS Referral Content Profile Document:

  1. Allergy to Iodinated Contrast
  2. Current medication: Amoxicillin
  3. TBD

40700: PCC XDS-MS Discharge Summary Aortic Dissection

Not available in the 10.10.0 release.

40500 is a test of one XDS-MS Discharge Summary document in the Aortic Dissection case. In this test, the Content Creator creates one XDS-MS Discharge Summary document that matches patient history. You are required to enter the data specified by this test. The XDS-MS Discharge Summary document may contain other data. If so, the test system should ignore that other data.

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

  1. Create one XDS-MS Discharge Summary document that matches that history/data for the Aortic Dissection case (Appendix A).
  2. Copy the file to the MESA test system where it can be accessed by the test scripts.
  3. Set the current directory to $MESA_TARGET/mesa_tests/pcc/actors/ccrt.
  4. Evaluate the XML file using the steps below.

Evaluation

  1. Run the evaluation script on the file of your choice (FILE) as described below:
    perl 40700/eval_40700.pl <log level> FILE
  2. The result file is found in 40700/grade_40700.txt. The test is successful when the grade file indicates 0 errors.
  3. Submit the grade to the Project Manager for evaluation.

Supplemental Information

You are welcome to reuse the document you tested in 40001, 40002, 40003, 40004, 40050.

Test 40700 is looking for these features in the XDS-MS Referral Content Profile Document:

  1. Allergy to Iodinated Contrast
  2. Current medication: Amoxicillin
  3. TBD

40701: PCC XDS-MS Discharge Summary Cardiac Referral

Not available in the 10.10.0 release.

40701 is a test of one XDS-MS Discharge Summary document in the Cardiac Referral case. In this test, the Content Creator creates one XDS-MS Discharge Summary document that matches patient history. You are required to enter the data specified by this test. The Discharge Summary document may contain other data. If so, the test system should ignore that other data.

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

  1. Create one XDS-MS Discharge Summary document that matches that history/data for the Cardiac Referral case (Appendix B).
  2. Copy the file to the MESA test system where it can be accessed by the test scripts.
  3. Set the current directory to $MESA_TARGET/mesa_tests/pcc/actors/ccrt.
  4. Evaluate the XML file using the steps below.

Evaluation

  1. Run the evaluation script on the file of your choice (FILE) as described below:
    perl 40701/eval_40701.pl <log level> FILE
  2. The result file is found in 40701/grade_40701.txt. The test is successful when the grade file indicates 0 errors.
  3. Submit the grade to the Project Manager for evaluation.

Supplemental Information

You are welcome to reuse the document you tested in 40001, 40002, 40003, 40004, 40050.

Test 40701 is looking for these features in the Discharge Summary Profile Document:

  1. Allergy to Iodinated Contrast
  2. Current medication: Amoxicillin
  3. TBD

Test Case 12504: XDS-MS - Document Display with XSLT

Not available in 10.3.0 release.

In test 12504, the CDA document is transformed using an XSLT stylesheet. The purpose of the resulting document is to allow a Project Manager to visually inspect the document. It is not necessarily intended to produce an output that is “appealing to the clinician.”

References

 

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

perl 12504/doc_src_12504.pl FILE

Evaluation

Test Case 12505: XDS-MS - Schematron Care Record Summary

Not available in 10.3.0 release.

In test 12505, a Schematron test is used to extract data from an XDS-MS document and examine those data for specific values. This is according to the Care Record Summary.

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

Evaluation

perl 12505/eval_12505.pl <log level> FILE

Test Case 12506: XDS-MS - Schematron XDS-MS Content

Not available in 10.3.0 release.

In test 12506, a Schematron test is used to extract data from an XDS-MS document and examine those data for specific values. This is according to the XDS-MS content as defined in the XDS-MS Integration Profile.

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

Evaluation

perl 12506/eval_12506.pl <log level> FILE

Test Case 12510: XDS-MS - Create Discharge Summary

Not available in 10.3.0 release.

In test 12510, the Document Source creates a Discharge Summary with content that is defined by the test. The test has several purposes:

References

Special Instructions

Create a Discharge Summary with this information. The patient name should include your company name (e.g., Philips, Zelda). All other information should match the requested parameters so that later tests will properly evaluate. If these parameters are too US specific, notify the MESA developers for appropriate modification.


Patient

Company, Zelda
DOB: 19580204
Sex: F

 

Address

4525 Scott Ave
St. Louis, MO 63110

 

Telephone

314 555 1671

 

Provider Organization

Gateway Hospital
600 Euclid Ave
St. Louis MO 63110
USA

 

Assigned Author

Hasselfeld, Brian

 

Author Address

700 Euclid Ave
St. Louis, MO 63110
USA

 

Assigned Custodian

Gateway Hospital
600 Euclid Ave
St. Louis MO 63110
USA

 

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

Evaluation

perl 12510/eval_12510.pl <log level> FILE

Test Case 12511: XDS-MS - Discharge Summary: Header

Not available in 10.3.0 release.

Test 12511 uses the Discharge Summary created for test 12510 and evaluates only “header” parts of the document. Those are defined loosely as CDA attributes that are before the demographics.

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

Evaluation

perl 12511/eval_12511.pl <log level> FILE

Test Case 12512: XDS-MS - Discharge Summary: Demographics

Not available in 10.3.0 release.

Test 12511 uses the Discharge Summary created for test 12510 and evaluates the demographics attributes in the Discharge Summary.

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

Evaluation

perl 12512/eval_12512.pl <log level> FILE

Test Case 12513: XDS-MS - Discharge Summary: Sections

Not available in 10.3.0 release.

Test 12513 uses the Discharge Summary created for test 12510 and evaluates individual sections of the document.

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

Evaluation

perl 12513/eval_12513.pl <log level> FILE

Test Case 12520: Create EDR

Not available in 10.3.0 release.

In test 12520, the Content Creator creates an EDR document (Emergency Department Referral) with content that is defined by the test. The test has several purposes:

  • The Content Creator will share this document with Content Consumers so they can view/render the document.
  • This document will be validated according to CDA Schema definitions.
  • This document will serve as the input to further tests.

References

Special Instructions

Create an EDR with this information. The patient name should include your company name (e.g., Philips, Zelda). All other information should match the requested parameters so that later tests will properly evaluate. If these parameters are too US specific, notify the MESA developers for appropriate modification.


Patient

Company, Zelda
DOB: 19580204
Sex: F

 

Address

4525 Scott Ave
St. Louis, MO 63110

 

Telephone

314 555 1671

 

Provider Organization

Gateway Hospital
600 Euclid Ave
St. Louis MO 63110
USA

 

Assigned Author

Hasselfeld, Brian

 

Author Address

700 Euclid Ave
St. Louis, MO 63110
USA

 

Assigned Custodian

Gateway Hospital
600 Euclid Ave
St. Louis MO 63110
USA

 

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

  • Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/doc_src.
  • Create an EDR document; this should be an XML file as defined in the XDS-MS Integration Profile.
  • Evaluate the XML file to make sure it passes the Schematron test using the steps below.

Evaluation

  1. Run the evaluation script on the file of your choice (FILE) as described below:
  2. perl 12520/eval_12520.pl <log level> FILE
  3. The result file is found in 12520/grade_12520.txt. Submit the grade to the Project Manager for evaluation.

 

 

Test Cases: XDS-SD

This section describes test cases associated with the XDS-SD (Scanned Documents) Integration Profile.

Test Case 14101: XDS-SD - Sample XDS-SD Documents

In test 14101, you submit a sample of a document that your system will produce; it will be CDA-wrapped PDF, CDA-wrapped plaintext, or one of each. The purpose of this test is to allow the Project Manager to post this sample to consumers so they can read/test/render the documents in advance of face-to-face testing.

References

Instructions

  1. Create an XDS-SD document that would be transmitted per the specifications in XDS, XDM and/or XDR. This should be an XML file as defined in the XDS-SD Integration Profile. If your system can create both CDA-wrapped PDF and CDA-wrapped plaintext, please submit 2 samples
  2. Name this file: <your_system_name_14101.xml
  3. If possible, render the document and perform a screen capture (JPEG or other common format).
  4. Place the XML file and screen capture in a zip file: <your_system_name_14101.zip>
  5. Upload the zip file into the Connectathon Wiki: http://ihewiki.wustl.edu/wiki.
  6. Find the entry for your Connectathon and test 14101. There should be an existing link you can click that will allow you to upload the file.
  7. Go to the Kudu tool and enter a note indicating you have uploaded your sample.
  8. As Content Consumer actors render your data, you may receive a request for interpretation or directives from the Project Manager to repair attributes. This may prove to be an iterative process.

Evaluation

  • Submit the file(s) created above to the Project Manager. The Project Manager will make this file available to Document Consumers.
  • Please submit this document 2 weeks in advance of the deadline for tests in the XDS-SD profile if possible. This will give Content Consumers the opportunity to review the document.

Test Case 14110: XDS-SD - Verify Wrapper Format - HL7 CDA R2

Test 14110 verifies that the content of the HL7 CDA R2 wrapper for the plaintext or PDF document follows the constraints identified in the XDS-SD Profile.

References

ITI TF-1:7.1.8.2

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

Evaluation

Supplemental Information

Appendix A: Aortic Dissection

This case will cover PCC content profile documents as follows:

  • XPHR
  • EDR
  • BPPC
  • PPHP
  • XDS-MS: Discharge Summary

The patient receives treatment for this condiition and documents are created in the order listed above.

A: Patient Demographics

Patient demographics for the Aortic Dissection Case are:

Name Randolph^Frederick
DOB 1959 02 03
Sex M

A: XPHR Document

This section describes the patient history and required data for the XPHR document.

Frederick Randolph begins with this information:

  1. Randolph is on a camping trip and develops an ear infection
  2. Randolph visits local community hospital and receives a prescription for Amoxicillin
  3. Randolph returns home with the prescription and enters the prescription in his PHR.
  4. Randolph also enters his allergy to Iodinated Contrast.
  5. Randolph visits physician for routine physical and brings XHPR document with Amoxicillin prescription and allergy to Iodinated Contrast.
  6. Physician imports XPHR document

XPHR Required Sections/Content

11450-4: PROBLEM LIST

  1. Ear infection, active, date 1-Oct-2006

HISTORY OF MEDICATION USE

Medication Frequency Route Dates of Use
Amoxicillin (250 mg tabs) 3 times per day oral Oct 1, 2006 - Oct 10, 2006

10160-0: HISTORY OF ALLERGIES

Allergen Reaction Comments
Iodinated contrast laryngeal oedema Reaction occurs within 10 minutes.

8716-3: VITAL SIGNS

Label Value Units
Height 1778 mm
Weight 82 kg

XPHR Optional Sections/Content

11369-6: HISTORY OF IMMUNIZATIONS

Vaccine Dates Notes
Influenza 8-Nov-2005  

11336-5: HISTORY OF HOSPITALIZATIONS+ HISTORY OF OUTPATIENT VISITS

Bicycle accident 14-Aug-2004. Head CT was negative. Determined that subject was allergic to iodinated contrast duirng the procedure.

46264-8: HISTORY OF MEDICAL DEVICE USE

None

10157-6: HISTORY OF FAMILY MEMBER DISEASES

Father died of lung cancer at age 55.

A: EDR Document

Frederick Randolph continues with this information:

  1. PCP (5202^SCHULTZ^KEVING^G^^DR) has received the XPHR extract previously described. For those systems that do not import or already create that data, they should enter that data into their systems as if the PCP had captured it.
  2. Randolph telephones PCP and reports these symptoms:
    • Chest pain that radiates to the back.
  3. SCHULTZ completes an EDR that refers Randolph to the Emergency Department at University Hospital.

EDR Required Sections/Content

42349-1: REASON FOR REFERRAL

  1. Physical exam and patient symptoms indicate possible aortic dissection.

10164-2: HISTORY OF PRESENT ILLNESS

  1. Patient has no history of suspected illness.

11450-4: PROBLEM LIST

  1. Ear infection, active, date 1-Oct-2006

10160-0: HISTORY OF MEDICATION USE

Medication Frequency Route Dates of Use
Amoxicillin (250 mg tabs) 3 times per day oral Oct 1, 2006 - Oct 10, 2006

10155-0: HISTORY OF ALLERGIES

Allergen Reaction Comments
Iodinated contrast laryngeal oedema Reaction occurs within 10 minutes.

A: BPPC Document

Frederick Randolph enters the Emergency Department of University Hospital and is asked to sign a consent form with the following policy:

  1. University Hospital Normal Policy on the use of patient data: Patient agrees the University Hospital has the right to place their patient data into one or more information systems in the hospital and that this information can be viewed by staff members for clinical use, billing and mandatory government reporting.

A: PPHP Document

Frederick Randolph is seen in the ED and has the tests listed below. The ED physician decides that a cardio-thoracic surgery is required, and a CT surgeon fills out a PPHP document according to the information below.

  1. ED physician finds elevated blood pressure and a wide mediastinum on CXR; aortic dissection is suspected.
  2. Pre and post contract CT would be the procedure of choice. Noting the allergy to iodinated contrast, the ED performs an MR with gadolinium instead.
  3. Cardio-thoracic surgeon (7303^DARROW^BARBARA^P^^DR) is to perform surgery and will perform open-chest aneurysm repair.
  4. DARROW completes a PPHP and stores this in the hospital system.

A: XDS-MS Discharge Summary Document

Surgery is performed; Randolph completes a two day recovery period in the hospital.

  1. Cardio-thoracic surgeon (7303^DARROW^BARBARA^P^^DR) completes a discharge summary.
  2. Randolph is discharged

XDS-MS Discharge Summary Required Sections/Content

11450-4: PROBLEM LIST

  1. Ear infection, active, date 1-Oct-2006
  2. Aortic aneurysm, active, date 1-Oct-2006

11348-0: HISTORY OF PAST ILLNESS

  1. Aortic aneurysm surgically repaired.

11535-2: HOSPITAL DISCHARGE DX

46241-6: HOSPITAL ADMISSION DX

10183-2: HOSPITAL DISCHARGE MEDICATIONS

10155-0: HISTORY OF ALLERGIES

Allergen Reaction Comments
Iodinated contrast laryngeal oedema Reaction occurs within 10 minutes.

8648-8: HOSPITAL COURSE

  1. Patient was evaluated in Emergency Department for Aortic Dissection.
  2. Patient was found to have elevated blood pressure and a wide mediastinum on standard CXR.
  3. Due to patient allergy to iodinated contrast, an MR with gadolinium was performed to confirm diagnosis.
  4. Patient was admitted to ICU and scheduled for surgery the next morning.
  5. Dr. Darrow performed open chest surgery and repaired a 6.0 cm aortic aneurysm.
  6. Patient was returned to ICU for two days of obseration and was then discharged.

18776-5: PLAN OF CARE

  1. Patient should continue with bed rest for 1 day following discharge.
  2. On the second day, patient should

Appendix B: Cardiac Referral

This case will cover PCC content profile documents as follows:

  • XPHR
  • XDS-MS: Referral
  • BPPC
  • PPHP
  • XDS-MS: Discharge Summary

The patient receives treatment for this condiition and documents are created in the order listed above.

A: Patient Demographics

Patient demographics for the Aortic Dissection Case are:

Name Wilson^Margaret
DOB 19480503
Sex F

B: XPHR Document

This section describes the patient history and required data for the XPHR document.

Margaret Wilson begins with this information:

  1. Wilson visits a trade show and is given a demonstration of how to create a PHR.
  2. At the trade show, Wilson creates a PHR and enters the information listed below (XPHR Required Sections/Content).
  3. Wilson returns home and later completes her normal 5K morning run. After feeling sluggish for two days, Wilson begins to experience chest pain.
  4. Wilson vists her PCP (Schultz) and brings her PHR.
  5. Physician imports XPHR document

XPHR Required Sections/Content

11450-4: PROBLEM LIST

  1. Stress fracture, right foot (healed) , date 1-Aug-2002

HISTORY OF MEDICATION USE

Medication Frequency Route Dates of Use
       

10160-0: HISTORY OF ALLERGIES

Allergen Reaction Comments
pollen congestion  

8716-3: VITAL SIGNS

Label Value Units
Height 1625 mm
Weight 50 kg

XPHR Optional Sections/Content

11369-6: HISTORY OF IMMUNIZATIONS

Vaccine Dates Notes
Influenza 8-Nov-2005  

11336-5: HISTORY OF HOSPITALIZATIONS+ HISTORY OF OUTPATIENT VISITS

1-Aug-2002: Visit to orthopedic surgeon because of recurring pain in right foot. After standard CXR, surgeon decided to cast foot to treat stress fracture.

46264-8: HISTORY OF MEDICAL DEVICE USE

None

10157-6: HISTORY OF FAMILY MEMBER DISEASES

Mother has diabetes.

B: XDS-MS Referral Document

Margaret Wilson continues with this information:

  1. PCP (5202^SCHULTZ^KEVING^G^^DR) has received the XPHR extract previously described. For those systems that do not import or already create that data, they should enter that data into their systems as if the PCP had captured it.
  2. Wilson has office visiti with SCHULTZ and reports these symptoms:
    • Chest pain
  3. SCHULTZ decides this is not an emergency situation, but refers Wilson to a Cardiologist at University Hospital. SCHULTZ creates an XDS-MS Referral document for (6404^WYNN^DONALD^^^DR)

XDS-MS Required Sections/Content

42349-1: REASON FOR REFERRAL

  1. Patient is otherwise healthy and is exhibiting chest pain.

10164-2: HISTORY OF PRESENT ILLNESS

  1. Patient has no history of cardiac illnes.

11450-4: PROBLEM LIST

  1. Stress fracture, right foot (healed) , date 1-Aug-2002

10160-0: HISTORY OF MEDICATION USE

Medication Frequency Route Dates of Use
       

10160-0: HISTORY OF ALLERGIES

Allergen Reaction Comments
pollen congestion  

B: BPPC Document

Margaret Wilson reports to the Cardiology Department of University Hospital and is asked to sign a consent form with the following policy:

  1. University Hospital Normal Policy on the use of patient data: Patient agrees the University Hospital has the right to place their patient data into one or more information systems in the hospital and that this information can be viewed by staff members for clinical use, billing and mandatory government reporting.

B: PPHP Document

  1. Dr. Wynn interviews Wilson and decides to perform a stress test.
  2. Stress test is inconclusive. Dr. Wynn decides to perform a Cardiac Catheterization procedure.
  3. Dr. Wynn completes a PPHP document as described below.

B: XDS-MS Discharge Summary Document

  1. Cardiac Catheterization procedure shows 80% blockage of the X. Dr. Wynn recommends CABG for Wilson to be performed by Dr. Darrow. (Dr. Darrow would normally create a PPHP, but that is skipped for this scenario).
  2. Dr. Darrow performs successful CABG on Wilson.
  3. After 3 day recovery in the hospital, Dr. Wynn completes XDS-MS Discharge Summary as listed below.

XDS-MS Discharge Summary Required Sections/Content

11450-4: PROBLEM LIST

  1. 80% blockage of X, treated with CABG.

11348-0: HISTORY OF PAST ILLNESS

11535-2: HOSPITAL DISCHARGE DX

46241-6: HOSPITAL ADMISSION DX

10183-2: HOSPITAL DISCHARGE MEDICATIONS

10155-0: HISTORY OF ALLERGIES

Allergen Reaction Comments
pollen congestion  

8648-8: HOSPITAL COURSE

  1. Patient was evaluated in for chest pain.
  2. A standard stress test was administered; results were inconclusive.
  3. A Cardiac Catheterization procedure was performed, indicating 80% blockage of X.
  4. Dr. Darrow peformed a successful CABG.
  5. Patient was returned to ICU for three days of obseration and was then discharged.

18776-5: PLAN OF CARE

  1. Patient should continue with bed rest for 1 day following discharge.
  2. On the second day, patient should