Difference between revisions of "MESA/Content Creator 40300-40399"

From IHE Wiki
Jump to navigation Jump to search
(Created page with "<big>'''MESA/Content Creator 40300-40399'''</big> __TOC__ =Content Creator Tests 40300-40399 = ==Introduction== This page documents tests for Content Creators in the numeric...")
 
(No difference)

Latest revision as of 08:36, 10 March 2019

MESA/Content Creator 40300-40399

Content Creator Tests 40300-40399

Introduction

This page documents tests for Content Creators in the numeric range 40300-40399

40312: APR: Spouse Module T1

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

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

References

  • Template ID: 1.3.6.1.4.1.19376.1.5.3.1.2.4.1
  • PCC TF 2:6.3.3.2

Instructions

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

Evaluation

  • Run the evaluation script on the file of your choice (FILE) as described below:
   perl schematron/eval_schematron.pl 40312 log_level FILE
  • In the script above:
    • 40312 is the test number. Use that value literally
    • log_level varies from 1 to 4. When you submit results, run at level 4 (most verbose)
    • FILE is your XML file
  • The result file is found in 40312/mesa_mir_40312.xml. The test is successful when the grade file indicates 0 errors.
  • Submit the grade to the Project Manager for evaluation. For Connectathon preparation, this normally means uploading the mesa_mir_40312.xml file into the Kudu/Gazelle system designated by the Project Manager.

Supplemental Information

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

Test 40312 is looking for these features in the Spouse header element:

  1. Please see PCC TF 2:6.3.3.2 for construction of the <participantt>
  2. Contains two templateID elements with proper OIDs
  3. Contains <code> element with proper SNOMED CT code (184142008)
  4. Following is the specified clinical content
    1. addr: Ignored in this test
    2. telecom: Ignored in this test
    3. assignedPerson.name:
       <name>
         <given>William</given>
         <family>Randolph</family>
       </name>

An example is found in the MESA distribution in $MESA_TARGET/mesa_tests/pcc/msgs/pcc-gen/apr-samples/40312.xml

40313: APR: Natural Father of Fetus T1: Known

40313 is a unit test where the Content Creator actor creates a PCC/CDA document that contains the Natural Father of Fetus header element. Because this test applies to different document types and specifies the content, the document/content produced may not make clinical sense. Ignore that issue and follow the test instructions.

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

References

  • Template ID: 1.3.6.1.4.1.19376.1.5.3.1.2.4.2
  • PCC TF 2:6.3.3.3

Instructions

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

Evaluation

  • Run the evaluation script on the file of your choice (FILE) as described below:
   perl schematron/eval_schematron.pl 40313 log_level FILE
  • In the script above:
    • 40313 is the test number. Use that value literally
    • log_level varies from 1 to 4. When you submit results, run at level 4 (most verbose)
    • FILE is your XML file
  • The result file is found in 40313/mesa_mir_40313.xml. The test is successful when the grade file indicates 0 errors.
  • Submit the grade to the Project Manager for evaluation. For Connectathon preparation, this normally means uploading the mesa_mir_40313.xml file into the Kudu/Gazelle system designated by the Project Manager.

Supplemental Information

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

Test 40313 is looking for these features in the Natural Father of Fetus header element:

  1. Please see PCC TF 2:6.3.3.3 for construction of the <participantt>
  2. Contains two templateID elements with proper OIDs
  3. Contains <code> element with proper SNOMED CT code (xx-fatherofbaby)
  4. Following is the specified clinical content
    1. addr: Ignored in this test
    2. telecom: Ignored in this test
    3. assignedPerson.name:
       <name>
         <given>Thomas</given>
         <family>Caster</family>
       </name>

An example is found in the MESA distribution in $MESA_TARGET/mesa_tests/pcc/msgs/pcc-gen/apr-samples/40313.xml

40314: APR: Natural Father of Fetus T1: Unknown

40314 is a unit test where the Content Creator actor creates a PCC/CDA document that contains the Natural Father of Fetus header element. Because this test applies to different document types and specifies the content, the document/content produced may not make clinical sense. Ignore that issue and follow the test instructions.

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

References

  • Template ID: 1.3.6.1.4.1.19376.1.5.3.1.2.4.2
  • PCC TF 2:6.3.3.3

Instructions

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

Evaluation

  • Run the evaluation script on the file of your choice (FILE) as described below:
   perl schematron/eval_schematron.pl 40314 log_level FILE
  • In the script above:
    • 40314 is the test number. Use that value literally
    • log_level varies from 1 to 4. When you submit results, run at level 4 (most verbose)
    • FILE is your XML file
  • The result file is found in 40314/mesa_mir_40314.xml. The test is successful when the grade file indicates 0 errors.
  • Submit the grade to the Project Manager for evaluation. For Connectathon preparation, this normally means uploading the mesa_mir_40314.xml file into the Kudu/Gazelle system designated by the Project Manager.

Supplemental Information

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

