From IHEWiki

Contents 1 Content Consumer 1.1 Introduction 1.2 Patient Identification 1.3 Configuration 1.4 Installation Test 1.5 Loading Test Data 2 Test Cases: XDS-SD 2.1 Test Case 14101: Sample XDS-SD Documents 3 Test Cases: MCH 3.1 Test Case 14352: MCH - Sample Prepop Content 4 Test Cases: PCC 4.1 40800: PCC XPHR Render Aortic Dissection 4.2 40801: PCC EDR Render Aortic Dissection 4.3 40802: PCC BPPC Render Aortic Dissection 4.4 40803: PCC XD-Lab Render Aortic Dissection 4.5 40804: PCC PPHP Render Aortic Dissection 4.6 40805: PCC XDS-MS Discharge Render Aortic Dissection 4.7 40806: PCC XDS-MS Discharge Render MESA Sample 2007-2008 4.8 40810: PCC XPHR Render Cardiac Referral 4.9 40811: PCC XDS-MS Referral Render Cardiac Referral 4.10 40812: PCC BPPC Render Cardiac Referral 4.11 40813: PCC XD-Lab Render Cardiac Referral 4.12 40814: PCC PPHP Render Cardiac Referral 4.13 40815: PCC XDS-MS Discharge Render Cardiac Referral 4.14 40816: PCC XDS-MS Referral Render MESA Sample 2007-2008 4.15 40817: PCC EDR ED Referral Render MESA Sample 2007-2008 4.16 40818: PCC XPHR Extract Render MESA Sample 2007-2008 4.17 40822: PCC Render Vendor XPHR 4.18 40830: PCC APS Render MESA Sample 2007-2008 4.19 40831: PCC EDES Render MESA Samples 2007-2008 4.20 40832: PCC FSA Render MESA Samples 2007-2008 4.21 40151: EDR Sample 4.22 40152: BPPC Sample 4.23 40153: PCC Render Vendor PPHP 4.24 40154: XDS-MS Discharge Summary Sample 4.25 40155: XDS-MS Referral Sample 4.26 40156: XD-Lab Sample 4.27 40157: XPHR Extract Sample 4.28 40158: XPHR Update Sample 4.29 40161: FSA/EDR Sample 4.30 40162: FSA/XDS-MS Sample 4.31 40163: FSA/XPHR Sample 4.32 40164: EDES Triage Note Sample 4.33 40165: EDES Nursing Note Sample 4.34 40166: EDES Composite Triage and ED Nursing Note Sample 4.35 40167: EDES ED Physician Note Sample 4.36 40168: Antepartum History and Physical Sample 4.37 40169: Antepartum Summary Sample 4.38 40170: Antepartum Laboratory Report Sample 4.39 40171: Antepartum Education Sample 4.40 40172: Immunization Content Sample 4.41 40180-01, -02, ...: Sample Documents: CDA

Content Consumer

Introduction

The MESA tests include a number of cases each of which rely on a sequence of messages between actors. These tests range across different integration profiles:

• XDS-MS
• XDS-SD
• PPHP
• EDR
• BPPC
• XPHR
• XD*-Lab

This document lists the transactions and messages for a number of cases. It may not describe the clinical scenario behind each case, but listing the transactions should clearly define what is expected of each actor. These are all of the transactions involving all of the actors. When you test with your particular actor, you may see only a subset of these messages.

Note that the tests for Content profiles such as XDS-MS and XDS-SD are over and above tests for the delivery of data for profiles XDS, XDM and XDR. The tests described in this document concern the content described in the XDS-MS and XDS-SD profile. The XDS/XDM/XDR tests concerned with delivery of data are documented elsewhere.

Patient Identification

Configuration

Starting the MESA Servers

There are no MESA servers to start for this test.

Installation Test

Loading Test Data

Test Cases: XDS-SD

This section describes test cases that are generally associated with the XDS-SD Integration Profile.

Test Case 14101: Sample XDS-SD Documents

The Document Consumer will import a number of documents supplied by different XDS-SD Document Sources. The Document Consumer fills out a worksheet indicating if the content could be imported/rendered. The purpose of this test is to give Document Consumers a chance to examine content in advance of a face to face test. This will allow some debugging of document content to be performed offline rather than in real time.

References

Instructions

1. Find samples uploaded by other vendors for test 14101 in kudu under MESA Tests -> Pre-Connectathon...Objects. This page will evolve as vendors add samples, so be patient.
2. Retrieve the documents created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
3. You will find a table listing the systems which have submitted samples for test 14101. Extract this table and place it in a spreadsheet that can be read by Excel. Create columns labelled Reviewed (Y/N) and Comments
4. When you are finished, upload the spreadsheet as the results for this test.
5. If you find any documents that are problematic, contact the Project Manager as soon as possible so we can work with the source of the data.
6. The goal is no surprises.

Evaluation

The evaluation of this test is performed by examining the spreadsheet you provided to make sure you made a good faith effort to review the sample images.

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_Manager#Form_Manager_Test_14352:_RFD_Exchange_Sample_Pre-Population_XML

Test Cases: PCC

This section describes test cases that are generally associated with several different PCC profiles.

40800: PCC XPHR Render Aortic Dissection

In test 40800, the Content Consumer is asked to "process/render" a test document from the Aortic Dissection test case. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample document and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. The file $MESA_TARGET/mesa_tests/pcc/msgs/aortic/ad-xphr.xml represents a sample XPHR document according to the XPHR Integration Profile.

2. Import this document into your system by out of band means.

3. Render/process the content on your system. Generate some display (GUI, database dump, command line output) that demonstrates that you have successfully processed the document.

4. Perform a screen capture of the rendered output. Name the captured output <your-system-name>_40800<extension> and where <extension> is html, jpg, bmp, doc, etc. If the output is just a text file, then you can just submit the text file without performing a screen capture.

5. Create a separate text file (.txt, not word document) that briefly explains which option is supported and how that is demonstrated by the output in the step above.

6. Place both files (output file, text explanation) in a zip file (name_40800.zip) and submit that zip file for evaluation.

Evaluation

1. Submit the zip file created above to the Project Manager. The Project Manager will examine to determine sufficient information has been made available to the user.

Supplemental Information

40801: PCC EDR Render Aortic Dissection

Do not run this test. Instead, run test 40817.

In test 40801, the Content Consumer is asked to "process/render" a test document from the Aortic Dissection test case. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample document and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. The file $MESA_TARGET/mesa_tests/pcc/msgs/aortic/ad-edr.xml represents a sample EDR document according to the EDR Integration Profile.

