EVS Client tests

This section contains test cases performed with the Gazelle External Validation Service Front-end (aka EVS Client) tool.

Tool: http://gazelle.ihe.net/EVSClient

Tool user guide:  https://gazelle.ihe.net/gazelle-documentation/EVS-Client/user.html

4403: Radiation Dose SR Evaluation

Actors in the REM profile are required to create DICOM-compliant Radiation Dose SR objects.  This also applies to Dose Information Reporters that perform anonymization for transaction [RAD-63] Submit Dose Information

In this test, we validate your sample SRs using PixelMed's DoseUtility tool, one of the DICOM validators hosted in the Gazelle EVS client.

Instructions

  1. Access the EVS Client: http://gazelle.ihe.net/EVSClient
  2. Select menu IHE-->DICOM-->DICOM validation
  3. Upload the file you want to validate.
  4. Then, select Pixelmed from the dropdown list of DICOM validator tools 
  5. Click Execute
Evaluation
 
Capture your results:
  1. Select menu IHE / DICOM / Validated DICOM objects
  2. Examine your results and find the Permanent link to the results
  • You are finished with this test when you have either satisfied all of the errors detected by the tool. If you disagree with the results of the tool, you can write a short (1 or 2 line) description that describes why your object is correct and the DICOM tool software is in error.
  • For this pre-Connectathon test in gazelle, paste the Permanent link to your results into the comment field, instead of uploading a log file. (This is also where you can comment on the results of the validation).
  • Change the status of the test to Verified by vendor
  • The tool identifies errors in your content.

    14100: XDS-SD Schematron & PDF/A

    We use the gazelle External Validation Service (EVS Client) to:

    • verify the attributes in the XDS-SD document using schematron
    • verify that the scanned portion of the document is PDF/A

    References

    You can view the 'help' page for XDS-XD validtion on the EVS Client at: http://gazelle.ihe.net/content/xds-sd-document-validation

    Instructions

    First, check for valid CDA:
    1. Access the External Validation Service: http://gazelle.ihe.net/EVSClient
    2. Select menu: IHE / CDA / Validate
    3. Upload the XDS-SD file you wish to validate
    4. In the Model Based Validation dropdown list, select BASIC - CDA
    5. Select the Validate button
    Second, run the schematron:
    1. Select menu: IHE / CDA / Validate
    2. Upload the XDS-SD file you wish to validate
    3. In the Schematron dropdown list, select IHE XDS-SD
    4. Select the "Validate" button
    Next, find your results:
    1. Select menu: IHE / CDA / Validation Logs
    2. Use the interface to find your validated document. This will show your results.
    Finally, verify that you have valid PDF/A (if this is a PDF scanned document):
    1. Select menu: IHE / CDA / Validation Logs
    2. Use the interface to find your validated document
    3. Select the link to the document
    4. On the page of your results, scroll all the way down to the section labelled "CDA file content".
    5. Select the "html" tab.
    6. At the top, you will see a link to your pdf. Click on the link and the validation will be performed.
    Evaluation
     
    Capture your results:
    1. Create a screen capture of your 'passed' schematron results
    2. (if the scanned doc is PDF, not plain text) Create a screen capture showing Validation Result of "PDF/A Well-Formed"
    3. upload the screen capture(s) into gazelle as results for this test.
    4. Change the status of the test to Verified by vendor
    The tool identifies errors in your content.

    16405: BPPC Privacy Policy for Connectathon testing

    This is not a test using a tool.

    We want all systems involved in BPPC testing at the Connectathon to read the BPPC Privacy Policy Definition for Connectathon Testing.  This contains the policy for XDS Affinity Domains at the Connectathon, including two BPPC-relaed items, and defines the conditions for BPPC testing at the COnnectathon

    Prior to arriving at the Connectathon, read the privacy policy at http://ihewiki.wustl.edu/wiki/index.php/File:Connectathon_BPPC_Privacy_Policy_definition.doc

     
    Evaluation
     
    There is no log to upload for this test.  It is just intended to ensure that you arrive at Connectathon prepared for BPPC testing.

    30400 : LPOCT : Accepted Observation Set (for the POCDM)

    This test concerns the POCDM actor of the LPOCT profile. You will need to validate with EVSClient tool the IHE conformance of your HL7 messages.

    Instructions

    As your system implements the  POCDM   actor, you will need to test the HL7 messages used in the LAB-32 transaction : "Accepted Observation Set".
    Your system must be able to send HL7 messages (to the Oder Filler actor) of types :

    • ORU^R30^ORU_R30, for the LAB-32  transaction
    • ORU^R31^ORU_R30 , for the LAB-32  transaction

    To test the IHE conformance of your HL7 messages, go to the EVSCLient tool at this location : EVSClient
    If it is your first time with this tool, please read the user manual : EVSClient User Manual
        
    In the EVSClient tool, go to the HL7 menu entry and choose "HL7v2" then click on "Message Validation".
    Paste your message to validate in the box. (You can hit the "Guess" button to preset the Message Profile OID.)
        
    For example, for the ORU^R30^ORU_R30 message :

    1. Copy the ORU^R30^ORU_R30 HL7 message from your system. Paste it in the box in the EVSClient page. 
    2. Select the Message profile OID according to your message. In this example : 
      • Affinity Domain : IHE
      • Domain : Laboratory
      • Actor : Point Of Care Data Manager
      • Transaction : LAB-32
      • Message Type : ORU^R30^ORU_R30
      • HL7 Version : HL7v2.5
    3. Once you have selected the Profile OID, press the "Validate" button. If the Validation Result is not "PASSED", it means your HL7 message is not according to the LPOCT Profile of the Laboratory  Technical Framework. If the Validation Result is "PASSED", copy the "Permanent link" and paste it in Gazelle as the result of this test. For further details, see this tutorial : How enter your pre-connectathon test result in Gazelle (only for the LAW, LCSD, LPOCT and LBL Profiles of the Laboratory Domain) ?


    Do this for all messages and don't forget to copy/paste the "Permanent link" of the validation result to Gazelle.

    Evaluation

    • The validation status shall be "PASSED" for all messages.
    • The message type shall be the right message type, according to IHE.
    • Each of the three messages must be validated at least one time and the permanent link must be paste to Gazelle.

    30401 : LPOCT : Accepted Observation Set (for the Order Filler)

    This test concerns the Order Filler actor of the LPOCT profile. You will need to validate with EVSClient tool the IHE conformance of your HL7 messages.

    Instructions

    As your system implements the Order Filler actor, you will need to test the HL7 messages used in the LAB-32 transaction : "Accepted Observation Set".
    Your system must be able to send HL7 message (to the POCDM actor) of type:

    • ACK^R33^ACK, for the LAB-32  transaction

    To test the IHE conformance of your HL7 messages, go to the EVSCLient tool at this location : EVSClient
    If it is your first time with this tool, please read the user manual : EVSClient User Manual
        
    In the EVSClient tool, go to the HL7 menu entry and choose "HL7v2" then click on "Message Validation".
    Paste your message to validate in the box. (You can hit the "Guess" button to preset the Message Profile OID.)
        
    For example, for the ACK^R33^ACK message :

    1. Copy the ACK^R33^ACK HL7 message from your system. Paste it in the box in the EVSClient page. 
    2. Select the Message profile OID according to your message. In this example : 
      • Affinity Domain : IHE
      • Domain : Laboratory
      • Actor : Department System Scheduler/Order Filler
      • Transaction : LAB-32
      • Message Type : ACK^R33^ACK
      • HL7 Version : HL7v2.5
    3. Once you have selected the Profile OID, press the "Validate" button. If the Validation Result is not "PASSED", it means your HL7 message is not according to the LPOCT Profile of the Laboratory  Technical Framework. If the Validation Result is "PASSED", copy the "Permanent link" and paste it in Gazelle as the result of this test. For further details, see this tutorial : How enter your pre-connectathon test result in Gazelle (only for the LAW, LCSD, LPOCT and LBL Profiles of the Laboratory Domain) ?


    Do this for all messages and don't forget to copy/paste the "Permanent link" of the validation result to Gazelle.

    Evaluation

    • The validation status shall be "PASSED" for all messages.
    • The message type shall be the right message type, according to IHE.
    • The Acknowledgment code of the ACK^R33^ACK messages shall be "AA" (MSA-1).
    • Each of the three messages must be validated at least one time and the permanent link must be paste to Gazelle.

    EVS_ADX_Validation

    This test applies to the Content Data Structure Creator actor in the Aggregate Data Exchange (ADX) profile.

    This test ensures that the DSD file produced by the Content Data Structure Creator actor is conformant to the ADX schematron specification.

    Reference:  QRPH TF-3: 8.2 and Appendix 8A, currently in the ADX Trial Implementation Supplement.

    The gazelle External Validation Service (aka EVSClient) hosts the schmatron file and is used to check the DSD.

    Instructions

      1. Access the Gazelle EVSClient application: http://gazelle.ihe.net/EVSClient
      2. From the EVS Client user interface, select menu IHE-->SDMX-->Validate
      3. Upload the XML file for the document produced by your application
      4. Select the schmatron for ADX.
      5. Click on Validate

      Evaluation

        1. The tool reports the results of the evaluation
        2. The EVS Client creates a Permanent link to your results.
        3. If you are performing a pre-Connectathon test in gazelle, paste the Permanent links to your results into the comment field, instead of uploading a log file.
        4. Change the status of the test to Verified by vendor

        EVS_APPC_Validation

        This test applies to the Content Creator actor in the Advanced Patient Privacy Consents (APPC) profile.

        This test ensures that the file produced by the Content Creator actor is conformant to the specification.

        Reference:  ITITF-3: 5.6, currently in the APPC Trial Implementation Supplement.

        The gazelle External Validation Service (aka EVSClient) hosts the schmatron file used to check the APPC documents.

        Instructions

          1. Access the Gazelle EVSClient application: http://gazelle.ihe.net/EVSClient
          2. From the EVS Client user interface, select menu IHE-->APPC-->Validate
          3. Upload the XML file for the document produced by your application
          4. Select the APPC schematron
          5. Click on Validate

          Evaluation

            1. The tool reports the results of the evaluation
            2. The EVS Client creates a Permanent link to your results.
            3. If you are performing a pre-Connectathon test in gazelle, paste the Permanent links to your results into the comment field, instead of uploading a log file.
            4. Change the status of the test to Verified by vendor

            EVS_Assertion-related_Message_Validation

            You will use the Gazelle EVSClielnt to validate messages in SAML- and XACML-related profiles.

            These messages are used in several IHE profiles.  The messages you validate will depend on the profile/actor pairs supported by your test system.

            Instructions

            • Access the Gazelle EVSClient application: http://gazelle.ihe.net/EVSClient
            • From the EVS Client user interface, select menu IHE-->Assertions-->Validate.
            • Paste/upload your the XML file for the message produced by your application
            • Select the correct Model Based Validator from the dropdown list:
              • ITI-40 XUA Provide X-User Assertion 
              • ITI-40 XUA Authz-Consent option
              • ITI-40 XUA Purpose of Use option
              • ITI-40 XUA Subject Role option
              • ITI-79 SeR Authorization Decisions Query Request
              • ITI-79 SeR Authorization Decisions Query Response
            • Click on Validate.

            Evaluation

            • The EVS Client creates a Permanent link to your results.
            • For this pre-Connectathon test in gazelle, paste the Permanent link(s) to your results into the comment field, instead of uploading a log file.
            • Change the status of the test to Verified by vendor

            EVS_CDA_Validation

            You will use the Gazelle EVSClient to evaluate CDA documents defined in IHE profiles in several domains.

            The documents you validate will depend upon the profile/actor pairs supported by your test system, and the availability of schematron or model-based validation available in the EVSclient

            Instructions

              1. Access the Gazelle EVSClient application: http://gazelle.ihe.net/EVSClient
              2. From the EVS Client user interface, select menu IHE-->CDA-->Validate
              3. Upload the XML file for the document produced by your application
              4. Select a validator (the list is found below)
              5. Click on Validate

              Evaluation

                1. The EVS Client creates a Permanent link to your results.
                2. For this pre-Connectathon test in gazelle, paste the Permanent links to your results into the comment field, instead of uploading a log file.
                3. Change the status of the test to Verified by vendor

                These validators available in the Schematron dropdown list:
                      • C-CDA 2.1 All Document Types, templateId@extensions=2015-08-01
                      • IHE - CARD - Registry Content Submission (RCS-C)
                      • IHE - CARD - Registry Content Submission - Electrophysiology (RCS-EP)
                      • IHE - EYE - GEE Progress Note (2015 version)
                      • IHE - EYE - Summary Record (EC-Summary)
                      • IHE - ITI - Basic Patient Privacy Consent (BPPC)
                      • IHE - ITI - Cross-Enterprise Sharing of Scanned Docs (XDS-SD)
                      • IHE - LAB - Sharing Laboratory Reports (XD-LAB)
                      • IHE - PCC - Antepartum Education (APE)
                      • IHE - PCC - Antepartum History & Physical (APHP)
                      • IHE - PCC - Antepartum Summary (APS)
                      • IHE - PCC - Composite Triage & Nursing Note (CTNN)
                      • IHE - PCC - Emergency Dept Referral (EDR)
                      • IHE - PCC - eNursing Summary (ENS)
                      • IHE - PCC - Immunization Content (IC)
                      • IHE - PCC - Labor & Delivery History & Physical (LDHP)
                      • IHE - PCC - Labor & Delivery Summary (LDS)
                      • IHE - PCC - Maternal Discharge Summary (MDS)
                      • IHE - PCC - Newborn  Discharge Summary (NDS)
                      • IHE - PCC - Nursing Note (NN)
                      • IHE - PCC - Patient Plan of Care (PPOC)
                      • IHE - PCC - PHMR
                      • IHE - PCC - Physician Note (PN)
                      • IHE - PCC - Post partum Visit Summary (PPVS)
                      • IHE - PCC - Triage Note (TN)
                      • IHE - PCC - XDS-MS Dischange Summary
                      • IHE - PCC - XDS-MS Referral Note
                      • IHE - PCC - XPHR Extract
                      • IHE - PCC - XPHR Update
                      • IHE - PHARM - Pharmacy Dispense (DIS)
                      • IHE - PHARM - Pharmacy Pharmaceutical Advice (PADV)
                      • IHE - PHARM - Pharmacy Prescription (PRE)
                      • IHE - QPRH - Clincial Research Document (CRD)
                      • IHE - QRPH - Physican Reporting to Public Health-Cancer Registry (PRPH-Ca)
                    These validators are available in the Model Based Validator dropdown list:
                          • HL7 - CDA Release 2
                          • HL7 - CDA Release 2 (strict)
                          • IHE - CARD - Cath Report Content (CRC)
                          • IHE - CARD - Registry Content Submission (RCS-C)
                          • IHE - CARD - Registry Content Submission - Electrophysiology (RCS-EP)
                          • IHE - EYE - GEE Progress Notes (2015 version)
                          • IHE - EYE - Summary Record (EC Summary)_
                          • IHE - ITI - Basic Patient Privacy Consent (BPPC)
                          • IHE - ITI - Cross-Enterprise Sharing of Scanned Docs (XDS-SD)
                          • IHE - LAB - Sharing Laboratory Reports (XD-LAB)
                          • IHE - PATH - Anatomic Pathology Structured Report (APSR)
                          • IHE - PCC - Common templates
                          • IHE - PHARM - Pharmacy Dispense (DIS)
                          • IHE - PHARM - Pharmacy Pharmaceutical Advice (PADV)
                          • IHE - PHARM - Pharmacy Prescription (PRE)
                          • IHE - RAD - CDA document wrapper (XDS-I.b)

                        EVS_DICOM_Object_Evaluation

                        We use DICOM validator tools hosted in the Gazelle External Validation Service (EVS Client) to evaluate your DICOM objects.

                        In this test, Acquisition Modality & Evidence Creator systems evaluate samples of Composite Objects that you create using the DICOM evaluation tools available in the Gazelle External Validation Service (EVS).   This test also applies to actors such as Importers that modify objects originally created by other actors.

                        The number of evaluations you run depends on the types of images or SRs that you produce. We will not list specific requirements, but ask you to apply good judgment. For example, a CT scanner that produces Localizer and Axial images would evaluate samples from both of those image types. A CR device may evaluate an AP chest, a lateral chest and an image of a limb.

                        You must evaluate and provide the output for at least one DICOM Composite Object using '''one'' of the available validation tools (your choice).  One or more of these tools may be available from within the Gazelle EVSClient.  (Note:  The links below are for resource pages for each tool.)

                        Evaluating your objects using the different tools available as well as evaluating different objects can only help your implementation.

                        There are two ways to access the validators: (1) in the Samples of Gazelle Test Management, or (2) directly in the EVSClient tool.  Either method may be used.

                        (1) Instructions for accessing the DICOM validators from the Samples area of Gazelle Test Management:

                        1. Access Gazelle Test Management (eg Gazelle NA or Gazelle EU) and log in.
                        2. Select menu Connectathon-->Connectathon-->List of samples
                        3. Select your test system from the dropdown list
                        4. On the 'Samples to share' tab, find the entry for 'DICOM_OBJECTS
                        5. Select the '+' and proceed to upload a DICOM file(s)
                        6. Once the file is uploaded, you will be able to use the green triangle icon to call the DICOM validator in EVSClient.

                         

                        (2) Instructions for accessing the DICOM validators in the Gazelle EVS Client Tool:

                        1. Access the Gazelle EVS Client: http://gazelle.ihe.net/EVSClient
                        2. Select menu IHE-->DICOM-->DICOM validation
                        3. Upload the file you want to validate.
                        4. Then, select one of the DICOM validator tools from the dropdown list.  To get the best coverage, we encourage you to try multiple validators, as applicable.
                        5. Click Execute.
                        6. You will see your results. (to find them later, Select menu IHE-->DICOM-->Validated DICOM objects)
                        7. The tool identifies errors in your content.  Examine your results.
                          -->You are finished with this test when you have either satisfied all of the errors detected by the tool. If you disagree with the results of the tool, you can write a short (1 or 2 line) description that describes why your object is correct and the DICOM tool software is in error.
                        8. Find the Permanent link to the results

                        Finally, capture your results:

                        1. For this pre-Connectathon test, instead of uploading a log file, you will paste the Permanent link to your results.  Copy either  the permanent link to your sample or the permanent link to your results in the EVSClient and paste it into the comment field of the EVS_DICOM_Object_Validation test instance in Gazelle Test Management. (This is also where you can comment on the results of the validation.)  
                        2. Change the status of the test to Verified by vendor

                        EVS_DSG_Validation

                        This test applies to the Content Creator actor in the Document Digital Signature (DSG) profile.

                        This test ensures that the file produced by the Content Creator actor is conformant to the specification.

                        Reference:  ITI TF-3: 5.5.

                        Instructions

                          1. Instructions are in the EVS Client User Manual here: https://gazelle.ihe.net/gazelle-documentation/EVS-Client/user.html#validation-of-digital-signatures

                          Evaluation

                            1. The tool reports the results of the evaluation
                            2. The EVS Client creates a Permanent link to your results.
                            3. If you are performing a pre-Connectathon test in gazelle, paste the Permanent link to your results into the comment field, instead of uploading a log file.
                            4. Change the status of the test to Verified by vendor

                            EVS_DSUB_Message_Validation

                            You will use the Gazelle EVSClient to validate messages in the DSUB profile..

                            The messages you validate will depend upon the profile/actor pairs supported by your test system

                            Instructions

                            • Access the Gazelle EVSClient application: http://gazelle.ihe.net/EVSClient
                            • From the EVS Client user interface, select menu IHE-->DSUB-->Validate
                            • Upload the XML file for the message produced by your application
                            • Select the correct Model Based Validator from the dropdown list:
                              • ITI-52 Document Metadata Subscribe Request
                              • ITI-52 Document Metadata Subscribe Response
                              • ITI-52 Document Metadata Unsubscribe Request
                              • ITI-52 Document Metadata Unsubscribe Response
                              • ITI-53 Document Metadata Notify Request
                              • ITI-53 Document Metadata Publish Request
                            • Click on Validate.

                            Evaluation

                            • The EVS Client creates a Permanent link to your results.
                            • For this pre-Connectathon test in gazelle, paste the Permanent links to your results into the comment field, instead of uploading a log file.
                            • Change the status of the test to Verified by vendor

                            EVS_FHIR_Resource_Validation

                            Test Summary

                            You will use the Gazelle EVSClient to validate FHIR®© Resources either created by your application or returned by your application in response to a query.

                            Important notes: This test appears on the pre-Connectathon test list for actors in all FHIR-based profiles, but... 

                            • If your actor only consumes FHIR Resources (ie it only receives them from other actors), then you can skip this test.  **However** you may be interested in testing with Resources submitted by others and collected in the tool.  In the EVSClient, select menu FHIR ®©-->Validation logs and use the filters on the page to find Resources of interest to you.
                            • If your application initiates a transaction containing one or more FHIR Resources in XML or JSON format, you should perform this test to use the EVSClient tool ensure the Resource(s) you create pass a schematron test.
                            • If your application responds to a query and returns FHIR Resource(s) in XML or JSON format, you should perform this test.
                            • How do I know which Resources to test?  IHE transactions that transmit FHIR-based Resources identify the actor(s) and the applicable Resources.  We will not restate the requirements for each actor here, but here are three examples:
                                • An PDQm Patient Demographics Supplier responds to an [ITI-78] query by sending a Bundle of one or more Patient Resources
                                • An MHD Document Source sends [ITI-65].  That transaction contains a DocumentManifest Resource, 1 or more DocumentReference Resource, zero or more List Resources, and zero or more Binary Resources.
                                • A mACM Alert Reporter sends an [ITI-84] alert request that contains a CommunicationRequest Resource.  The Alert Aggregator's  [ITI-84] response contains a CommunicationRequest Resource and Communication Resource(s).
                            • What kind of validation is performed?  The FHIR Resource validators in the EVSClient test the 'base requirements' for the Resources defined in HL7 FHIR.  Some IHE Profiles define extensions or additional constraints on Resources that are not tested here.

                            Instructions

                            • Identify the FHIR Resources applicable to the IHE transactions supported by your application
                            • Access the Gazelle EVSClient application: http://gazelle.ihe.net/EVSClient
                            • From the EVS Client user interface, select menu FHIR ®©-->Validate
                            • Upload the XML file for the Resource produced by your application
                            • Select the correct Schematron from the dropdown list:
                            • Click on Validate.
                            • Repeat as needed for other Resources.

                            Evaluation

                            • The EVSClient creates a Permanent link to your results under FHIR®© -->Validation Logs
                            • For this pre-Connectathon test in gazelle, paste the Permanent link(s) to your results into the comment field, instead of uploading a log file.  
                            • Change the status of the test to Verified by vendor

                            EVS_HL7v2.x_Message_Validation

                            You will use the Gazelle EVSClient to validate HL7v2.x based messages.  

                            These messages are applicable across many IHE profiles in several domains.  The messages you validate will depend upon the profile/actor pairs supported by your test system.

                            Instructions

                            • Access the Gazelle EVSClient application: https://gazelle.ihe.net/EVSClient
                            • From the EVS Client user interface, select menu IHE-->HL7v2.x-->Validate
                            • Upload the file (in ER7 format) for the HL7 message produced by your application
                            • From the Transaction column, select the applicable transaction (eg RAD-1)
                            • From the HL7 version column, select 2.3.1, 2.5, or 2.5.1
                            • Some transactions require actors to support for multiple messages (eg, new order, cancel order...). If multiple messages are listed, test them all.
                            • The following validations are available:
                              • CARD-7 Encapsulated Report Submission
                              • CARD-8 Report Reference SubmissionITI-8 v2.3.1 Patient Identity Feed
                              • ITI-8 v2.3.1 Patient Identity Feed
                              • ITI-9 v2.3.1 PIX Query
                              • ITI-10 v2.3.1 PIX Update Notification
                              • ITI-21 v2.5 Patient Demographics Query
                              • ITI-22 v2.5 Patient Demographics and Visit Query
                              • ITI-30 v2.5 Patient Identity Management
                              • ITI-31 v2.5 Patient Encounter Management
                              • ITI-64 v2.5 Notify XAD-PID Link Change
                              • LAB-1 Lab Placer Order Management
                              • LAB-2 Lab Filler Order Management
                              • LAB-3 Order Results Management
                              • LAB-4 Work Order Management
                              • LAB-5 Test Result Management
                              • LAB-21 WOS Download
                              • LAB-22 WOS Query
                              • LAB-23 AWOS Status Change
                              • LAB-26 SWOS Status Change
                              • LAB-27 Query for AWPS
                              • LAB-28 AWOS Broadcast
                              • LAB-29 AWOS Status Change
                              • LAB-32 POCT observation accepted
                              • LAB-35 Sub-order Management
                              • LAB-36 Sub-order Results Delivery
                              • LAB-51 Laboratory Code Set Management
                              • LAB-61 Label delivery request
                              • LAB-62 Query for lable delivery instructions
                              • LAB-63 Labels and Containers Delivered
                              • PHARM-H1 Prescription Order
                              • PHARM-H2 Validated Order
                              • PHARM-H3 Medication Preparation Report
                              • PHARM-H4 Administration Report
                              • PHARM-H5 Advance Prescription Notification
                              • PHARM-H6 Validated Order Confirmation
                              • RAD-1 v2.3.1 Patient Registration
                              • RAD-2 v2.3.1 and v2.5.1 Placer Order Management
                              • RAD-3 v2.3.1 and v2.5.1 Filler Order Management
                              • RAD-4 v2.3.1 and v2.5.1 Procedure Scheduled
                              • RAD-12 v2.3.1 Patient Update
                              • RAD-13 v2.3.1 and v2.5.1 Procedure Update
                              • RAD-28 v2.5 Structured Report Export
                              • RAD-35 v2.3.1 Charge Posted
                              • RAD-36 v2.3.1 Account Management
                              • RAD-48 v2.3.1 and v2.4 Appointment Notification
                            • Click on Validate.

                            Evaluation

                            • The EVS Client creates a Permanent link to your results.
                            • For this pre-Connectathon test in gazelle, paste the Permanent link(s) to your results into the comment field, instead of uploading a log file.
                            • Change the status of the test to Verified by vendor

                            EVS_HL7v3_Message_Validation

                            You will use the Gazelle EVSClient to validate HL7v3-based messages.  

                            These messages are applicable across many IHE profiles.  The messages you validate will depend upon the profile/actor pairs supported by your test system.

                            Instructions

                            • Access the Gazelle EVSClient application: http://gazelle.ihe.net/EVSClient
                            • From the EVS Client user interface, select menu IHE-->HL7v3-->Validate
                            • Upload the XML file for the HL7 message produced by your application
                            • You have a choice of a schematron or Model Based Validation for many messages.  We encourage you to perform both, if available.
                            • Some transactions require actors to support multiple messages. If multiple messages are listed, test them all.
                            • The following schematron validations are available:
                              • ITI-44  Patient Identity Feed (Register/Admit, Update, and Merge)
                              • ITI-45 PIXv2 Query Request
                              • ITI-45 PIXv3 Query Response
                              • ITI-47 PDQ v3Patient Demographics Query Response
                              • ITI-55 XCPD Cross-Gateway Patient Discovery Request
                              • ITI-55 XCPD Cross-Gateway Patient Discovery Response
                            • The following Model Based Validations are available:
                              • ITI-44 Patient Identity Feed (Add, Revise, and Merge record) 
                              • ITI-44 Patient Identity Feed Acknowledgement
                              • ITI-45 PIXv3 Query Request
                              • ITI-45 PIXv3 Query Response
                              • ITI-46 PIXv3 Update Notification
                              • ITI-46 PIXv3 Update Notification Acknowledgement
                              • ITI-47 PDQv3 Patient Demographics Query (incl continuation, cancellation)
                              • ITI-47 PDQv3 Patient Demographics Query Response
                              • PDQv3 Accept Acknowledgement
                              • ITI-55 XCPD Cross-Gateway Patient Discovery Query Request & deferred option 
                              • ITI-55 XCPD Cross-Gateway Patient Discovery Query Repoonse
                              • ITI-56 XCPD Patient Location Query Request
                              • ITI-56 XCPD Patient Location Query Response
                              • XCPD Accept Acknowlegement
                            • Click on Validate.

                            Evaluation

                            • The EVS Client creates a Permanent link to your results.
                            • For this pre-Connectathon test in gazelle, paste the Permanent link(s) to your results into the comment field, instead of uploading a log file.
                            • Change the status of the test to Verified by vendor

                            EVS_HPD_Message_Validation

                            You will use the Gazelle EVSClient to validate messages in the HPD profile..

                            The messages you validate will depend upon the profile/actor pairs supported by your test system

                            Instructions

                            • Access the Gazelle EVSClient application: http://gazelle.ihe.net/EVSClient
                            • From the EVS Client user interface, select menu IHE-->HPD-->Validate
                            • Upload the XML file for the message produced by your application
                            • Select the correct Model Based Validator from the dropdown list:
                              • ITI-58 Provider Information Query Request
                              • ITI-58 Provider Information Query Response
                              • ITI-59 Provider Information Feed Request
                              • ITI-59 Provider Information Feed Response
                              • DSMLv2 Batch Request
                              • DSMLv2 Batch Response
                            • Click on Validate.

                            Evaluation

                            • The EVS Client creates a Permanent link to your results.
                            • For this pre-Connectathon test in gazelle, paste the Permanent links to your results into the comment field, instead of uploading a log file.
                            • Change the status of the test to Verified by vendor

                            EVS_SOLE_Event_Report_Check

                            Overview of the test

                            This test has two parts:

                            (1) First, the Event Reporter identifies the SOLE events that it supports.  This helps your Connectathon test partners and the Connectathon monitors understand the capabilities of your system.

                            (2)  Then, you will use the Gazelle EVSClient tool to test the content of the event record(s) you create against the DICOM schema & SOLE Event Requirements. This tool does not test the transport of the event record.

                            (1) Identify your SOLE Event Reports

                            • We use a google doc to collect this information from all SOLE Event Reporters.  Click HERE to open it.
                            • The rows in the table list the Baseline SOLE events from the SOLE Profile, Vol 3, Table 6.3.2-1.
                            • The columns hold information for each Connectathon test system.  Column C is an example
                            • In the next available column, add your company and test system name, then mark the Events you support with an 'X'.

                            (2) Test your SOLE Event Reports

                            First access the Gazelle EVSClient tool: https://gazelle.ihe.net/EVSClient/home.seam

                            • Log in to the tool:  There are separate CAS systems for European and North American Connectathons.  The European CAS is linked to http://gazelle.ihe.net/EU-CAT/ and the North American CAS is linked to http://ihe.wustl.edu/gazelle-na/.   You will use your username & password from Gazelle for either the European or NA Connectathon:
                            • On the tool home page, find the "Login" link at the upper right of the page.  
                            • Select either "European Authentication" or "North American Authentication"
                            • Enter the username and password from either the European or North American instances of gazelle linked above

                            Perform the validation:

                            1. In the Gazelle EVSClient, select menu IHE-->Audit messages-->Validate
                            2. Select the Add button, and upload the XML file for your event report
                            3. From the Model based validation dropdown list, select the entry that matches the event, eg "IHE - RAD - SOLE101 - Order Filled"
                            4. Select the Validate button.  
                            5. You should validate at least 3 event records; of course, we encourage you to do more.
                            6. In the Validation Results displayed, find the Permanent Link to the results.  Copy/paste the link(s) into the chat window in Gazelle Test Management for pre-Connectathon test 'EVS_SOLE_Event_Report_Check', and change the status of the test to "Verified by vendor".

                            Evaluation

                            The tool reports the results of the validation of your messages.  We are looking for PASSED validation results.

                            EVS_SVS_Message_Validation

                            You will use the Gazelle EVSClient to validate messages in the SVS profile.

                            The messages you validate will depend upon the profile/actor pairs supported by your test system

                            Instructions

                            • Access the Gazelle EVSClient application: http://gazelle.ihe.net/EVSClient
                            • From the EVS Client user interface, select menu IHE-->SVS-->Validate
                            • Upload the XML file for the message produced by your application
                            • Select the correct Model Based Validator from the dropdown list:
                              • ITI-48 Retrieve Value Set Request
                              • ITI-48 Retrieve Value Set Response
                              • ITI-60 Retrieve Multiple Value Sets Request
                              • ITI-60 Retrieve Multiple Value Sets Response
                            • Click on Validate.

                            Evaluation

                            • The EVS Client creates a Permanent link to your results.
                            • For this pre-Connectathon test in gazelle, paste the Permanent links to your results into the comment field, instead of uploading a log file.
                            • Change the status of the test to Verified by vendor

                            EVS_WADO-RAD-55

                            This tests the request in the RAD-55 transaction in the XDS-I.b profile

                            In XDS-I, the Imaging Document Consumer is required to support one or more of RAD-55, RAD-68 or RAD-16 (or other C-MOVE).

                            • If your Imaging Document Consumer does not support RAD-55, you should skip this test.

                            The aim of this test is to verify that the Imaging Document Consumer is able to create a valid WADO request (the list of parameters is well specified, there are no inconsistency between them, etc). To do so, we use a WADO validator of the request from EVSClient tool.

                            In this test we do not verify that the request was well treated, or not, by the server side.

                            Instructions

                            • From the EVS Client user interface, select menu IHE-->DICOMWeb-->Validate
                            • Paste/upload your request, select the correct validator, and Validate.(Yes you can use any WADO back-end and any data set, to create your request ), please refer to this documentation of EVSClient WADO validation.

                            Evaluation

                            • The EVS Client creates a Permanent link to your results
                            • For this pre-Connectathon test in gazelle, paste the Permanent links to your results into the comment field, instead of uploading a log file.
                            • Change the status of the test to Verified by vendor

                            EVS_XD*_XC*_Message_Validation

                            You will use the Gazelle EVSClient to validate messages for the Cross-Enterprise (XD*) and Cross-Community (XC*) family of profiles.

                            The messages you validate will depend upon the profile/actor pairs supported by your test system

                            Instructions

                            • Access the gazelle EVSClient application: http://gazelle.ihe.net/EVSClient
                            • From the EVS Client user interface, select menu IHE-->XD* Metadata-->Validate
                            • Upload the XML file for the message produced by your application
                            • Select the correct Model Based Validator from the dropdown list:
                              • ITI-18 Registry Stored Query Request
                              • ITI-18 Registry Stored Query Response
                              • ITI-32 Distribute Document Set on Media (metadata)
                              • ITI-38 Cross-Gateway Query Request
                              • ITI-38 Cross-Gateway Query Response
                              • ITI-39 Cross-Gateway Retrieve Request
                              • ITI-39 Cross-Gateway Retrieve Response
                              • ITI-41 Provide & Register Document Set Request
                              • ITI-41 XDR Provide & Register Document Set Limited Metadata Request
                              • ITI-41 Provide & Register Document Set Response
                              • ITI-42 Register Document Set Request
                              • ITI-42 Register Document Set Response
                              • ITI-43 Retrieve Document Set Request
                              • ITI-43 Retrieve Document Set Response
                              • ITI-51 Multi-Patient Query Request
                              • ITI-51 Multi-Patient Query Response
                              • ITI-61 Register On-Demand Document Entry Request
                              • ITI-61 Register On-Demand Document Entry Response
                              • ITI-62 Delete Document Set Request
                              • ITI-62 Delete Document Set Response
                              • ITI-63 Cross-Gateway Fetch Request
                              • ITI-63 Cross-Gateway Fetch Response
                              • ITI-79 Authorization Decisions Query Request
                              • ITI-79 Authorization Decisions Query Response
                              • PHARM-1 request
                              • PHARM-1 response
                              • RAD-68 Provide & Register Imaging Doc Set-MTOM/XOP Request
                              • RAD-68 Provide & Register Imaging Doc Set-MTOM/XOP Response
                              • RAD-69 Retrieve Imaging Document Set Request
                                • If your Imaging Doc Consumer does not support RAD-69, then skip this.
                              • RAD-69 Retrieve Imaging Document Set Response
                              • RAD-75 Cross-Gateway Retrieve Imaging Document Set Request
                              • RAD-75 Cross-Gateway Retrieve Imaging Document Set Response
                            • Click on Validate.

                            Evaluation

                            • The EVS Client creates a Permanent link to your results.
                            • For this pre-Connectathon test in gazelle, paste the Permanent links to your results into the comment field, instead of uploading a log file.
                            • Change the status of the test to Verified by vendor

                            EVS_XDW

                            Content Creator creates a Workflow dDocument and validates it

                            Content Creator will create a workflow document produced by your application.  This could be as defined in the base XDW profile, or on the specialized workflow documents such as XTHM, XBeR, and others.

                            Then you will use gazelle's XDW Validator to verify your Workflow Document.

                            Finally, you will upload your sample document into gazelle so that Content Consumers can access your sample and test with it prior to the Connectathon.  We ask you to upload your sample two weeks in advance of the pre-Connectathon test deadline to give Consumers time to test with your document.

                            Instructions

                            For this pre-Connectathon test, you will create a Workflow Document for a task that is relevant to your product/application; the contents of the task you complete should be in the context of the clinical functions your product performs.

                            For this test, you do not have to submit your workflow document to an XDS Repository/Registry.

                            (1) Once you have created/updated the workflow document, upload your sample into gazelle & run the validation:

                            • Log into gazelle.
                            • Select menu:  Connectathon / List of Samples
                            • Select the Samples to share tab for your test system
                            • For the XDW entry (or XTHM, or XBeR... entry) select the 'Add sample' (+) icon.
                            • Upload the XML for your XDW document.  Name the XML file using this convention: <your-system-name>-<profile>.xml, eg EHR_XYXMedicalCo-XTHM.xml
                            • Select the "Validate" icon.

                            Alternative:  Access XDW Validator via the Gazelle External Validation Service (EVS):

                            • Access the External Validation Service: http://gazelle.ihe.net/EVSClient
                            • Select menu:  IHE / XDW / Validate
                            • Upload the XML for your XDW document.
                            • Select the appropriate Validator from the 'Model Based Validation' drop-down list.
                            • Select the Validate button
                            • Next, find your results.  Select menu:  IHE / XDW / Validated XDW documents
                            • Use the interface to find your validated document.  This will show your results.

                            Evaluation

                            • The validation service creates a Permanent link to your results
                            • For this pre-Connectathon test in gazelle, paste the Permanent links to your results into the comment field, instead of uploading a log file.
                            • Change the status of the test to Verified by vendor

                            Your test partners that are Content Consumers will also be able to access your sample in gazelle.

                            EVS_XDW-update

                            Content Updater updates a Workflow Document

                            In this test you will access a sample workflow made by a Content Creator; then you will update that document using your application, and use the XDW Validator provided in gazelle to validate your updated document.  

                            Finally, you will upload your 'updated' Workflow Document into gazelle as a sample.   We ask you to upload your sample two weeks in advance of the pre-Connectathon test deadline to give Consumers time to test with your document.

                            Instructions

                            For this pre-Connectathon test, you will update a workflow document 

                            (1) For the base XDW profile, access this sample workflow document: XDW-Document-for-Updater.xml

                            --  If you are testing XBeR, XTHM, we do not have a generic sample for you to start from.  You may use a sample submitted by a 'Creator' vendor in your profile.

                            (2) Download the Workflow Document into your local environment, then update the document and add a task that is relevant to your product/application.

                            • Your new task should contain an input document, and output document, or both

                            For this test, you do not have to submit your workflow document to an XDS Repository/Registry

                            (3) Once you have created the updated workflow document, upload your sample into gazelle & run the validation:

                            • Log into gazelle.
                            • Select menu:  Connectathon / List of Samples
                            • Select the Samples to share tab for your test system
                            • For the XDW entry, select the 'Add sample' (+) icon.
                            • Upload the XML for your XDW document.  Name the XML file using this convention:
                              • SYSTEMNAME_XDW.xml, where "SYSTEMNAME" is your test system's name in gazelle, eg: EHR_XYZmed_XDW.xml
                            • Select use "Pre-Connectathon" from the dropdown list on the summary of the sample.
                            • Select the "Validate" button.

                            Alternative:  Access XDW Validator via the Gazelle External Validation Service (EVS):

                            • Access the External Validation Service: http://gazelle.ihe.net/EVSClient
                            • Select menu:  IHE / XDW / Validate
                            • Upload the XML for your XDW document.
                            • Select the Validate button
                            • Next, find your results.  Select menu:  IHE / XDW / Validated XDW documents
                            • Use the interface to find your validated document.  This will show your results.

                            Evaluation

                            • The validation service creates a Permanent link to your results
                            • For this pre-Connectathon test in gazelle, paste the Permanent links to your results into the comment field, instead of uploading a log file.
                            • Change the status of the test to Verified by vendor

                            Your test partners that are Content Consumers will also be able to access your sample in gazelle.

                            AttachmentSize
                            File XDW-Document-for-Updater.xml3.9 KB