Test 40314 is looking for these features in the Natural Father of Fetus header element:

  1. Please see PCC TF 2:6.3.3.3 for construction of the <participantt>
  2. Contains two templateID elements with proper OIDs
  3. Contains <code> element with proper SNOMED CT code (xx-fatherofbaby)
  4. Following is the specified clinical content
    1. addr: Ignored in this test
    2. telecom: Ignored in this test
    3. Father is unknown and encoded as follows:

An example is found in the MESA distribution in $MESA_TARGET/mesa_tests/pcc/msgs/pcc-gen/apr-samples/40314.xml

40315: APR: Chief Complaint: H and P T1

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

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

References

  • Template ID: 1.3.6.1.4.1.19376.1.5.3.1.1.13.2.1
  • PCC TF 2:6.4.3.1.3

Instructions

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

Evaluation

  • Run the evaluation script on the file of your choice (FILE) as described below:
   perl schematron/eval_schematron.pl 40315 log_level FILE
  • In the script above:
    • 40315 is the test number. Use that value literally
    • log_level varies from 1 to 4. When you submit results, run at level 4 (most verbose)
    • FILE is your XML file
  • The result file is found in 40315/mesa_mir_40315.xml. The test is successful when the grade file indicates 0 errors.
  • Submit the grade to the Project Manager for evaluation. For Connectathon preparation, this normally means uploading the mesa_mir_40315.xml file into the Kudu/Gazelle system designated by the Project Manager.

Supplemental Information

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

Test 40315 is looking for these features in the Chief Complaint section:

  1. Please see PCC TF 2:6.4.3.1.3 for construction of the <component>
  2. Contains one templateID element with proper OID
  3. Contains <code> element with proper LOINC code (10154-3)
  4. Following is the specified clinical content
    1. Text for chief complaint (use verbatim)
   Patient complains of feeling anemic.

An example is found in the MESA distribution in $MESA_TARGET/mesa_tests/pcc/msgs/pcc-gen/apr-samples/40315.xml

40316: APR: History of Present Illness

40316 is a unit test where the Content Creator actor creates a PCC/CDA document that contains the History of Present Illness section. Because this test applies to different document types and specifies the content, the document/content produced may not make clinical sense. Ignore that issue and follow the test instructions.

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

References

  • Template ID: 1.3.6.1.4.1.19376.1.5.3.1.3.4
  • PCC TF 2:6.4.3.2.1

Instructions

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

Evaluation

  • Run the evaluation script on the file of your choice (FILE) as described below:
   perl schematron/eval_schematron.pl 40316 log_level FILE
  • In the script above:
    • 40316 is the test number. Use that value literally
    • log_level varies from 1 to 4. When you submit results, run at level 4 (most verbose)
    • FILE is your XML file
  • The result file is found in 40316/mesa_mir_40316.xml. The test is successful when the grade file indicates 0 errors.
  • Submit the grade to the Project Manager for evaluation. For Connectathon preparation, this normally means uploading the mesa_mir_40316.xml file into the Kudu/Gazelle system designated by the Project Manager.

Supplemental Information

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

Test 40316 is looking for these features in the History of Present Illness section:

  1. Please see PCC TF 2:6.4.3.1.3 for construction of the <component>
  2. Contains one templateID element with proper OID
  3. Contains <code> element with proper LOINC code (10164-2)
  4. Following is the specified clinical content
    1. Text for chief complaint (use verbatim)
   Patient has felt sluggish for past two weeks.

An example is found in the MESA distribution in $MESA_TARGET/mesa_tests/pcc/msgs/pcc-gen/apr-samples/40316.xml

40317: APR: Past Medical History

40317 is a unit test where the Content Creator actor creates a PCC/CDA document that contains the Past Medical History section. Because this test applies to different document types and specifies the content, the document/content produced may not make clinical sense. Ignore that issue and follow the test instructions.

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

References

  • Template ID: 1.3.6.1.4.1.19376.1.5.3.1.3.8
  • PCC TF 2:6.4.3.2.5
  • PCC TF 2:6.5.1

Instructions

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

Evaluation

  • Run the evaluation script on the file of your choice (FILE) as described below:
   perl schematron/eval_schematron.pl 40317 log_level FILE
  • In the script above:
    • 40317 is the test number. Use that value literally
    • log_level varies from 1 to 4. When you submit results, run at level 4 (most verbose)
    • FILE is your XML file
  • The result file is found in 40317/mesa_mir_40317.xml. The test is successful when the grade file indicates 0 errors.
  • Submit the grade to the Project Manager for evaluation. For Connectathon preparation, this normally means uploading the mesa_mir_40317.xml file into the Kudu/Gazelle system designated by the Project Manager.

Supplemental Information

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

Test 40317 is looking for these features in the Past Medical History section:

  • Please see PCC TF 2:6.4.3.1.3 for construction of the <component>
  • Contains one templateID element with proper OID
  • Contains <code> element with proper LOINC code (11348-0)
  • Following is the specified clinical content
    • Text for chief complaint (use verbatim if possible)
   Patient has history of diabetes, seasonal allergies and a latex allergy.
  • Include the following entries with appropriate SNOMED CT codes
    • Diabetes / 73211009
    • Seasonal Allergies / 367498001
    • Latex Allergy / 300916003