2. Import this document into your system by out of band means.

3. Render/process the content on your system. Generate some display (GUI, database dump, command line output) that demonstrates that you have successfully processed the document.

4. Perform a screen capture of the rendered output. Name the captured output <your-system-name>_40801<extension> and where <extension> is html, jpg, bmp, doc, etc. If the output is just a text file, then you can just submit the text file without performing a screen capture.

5. Create a separate text file (.txt, not word document) that briefly explains which option is supported and how that is demonstrated by the output in the step above.

6. Place both files (output file, text explanation) in a zip file (name_40801.zip) and submit that zip file for evaluation.

Evaluation

1. Submit the zip file created above to the Project Manager. The Project Manager will examine to determine sufficient information has been made available to the user.

Supplemental Information

40802: PCC BPPC Render Aortic Dissection

In test 40802, the Content Consumer is asked to "process/render" a test document from the Aortic Dissection test case. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample document and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. The file $MESA_TARGET/mesa_tests/pcc/msgs/pcc-gen/aortic/ad-bppc.xml represents a sample BPPC document according to the BPPC Integration Profile.

2. Import this document into your system by out of band means.

3. Render/process the content on your system. Generate some display (GUI, database dump, command line output) that demonstrates that you have successfully processed the document.

4. Perform a screen capture of the rendered output. Name the captured output <your-system-name>_40802<extension> and where <extension> is html, jpg, bmp, doc, etc. If the output is just a text file, then you can just submit the text file without performing a screen capture.

5. Create a separate text file (.txt, not word document) that briefly explains which option is supported and how that is demonstrated by the output in the step above.

6. Place both files (output file, text explanation) in a zip file (name_40802.zip) and submit that zip file for evaluation.

Evaluation

1. Submit the zip file created above to the Project Manager. The Project Manager will examine to determine sufficient information has been made available to the user.

Supplemental Information

40803: PCC XD-Lab Render Aortic Dissection

In test 40803, the Content Consumer is asked to "process/render" a test document from the Aortic Dissection test case. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample document and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. The file $MESA_TARGET/mesa_tests/pcc/msgs/aortic/ad-lab.xml represents a sample XD*-Lab document according to the XD*-Lab Integration Profile.

2. Import this document into your system by out of band means.

3. Render/process the content on your system. Generate some display (GUI, database dump, command line output) that demonstrates that you have successfully processed the document.

4. Perform a screen capture of the rendered output. Name the captured output <your-system-name>_40803<extension> and where <extension> is html, jpg, bmp, doc, etc. If the output is just a text file, then you can just submit the text file without performing a screen capture.

5. Create a separate text file (.txt, not word document) that briefly explains which option is supported and how that is demonstrated by the output in the step above.

6. Place both files (output file, text explanation) in a zip file (name_40803.zip) and submit that zip file for evaluation.

Evaluation

1. Submit the zip file created above to the Project Manager. The Project Manager will examine to determine sufficient information has been made available to the user.

Supplemental Information

40804: PCC PPHP Render Aortic Dissection

In test 40804, the Content Consumer is asked to "process/render" a test document from the Aortic Dissection test case. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample document and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. The file $MESA_TARGET/mesa_tests/pcc/msgs/aortic/ad-pphp.xml represents a sample PPHP document according to the PPHP Integration Profile.

2. Import this document into your system by out of band means.

3. Render/process the content on your system. Generate some display (GUI, database dump, command line output) that demonstrates that you have successfully processed the document.

4. Perform a screen capture of the rendered output. Name the captured output <your-system-name>_40804<extension> and where <extension> is html, jpg, bmp, doc, etc. If the output is just a text file, then you can just submit the text file without performing a screen capture.

5. Create a separate text file (.txt, not word document) that briefly explains which option is supported and how that is demonstrated by the output in the step above.

6. Place both files (output file, text explanation) in a zip file (name_40804.zip) and submit that zip file for evaluation.

Evaluation

1. Submit the zip file created above to the Project Manager. The Project Manager will examine to determine sufficient information has been made available to the user.

Supplemental Information

40805: PCC XDS-MS Discharge Render Aortic Dissection

Do not run test 40805. Do run test 40806.

In test 40805, the Content Consumer is asked to "process/render" a test document from the Aortic Dissection test case. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample document and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. The file $MESA_TARGET/mesa_tests/pcc/msgs/aortic/ad-discharge.xml represents a sample XDS-MS Discharge Summary document according to the XDS-MS Integration Profile.

2. Import this document into your system by out of band means.

3. Render/process the content on your system. Generate some display (GUI, database dump, command line output) that demonstrates that you have successfully processed the document.

4. Perform a screen capture of the rendered output. Name the captured output <your-system-name>_40805<extension> and where <extension> is html, jpg, bmp, doc, etc. If the output is just a text file, then you can just submit the text file without performing a screen capture.

5. Create a separate text file (.txt, not word document) that briefly explains which option is supported and how that is demonstrated by the output in the step above.

6. Place both files (output file, text explanation) in a zip file (name_40805.zip) and submit that zip file for evaluation.

Evaluation

1. Submit the zip file created above to the Project Manager. The Project Manager will examine to determine sufficient information has been made available to the user.

Supplemental Information

40806: PCC XDS-MS Discharge Render MESA Sample 2007-2008

Special Instructions

The instructions below are written as if the sample was perfect. It is not. You will find the most recent version of the sample on the wiki and not in the MESA distribution. As you examine the sample, please pass your comments back to the larger group of PCC implementors. For January 2008, this will have to be a group learning experience. We do not have a perfect sample to provide.

The sample is on this wiki at: NA2008/Test_40806

Regular Instructions

In test 40806, the Content Consumer is asked to "process/render" a sample test document. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample document and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. The file $MESA_TARGET/mesa_tests/pcc/msgs/pcc-gen/tf-samples/discharge-sample-mesa.xml represents a sample XDS-MS Discharge Summary document according to the XDS-MS Integration Profile.

2. Import this document into your system by out of band means.

3. Render/process the content on your system. Generate some display (GUI, database dump, command line output) that demonstrates that you have successfully processed the document.

4. Perform a screen capture of the rendered output. Name the captured output <your-system-name>_40806<extension> and where <extension> is html, jpg, bmp, doc, etc. If the output is just a text file, then you can just submit the text file without performing a screen capture.

5. Create a separate text file (.txt, not word document) that briefly explains which option is supported and how that is demonstrated by the output in the step above.

6. Place both files (output file, text explanation) in a zip file (name_40806.zip) and submit that zip file for evaluation.

Evaluation

