From IHEWiki

MESA/Content Creator

Contents 1 Content Creator (an Abstract Actor) 1.1 Introduction 1.2 Patient Identification 1.3 Configuration 1.4 Starting the MESA Servers 1.5 Installation Test 1.6 Loading Test Data 2 General Test Cases for Content Profiles 2.1 40001: CDA R2 Valid Schema 2.2 40001-01, -02, -03, ....: CDA R2 Valid Schema 2.3 40002: PCC Valid Schema 2.4 40003: PCC Schematron Patient Randolph 2.5 40004: PCC Schematron Patient Wilson 2.6 40050: PCC Schematron 2.7 40050-01, -02, -03, ....: Content Profile Structure Tests (Schematron) 2.8 40051: PCC Schematron CRS 2.9 40052: PCC Placeholder 2.10 40100: PCC Schematron XPHR 2.11 40101:PCC Emergency Department Referral 2.12 40102: PCC Schematron BPPC 2.13 40103: PCC Schematron PPHP 2.14 40104: PCC Schematron XDS-MS Discharge Summary 2.15 40105:PCC XDS-MS Referral 2.16 40106: PCC Schematron XD-Lab 2.17 40107: PCC Schematron XPHR Extract 2.18 40108: PCC Schematron XPHR Update 2.19 40114: PCC Schematron EDES Triage Note 2.20 40117: PCC Schematron EDES Physician Note 2.21 40151: EDR Sample 2.22 40152: BPPC Sample 2.23 40154: XDS-MS Discharge Summary Sample 2.24 40155: XDS-MS Referral Sample 2.25 40156: XD-Lab Sample 2.26 40157: XPHR Extract Sample 2.27 40158: XPHR Update Sample 2.28 40161: FSA/EDR Sample 2.29 40162: FSA/XDS-MS Sample 2.30 40163: FSA/XPHR Sample 2.31 40164: EDES Triage Note Sample 2.32 40165: EDES Nursing Note Sample 2.33 40166: EDES Composite Triage and ED Nursing Note Sample 2.34 40167: EDES ED Physician Note Sample 2.35 40168: Antepartum History and Physical Sample 2.36 40169: Antepartum Summary Sample 2.37 40170: Antepartum Laboratory Report Sample 2.38 40171: Antepartum Education Sample 2.39 40172: Immunization Content Sample 2.40 40180-01, -02, -03, ....: Sample Documents: CDA 2.41 40200: PCC XPHR Aortic Dissection 2.42 40201: PCC XPHR Cardiac Referral 2.43 40250: PCC Active Problems 1 2.44 40251: PCC Geriatic Depression Scale Section 1 2.45 403xx: 40300-40399 Tests 2.46 40300: PCC EDR Aortic Dissection 2.47 40301: PCC EDR Cardiac Referral 2.48 40400: PCC BPPC Aortic Dissection 2.49 40401: PCC BPPC Cardiac Referral 2.50 40500: PCC PPHP Aortic Dissection 2.51 40501: PCC PPHP Cardiac Referral 2.52 40600: PCC XDS-MS Referral Aortic Dissection 2.53 40601: PCC XDS-MS Referral Cardiac Referral 2.54 40700: PCC XDS-MS Discharge Summary Aortic Dissection 2.55 40701: PCC XDS-MS Discharge Summary Cardiac Referral 2.56 Test Case 12504: XDS-MS - Document Display with XSLT 2.57 Test Case 12505: XDS-MS - Schematron Care Record Summary 2.58 Test Case 12506: XDS-MS - Schematron XDS-MS Content 2.59 Test Case 12510: XDS-MS - Create Discharge Summary 2.60 Not available in 10.3.0 release. 2.61 Test Case 12511: XDS-MS - Discharge Summary: Header 2.62 Test Case 12512: XDS-MS - Discharge Summary: Demographics 2.63 Test Case 12513: XDS-MS - Discharge Summary: Sections 2.64 Test Case 12520: Create EDR 2.65 Test Case 12511: XDS-MS - Discharge Summary: Header 2.66 Test Case 12512: XDS-MS - Discharge Summary: Demographics 2.67 Test Case 12513: XDS-MS - Discharge Summary: Sections 2.68 Test Case 12520: Create EDR 3 Test Cases: XDS-SD 3.1 Test Case 14101: XDS-SD - Sample XDS-SD Documents 3.2 Test Case 14110: XDS-SD - Verify Wrapper Format - HL7 CDA R2 4 Test Cases: MCH 4.1 Test Case 14352: MCH - Sample Prepop Content 5 Appendix A: Aortic Dissection 5.1 A: Patient Demographics 5.2 A: XPHR Document 5.2.1 XPHR Required Sections/Content 5.2.2 XPHR Optional Sections/Content 5.3 A: EDR Document 5.3.1 EDR Required Sections/Content 5.3.2 A: BPPC Document 5.3.3 A: PPHP Document 5.3.4 A: XDS-MS Discharge Summary Document 5.3.5 XDS-MS Discharge Summary Required Sections/Content 6 Appendix B: Cardiac Referral 6.1 A: Patient Demographics 6.2 B: XPHR Document 6.2.1 XPHR Required Sections/Content 6.2.2 XDS-MS Required Sections/Content 6.2.3 B: BPPC Document 6.2.4 B: PPHP Document 6.2.5 B: XDS-MS Discharge Summary Document 6.2.6 XDS-MS Discharge Summary Required Sections/Content

