EVS_FHIR_IG-based_Validation
The Gazelle External Validation Service (EVS) performs validation using FHIR StructureDefinitions contained in IHE profiles published in FHIR Implementation Guide (IG) format (e.g. the ITI Mobile Access to Health Documents (MHD) IG, and many others). The StructureDefinitions used by EVS are found on the "Artifacts" page of the IG.
In this test, you will use the Gazelle EVS 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.
The validators are available in EVS under menu IHE-->FHIR IG-based -->Validate.
This test appears in Gazelle Test Management as a Preparatory test, so...
- If your actor icreates FHIR resources and/or initiates a transaction containing one or more FHIR Resources in XML or JSON format, you should perform this test to use the EVS 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 audits a transaction using an ATNA ATX FHIR Feed (AuditEvent), you should validate your audit messages.
- 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 IPS Content Creator creates a FHIR bundle with IPS content.
- 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.
- 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, Practitioner, Organzation, etc Resources. These are the ones you should test.
- Identify the FHIR Resources and FHIR-based transactions supported by your application.
- Access the Gazelle EVS: https://gazelle.ihe.net/evs
- From the EVS user interface, select menu IHE-->FHIR IG-based-->Validate
- Upload the XML or JSON file produced by your application
- Select the correct Validator from the dropdown list.
- Click on Validate.
- Repeat as needed for other resources or transactions.
- The EVS creates a Permanent link to your results under IHE-->FHIR IG-based-->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.