1. Submit the zip file created above to the Project Manager. The Project Manager will examine to determine sufficient information has been made available to the user.

Supplemental Information

40810: PCC XPHR Render Cardiac Referral

In test 40810, the Content Consumer is asked to "process/render" a test document from the Cardiac Referral test case. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample document and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. The file $MESA_TARGET/mesa_tests/pcc/msgs/card/cardref-xphr.xml.xml represents a sample XPHR document according to the XPHR Integration Profile.

2. Import this document into your system by out of band means.

3. Render/process the content on your system. Generate some display (GUI, database dump, command line output) that demonstrates that you have successfully processed the document.

4. Perform a screen capture of the rendered output. Name the captured output <your-system-name>_40810<extension> and where <extension> is html, jpg, bmp, doc, etc. If the output is just a text file, then you can just submit the text file without performing a screen capture.

5. Create a separate text file (.txt, not word document) that briefly explains which option is supported and how that is demonstrated by the output in the step above.

6. Place both files (output file, text explanation) in a zip file (name_40810.zip) and submit that zip file for evaluation.

Evaluation

1. Submit the zip file created above to the Project Manager. The Project Manager will examine to determine sufficient information has been made available to the user.

Supplemental Information

40811: PCC XDS-MS Referral Render Cardiac Referral

Do not run this test. Instead, run test 40816.

In test 40811, the Content Consumer is asked to "process/render" a test document from the Cardiac Referral test case. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample document and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. The file $MESA_TARGET/mesa_tests/pcc/msgs/card/cardref-referral.xml.xml represents a sample XDS-MS Referral document according to the XDS-MS Integration Profile.

2. Import this document into your system by out of band means.

3. Render/process the content on your system. Generate some display (GUI, database dump, command line output) that demonstrates that you have successfully processed the document.

4. Perform a screen capture of the rendered output. Name the captured output <your-system-name>_40811<extension> and where <extension> is html, jpg, bmp, doc, etc. If the output is just a text file, then you can just submit the text file without performing a screen capture.

5. Create a separate text file (.txt, not word document) that briefly explains which option is supported and how that is demonstrated by the output in the step above.

6. Place both files (output file, text explanation) in a zip file (name_40811.zip) and submit that zip file for evaluation.

Evaluation

1. Submit the zip file created above to the Project Manager. The Project Manager will examine to determine sufficient information has been made available to the user.

Supplemental Information

40812: PCC BPPC Render Cardiac Referral

In test 40812, the Content Consumer is asked to "process/render" a test document from the Cardiac Referral test case. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample document and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. The file $MESA_TARGET/mesa_tests/pcc/msgs/card/cardref-bppc.xml.xml represents a sample BPPC document according to the BPPC Integration Profile.

2. Import this document into your system by out of band means.

3. Render/process the content on your system. Generate some display (GUI, database dump, command line output) that demonstrates that you have successfully processed the document.

4. Perform a screen capture of the rendered output. Name the captured output <your-system-name>_40812<extension> and where <extension> is html, jpg, bmp, doc, etc. If the output is just a text file, then you can just submit the text file without performing a screen capture.

5. Create a separate text file (.txt, not word document) that briefly explains which option is supported and how that is demonstrated by the output in the step above.

6. Place both files (output file, text explanation) in a zip file (name_40812.zip) and submit that zip file for evaluation.

Evaluation

1. Submit the zip file created above to the Project Manager. The Project Manager will examine to determine sufficient information has been made available to the user.

Supplemental Information

40813: PCC XD-Lab Render Cardiac Referral

This test is broken. We are missing the sample document.

In test 40813, the Content Consumer is asked to "process/render" a test document from the Cardiac Referral test case. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample document and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. The file $MESA_TARGET/mesa_tests/pcc/msgs/card/cardref-lab.xml.xml represents a sample XD*-Lab document according to the XD*-Lab Integration Profile.

2. Import this document into your system by out of band means.

3. Render/process the content on your system. Generate some display (GUI, database dump, command line output) that demonstrates that you have successfully processed the document.

4. Perform a screen capture of the rendered output. Name the captured output <your-system-name>_40813<extension> and where <extension> is html, jpg, bmp, doc, etc. If the output is just a text file, then you can just submit the text file without performing a screen capture.

5. Create a separate text file (.txt, not word document) that briefly explains which option is supported and how that is demonstrated by the output in the step above.

6. Place both files (output file, text explanation) in a zip file (name_40813.zip) and submit that zip file for evaluation.

Evaluation

1. Submit the zip file created above to the Project Manager. The Project Manager will examine to determine sufficient information has been made available to the user.

Supplemental Information

40814: PCC PPHP Render Cardiac Referral

In test 40814, the Content Consumer is asked to "process/render" a test document from the Cardiac Referral test case. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample document and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. The file $MESA_TARGET/mesa_tests/pcc/msgs/card/cardref-pphp.xml.xml represents a sample PPHP document according to the PPHP Integration Profile.

2. Import this document into your system by out of band means.

3. Render/process the content on your system. Generate some display (GUI, database dump, command line output) that demonstrates that you have successfully processed the document.

4. Perform a screen capture of the rendered output. Name the captured output <your-system-name>_40814<extension> and where <extension> is html, jpg, bmp, doc, etc. If the output is just a text file, then you can just submit the text file without performing a screen capture.

5. Create a separate text file (.txt, not word document) that briefly explains which option is supported and how that is demonstrated by the output in the step above.

6. Place both files (output file, text explanation) in a zip file (name_40814.zip) and submit that zip file for evaluation.

Evaluation

1. Submit the zip file created above to the Project Manager. The Project Manager will examine to determine sufficient information has been made available to the user.

Supplemental Information

40815: PCC XDS-MS Discharge Render Cardiac Referral

Do not run this test. Do run test 40806.

In test 40815, the Content Consumer is asked to "process/render" a test document from the Cardiac Referral test case. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample document and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. The file $MESA_TARGET/mesa_tests/pcc/msgs/card/cardref-discharge.xml.xml represents a sample XDS-MS Discharge Summary document according to the XDS-MS Integration Profile.

2. Import this document into your system by out of band means.

3. Render/process the content on your system. Generate some display (GUI, database dump, command line output) that demonstrates that you have successfully processed the document.

4. Perform a screen capture of the rendered output. Name the captured output <your-system-name>_40815<extension> and where <extension> is html, jpg, bmp, doc, etc. If the output is just a text file, then you can just submit the text file without performing a screen capture.

5. Create a separate text file (.txt, not word document) that briefly explains which option is supported and how that is demonstrated by the output in the step above.