Content Creator (an Abstract Actor)

Introduction

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

• ITI XDS Scanned Documents
• PCC Content Profiles

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.

• 40001: CDA R2 Valid Schema. In this test, your document is validated against the CDA R2 schema. If you produce more than one kind of content document, you would logically run this test against each kind of content you produce. The Project Managers will simplify requirements and ask you to submit results from one document (pick one). The engineering manager in your company would ask you to run this test on all documents you produce.

• 40003: PCC Schematron Patient Randolph. In this test, you create a content document with specified patient demographics. This is only a test to make sure you properly represent the demographics listed. As with 40001, you would logically run this test for all content you produce. Also as with 40001, you will submit results for only one content document. Therefore, produce at least one content document with the proper demographics and run this test.

• 40050: PCC Schematron General: This is a test that your content document follows the general rules defined for PCC content profiles. As with 40001 and 40003, pick one of your content profiles and submit the results for this test. We would repeat that the engineering manager in your company would require you to run this test against all content documents you produce.

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

40001 is now deprecated in favor for 40001-xx. This version required you to load schema defintions from HL7, and not all organizations had access to that material. The 40001-xx tests provide a different mechanism. 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

40001-01, -02, -03, ....: CDA R2 Valid Schema

Test 40001 is now a family of tests. Each test performs the same function. You need to create a CDA R2 document and pass that document through validation software provided by NIST. That software makes sure your document is valid according to the CDA R2 schema.

Each of the tests (01, 02, 03, ...) is for a specific document type, but the test is the same. You will validate your document with the NIST tools. We have different test numbers to let us keep track of the document type in the results database.

References

Instructions

1. Create a document according to the test number (see table below).
2. Use the NIST CDA validation web tool to upload and validate your document.
3. When you select the link for Validation Tool, you will then select the box for testing "CDA R2". You are only testing that this is a valid CDA document. You are not testing that it is a valid PCC XXX document.
4. For the level of testing, select the option that gives the most detailed results (errors, warnings, notes).
5. Complete the validation with the NIST web server. When that is complete and the results show you have a valid document, copy the results and paste them into a text (.txt) file. Name that file SYSTEM_NAME_40001-xx.txt where
   1. SYSTEM_NAME is the keyword of your system name in Kudu/Gazelle.
   2. xx is the test number (01, 02, ...)
6. Upload the text file into the Kudu/Gazelle tool.

Evaluation

Administrative Notes These are the test numbers that correspond to PCC document types:

Test Number	PCC Document	Comments
40001-01	XDS-MS Referral Document	NA
40001-02	XDS-MS Discharge Summary	NA
40001-03	ED Referral	NA
40001-04	XPHR Extract	NA
40001-05	XPHR Update	NA
40001-06	Antepartum History and Physical	NA
40001-07	Antepartum Summary	NA
40001-08	Antepartum Laboratory Report	NA
40001-09	Antepartum Education	NA
40001-10	Triage Note	NA
40001-11	ED Nursing Note	NA
40001-12	Composite Triage and ED Nursing Note	NA
40001-13	ED Phyisician Note	NA
40001-14	Immunization Content	NA
40001-15	Sharing Lab Report	NA
40001-16	Basic Patient Privacy Consent	NA
40001-17	Functional Status Assessment	NA
40001-18	XDS-SD Scanned Document	NA

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

Test 40050 is deprecated. It is replaced by individual tests for specific document types. These are found in 40050-01, 40050-02, ...

