Manual Scrutiny tests

This section contains test cases where sample messages and objects are:

  • manually verified in the absence of a tool
  • exchanged between test partners in advance of the Connectathon

 

EYECARE-15_Manual_Evaluation

EYECARE-15 is a Patient Registration message

In this test, we ask you to provide a sample message produced by your system, and we will validate your message by manual evaluation using the requirements in the Eye Care Technical Framework.

This is the same evaluation we will perform during the Connectathon.  This test enables you to prepare in advance.

Instructions
  1. Capture an ADT^A04 message as produced by your system.  Create a file containing the contents of that message.
  2. In Gazelle, select menu Connectathon-->List of samples.
  3. On the "systems" dropdown list, select your system name
  4. On the "Samples to share" tab, find the entry for "EYECARE-15"
  5. Upload the file containing your HL7 message.  If you need help managing samples, refer to this help page.

Finally, update the status of this pre-Connectathon test in gazelle to signal that your message is ready for evaluation:

  1. In Gazelle, select menu Connectathon-->Pre-Connectathon testing 
  2. Find the entry for this test instance, and change the status to "Verified by Vendor"
 
We examine your message using the same evalution defined in the Connectathon test for this message:
 
1. in Gazelle, select menu Connectathon-->Connectathon.
2. Find test "EYECARE-15_Scrutiny"
3. In the Evaluation section of that test, you will find the message segments and fields that we will look for in your message.
 
 

EYECARE-16_Manual_Evaluation

EYECARE-16 is a Appointment Scheduling Management message

In this test, we ask you to provide a sample message produced by your system, and we will validate your message by manual evaluation using the requirements in the Eye Care Technical Framework.

This is the same evaluation we will perform during the Connectathon.  This test enables you to prepare in advance.

Instructions
  1. There are multiple SIU messages supported in the EYECARE-16 transaction.  You will capture these messages as produced by your system.  Create a files containing the contents of each message:
    1. SIU^S12 New Appointment
    2. SIU^S14 Modify Appointment
    3. SIU^S15 Cancel Appointment
    4. SIU^S17 Delete Appointment
    5. SIU^S26 Patient No Show
  2. In Gazelle, select menu Connectathon-->List of samples.
  3. On the "systems" dropdown list, select your system name
  4. On the "Samples to share" tab, find the entry for "EYECARE-16"
  5. Upload the files containing your HL7 messages.  If you need help managing samples, refer to this help page.

Finally, update the status of this pre-Connectathon test in gazelle to signal that your message is ready for evaluation:

  1. In Gazelle, select menu Connectathon-->Pre-Connectathon testing 
  2. Find the entry for this test instance, and change the status to "Verified by Vendor"
 
We examine your message using the same evalution defined in the Connectathon test for this message:
 
1. in Gazelle, select menu Connectathon-->Connectathon.
2. Find test "EYECARE-16_Scrutiny"
3. In the Evaluation section of that test, you will find the message segments and fields that we will look for in your message.
 
 

EYECARE-17_Manual_Evaluation

EYECARE-17 is a Charge Posting message

In this test, we ask you to provide a sample message produced by your system, and we will validate your message by manual evaluation using the requirements in the Eye Care Technical Framework.

This is the same evaluation we will perform during the Connectathon.  This test enables you to prepare in advance.

Instructions
  1. Capture an DFT^P03 message as produced by your system.  Create a file containing the contents of that message.
  2. In Gazelle, select menu Connectathon-->List of samples
  3. On the "systems" dropdown list, select your system name
  4. On the "Samples to share" tab, find the entry for "EYECARE-17"
  5. Upload the file containing your HL7 message.  If you need help managing samples, refer to this help page.

Finally, update the status of this pre-Connectathon test in gazelle to signal that your message is ready for evaluation:

  1. In Gazelle, select menu Connectathon-->Pre-Connectathon testing 
  2. Find the entry for this test instance, and change the status to "Verified by Vendor"
 
We examine your message using the same evalution defined in the Connectathon test for this message:
 
1. in Gazelle, select menu Connectathon-->Connectathon.
2. Find test "EYECARE-17_Scrutiny"
3. In the Evaluation section of that test, you will find the message segments and fields that we will look for in your message.
 
 

EYECARE-21_Manual_Evaluation

