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.

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.

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: https://gazelle.ihe.net/evs
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. Finally, paste the Permanent Link into Gazelle Test Management as the results for this test.

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:  ITI TF-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: https://gazelle.ihe.net/evs
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. Finally, paste the Permanent Link into Gazelle Test Management as the results for this test.

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. Paste the Permanent Link into Gazelle Test Management as the results for this test.

This test has been deprecated as of the 2022 IHE Connectathon

• Test Summary
• Scope of testing available in Gazelle EVSClient
• Who this test applies to
• Instructions
• Evaluation

Test Summary

You will use the Gazelle EVSClient tool to validate:

• FHIR®© Resources created by your application and/or returned by your application in response to a query
• IHE transactions based on FHIR:  outbound messages and responses with constraints defined in IHE transaction definitions.

Scope of testing available in Gazelle EVSClient

1. Validation of Resources using the baseline requirements defined in FHIR.   This is available in EVSClient under menu FHIR®©-->Validate.
2. Validation of Resources and transactions based on constraints defined in IHE profiles.  This is available in EVSClient under menu IHE-->FHIR®©-->Validate.  The contraints tested by EVSClient are defined in FHIR conformance resources published by IHE (e.g., StructureDefinition and ValueSet resources)
   

• For IHE profiles published in FHIR Implementation Guide (IG) format (e.g. MHD, mCSD, and more), conformance resources are found on the "Artifacts" page of the IG.
  
• For IHE profiles published in PDF format, conformance resources are found on https://github.com/IHE/fhir

Who this test applies to

This test appears in Gazelle Test Management as a preparatory test for actors in all FHIR-based IHE profiles, so... 

• If your actor 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) and transactions you create pass validation.
• If your actor responds to a query and returns FHIR Resource(s) in XML or JSON format, you should perform this test.
• If your actor, produces/sends FHIR Resources, how do you know which resources and transactions to test?  IHE profiles that exchange FHIR-based Resources identify the actor(s) and the applicable transactions and resources.  We will not restate the requirements for each actor here, but here are some examples:
• A PDQm Patient Demographics Supplier responds to an [ITI-78] query by sending a Bundle of one or more Patient Resources.  The Patient Resource is not constrained in the PDQm profile.
• An MHD Document Source sends [ITI-65].  Depending on the type of submission, ITI-65 sends a Transaction Bundle with a combination of List, DocumentReference, Binary and Patient Resources, with constraints defined in MHD.
• 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).
• An ATNA Secure Node/Application that supports the ATX: FHIR Feed option for [ITI-20] sends AuditEvent Resources to an Audit Record Repository; some IHE transactions have constraints on the AuditEvent Resource.
• You should validate Resources that your system has created.  For some actors (e.g. PDQm Supplier, mCSD Supplier), Connectathon technical managers provide pre-defined test data used in Connectathon tests.   You should not validate these resources; instead, we assume that your application is also able to create Patient, Practioner, Organzation, etc Resources.  These are the ones you should test.
• If your actor only consumes FHIR Resources (i.e., 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 IHE-->FHIR®©-->Validation logs and use the filters on the page to find Resources of interest to you.)

Instructions

• Identify the FHIR Resources and FHIR-based transactions supported by your application,
• Access the Gazelle EVSClient application: https://gazelle.ihe.net/evs
• From the EVSClient user interface, select menu IHE-->FHIR®©-->Validate (to test IHE constraints) or FHIR®©-->Validate (to test baseline requirements for FHIR Resources)
• Upload the XML or JSON file produced by your application
• Select the correct Model Based Validation from the dropdown list.
• Click on Validate.
• Repeat as needed for other resources or transactions.

Evaluation

• The EVSClient creates a Permanent link to your results under IHE-->FHIR®©-->Validation Log or FHIR®©-->Validation Log
• Paste the Permanent Link into Gazelle Test Management as the results for this test.
• Many systems will have more than one result to report.

Overview

You will use the Gazelle External Validation Service (EVS) 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 EVS application:  https://gazelle.ihe.net/evs
• From the EVS user interface, select menu IHE-->HL7v2.x messages-->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.  Note that the tool is updated over time, so there may be additional validators available in the tool itself.
• 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 creates a Permanent link to your results.
• Paste the Permanent Link into Gazelle Test Management as the results for this test.

Overview

You will use the Gazelle External Validation Services (EVS) 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 EVS application: https://gazelle.ihe.net/evs
• 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 creates a Permanent link to your results. Copy/Paste the Permanent Link into Gazelle Test Management as the results for this test.

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 the XDW Validator in Gazelle EVS Client to verify your Workflow Document.

Finally, you will upload your sample document into Gazelle Test Management so that Content Consumers can access your sample and test with it prior to the Connectathon. 

Instructions

For this 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 it into the Samples area of Gazelle Test Management:

• 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: https://gazelle.ihe.net/evs
• 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
• Paste the Permanent Link into Gazelle Test Management as the results for this test.

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

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 EVS Client to validate your updated document.  

Finally, you will upload your 'updated' Workflow Document into the Samples area of Gazelle Test Management.  

Instructions

For this 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 document into the Samples area of Gazelle Test Management:

• 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: https://gazelle.ihe.net/evs
• 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 EVS Client creates a Permanent link to your results.
• Paste the Permanent Link into Gazelle Test Management as the results for this test.

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