40050-01, -02, -03, ....: Content Profile Structure Tests (Schematron)

Test 40050 is now a family of tests. Each test performs the same function. You need to create a CDA R2 document and pass that document through validation software provided by NIST. That software makes sure your document conforms to the structure rules defined by PCC using schematron rules defined by PCC and implemented by NIST software.

Each of the tests (01, 02, 03, ...) is for a specific document type, but the test is the same. You will validate your document with the NIST tools. We have different test numbers to let us keep track of the document type in the results database.

References

Instructions

1. Create a document according to the test number (see table below).
2. Use the NIST CDA validation web tool to upload and validate your document.
3. When you select the link for Validation Tool, you will then select the box for testing

the appropriate document type. If you are creating an XDS-MS Referral Document, you need to test that document against the XDS-MS Referral rules and not the XDS-MS Discharge Summary rules.

1. For the level of testing, select the option that gives the most detailed results (errors, warnings, notes).
2. Complete the validation with the NIST web server. When that is complete and the results show you have a valid document, copy the results and paste them into a text (.txt) file. Name that file SYSTEM_NAME_40050-xx.txt where
   1. SYSTEM_NAME is the keyword of your system name in Kudu/Gazelle.
   2. xx is the test number (01, 02, ...)
3. Upload the text file into the Kudu/Gazelle tool.

Evaluation

Administrative Notes Not all schematron tests are complete as of 5-Dec-2008. Kudu is only configured to accept values for tests that are ready for testing. Do not run other schematron tests until you see entries in Kudu.

These are the test numbers that correspond to PCC document types:

Test Number	PCC Document	Comments
40050-01	XDS-MS Referral Document	NA
40050-02	XDS-MS Discharge Summary	NA
40050-03	ED Referral	NA
40050-04	XPHR Extract	NA
40050-05	XPHR Update	Not ready
40050-06	Antepartum History and Physical	Not ready
40050-07	Antepartum Summary	Not ready
40050-08	Antepartum Laboratory Report	NA
40050-09	Antepartum Education	NA
40050-10	Triage Note	HITSP/C28 (Triage) on NIST site
40050-11	ED Nursing Note	HITSP/C28 (Nursing) on NIST site
40050-12	Composite Triage and ED Nursing Note	NA
40050-13	ED Phyisician Note	HITSP/C28 (Physician) on NIST site
40050-14	Immunization Content	Not ready
40050-15	Sharing Lab Report	Not ready
40050-16	Basic Patient Privacy Consent	Not ready
40050-17	Functional Status Assessment	NA

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:

1.

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/mir_mesa_40100.xml. The test is successful when the grade file indicates 0 errors.

3. Submit the grade to the Project Manager for evaluation (load into Kudu, Gazelle)

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 Emergency Department Referral

40101 tests general structure and content of an ED Referral content profile document.

References

PCC TF 2: 6.4.1.7.4

Instructions

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

1. Create an ED Referral Content Profile Document that satisfies the ED 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 40101/eval_40101.pl <log level> FILE

2. The result file is found in 40101/mir_mesa_40101.xml. The test is successful when the grade file indicates 0 errors.

3. Submit the grade to the Project Manager for evaluation. For pre-Connectathon testing, this normally means uploading the XML file into the Kudu or Gazelle tool.

Supplemental Information

You are welcome to reuse the document you tested in other tests.

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

1. Required sections listed in PCC TF 2: 6.4.1.7.4
2. Sections listed as R2 in PCC TF 2: 6.4.1.7.4

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:

1.

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:

1.

40104: PCC Schematron XDS-MS Discharge Summary

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

References

PCC TF 2: 6.4.1.4.4

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/mir_mesa_40104.xml. The test is successful when the grade file indicates 0 errors.

3.Submit the grade to the Project Manager for evaluation. This normally means uploading the result XML file into the Kudu or Gazelle tool.

Supplemental Information

You are welcome to reuse the document created for other tests.

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

1. Required sections listed in PCC TF 2: 6.4.1.4.4
2. Sections listed as R2 in PCC TF 2: 6.4.1.4.4

40105:PCC XDS-MS Referral

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

References

PCC TF 2: 6.4.1.3.4

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/mir_mesa_40105.xml. The test is successful when the grade file indicates 0 errors.

3. Submit the grade to the Project Manager for evaluation. For pre-Connectathon testing, this normally means uploading the XML file into the Kudu or Gazelle tool.

Supplemental Information

You are welcome to reuse the document you tested in other tests.

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