EYECARE-21 is a Procedure Scheduled message

In this test, we ask you to provide a sample message produced by your system, and we will validate your message by manual evaluation using the requirements in the Eye Care Technical Framework.

This is the same evaluation we will perform during the Connectathon.  This test enables you to prepare in advance.

Instructions
  1. Capture an OMG^019 message as produced by your system.  Create a file containing the contents of that message.
  2. In Gazelle, select menu Connectathon-->List of samples
  3. On the "systems" dropdown list, select your system name
  4. On the "Samples to share" tab, find the entry for "EYECARE-21"
  5. Upload the file containing your HL7 message.  If you need help managing samples, refer to this help page.

Finally, update the status of this pre-Connectathon test in gazelle to signal that your message is ready for evaluation:

  1. In Gazelle, select menu Connectathon-->Pre-Connectathon testing 
  2. Find the entry for this test instance, and change the status to "Verified by Vendor"
 
We examine your message using the same evalution defined in the Connectathon test for this message:
 
1. in Gazelle, select menu Connectathon-->Connectathon.
2. Find test "EYECARE-21_Scrutiny"
3. In the Evaluation section of that test, you will find the message segments and fields that we will look for in your message.
 
 

EYECARE-23-24_Manual_Evaluation

EYECARE-23 is XML for Refractive Measurement (no Pat ID)

EYECARE-24 is XML for Refrative Measurement (valid Pat ID)

In this test, we ask you to provide a sample message produced by your system, and we will validate your message by manual evaluation using the requirements in the Eye Care Technical Framework and in the JOIA 1.5 specification.

This is the same evaluation we will perform during the Connectathon.  This test enables you to prepare in advance.

Instructions
  1. Capture an the XML message as produced by your system.  Create an XML file containing the contents of that message.
  2. In Gazelle,select menu Connectathon-->List of samples
  3. On the "systems" dropdown list, select your system name
  4. On the "Samples to share" tab, find the entry for "EYECARE-23" or "EYECARE-24" as applicable
  5. Upload the file containing your HL7 message.  If you need help managing samples, refer to this help page.

Finally, update the status of this pre-Connectathon test in gazelle to signal that your message is ready for evaluation:

  1. In Gazelle, select menu Connectathon-->Pre-Connectathon testing 
  2. Find the entry for this test instance, and change the status to "Verified by Vendor"
 
We examine your message using the same evalution defined in the Connectathon test for this message:
 
1. in Gazelle, select menu Connectathon-->Connectathon.
2. Find test "EYECARE-23-24_Scrutiny"
3. In the Evaluation section of that test, you will find the content that we will look for in your XML.
 
 

RAD-2_with_CDS_Manual_Evaluation

In this pre-Connectathon test, we will evaluate a sample RAD-2 OMG message produced by your system.

Since CDS-OAT is a new profile, we do not yet have a tool to evaluate the specific requirements for RAD-2 in CDS-OAT, so we will validate your message using:

  • the gazelle EVSclient tool to validate the base requirements for RAD-2
  • and, manual scrutiny of the message for requirement added for compliance to the CDS-OAT profile.

This is the same evaluation we will perform during the Connectathon.  This test enables you to prepare in advance.

Instructions
  1. Capture a [RAD-2] OMG^019 message as produced by your system.  Create a file containing the contents of that message.
  2. In the EVSclient tool, select menu IHE-->HL7v2.x
  3. Paste a copy of your OMG message into the tool and run the validator for RAD-2 OMG, HL7 v2.5.1.
  4. Find the permanent link to you validation reult
  5. In Gazelle, select menu Connectathon-->Pre-Connectathon testing and find your list of pre-Connectathon by clicking on the link in the "To complete" column
  6. Paste the permanent link to your validation results (from step 4 above) into the chat window for this pre-Connectathon test.
  7. Change the Status of your test to "Verified by vendor"
Evaluation
 
We examine your message using the same evalution defined in the Connectathon test for this message:
 
1. in Gazelle, select menu Connectathon-->Connectathon.
2. Find test "RAD-2_with_CDS_Scrutiny" for your test system
3. In the Evaluation section of that test, you will find the message segments and fields that we will look for in your message.
 
 

RAD-35_with_CDS_Manual_Evaluation