6. Place both files (output file, text explanation) in a zip file (name_40815.zip) and submit that zip file for evaluation.

Evaluation

1. Submit the zip file created above to the Project Manager. The Project Manager will examine to determine sufficient information has been made available to the user.

Supplemental Information

40816: PCC XDS-MS Referral Render MESA Sample 2007-2008

Special Instructions

The instructions below are written as if the sample was perfect. It is not. You will find the most recent version of the sample on the wiki and not in the MESA distribution. As you examine the sample, please pass your comments back to the larger group of PCC implementors. For January 2008, this will have to be a group learning experience. We do not have a perfect sample to provide.

The sample is on this wiki at: NA2008/Test_40816

Regular Instructions

In test 40816, the Content Consumer is asked to "process/render" a sample test document. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample document and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. The file $MESA_TARGET/mesa_tests/pcc/msgs/pcc-gen/tf-samples/referral-sample-mesa.xml represents a sample XDS-MS Referral document according to the XDS-MS Integration Profile.

2. Import this document into your system by out of band means.

3. Render/process the content on your system. Generate some display (GUI, database dump, command line output) that demonstrates that you have successfully processed the document.

4. Perform a screen capture of the rendered output. Name the captured output <your-system-name>_40816<extension> and where <extension> is html, jpg, bmp, doc, etc. If the output is just a text file, then you can just submit the text file without performing a screen capture.

5. Create a separate text file (.txt, not word document) that briefly explains which option is supported and how that is demonstrated by the output in the step above.

6. Place both files (output file, text explanation) in a zip file (name_40816.zip) and submit that zip file for evaluation.

Evaluation

1. Submit the zip file created above to the Project Manager. The Project Manager will examine to determine sufficient information has been made available to the user.

Supplemental Information

40817: PCC EDR ED Referral Render MESA Sample 2007-2008

Special Instructions

The instructions below are written as if the sample was perfect. It is not. You will find the most recent version of the sample on the wiki and not in the MESA distribution. As you examine the sample, please pass your comments back to the larger group of PCC implementors. For January 2008, this will have to be a group learning experience. We do not have a perfect sample to provide.

The sample is on this wiki at: NA2008/Test_40817

Regular Instructions

In test 40816, the Content Consumer is asked to "process/render" a sample test document. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample document and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. The file $MESA_TARGET/mesa_tests/pcc/msgs/pcc-gen/tf-samples/ed-referral-sample-mesa.xml represents a sample ED Referral document according to the EDR Integration Profile.

2. Import this document into your system by out of band means.

3. Render/process the content on your system. Generate some display (GUI, database dump, command line output) that demonstrates that you have successfully processed the document.

4. Perform a screen capture of the rendered output. Name the captured output <your-system-name>_40817<extension> and where <extension> is html, jpg, bmp, doc, etc. If the output is just a text file, then you can just submit the text file without performing a screen capture.

5. Create a separate text file (.txt, not word document) that briefly explains which option is supported and how that is demonstrated by the output in the step above.

6. Place both files (output file, text explanation) in a zip file (name_40817.zip) and submit that zip file for evaluation.

Evaluation

1. Submit the zip file created above to the Project Manager. The Project Manager will examine to determine sufficient information has been made available to the user.

Supplemental Information

40818: PCC XPHR Extract Render MESA Sample 2007-2008

Special Instructions

The instructions below are written as if the sample was perfect. It is not. You will find the most recent version of the sample on the wiki and not in the MESA distribution. As you examine the sample, please pass your comments back to the larger group of PCC implementors. For January 2008, this will have to be a group learning experience. We do not have a perfect sample to provide.

The sample is on this wiki at: NA2008/Test_40818

Regular Instructions

In test 40817, the Content Consumer is asked to "process/render" a sample test document. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample document and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. The file $MESA_TARGET/mesa_tests/pcc/msgs/pcc-gen/tf-samples/xphr-extract-sample-mesa.xml represents a sample XPHR Extract document according to the XPHR Integration Profile.

2. Import this document into your system by out of band means.

3. Render/process the content on your system. Generate some display (GUI, database dump, command line output) that demonstrates that you have successfully processed the document.

4. Perform a screen capture of the rendered output. Name the captured output <your-system-name>_40818<extension> and where <extension> is html, jpg, bmp, doc, etc. If the output is just a text file, then you can just submit the text file without performing a screen capture.

5. Create a separate text file (.txt, not word document) that briefly explains which option is supported and how that is demonstrated by the output in the step above.

6. Place both files (output file, text explanation) in a zip file (name_40818.zip) and submit that zip file for evaluation.

Evaluation

1. Submit the zip file created above to the Project Manager. The Project Manager will examine to determine sufficient information has been made available to the user.

Supplemental Information

40822: PCC Render Vendor XPHR

This test is now deprecated in favor of 40180-xx

In test 40822, the Content Consumer is asked to "process/render" a set of test documents that are supplied by other test participants. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample documents and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. Look on the Connectathon Wiki for the BPPC samples for your Connectathon. The URL is http://ihewiki.wustl.edu/wiki.. This page will evolve as vendors add samples, so be patient.

2. The EDR page will contain a spreadsheet (40152.xls) and a set of XML files contributed by vendors.

3. Process/render each document submitted by a vendor. (Again, use your imagination.)

4. Fill out the "Comment" column in the spreadsheet that indicates if you could successfully process/render each document.

5. Assuming that the process/render step is successful, follow the normal process of submitting the result (spreadsheet) to the Project Manager.

6. If there are any issues with any of the sample documents, send an email to the Project Manager immediately to alert him/her to the issue. This would allow the Project Manager to coordinate with the other systems involved.

Evaluation

1. Complete the file 40822.xls by filling in the "Comment" column.

2. Submit the 40822.xls file to the Project Manager for evaluation.

3. Email comments immediately to the Project Manager if there are issues with any of the supplied samples.

Supplemental Information

40830: PCC APS Render MESA Sample 2007-2008

Special Instructions

The instructions below are written as if the sample was perfect. It is not. You will find the most recent version of the sample on the wiki and not in the MESA distribution. As you examine the sample, please pass your comments back to the larger group of PCC implementors. For January 2008, this will have to be a group learning experience. We do not have a perfect sample to provide.

The sample is on this wiki at: NA2008/Test_40830

Regular Instructions

In test 40830, the Content Consumer is asked to "process/render" a sample test document. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample document and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. The file $MESA_TARGET/mesa_tests/pcc/msgs/pcc-gen/tf-samples/aps-mesa.xml represents a sample APS document according to the APS Integration Profile.