1. Required sections listed in PCC TF 2: 6.4.1.3.4
2. Sections listed as R2 in PCC TF 2: 6.4.1.3.4

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:

1.

40107: PCC Schematron XPHR Extract

40107 tests general structure and content of an XPHR Extract 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 PCC XPHR Extract Document requirements.

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 40107/eval_40107.pl <log level> FILE

2. The result file is found in 40107/mir_mesa_40107.xml. The test is successful when the grade file indicates 0 errors.

3. Submit the grade to the Project Manager for evaluation (load into Kudu, Gazelle)

Supplemental Information

40108: PCC Schematron XPHR Update

40108 tests general structure and content of an XPHR Update 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 PCC XPHR Update Document requirements.

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 40108/eval_40108.pl <log level> FILE

2. The result file is found in 40108/mir_mesa_40108.xml. The test is successful when the grade file indicates 0 errors.

3. Submit the grade to the Project Manager for evaluation (load into Kudu, Gazelle)

Supplemental Information

40114: PCC Schematron EDES Triage Note

40114 tests general structure and content of an EDES Triage 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 PCC EDES Triage Document requirements.

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 40114/eval_40114.pl <log level> FILE

2. The result file is found in 40114/mir_mesa_40114.xml. The test is successful when the grade file indicates 0 errors.

3. Submit the grade to the Project Manager for evaluation (load into Kudu, Gazelle)

Supplemental Information

40117: PCC Schematron EDES Physician Note

40117 tests general structure and content of an EDES Physician Note 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 PCC XPHR Update Document requirements.

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 40117/eval_40117.pl <log level> FILE

2. The result file is found in 40117/mir_mesa_40117.xml. The test is successful when the grade file indicates 0 errors.

3. Submit the grade to the Project Manager for evaluation (load into Kudu, Gazelle)

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. Upload the XML file and screen capture snapshot into kudu under MESA Tests -> Pre-Connectathon...Objects for test 40151.

6. Create a short txt file indicating you have completed the upload step. Upload that txt file into the Kudu system under the MESA test log results for this test.

7. 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. Upload the XML file and screen capture snapshot into kudu under MESA Tests -> Pre-Connectathon...Objects for test 40152.

6. Create a short txt file indicating you have completed the upload step. Upload that txt file into the Kudu system under the MESA test log results for this test. .

7. 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. Upload the XML file and screen capture snapshot into kudu under MESA Tests -> Pre-Connectathon...Objects for test 40154.

6. Create a short txt file indicating you have completed the upload step. Upload that txt file into the Kudu system under the MESA test log results for this test. .

7. 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. Upload the XML file and screen capture snapshot into kudu under MESA Tests -> Pre-Connectathon...Objects for test 40155.

6. Create a short txt file indicating you have completed the upload step. Upload that txt file into the Kudu system under the MESA test log results for this test. .

7. 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. Upload the XML file and screen capture snapshot into kudu under MESA Tests -> Pre-Connectathon...Objects for test 40156.

6. Create a short txt file indicating you have completed the upload step. Upload that txt file into the Kudu system under the MESA test log results for this test.

7. 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. Upload the XML file and screen capture snapshot into kudu under MESA Tests -> Pre-Connectathon...Objects for test 40157.

6. Create a short txt file indicating you have completed the upload step. Upload that txt file into the Kudu system under the MESA test log results for this test.

7. 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 XPHR Update document that satisfies the XHPR 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. Upload the XML file and screen capture snapshot into kudu under MESA Tests -> Pre-Connectathon...Objects for test 40158.

6. Create a short txt file indicating you have completed the upload step. Upload that txt file into the Kudu system under the MESA test log results for this test.

7. 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

40161: FSA/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 40161, you submit a sample of an FSA/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 FSA/EDR document.

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>_40161.xml

4. If possible, render the document and perform a screen capture (JPEG or other common format).

5. Upload the XML file and screen capture snapshot into kudu under MESA Tests -> Pre-Connectathon...Objects for test 40161.

6. Create a short txt file indicating you have completed the upload step. Upload that txt file into the Kudu system under the MESA test log results for this test.

7. 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

40162: FSA/XDS-MS 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 40162, you submit a sample of an FSA/XDS-MS 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 FSA/XDS-MS document.

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>_40162.xml

4. If possible, render the document and perform a screen capture (JPEG or other common format).

5. Upload the XML file and screen capture snapshot into kudu under MESA Tests -> Pre-Connectathon...Objects for test 40162.

