EVS_FHIR_Validation

This test has been deprecated as of the 2022 IHE Connectathon

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.