2. Import this document into your system by out of band means.

3. Render/process the content on your system. Generate some display (GUI, database dump, command line output) that demonstrates that you have successfully processed the document.

4. Perform a screen capture of the rendered output. Name the captured output <your-system-name>_40830<extension> and where <extension> is html, jpg, bmp, doc, etc. If the output is just a text file, then you can just submit the text file without performing a screen capture.

5. Create a separate text file (.txt, not word document) that briefly explains which option is supported and how that is demonstrated by the output in the step above.

6. Place both files (output file, text explanation) in a zip file (name_40830.zip) and submit that zip file for evaluation.

Evaluation

1. Submit the zip file created above to the Project Manager. The Project Manager will examine to determine sufficient information has been made available to the user.

Supplemental Information

40831: PCC EDES Render MESA Samples 2007-2008

Special Instructions

The instructions below are written as if the sample was perfect. It is not. You will find the most recent version of the sample on the wiki and not in the MESA distribution. As you examine the sample, please pass your comments back to the larger group of PCC implementors. For January 2008, this will have to be a group learning experience. We do not have a perfect sample to provide.

The sample is on this wiki at: NA2008/Test_40831

Regular Instructions

In test 40831, the Content Consumer is asked to "process/render" a sample test document. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample document and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. There are four MESA sample EDES documents. These are all located in $MESA_TARGET/mesa_tests/pcc/msgs/pcc-gen:

 edes-composite-triage-nursing-mesa.xml
 edes-nursing-note-mesa.xml
 edes-physician-note-mesa.xml
 edes-triage-mesa.xml

2. Import these documents into your system by out of band means.

3. Render/process the content on your system. Generate some display (GUI, database dump, command line output) that demonstrates that you have successfully processed the document.

4. Perform a screen capture of the rendered output. Name the captured output <your-system-name>_40831<extension> and where <extension> is html, jpg, bmp, doc, etc. If the output is just a text file, then you can just submit the text file without performing a screen capture.

5. Create a separate text file (.txt, not word document) that briefly explains which option is supported and how that is demonstrated by the output in the step above.

6. Place both files (output file, text explanation) in a zip file (name_40831.zip) and submit that zip file for evaluation.

Evaluation

1. Submit the zip file created above to the Project Manager. The Project Manager will examine to determine sufficient information has been made available to the user.

Supplemental Information

40832: PCC FSA Render MESA Samples 2007-2008

Special Instructions

The instructions below are written as if the sample was perfect. It is not. You will find the most recent version of the sample on the wiki and not in the MESA distribution. As you examine the sample, please pass your comments back to the larger group of PCC implementors. For January 2008, this will have to be a group learning experience. We do not have a perfect sample to provide.

The sample is on this wiki at: NA2008/Test_40832

Regular Instructions

In test 40832, the Content Consumer is asked to "process/render" sample test documents. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample document and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. There are three MESA sample FSA documents. These are all located in $MESA_TARGET/mesa_tests/pcc/msgs/pcc-gen:

 fsa-ed-referral-mesa.xml
 fsa-referral-mesa.xml
 fsa-xphr-extract-mesa.xml

2. Import these documents into your system by out of band means.

3. Render/process the content on your system. Generate some display (GUI, database dump, command line output) that demonstrates that you have successfully processed the document.

4. Perform a screen capture of the rendered output. Name the captured output <your-system-name>_40832<extension> and where <extension> is html, jpg, bmp, doc, etc. If the output is just a text file, then you can just submit the text file without performing a screen capture.

5. Create a separate text file (.txt, not word document) that briefly explains which option is supported and how that is demonstrated by the output in the step above.

6. Place both files (output file, text explanation) in a zip file (name_40832.zip) and submit that zip file for evaluation.

Evaluation

1. Submit the zip file created above to the Project Manager. The Project Manager will examine to determine sufficient information has been made available to the user.

Supplemental Information

40151: EDR Sample

This is deprecated. Please see test 40180-xx

In test 40151, the Content Consumer is asked to "process/render" a set of test documents that are supplied by other test participants. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample documents and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. Find samples uploaded by other vendors for test 40151 in kudu under MESA Tests -> Pre-Connectathon...Objects. This page will evolve as vendors add samples, so be patient.
2. Retrieve the documents created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
3. You will find a table listing the systems which have submitted samples for test 40151. Extract this table and place it in a spreadsheet that can be read by Excel. Create columns labelled Reviewed (Y/N) and Comments
4. When you are finished, upload the spreadsheet as the results for this test.
5. If you find any documents that are problematic, contact the Project Manager as soon as possible so we can work with the source of the data.
6. The goal is no surprises.

Evaluation

1. Complete the file 40151.xls by filling in the "Reviewed Y/N" and "Comment" columns.

2. Submit the 40151.xls file to the Project Manager for evaluation.

3. Email comments immediately to the Project Manager if there are issues with any of the supplied samples.

Supplemental Information

40152: BPPC Sample

This is deprecated. Please see test 40180-xx

In test 40152, the Content Consumer is asked to "process/render" a set of test documents that are supplied by other test participants. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample documents and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. Find samples uploaded by other vendors for test 40152 in kudu under MESA Tests -> Pre-Connectathon...Objects. This page will evolve as vendors add samples, so be patient.
2. Retrieve the documents created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
3. You will find a table listing the systems which have submitted samples for test 40152. Extract this table and place it in a spreadsheet that can be read by Excel. Create columns labelled Reviewed (Y/N) and Comments
4. When you are finished, upload the spreadsheet as the results for this test.
5. If you find any documents that are problematic, contact the Project Manager as soon as possible so we can work with the source of the data.
6. The goal is no surprises.

Evaluation

1. Complete the file 40152.xls by filling in the "Comment" column.

2. Submit the 40152.xls file to the Project Manager for evaluation.

3. Email comments immediately to the Project Manager if there are issues with any of the supplied samples.

Supplemental Information

40153: PCC Render Vendor PPHP

This is deprecated. Please see test 40180-xx

In test 40153, the Content Consumer is asked to "process/render" a set of test documents that are supplied by other test participants. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample documents and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. Find samples uploaded by other vendors for test 40153 in kudu under MESA Tests -> Pre-Connectathon...Objects. This page will evolve as vendors add samples, so be patient.
2. Retrieve the documents created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
3. You will find a table listing the systems which have submitted samples for test 40153. Extract this table and place it in a spreadsheet that can be read by Excel. Create columns labelled Reviewed (Y/N) and Comments
4. When you are finished, upload the spreadsheet as the results for this test.
5. If you find any documents that are problematic, contact the Project Manager as soon as possible so we can work with the source of the data.
6. The goal is no surprises.