6. Create a short txt file indicating you have completed the upload step. Upload that txt file into the Kudu system under the MESA test log results for this test.

7. 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

40163: FSA/XPHR 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 40163, you submit a sample of an FSA/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 FSA/XPHR document.

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>_40163.xml

4. If possible, render the document and perform a screen capture (JPEG or other common format).

5. Upload the XML file and screen capture snapshot into kudu under MESA Tests -> Pre-Connectathon...Objects for test 40163.

6. Create a short txt file indicating you have completed the upload step. Upload that txt file into the Kudu system under the MESA test log results for this test.

7. 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

None

40164: EDES Triage Note 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 40164, you submit a sample of an EDES Triage Note 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 EDES Triage Note document.

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>_40164.xml

4. If possible, render the document and perform a screen capture (JPEG or other common format).

5. Upload the XML file and screen capture snapshot into kudu under MESA Tests -> Pre-Connectathon...Objects for test 40164.

6. Create a short txt file indicating you have completed the upload step. Upload that txt file into the Kudu system under the MESA test log results for this test.

7. 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

None

40165: EDES Nursing Note 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 40165, you submit a sample of an EDES Nursing Note 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 EDES Nursing Note document.

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>_40165.xml

4. If possible, render the document and perform a screen capture (JPEG or other common format).

5. Upload the XML file and screen capture snapshot into kudu under MESA Tests -> Pre-Connectathon...Objects for test 40165.

6. Create a short txt file indicating you have completed the upload step. Upload that txt file into the Kudu system under the MESA test log results for this test.

7. 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

None

40166: EDES Composite Triage and ED Nursing Note 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 40166, you submit a sample of an EDES Composite Triage and ED Nursing Note 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 EDES Composite Triage and ED Nursing Note document.

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>_40166.xml

4. If possible, render the document and perform a screen capture (JPEG or other common format).

5. Upload the XML file and screen capture snapshot into kudu under MESA Tests -> Pre-Connectathon...Objects for test 40166.

6. Create a short txt file indicating you have completed the upload step. Upload that txt file into the Kudu system under the MESA test log results for this test.

7. 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

None

40167: EDES ED Physician Note 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 40167, you submit a sample of an EDES ED Physician Note 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 EDES ED Physician Note document.

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>_40167.xml

4. If possible, render the document and perform a screen capture (JPEG or other common format).

5. Upload the XML file and screen capture snapshot into kudu under MESA Tests -> Pre-Connectathon...Objects for test 40167.

6. Create a short txt file indicating you have completed the upload step. Upload that txt file into the Kudu system under the MESA test log results for this test.

7. 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

None

40168: Antepartum History and Physical 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 40168, you submit a sample of an Antepartum History and Physical 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 Antepartum History and Physical document.

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>_40168.xml

4. If possible, render the document and perform a screen capture (JPEG or other common format).

5. Upload the XML file and screen capture snapshot into kudu under MESA Tests -> Pre-Connectathon...Objects for test 40168.

6. Create a short txt file indicating you have completed the upload step. Upload that txt file into the Kudu system under the MESA test log results for this test.

7. 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

None

40169: Antepartum 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 40169, you submit a sample of an Antepartum 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 Antepartum Summary document.

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>_40169.xml

4. If possible, render the document and perform a screen capture (JPEG or other common format).

5. Upload the XML file and screen capture snapshot into kudu under MESA Tests -> Pre-Connectathon...Objects for test 40169.

6. Create a short txt file indicating you have completed the upload step. Upload that txt file into the Kudu system under the MESA test log results for this test.

7. 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

None

40170: Antepartum Laboratory Report 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 40170, you submit a sample of an Antepartum Laboratory Report 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 Antepartum Laboratory Report document.

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>_40170.xml

4. If possible, render the document and perform a screen capture (JPEG or other common format).

5. Upload the XML file and screen capture snapshot into kudu under MESA Tests -> Pre-Connectathon...Objects for test 40170.

6. Create a short txt file indicating you have completed the upload step. Upload that txt file into the Kudu system under the MESA test log results for this test.

7. 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

None

40171: Antepartum Education 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 40171, you submit a sample of an Antepartum Education Report 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 Antepartum Education document.

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>_40171.xml

4. If possible, render the document and perform a screen capture (JPEG or other common format).

5. Upload the XML file and screen capture snapshot into kudu under MESA Tests -> Pre-Connectathon...Objects for test 40171.

6. Create a short txt file indicating you have completed the upload step. Upload that txt file into the Kudu system under the MESA test log results for this test.

