Special Instructions
The 00_FHIR-based_Profile_Testing_Overview no-peer 'test'
identifies the server used to perform validation on HL7® FHIR®
Resource(s) during the Connectathon. That server contains validators
for the base FHIR requirements for the Resources tested here.
Description
This is a no-peer test to verify FHIR Resource(s) created/used by one these actors in the context of other peer-to-peer tests.
- ATNA Secure Node or Secure Application that supports the ATX: FHIR Feed Option sending AuditEvent Resources to an Audit Record Repository in [ITI-20].
- ATNA Audit Record Repository or SOLE Event Repository (AuditEvent Resources sent in response to an [ITI-81] query from an Audit Consumer).
IHE-specific constraints for this profile, if any, are identified in the Evaluation section below.
This test is performed in parallel with other peer-to-peer tests
performed for this profile. The purpose is to demonstrate that your
actor creates/exchanges valid FHIR Resource(s) in the context of the
transactions you support. We create this separate 'Resource_Check' test
so that this validation is performed once, and not repeatedly for
multiple peer-to-peer tests you run with your test partners.
You will validate one instance of each Resource listed in Column 1.
The Resource is taken from an instance of a peer-to-peer test listed in
Column 2.
| FHIR Resource(s) evaluated in this test (JSON or XML format): | Resource(s) taken from one of these peer-to-peer tests: |
AuditEvent
| ATNA_Logging_FHIR-Feed (Secure Node/Application with ATX: FHIR Feed)
ITI-81_Query_JSON-or-XML (for the Audit Record Repository or Event Repository actor)
|
Evaluation
Monitors:
Resource(s) to be validated in this test are attached to Test Step 100 (and perhaps additional Resources in Step 200, 300...).
For each Resource attached:
- TEST STEP 100: Verify that the Resource was taken from a
test performed during the Connectathon week (we do not want to validate
Resources created before the event).
- TEST STEP 110 & 130:
Verify that the resources were validated with the EVSClient EPR AuditEvent validator.
Repeat (1) - (2) for additional Resources, if any.
Profile-specific constraints on the AuditEvent Resource? None.
Mark this test "Verified" if all were successful.