Evaluation

1. Complete the file 40153.xls by filling in the "Comment" column.

2. Submit the 40153.xls file to the Project Manager for evaluation.

3. Email comments immediately to the Project Manager if there are issues with any of the supplied samples.

Supplemental Information

40154: XDS-MS Discharge Summary Sample

This is deprecated. Please see test 40180-xx

In test 40154, the Content Consumer is asked to "process/render" a set of test documents that are supplied by other test participants. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample documents and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. Find samples uploaded by other vendors for test 40154 in kudu under MESA Tests -> Pre-Connectathon...Objects. This page will evolve as vendors add samples, so be patient.
2. Retrieve the documents created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
3. You will find a table listing the systems which have submitted samples for test 40154. Extract this table and place it in a spreadsheet that can be read by Excel. Create columns labelled Reviewed (Y/N) and Comments
4. When you are finished, upload the spreadsheet as the results for this test.
5. If you find any documents that are problematic, contact the Project Manager as soon as possible so we can work with the source of the data.
6. The goal is no surprises.

Evaluation

1. Complete the file 40154.xls by filling in the "Comment" column.

2. Submit the 40154.xls file to the Project Manager for evaluation.

3. Email comments immediately to the Project Manager if there are issues with any of the supplied samples.

Supplemental Information

40155: XDS-MS Referral Sample

This is deprecated. Please see test 40180-xx

In test 40155, the Content Consumer is asked to "process/render" a set of test documents that are supplied by other test participants. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample documents and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. Find samples uploaded by other vendors for test 40155 in kudu under MESA Tests -> Pre-Connectathon...Objects. This page will evolve as vendors add samples, so be patient.
2. Retrieve the documents created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
3. You will find a table listing the systems which have submitted samples for test 40155. Extract this table and place it in a spreadsheet that can be read by Excel. Create columns labelled Reviewed (Y/N) and Comments
4. When you are finished, upload the spreadsheet as the results for this test.
5. If you find any documents that are problematic, contact the Project Manager as soon as possible so we can work with the source of the data.
6. The goal is no surprises.

Evaluation

1. Complete the file 40155.xls by filling in the "Comment" column.

2. Submit the 40155.xls file to the Project Manager for evaluation.

3. Email comments immediately to the Project Manager if there are issues with any of the supplied samples.

Supplemental Information

40156: XD-Lab Sample

This is deprecated. Please see test 40180-xx

In test 40156, the Content Consumer is asked to "process/render" a set of test documents that are supplied by other test participants. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample documents and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. Find samples uploaded by other vendors for test 40156 in kudu under MESA Tests -> Pre-Connectathon...Objects. This page will evolve as vendors add samples, so be patient.
2. Retrieve the documents created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
3. You will find a table listing the systems which have submitted samples for test 40156. Extract this table and place it in a spreadsheet that can be read by Excel. Create columns labelled Reviewed (Y/N) and Comments
4. When you are finished, upload the spreadsheet as the results for this test.
5. If you find any documents that are problematic, contact the Project Manager as soon as possible so we can work with the source of the data.
6. The goal is no surprises.

Evaluation

1. Complete the file 40156.xls by filling in the "Comment" column.

2. Submit the 40156.xls file to the Project Manager for evaluation.

3. Email comments immediately to the Project Manager if there are issues with any of the supplied samples.

Supplemental Information

40157: XPHR Extract Sample

This is deprecated. Please see test 40180-xx

In test 40157, the Content Consumer is asked to "process/render" a set of test documents that are supplied by other test participants. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample documents and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. Find samples uploaded by other vendors for test 40157 in kudu under MESA Tests -> Pre-Connectathon...Objects. This page will evolve as vendors add samples, so be patient.
2. Retrieve the documents created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
3. You will find a table listing the systems which have submitted samples for test 40157. Extract this table and place it in a spreadsheet that can be read by Excel. Create columns labelled Reviewed (Y/N) and Comments
4. When you are finished, upload the spreadsheet as the results for this test.
5. If you find any documents that are problematic, contact the Project Manager as soon as possible so we can work with the source of the data.
6. The goal is no surprises.

Evaluation

1. Complete the file 40157.xls by filling in the "Comment" column.

2. Submit the 40157.xls file to the Project Manager for evaluation.

3. Email comments immediately to the Project Manager if there are issues with any of the supplied samples.

Supplemental Information

40158: XPHR Update Sample

This is deprecated. Please see test 40180-xx

In test 40158, the Content Consumer is asked to "process/render" a set of test documents that are supplied by other test participants. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample documents and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. Find samples uploaded by other vendors for test 40158 in kudu under MESA Tests -> Pre-Connectathon...Objects. This page will evolve as vendors add samples, so be patient.
2. Retrieve the documents created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
3. You will find a table listing the systems which have submitted samples for test 40158. Extract this table and place it in a spreadsheet that can be read by Excel. Create columns labelled Reviewed (Y/N) and Comments
4. When you are finished, upload the spreadsheet as the results for this test.
5. If you find any documents that are problematic, contact the Project Manager as soon as possible so we can work with the source of the data.
6. The goal is no surprises.

Evaluation

1. Complete the file 40158.xls by filling in the "Comment" column.

2. Submit the 40158.xls file to the Project Manager for evaluation.

3. Email comments immediately to the Project Manager if there are issues with any of the supplied samples.

Supplemental Information

40161: FSA/EDR Sample

This is deprecated. Please see test 40180-xx

This is for FSA content stored in an EDR document.

In test 40161, the Content Consumer is asked to "process/render" a set of test documents that are supplied by other test participants. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample documents and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. Find samples uploaded by other vendors for test 40161 in kudu under MESA Tests -> Pre-Connectathon...Objects. This page will evolve as vendors add samples, so be patient.
2. Retrieve the documents created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
3. You will find a table listing the systems which have submitted samples for test 40161. Extract this table and place it in a spreadsheet that can be read by Excel. Create columns labelled Reviewed (Y/N) and Comments
4. When you are finished, upload the spreadsheet as the results for this test.
5. If you find any documents that are problematic, contact the Project Manager as soon as possible so we can work with the source of the data.
6. The goal is no surprises.

Evaluation

1. Complete the file 40161.xls by filling in the "Comment" column.

2. Submit the 40161.xls file to the Project Manager for evaluation.

3. Email comments immediately to the Project Manager if there are issues with any of the supplied samples.

Supplemental Information

None

40162: FSA/XDS-MS Sample