An example is found in the MESA distribution in $MESA_TARGET/mesa_tests/pcc/msgs/pcc-gen/apr-samples/40317.xml

40318: APR: History of Infection

To be written

40319: APR: Pregnancy History: 0 pregnancies

40319 is a unit test where the Content Creator actor creates a PCC/CDA document that contains the Past Medical History section. Because this test applies to different document types and specifies the content, the document/content produced may not make clinical sense. Ignore that issue and follow the test instructions.

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

References

  • Template ID: 1.3.6.1.4.1.19376.1.5.3.1.1.5.3.4
  • PCC TF 2:
  • PCC TF 2:

Instructions

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

Evaluation

  • Run the evaluation script on the file of your choice (FILE) as described below:
   perl schematron/eval_schematron.pl 40319 log_level FILE
  • In the script above:
    • 40319 is the test number. Use that value literally
    • log_level varies from 1 to 4. When you submit results, run at level 4 (most verbose)
    • FILE is your XML file
  • The result file is found in 40319/mesa_mir_40319.xml. The test is successful when the grade file indicates 0 errors.
  • Submit the grade to the Project Manager for evaluation. For Connectathon preparation, this normally means uploading the mesa_mir_40319.xml file into the Kudu/Gazelle system designated by the Project Manager.

Supplemental Information

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

Test 40319 is looking for these features in the Past Medical History section:

  • Please see PCC TF 2: for construction of the <component>
  • Contains one templateID element with proper OID
  • Contains <code> element with proper LOINC code (11348-0)
  • Following is the specified clinical content
    • Text for chief complaint (use verbatim if possible)
   Patient has no previous pregnancies.
  • Include the following entries with appropriate SNOMED CT codes

An example is found in the MESA distribution in $MESA_TARGET/mesa_tests/pcc/msgs/pcc-gen/apr-samples/40319.xml

40325: APR: Social History

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

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

References

  • Template ID: 1.3.6.1.4.1.19376.1.5.3.1.3.16
  • PCC TF 2:
  • PCC TF 2:

Instructions

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

Evaluation

  • Run the evaluation script on the file of your choice (FILE) as described below:
   perl schematron/eval_schematron.pl 40325 log_level FILE
  • In the script above:
    • 40325 is the test number. Use that value literally
    • log_level varies from 1 to 4. When you submit results, run at level 4 (most verbose)
    • FILE is your XML file
  • The result file is found in 40325/mesa_mir_40325.xml. The test is successful when the grade file indicates 0 errors.
  • Submit the grade to the Project Manager for evaluation. For Connectathon preparation, this normally means uploading the mesa_mir_40325.xml file into the Kudu/Gazelle system designated by the Project Manager.

Supplemental Information

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

Test 40325 is looking for these features in the Social History section:

  • Please see PCC TF 2: for construction of the <component>
  • Contains two templateID elements with proper OID
  • Contains <code> element with proper LOINC code (29762-2)
  • Following is the specified clinical content
    • Text for chief complaint (use verbatim if possible)
   Patient smoked from age 16 through 19.
  • Include the following entries with appropriate SNOMED CT codes
    • Tobacco Use / SNOMED CT Code 266918002

An example is found in the MESA distribution in $MESA_TARGET/mesa_tests/pcc/msgs/pcc-gen/apr-samples/40325.xml

40326: APR: Coded Family Medical History

40326 is a unit test where the Content Creator actor creates a PCC/CDA document that contains the Coded Family Medical History section. Because this test applies to different document types and specifies the content, the document/content produced may not make clinical sense. Ignore that issue and follow the test instructions.

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

References

  • Template ID: 1.3.6.1.4.1.19376.1.5.3.1.3.15
  • PCC TF 2:
  • PCC TF 2:

Instructions

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

Evaluation

  • Run the evaluation script on the file of your choice (FILE) as described below:
   perl schematron/eval_schematron.pl 40326 log_level FILE
  • In the script above:
    • 40326 is the test number. Use that value literally
    • log_level varies from 1 to 4. When you submit results, run at level 4 (most verbose)
    • FILE is your XML file
  • The result file is found in 40326/mesa_mir_40326.xml. The test is successful when the grade file indicates 0 errors.
  • Submit the grade to the Project Manager for evaluation. For Connectathon preparation, this normally means uploading the mesa_mir_40326.xml file into the Kudu/Gazelle system designated by the Project Manager.

Supplemental Information

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

Test 40326 is looking for these features in the Coded Family Medical History section:

  • Please see PCC TF 2: for construction of the <component>
  • Contains two templateID elements with proper OID
  • Contains <code> element with proper LOINC code (10157-6)
  • Following is the specified clinical content
    • Text for chief complaint (use verbatim if possible)
   Father has Congenital Heart Defect.
  • Include the following entries with appropriate SNOMED CT codes
    • Congenital Heart Defect / SNOMED CT Code 13213009
    • This needs to be specified for the father

An example is found in the MESA distribution in $MESA_TARGET/mesa_tests/pcc/msgs/pcc-gen/apr-samples/40326.xml