In this pre-Connectathon test, we will evaluate a sample RAD-35 DFT message produced by your system.

Since CDS-OAT is a new profile, we do not yet have a tool to evaluate the specific requirements for RAD-35 in CDS-OAT, so we will validate your message using:manual scrutiny of the message for requirement added for compliance to the CDS-OAT profile.

This is the same evaluation we will perform during the Connectathon.  This test enables you to prepare in advance.

Instructions
  1. Capture a [RAD-35] DFT^P03 message as produced by your system.  Create a file containing the contents of that message.
  2. In Gazelle, select menu Connectathon-->Pre-Connectathon testing and find your list of pre-Connectathon by clicking on the link in the "To complete" column
  3. Paste a copy of your message into the chat window for this pre-Connectathon test.
  4. Change the Status of your test to "Verified by vendor"
Evaluation
 
We examine your message using the same evalution defined in the Connectathon test for this message:
 
1. in Gazelle, select menu Connectathon-->Connectathon.
2. Find test "RAD-35_with_CDS_Scrutiny" for your test system
3. In the Evaluation section of that test, you will find the message segments and fields that we will look for in your message.
 
 

RAD-3_with_CDS_Manual_Evaluation

In this pre-Connectathon test, we will evaluate a sample RAD-3 OMG message produced by your system.

Since CDS-OAT is a new profile, we do not yet have a tool to evaluate the specific requirements for RAD-3 in CDS-OAT, so we will validate your message using:

  • the gazelle EVSclient tool to validate the base requirements for RAD-3
  • and, manual scrutiny of the message for requirement added for compliance to the CDS-OAT profile.

This is the same evaluation we will perform during the Connectathon.  This test enables you to prepare in advance.

Instructions
  1. Capture a [RAD-3] OMG^019 message as produced by your system.  Create a file containing the contents of that message.
  2. In the EVSclient tool, select menu IHE-->HL7v2.x
  3. Paste a copy of your OMG message into the tool and run the validator for RAD-3 OMG, HL7 v2.5.1.
  4. Find the permanent link to you validation reult
  5. In Gazelle, select menu Connectathon-->Pre-Connectathon testing and find your list of pre-Connectathon by clicking on the link in the "To complete" column
  6. Paste the permanent link to your validation results (from step 4 above) into the chat window for this pre-Connectathon test.
  7. Change the Status of your test to "Verified by vendor"
Evaluation
 
We examine your message using the same evalution defined in the Connectathon test for this message:
 
1. in Gazelle, select menu Connectathon-->Connectathon.
2. Find test "RAD-3_with_CDS_Scrutiny" for your test system
3. In the Evaluation section of that test, you will find the message segments and fields that we will look for in your message.
 
 

RAD-4_with_CDS_Manual_Evaluation

In this pre-Connectathon test, we will evaluate a sample RAD-4 OMI message produced by your system.

Since CDS-OAT is a new profile, we do not yet have a tool to evaluate the specific requirements for RAD-4 in CDS-OAT, so we will validate your message using:

  • the gazelle EVSclient tool to validate the base requirements for RAD-4
  • and, manual scrutiny of the message for requirement added for compliance to the CDS-OAT profile.

This is the same evaluation we will perform during the Connectathon.  This test enables you to prepare in advance.

Instructions
  1. Capture a [RAD-3] OMI^023 message as produced by your system.  Create a file containing the contents of that message.
  2. In the EVSclient tool, select menu IHE-->HL7v2.x
  3. Paste a copy of your OMI message into the tool and run the validator for RAD-4 OMI, HL7 v2.5.1.
  4. Find the permanent link to you validation reult
  5. In Gazelle, select menu Connectathon-->Pre-Connectathon testing and find your list of pre-Connectathon by clicking on the link in the "To complete" column
  6. Paste the permanent link to your validation results (from step 4 above) into the chat window for this pre-Connectathon test.
  7. Change the Status of your test to "Verified by vendor"
Evaluation
 
We examine your message using the same evalution defined in the Connectathon test for this message:
 
1. in Gazelle, select menu Connectathon-->Connectathon.
2. Find test "RAD-4_with_CDS_Scrutiny" for your test system
3. In the Evaluation section of that test, you will find the message segments and fields that we will look for in your message.