This is deprecated. Please see test 40180-xx

This is for FSA content stored in an XDS-MS document.

In test 40162, the Content Consumer is asked to "process/render" a set of test documents that are supplied by other test participants. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample documents and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. Find samples uploaded by other vendors for test 40162 in kudu under MESA Tests -> Pre-Connectathon...Objects. This page will evolve as vendors add samples, so be patient.
2. Retrieve the documents created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
3. You will find a table listing the systems which have submitted samples for test 40162. Extract this table and place it in a spreadsheet that can be read by Excel. Create columns labelled Reviewed (Y/N) and Comments
4. When you are finished, upload the spreadsheet as the results for this test.
5. If you find any documents that are problematic, contact the Project Manager as soon as possible so we can work with the source of the data.
6. The goal is no surprises.

Evaluation

1. Complete the file 40162.xls by filling in the "Comment" column.

2. Submit the 40162.xls file to the Project Manager for evaluation.

3. Email comments immediately to the Project Manager if there are issues with any of the supplied samples.

Supplemental Information

None

40163: FSA/XPHR Sample

This is deprecated. Please see test 40180-xx

These are for FSA content stored in an XPHR document.

In test 40163, the Content Consumer is asked to "process/render" a set of test documents that are supplied by other test participants. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample documents and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. Find samples uploaded by other vendors for test 40163 in kudu under MESA Tests -> Pre-Connectathon...Objects. This page will evolve as vendors add samples, so be patient.
2. Retrieve the documents created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
3. You will find a table listing the systems which have submitted samples for test 40163. Extract this table and place it in a spreadsheet that can be read by Excel. Create columns labelled Reviewed (Y/N) and Comments
4. When you are finished, upload the spreadsheet as the results for this test.
5. If you find any documents that are problematic, contact the Project Manager as soon as possible so we can work with the source of the data.
6. The goal is no surprises.

Evaluation

1. Complete the file 40163.xls by filling in the "Comment" column.

2. Submit the 40163.xls file to the Project Manager for evaluation.

3. Email comments immediately to the Project Manager if there are issues with any of the supplied samples.

Supplemental Information

40164: EDES Triage Note Sample

This is deprecated. Please see test 40180-xx

This is for Triage Notes stored in an EDES document.

In test 40164, the Content Consumer is asked to "process/render" a set of test documents that are supplied by other test participants. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample documents and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. Find samples uploaded by other vendors for test 40164 in kudu under MESA Tests -> Pre-Connectathon...Objects. This page will evolve as vendors add samples, so be patient.
2. Retrieve the documents created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
3. You will find a table listing the systems which have submitted samples for test 40164. Extract this table and place it in a spreadsheet that can be read by Excel. Create columns labelled Reviewed (Y/N) and Comments
4. When you are finished, upload the spreadsheet as the results for this test.
5. If you find any documents that are problematic, contact the Project Manager as soon as possible so we can work with the source of the data.
6. The goal is no surprises.

Evaluation

1. Complete the file 40164.xls by filling in the "Comment" column.

2. Submit the 40164.xls file to the Project Manager for evaluation.

3. Email comments immediately to the Project Manager if there are issues with any of the supplied samples.

Supplemental Information

40165: EDES Nursing Note Sample

This is deprecated. Please see test 40180-xx

This is for Nursing Notes stored in an EDES document.

In test 40165, the Content Consumer is asked to "process/render" a set of test documents that are supplied by other test participants. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample documents and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. Find samples uploaded by other vendors for test 40165 in kudu under MESA Tests -> Pre-Connectathon...Objects. This page will evolve as vendors add samples, so be patient.
2. Retrieve the documents created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
3. You will find a table listing the systems which have submitted samples for test 40165. Extract this table and place it in a spreadsheet that can be read by Excel. Create columns labelled Reviewed (Y/N) and Comments
4. When you are finished, upload the spreadsheet as the results for this test.
5. If you find any documents that are problematic, contact the Project Manager as soon as possible so we can work with the source of the data.
6. The goal is no surprises.

Evaluation

1. Complete the file 40165.xls by filling in the "Comment" column.

2. Submit the 40165.xls file to the Project Manager for evaluation.

3. Email comments immediately to the Project Manager if there are issues with any of the supplied samples.

Supplemental Information

None

40166: EDES Composite Triage and ED Nursing Note Sample

This is deprecated. Please see test 40180-xx

This is for Composite Triage and ED Nursing Notes stored in an EDES document.

In test 40166, the Content Consumer is asked to "process/render" a set of test documents that are supplied by other test participants. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample documents and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. Find samples uploaded by other vendors for test 40166 in kudu under MESA Tests -> Pre-Connectathon...Objects. This page will evolve as vendors add samples, so be patient.
2. Retrieve the documents created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
3. You will find a table listing the systems which have submitted samples for test 40166. Extract this table and place it in a spreadsheet that can be read by Excel. Create columns labelled Reviewed (Y/N) and Comments
4. When you are finished, upload the spreadsheet as the results for this test.
5. If you find any documents that are problematic, contact the Project Manager as soon as possible so we can work with the source of the data.
6. The goal is no surprises.

Evaluation

1. Complete the file 40166.xls by filling in the "Comment" column.

2. Submit the 40166.xls file to the Project Manager for evaluation.

3. Email comments immediately to the Project Manager if there are issues with any of the supplied samples.

Supplemental Information

None

40167: EDES ED Physician Note Sample

This is deprecated. Please see test 40180-xx

This is for ED Physician Notes stored in an EDES document.

In test 40167, the Content Consumer is asked to "process/render" a set of test documents that are supplied by other test participants. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample documents and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. Find samples uploaded by other vendors for test 40167 in kudu under MESA Tests -> Pre-Connectathon...Objects. This page will evolve as vendors add samples, so be patient.
2. Retrieve the documents created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
3. You will find a table listing the systems which have submitted samples for test 40167. Extract this table and place it in a spreadsheet that can be read by Excel. Create columns labelled Reviewed (Y/N) and Comments
4. When you are finished, upload the spreadsheet as the results for this test.
5. If you find any documents that are problematic, contact the Project Manager as soon as possible so we can work with the source of the data.
6. The goal is no surprises.

Evaluation

1. Complete the file 40167.xls by filling in the "Comment" column.

2. Submit the 40167.xls file to the Project Manager for evaluation.

3. Email comments immediately to the Project Manager if there are issues with any of the supplied samples.

Supplemental Information

None

40168: Antepartum History and Physical Sample

This is deprecated. Please see test 40180-xx

This is for APR History and Physical documents.