7. 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

None

40172: Immunization Content 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 40172, you submit a sample of an Immunization Content 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 Immunization Content document.

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>_40172.xml

4. If possible, render the document and perform a screen capture (JPEG or other common format).

5. Upload the XML file and screen capture snapshot into kudu under MESA Tests -> Pre-Connectathon...Objects for test 40172.

6. Create a short txt file indicating you have completed the upload step. Upload that txt file into the Kudu system under the MESA test log results for this test.

7. 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

None

40180-01, -02, -03, ....: Sample Documents: CDA

Test 40180 is a family of tests. Each test performs the same function. You need to create a CDA R2 document and provide that as a sample for other participants to examine.

Each of the tests (01, 02, 03, ...) is for a specific document type, but the test is the same.

We have different test numbers to let us keep track of the document type in the results database.

References

Instructions

1. Create a document according to the test number (see table below). Name the XML file using this convention:
   1. SYSTEMNAME_TESTNUMBER_type.xml, for example
   2. ADT_X_40180-01_XDSMS_Referral.xml
   3. Get your system name right, get the test number right, use common sense to express the type.
2. Upload the document into the Kudu system (MESA Tests->Pre-Connectathon Images/CDAs/Objects.
   1. Click on the Objects to create table for your system and Add the appropriate document.
3. In the Kudu system, enter a brief note indicating this task is done.

Evaluation You pass this test by satisfying two criteria:

1. You upload your sample 30 days before the normal due date for test results. This is to allow other participants to review your result.
2. The other partners are able to view/import your documents

This is a rather asynchronous proces.

Administrative Notes

These are the test numbers that correspond to document types:

Test Number	PCC Document	Comments
40180-01	XDS-MS Referral Document	NA
40180-02	XDS-MS Discharge Summary	NA
40180-03	ED Referral	NA
40180-04	XPHR Extract	NA
40180-05	XPHR Update	NA
40180-06	Antepartum History and Physical	NA
40180-07	Antepartum Summary	NA
40180-08	Antepartum Laboratory Report	NA
40180-09	Antepartum Education	NA
40180-10	Triage Note	NA
40180-11	ED Nursing Note	NA
40180-12	Composite Triage and ED Nursing Note	NA
40180-13	ED Phyisician Note	NA
40180-14	Immunization Content	NA
40180-15	Sharing Lab Report	NA
40180-16	Basic Patient Privacy Consent	NA
40180-17	Functional Status Assessment	Do not perform this test. See -23, -24, -25
40180-18	Labor/Delivery Admission History and Physical	NA
40180-19	Labor/Delivery Summary	NA
40180-20	Maternal Discharge Summary	NA
40180-21	EMS Transfer of Care	NA
40180-22	Patient Plan of Care	NA
40180-23	Functional Status Assessment in EDR	NA
40180-24	Functional Status Assessment in XPHR	NA
40180-25	Functional Status Assessment in XDS-MS	NA

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:

1.

40250: PCC Active Problems 1

40250 is a unit test where the Content Creator actor creates a PCC/CDA document that contains the Active Problems data element. Because this test applies to different document types and specifies the content, the document/content produced may not make clinical sense. Ignore that issue and follow the test instructions.

This test is similar to other unit tests which require specific content. You are free to use the same document to satisfy these different tests.

References

• PCC TF 2:5.4.3.2.3
• PCC TF 2:5.4.4.11

Instructions

1. Create a patient record in your system contains an Active Problems data element as specified below (Supplemental Information).
2. Direct your system to export/produce a PCC/CDA document that contains the requested data. If your system needs a communication partner to receive the document, you will need to manage that process. These tools do not provide that partner.
3. Copy the file to the MESA test system where it can be accessed by the test scripts.
4. Use a Windows Command Prompt window (terminal emulator) or unix terminal simulator. Set the current directory to $MESA_TARGET/mesa_tests/pcc/actors/ccrt.
5. Evaluate the XML file using the steps below.

Evaluation

• Run the evaluation script on the file of your choice (FILE) as described below:

   perl 40250/eval_40250.pl <log level> FILE

• The result file is found in 40250/mesa_mir_40250.xml. The test is successful when the grade file indicates 0 errors.
• Submit the grade to the Project Manager for evaluation. For Connectathon preparation, this normally means uploading the mesa_mir_40250.xml file into the Kudu/Gazelle system designated by the Project Manager.

Supplemental Information

You are welcome to reuse the document you tested in other unit tests.

Test 40250 is looking for these features in the Active Problems data element:

1. Please see PCC TF 2:5.4.3.2.3.1 for construction of the <component>
2. Contains two templateID elements with proper OIDs
3. Contains <code> element with proper LOINC code (11450-4)
4. Following is the specified clinical content
5. Contains <text> element with this text: Patient complains of
   1. Contains one entry Allergy to penicillin / effective time low=20051216, high is absent
   2. Contains second entry with 'Hypertension / effective time low=20041223, high is absent

Sample of Active Problems for Test 40250

40251: PCC Geriatic Depression Scale Section 1

40251 is a unit test where the Content Creator actor creates a PCC/CDA document that contains the Geriatric Depression Scale Section of the Functional Status Assessment . Because this test applies to different document types and specifies the content, the document/content produced may not make clinical sense. Ignore that issue and follow the test instructions.

This test is similar to other unit tests which require specific content. You are free to use the same document to satisfy these different tests.

References

• PCC TF 2:5.4.3.2.20
• PCC TF 2:5.4.4.38

Instructions

1. Create a patient record in your system contains a Functional Status Assessment section in a Geriatric Depression Scale section as specified below (Supplemental Information).
2. Direct your system to export/produce a PCC/CDA document that contains the requested data. If your system needs a communication partner to receive the document, you will need to manage that process. These tools do not provide that partner.
3. Copy the file to the MESA test system where it can be accessed by the test scripts.
4. Use a Windows Command Prompt window (terminal emulator) or unix terminal simulator. Set the current directory to $MESA_TARGET/mesa_tests/pcc/actors/ccrt.
5. Evaluate the XML file using the steps below.

Evaluation

• Run the evaluation script on the file of your choice (FILE) as described below:

   perl 40251/eval_40251.pl <log level> FILE

• The result file is found in 40251/mesa_mir_40251.xml. The test is successful when the grade file indicates 0 errors.
• Submit the grade to the Project Manager for evaluation. For Connectathon preparation, this normally means uploading the mesa_mir_40251.xml file into the Kudu/Gazelle system designated by the Project Manager.

Supplemental Information

You are welcome to reuse the document you tested in other unit tests.

Test 40251 is looking for these features in the Geriatric Depression Scale section :

1. Conduct a survey using the Geriatic Depression Scale questions. These are encoded in PCC 2:5.4.4.39.3
2. For each question in the survey, the answer recorded is "yes". Record individual observations for each "yes" answer.
3. Record a computation of the overall score. The answer is not 30.

MESA/CDA-Sample-40251 | Sample of Active Problems for Test 40251

403xx: 40300-40399 Tests

The 403xx series tests are stored on a separate page.

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:

• Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/doc_src.
• Create an XDS-MS document that would be submitted to a Document Repository. This should be an XML file as defined in the XDS-MS Integration Profile.
• Transform the document using an XSLT transform using this step:

   perl 12504/doc_src_12504.pl FILE

Evaluation

• The transform step above creates a file in the 12504 directory: 12504.html. View the HTML file to determine if it looks “reasonable”.
• Rename the HTML file to SYSTEM_12504.html.
• Submit the HTML file to the Project Manager for 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:

• Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/doc_src.
• Create an XDS-MS document that would be submitted to a Document Repository. 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

• Run the evaluation script on the file of your choice (FILE) as described below:

   perl 12505/eval_12505.pl <log level> FILE

• The result file is found in 12505/grade_12505.txt. Submit the grade to the Project Manager for evaluation.

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:

• Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/doc_src.
• Create an XDS-MS document that would be submitted to a Document Repository. 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

• Run the evaluation script on the file of your choice (FILE) as described below:

   perl 12506/eval_12506.pl <log level> FILE

• The result file is found in 12506/grade_12506.txt. Submit the grade to the Project Manager for evaluation

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:

• The Document Source will share this document with Document 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 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	3145551671
Provider Organization	Gateway Hospital 600 Euclid Ave St. Louis MO 63110
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 XDS-MS document that would be submitted to a Document Repository. 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

• Run the evaluation script on the file of your choice (FILE) as described below:

   perl 12510/eval_12510.pl <log level> FILE

• The result file is found in 12510/grade_12510.txt. Submit the grade to the Project Manager for evaluation.

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:

• Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/doc_src.
• Use the Discharge Summary created for test 12510.
• Evaluate the XML file to make sure it passes the Schematron test using the steps below.

Evaluation

• Run the evaluation script on the file of your choice (FILE) as described below:

   perl 12511/eval_12511.pl <log level> FILE

• The result file is found in 12511/grade_12511.txt. Submit the grade to the Project Manager for evaluation.

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:

• Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/doc_src.
• Use the Discharge Summary created for test 12510.
• Evaluate the XML file to make sure it passes the Schematron test using the steps below.

Evaluation

• Run the evaluation script on the file of your choice (FILE) as described below:

   perl 12512/eval_12512.pl <log level> FILE

• The result file is found in 12512/grade_12512.txt. Submit the grade to the Project Manager for evaluation.

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:

• Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/doc_src.
• Use the Discharge Summary created for test 12510.
• Evaluate the XML file to make sure it passes the Schematron test using the steps below.

Evaluation

• Run the evaluation script on the file of your choice (FILE) as described below:

   perl 12513/eval_12513.pl <log level> FILE

• The result file is found in 12513/grade_12513.txt. Submit the grade to the Project Manager for evaluation

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	3145551671
Provider Organization	Gateway Hospital 600 Euclid Ave St. Louis MO 63110
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 XDS-MS document that would be submitted to a Document Repository. 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

• Run the evaluation script on the file of your choice (FILE) as described below:

   perl 12510/eval_12510.pl <log level> FILE

• The result file is found in 12510/grade_12510.txt. Submit the grade to the Project Manager for evaluation.

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:

• Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/doc_src.
• Use the Discharge Summary created for test 12510.
• Evaluate the XML file to make sure it passes the Schematron test using the steps below.

Evaluation

• Run the evaluation script on the file of your choice (FILE) as described below:

   perl 12511/eval_12511.pl <log level> FILE

• The result file is found in 12511/grade_12511.txt. Submit the grade to the Project Manager for evaluation.

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:

• Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/doc_src.
• Use the Discharge Summary created for test 12510.
• Evaluate the XML file to make sure it passes the Schematron test using the steps below.

Evaluation

• Run the evaluation script on the file of your choice (FILE) as described below:

   perl 12512/eval_12512.pl <log level> FILE

• The result file is found in 12512/grade_12512.txt. Submit the grade to the Project Manager for evaluation.

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:

• Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/doc_src.
• Use the Discharge Summary created for test 12510.
• Evaluate the XML file to make sure it passes the Schematron test using the steps below.

Evaluation

• Run the evaluation script on the file of your choice (FILE) as described below:

   perl 12513/eval_12513.pl <log level> FILE

• The result file is found in 12513/grade_12513.txt. Submit the grade to the Project Manager for evaluation.

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	3145551671
Provider Organization	Gateway Hospital 600 Euclid Ave St. Louis MO 63110
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:

   perl 12520/eval_12520.pl <log level> FILE

2. 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 the files: <your_system_name>_14101_pdf.xml and <your_system_name>_14101_test.xml

3. If possible, render the documents and perform a screen capture (JPEG or other common format).

5. Upload the XML files and screen capture snapshots into kudu under MESA Tests -> Pre-Connectathon...Objects for test 14101.

7. Create a short txt file indicating you have completed the upload step. Upload that txt file into the Kudu system under the MESA test log results for this test.

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

• 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:

• Set the current directory to $MESA_TARGET/mesa_tests/iti/actors/ccrt.
• Create an scanned document document; this should be an CDA-wrapped document (XML file) as defined in the XDS-XD Integration Profile.
• Evaluate the XML file to make sure it passes the Schematron test using the steps below.

Evaluation

• Run the evaluation script on your XML file (FILE) as described below:

   perl  14110/eval_14110.pl <log_level> FILE

• The result file is found in 14110/grade_14110.txt. Submit the grade to the Project Manager for evaluation.

Supplemental Information

Test Cases: MCH

This section describes test cases associated with the MCH (Mother & Child Health) Integration Profile.

Test Case 14352: MCH - Sample Prepop Content

See test description: http://ihewiki.wustl.edu/wiki/index.php/MESA/Form_Filler#Form_Filler_Test_14352:_RFD_Exchange_Sample_Pre-Population_XML

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

1.

46241-6: HOSPITAL ADMISSION DX

1.

10183-2: HOSPITAL DISCHARGE MEDICATIONS

1.

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	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

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

1.

11535-2: HOSPITAL DISCHARGE DX

1.

46241-6: HOSPITAL ADMISSION DX

1.

10183-2: HOSPITAL DISCHARGE MEDICATIONS

1.

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