MESA/Content Creator

MESA/Content Creator

BPPC - Basic Patient Privacy Consents Profile

This section describes test cases associated with the BPPC Profile.

Test Case 16405: BPPC Privacy Policy for Connectathon testing

This is not a real test. We want all actors involved in BPPC testing to read the "BPPC Privacy Policy Definition for Connectathon Testing". This contains the policy for XDS Affinity Domains at the Connectathon, including 2 BPPC-related items, and defines conditions for BPPC testing at the Connectathon.

Prior to arriving at the Connectathon, read this document: Privacy Policy for Connectathon Testing

Evaluation

There is no log to upload for this "test".

DEN - Document Encryption profile

This section describes test cases associated with the DEN (Document Encryption) Profile.

Test Case 15900: DEN - Access Resource Material and Profile Authors' Examples

The authors of the Document Encryption profile have compiled a resource page to assist implementers of DEN. This 'test' is intended to ensure that you find this page. See: http://wiki.ihe.net/index.php?title=Document_Encryption_-_Implementation_Notes_and_Examples

Instructions

There is no test or script to run. Access the resource page linked above. We hope you find this helpful. Perhaps you have something to add to this page to help other DEN developers.

Submit a small text file into gazelle as results for this test. Include in the file today's date and a note indicating that you found and read the page.

Evaluation

The project manager will mark this test 'Verified' when s/he reads the text file indicating that you found the DEN resource page.

Test Case 15905: DEN - Sample Encrypted Documents

In test 15905, you submit one or more sample encrypted document that your system(s) will produce; The purpose of this test is to allow us to post samples to Content Consumers so they can read/test/render the documents in advance of face-to-face testing.

References

Instructions

1. Create an encryped document per the specifications in the DEN profile. 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. In the filename, include <your_gazelle_system_name>_15905

3. Upload the file(s) into gazelle under menu Connectathon -> List of samples on the Samples to share tab for DEN test 15905.

4. Create a short txt file indicating you have completed the upload step. Upload that txt file into gazelle as results for this test.

5. As Content Consumer actors import your data, you may receive a request for interpretation or directives from the Project Manager to make repairs. This may prove to be an iterative process.

Evaluation

• Please submit sample encrypted documents 2 weeks in advance of the deadline. This will give Content Consumers the opportunity to review the document.

General Test Cases for Content Profiles: PCC, QRPH, CARD and ITI

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 the Content profiles

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

Test 40001 is 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.

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 or QRPH or CARD 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 Gazelle.
   2. xx is the test number (01, 02, ...)
6. Upload the text file into the Gazelle tool.

Evaluation Output of the test must show valid CDA R2.

Administrative Notes These are the test numbers that correspond to PCC, ITI, CARD or QRPH document types:

Test Number	PCC Document
40001-01	XDS-MS Referral Document
40001-02	XDS-MS Discharge Summary
40001-03	ED Referral
40001-04	XPHR Extract
40001-05	XPHR Update
40001-06	Antepartum History and Physical
40001-07	Antepartum Summary
40001-08	Antepartum Laboratory Report
40001-09	Antepartum Education
40001-10	Triage Note
40001-11	ED Nursing Note
40001-12	Composite Triage and ED Nursing Note
40001-13	ED Physician Note
40001-14	Immunization Content
40001-15	Sharing Lab Report (Lab domain)
40001-16	Basic Patient Privacy Consent (ITI domain)
40001-17	XDS-SD Scanned Document (ITI domain) is tested w/ EVS Client in test 14110
40001-18	Labor/Delivery Admission History and Physical
40001-19	Labor/Delivery Summary
40001-20	Maternal Discharge Summary
40001-21	EMS Transfer of Care
40001-22	Patient Plan of Care
40001-26	eNursing Summary
40001-27	Newborn Discharge Summary
40001-28	Postpartum Visit Summary
40001-29	EMS Transport Summary
40001-30	Interfacility Transport Summary
40001-31	Reconciliation of Diagnoses, Allergies & Meds

Administrative Notes These are the test numbers that correspond to QRPH domain content types:

Test Number	QRPH content
40001-100	Clinical Research Document (CRD)
40001-101	Drug Safety Content (DSC)
40001-102	Early Hearing Care Plan (EHCP)
40001-106	Physician Reporting to a Public Health Repository - Cancer Registry (PRPH-Ca)

Administrative Notes These are the test numbers that correspond to CARD domain content types:

Test Number	CARD content
40001-200	Cardiology Imaging Report Content (CIRC)

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

Test 40050 is 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 or QRPH using schematron rules defined by PCC/QRPH/CARD 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.

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 for Errors only. For IHE testing, you are not required to repair items flagged with warnings or 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 Gazelle.
   2. xx is the test number (01, 02, ...)
3. Upload the text file into the Gazelle tool.

Evaluation

The output should show no errors. For IHE testing, you are not required to repair items flagged with warnings or notes.

These are the test numbers that correspond to document types:

Test Number	PCC Document	Add'l notes
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	NA
40050-06	Antepartum History and Physical	NA
40050-07	Antepartum Summary	NA
40050-08	Antepartum Laboratory Report	Not ready
40050-09	Antepartum Education	NA
40050-10	Triage Note	NA
40050-11	ED Nursing Note	NA
40050-12	Composite Triage and ED Nursing Note	NA
40050-13	ED Physician Note	NA
40050-14	Immunization Content	NA
40050-15	Sharing Lab Report (Lab domain)	NA
40050-16	Basic Patient Privacy Consent (ITI domain)	NA
40050-18	Labor/Delivery Admission History and Physical	NA
40050-19	Labor/Delivery Summary	NA
40050-20	Maternal Discharge Summary	NA
40050-22	Patient Plan of Care	NA
40050-26	eNursing Summary	NA
40050-27	Newborn Discharge Summary	NA
40050-28	Postpartum Visit Summary	NA
40050-29	EMS Transport Summary	Not ready
40050-30	Interfacility Transport Summary	Not ready
40050-31	RECON	Not ready
40050-100	QRPH domain - CRD profile	NA
40050-200	CARD domain - CIRC: Cardiology Imaging Report Content	Not ready

40051-01, -02, -03, ....: Content Profile Structure Tests (MDHT Based)

Test 40051 is 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 MIR based on MDHT software. That software makes sure your document conforms to the document specifications.

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 MIR/MDHT tools. We have different test numbers to let us keep track of the document type in the results database.

Instructions

1. Create a document according to the test number (see table below).
2. Use the MDHT Based CDA Validation to validate your document.
3. Complete the validation with the MDHT based software. When that is complete and the results show you have a valid document, perform a screen capture of the application showing that the validation completed with warnings only or no errors. Name that file SYSTEM_NAME_40050-xx.yyy where
   1. SYSTEM_NAME is the keyword of your system name in Gazelle.
   2. xx is the test number (01, 02, ...)
      1. yyy is the proper extension for your screen capture (png, jpg, ...)
4. Upload the text file into the Gazelle tool.

Evaluation

The output should show no errors. For IHE testing, you are not required to repair items flagged with warnings or notes.

These are the test numbers that correspond to document types:

Test Number	PCC Document	Add'l notes
40051-300	General Eye Evaluation	NA

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

This test definition has moved. See: https://gazelle.ihe.net/content/cdadocumentsampleexchange

40181-01, -02, -03, ....: CDA Documents: Scrutiny

Test 40181 is a family of tests. Each test performs the same function. You need to create a CDA R2 document that contains clinical content defined here: Connectathon_CDA_Content_Test_Requirements. A project manager will evaluate the document to determine if the content provided matches what would be expected for the test.

New for NA2012 Connectathon:

• NIST Validation Tool has a new location: http://hit-testing.nist.gov/cda-validation/validation.html
• New content document requirement for all content documents.
  • All sections SHALL have an instance id to uniquely identify that section content module. See IHE PCC Technical Framework, Volume 2, Section 6.3.3.

Tips for Content Creators:

• You need to self-verify your pre-connectathon samples prior to submitting them to Gazelle so you can identify and correct any errors in advance.
  • If NIST validation produces errors, do not submit your sample for validation. Your sample will be marked as 'Failed' if it does not pass NIST validation.
  • If your provided content does not match the expected content as instructed at Connectathon_CDA_Content_Test_Requirements, do not submit your sample for validation. Your sample will be marked as 'Failed' if it does not pass content scrutiny.

The theory behind this test is that a clinician should be able to express clinical content of his/her choosing. Your system needs to be able to express that content to satisfy intent of the clinician. Further information about the expected level of conformance is found with the content information: Connectathon_CDA_Content_Test_Requirements.

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.

Instructions

1. Create a document according to the test number (see table below). Use the clinical content defined here: Connectathon_CDA_Content_Test_Requirements. Name the XML file using this convention:
   1. SYSTEMNAME_TESTNUMBER_type.xml, for example
   2. EHR_XYZmed_40181-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 gazelle system under Connectathon-->List of samples.
   1. Click on the Samples to share tab for your system and Add the appropriate document.
3. In the gazelle Pre-connectathon Testing "Tests to do" page, upload a brief note (txt file) indicating this task is done and submit the file as the results for this test.

Evaluation

A project manager will use the tools found on the page with the clinical content to evaluate your document. The manager will determine if your document satisfies the content requirements that are listed. Further details are listed with the content. In general, there are some pieces of information that should match exactly (a coded value) while there is other information that should carry the same semantic meaning (a text field that might be dictated by a user or come from a pick list).

Administrative Notes

These are the test numbers that correspond to document types:

Test Number	PCC, QRPH, ITI, or CARD Document	Comments
40181-01	XDS-MS Referral Document	NA
40181-02	XDS-MS Discharge Summary	NA
40181-03	ED Referral	NA
40181-04	XPHR Extract	NA
40181-05	XPHR Update	NA
40181-06	Antepartum History and Physical	NA
40181-07	Antepartum Summary	NA
40181-08	Antepartum Laboratory Report	NA
40181-09	Antepartum Education	NA
40181-10	Triage Note	NA
40181-11	ED Nursing Note	NA
40181-12	Composite Triage and ED Nursing Note	NA
40181-13	ED Phyisician Note	NA
40181-14	Immunization Content	NA
40181-15	Sharing Lab Report	NA
40181-16	ITI - Basic Patient Privacy Consent	NA
40181-17	ITI - XDS-SD Scanned Document	NA
40181-18	Labor/Delivery Admission History and Physical	NA
40181-19	Labor/Delivery Summary	NA
40181-20	Maternal Discharge Summary	NA
40181-21	EMS Transfer of Care	NA
40181-22	Patient Plan of Care	NA
40181-23	Functional Status Assessment in EDR	NA
40181-24	Functional Status Assessment in XPHR	NA
40181-25	Functional Status Assessment in XDS-MS	NA
40181-26	eNursing Summary	NA
40181-27	Newborn Discharge Summary	NA
40181-28	Postpartum Visit Summary	NA
40181-33	Routine Interfacility Patient Transport	NA
40181-100	QRPH - CRD: Clinical Research Document	NA
40181-101	QRPH - DSC: Drug Safety Content	NA
40181-102	QRPH - EHCP: Early Hearing Care Plan	NA
40181-105	QRPH - Maternal Child Health & Fetal Death Reporting	NA
40181-106	QRPH - Physician Reporting to a Public Health Repository-Cancer Registry - Form_Filler	NA
40181-107	QRPH - Physician Reporting to a Public Health Repository-Cancer Registry - Form_Receiver	NA
40181-200	CARD - Cardiology Imaging Report Content	NA

ADX - Aggregate Data Exchange Profile

This section contains applicable to the actors in the QRPH Aggregate Data Exchange (ADX) profile: Content Data Structure Creator, Content Creator, Content Consumer.

40190: Content Data Structure Creator - Submit ADX Definition Files

In this test, we gather the ADX-compliant DSD and schema created by the Content Data Structure Creator actor in the ADX profile. The purpose of this test is to make these files accessible to all ADX test partners prior to the Connectathon, enabling pre-Connectathon testing & debugging. The goal is 'no surprises'.

Content Data Structure Creators will use the 'Samples to share' area of gazelle to upload those files.

References

• ADX Trial Implementation Supplement, Vol
  • Section 8.2 - The Data Structure Definition
  • Appendix 8A - Schematron constraining ADX/DSD
  • Appendix 8B - XSLT to generate ADX/XSD schema from DSD
  • Appendix 8E - (Informative) Sample ADX DSD
  • Appendix 8F - (Informative) Generated sample ADX data schema

Instructions

1. Content Creator Structure Creators create an ADX-compliant DSD file and the associated schema (XSD).
2. Upload the DSD file into the gazelle system under menu Connectathon-->List of samples.
   1. Click on the Samples to share tab for your test system and find the ADX entry.
   2. Click on the green 'plus' icon and proceed to upload your file
3. Repeat the above steps to upload your XSD file
4. Some Content Data Structure Creators may implement more than one DSD. You may upload as many as are applicable to your system.
5. Your files are now available to your Content Creator and Content Consumer test partners.
6. Create a short .txt file indicating that you have completed the upload and submit that file into the gazelle under Connectathon-->Pre-connectathon Testing as the results for pre-Connectathon test 40190.

Evaluation

1. Your DSD should be compliant with the schematron constraining ADX DSDs. See References section above.
2. When your partners test with your DSD and XSD, they may have feedback for you.

40190: Content Creator or Consumer - Access ADX Definition Files

In the above test, we gathered the ADX-compliant DSD and schema created by the Content Data Structure Creator actor in the ADX profile.

In this one, the Content Creator or Content Consumer actors access those files enabling pre-Connectathon testing & debugging. The goal is 'no surprises'.

Content Data Structure Creators will use the 'Samples to share' area of gazelle to upload those files.

References

• ADX Trial Implementation Supplement, Vol
  • Section 8.2 - The Data Structure Definition
  • Appendix 8A - Schematron constraining ADX/DSD
  • Appendix 8B - XSLT to generate ADX/XSD schema from DSD
  • Appendix 8E - (Informative) Sample ADX DSD
  • Appendix 8F - (Informative) Generated sample ADX data schema

Instructions

1. Content Creator or Content Consumer find the available ADX definition files uploaded into gazelle:
   1. Log in to gazelle and select menu Connectathon-->List of samples
   2. Click on the Samples for Rendering tab for your test system and find the ADX entry.
   3. You will see a list of Content Data Structure Creator test systems.
   4. If there is a small triangle in front of the system name, you can open the entry. If you don't see a triangle, your partner has not yet provided the ADX definition files.
   5. Click on the link to the entry to see details, and download their sample file(s).
2. You should find entries for both a DSD and XSD file for your Content Data Structure Creator test partner(s).
3. Create a short .txt file indicating that you have obtained the files and submit that .txt file into the gazelle under Connectathon-->Pre-connectathon Testing as the results for pre-Connectathon test 40190.

Evaluation

There is no specific evaluation for Content Creators and Consumers for this test. We want you to test with the ADX definition files prior to the Connectathon.

If you find any problem with the data definition files, send an email to the Technical Project Manager so s/he can facilitate getting this fixed prior to Connectathon