In test 40168, the Content Consumer is asked to "process/render" a set of test documents that are supplied by other test participants. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample documents and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. Find samples uploaded by other vendors for test 40168 in kudu under MESA Tests -> Pre-Connectathon...Objects. This page will evolve as vendors add samples, so be patient.
2. Retrieve the documents created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
3. You will find a table listing the systems which have submitted samples for test 40168. Extract this table and place it in a spreadsheet that can be read by Excel. Create columns labelled Reviewed (Y/N) and Comments
4. When you are finished, upload the spreadsheet as the results for this test.
5. If you find any documents that are problematic, contact the Project Manager as soon as possible so we can work with the source of the data.
6. The goal is no surprises.

Evaluation

1. Complete the file 40168.xls by filling in the "Comment" column.

2. Submit the 40168.xls file to the Project Manager for evaluation.

3. Email comments immediately to the Project Manager if there are issues with any of the supplied samples.

Supplemental Information

None

40169: Antepartum Summary Sample

This is deprecated. Please see test 40180-xx

This is for APR Summary documents.

In test 40169, the Content Consumer is asked to "process/render" a set of test documents that are supplied by other test participants. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample documents and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. Find samples uploaded by other vendors for test 40169 in kudu under MESA Tests -> Pre-Connectathon...Objects. This page will evolve as vendors add samples, so be patient.
2. Retrieve the documents created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
3. You will find a table listing the systems which have submitted samples for test 40169. Extract this table and place it in a spreadsheet that can be read by Excel. Create columns labelled Reviewed (Y/N) and Comments
4. When you are finished, upload the spreadsheet as the results for this test.
5. If you find any documents that are problematic, contact the Project Manager as soon as possible so we can work with the source of the data.
6. The goal is no surprises.

Evaluation

1. Complete the file 40169.xls by filling in the "Comment" column.

2. Submit the 40169.xls file to the Project Manager for evaluation.

3. Email comments immediately to the Project Manager if there are issues with any of the supplied samples.

Supplemental Information

None

40170: Antepartum Laboratory Report Sample

This is deprecated. Please see test 40180-xx

This is for Laboratory Report content stored in an APR document.

In test 40170, the Content Consumer is asked to "process/render" a set of test documents that are supplied by other test participants. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample documents and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. Find samples uploaded by other vendors for test 40170 in kudu under MESA Tests -> Pre-Connectathon...Objects. This page will evolve as vendors add samples, so be patient.
2. Retrieve the documents created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
3. You will find a table listing the systems which have submitted samples for test 40170. Extract this table and place it in a spreadsheet that can be read by Excel. Create columns labelled Reviewed (Y/N) and Comments
4. When you are finished, upload the spreadsheet as the results for this test.
5. If you find any documents that are problematic, contact the Project Manager as soon as possible so we can work with the source of the data.
6. The goal is no surprises.

Evaluation

1. Complete the file 40170.xls by filling in the "Comment" column.

2. Submit the 40170.xls file to the Project Manager for evaluation.

3. Email comments immediately to the Project Manager if there are issues with any of the supplied samples.

Supplemental Information

None

40171: Antepartum Education Sample

This is deprecated. Please see test 40180-xx

This is for Education content stored in an APR document.

In test 40171, the Content Consumer is asked to "process/render" a set of test documents that are supplied by other test participants. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample documents and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. Find samples uploaded by other vendors for test 40171 in kudu under MESA Tests -> Pre-Connectathon...Objects. This page will evolve as vendors add samples, so be patient.
2. Retrieve the documents created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
3. You will find a table listing the systems which have submitted samples for test 40171. Extract this table and place it in a spreadsheet that can be read by Excel. Create columns labelled Reviewed (Y/N) and Comments
4. When you are finished, upload the spreadsheet as the results for this test.
5. If you find any documents that are problematic, contact the Project Manager as soon as possible so we can work with the source of the data.
6. The goal is no surprises.

Evaluation

1. Complete the file 40171.xls by filling in the "Comment" column.

2. Submit the 40171.xls file to the Project Manager for evaluation.

3. Email comments immediately to the Project Manager if there are issues with any of the supplied samples.

Supplemental Information

None

40172: Immunization Content Sample

This is deprecated. Please see test 40180-xx

This is for Immunization Content documents.

In test 40172, the Content Consumer is asked to "process/render" a set of test documents that are supplied by other test participants. You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample documents and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. Find samples uploaded by other vendors for test 40172 in kudu under MESA Tests -> Pre-Connectathon...Objects. This page will evolve as vendors add samples, so be patient.
2. Retrieve the documents created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
3. You will find a table listing the systems which have submitted samples for test 40172. Extract this table and place it in a spreadsheet that can be read by Excel. Create columns labelled Reviewed (Y/N) and Comments
4. When you are finished, upload the spreadsheet as the results for this test.
5. If you find any documents that are problematic, contact the Project Manager as soon as possible so we can work with the source of the data.
6. The goal is no surprises.

Evaluation

1. Complete the file 40172.xls by filling in the "Comment" column.

2. Submit the 40172.xls file to the Project Manager for evaluation.

3. Email comments immediately to the Project Manager if there are issues with any of the supplied samples.

Supplemental Information

None

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

Tests 40180-01, 40180-02, 40180-xx are a series of tests where the Content Consumer is asked to "process/render" a set of test documents that are supplied by other test participants. The 40180 is the general category for exchanging samples. The -01, -02, ... suffix designates the document type. There is a table below the lists the document types.

You need to use your imagination for this test. Process/render means to apply one or more of the options that are listed below:

• View
• Document Import
• Section Import
• Discrete Data Import

You will perform one or more of those actions on the sample documents and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system.

References

Instructions

1. Find samples uploaded by other vendors for test 40180-xx in kudu under MESA Tests -> Pre-Connectathon...Objects. This page will evolve as vendors add samples, so be patient.
2. Retrieve the documents created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
3. Complete this Media:Cross_Participant_Sample_Evaluation_Form.xls for the specific document type and samples provided by other participants. Use the color key in the spreadsheet to indicate your experience with processing the samples. We have included examples in the spreadsheet.
4. When you are finished, upload the spreadsheet as the results for this test.
5. If you find any documents that are problematic, contact the Project Manager as soon as possible so we can work with the source of the data.
6. The goal is no surprises.

Evaluation

1. Download and complete the form for the specific document type.
2. Upload completed form into Kudu under the proper test number. Please use a separate form for each test number.
3. Email comments immediately to the Project Manager if there are issues with any of the supplied samples.

Supplemental Information

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