US Core Testing Guide - Local Development build (v4.0.0-1). See the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
The following artifacts define the types of individuals and/or systems that will interact as part of the use cases covered by this implementation guide.
US Core Requestor |
US Core Requestor Actor |
US Core Responder |
US Core Responder Actor |
The following artifacts describe the specific requirements to be met by systems compliant with the implementation guide.
US Core 4.0.0 Requirements for US Core General Security Considerations |
Patient Privacy and Security<br/><br/>US Core transactions often use patient-specific information, which could be exploited by malicious actors resulting in the exposure of patient data. For this reason, all US Core transactions must be secured appropriately with access to limited authorized individuals, data protected in transit, and appropriate audit measures taken.<br/><br/>Implementers SHOULD be aware of these security considerations associated with FHIR transactions, particularly those related to:<br/><br/>* Communications<br/>* Authentication<br/>* Authorization/Access Control<br/>* Audit Logging<br/>* Digital Signatures<br/>* Security Labels<br/>* Narrative<br/><br/>Clinical Safety<br/><br/>When implementing FHIR and US Core, implementers need to be aware of the risks and tradeoffs and are encouraged to review the clinical safety section in the core specification. |
US Core 4.0.0 Requirements for US Core Responder CapabilityStatement |
US Core 4.0.0 Requirements for US Core Responder returning CapabilityStatement |
US Core 4.0.0 Requirements for US Core Responder returning AllergyIntolerance |
US Core 4.0.0 Requirements for US Core Responder returning AllergyIntolerance |
The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.
R4 US Core TG Server Capability Statement |
CapabilityStatement describing the minimal required capabilities of a FHIR Server supporting the US Core 4.0.0 Testing Guide. |
These test plans are available to verify test coverage for this implementation guide
HL7 FHIR R4 US Core AllergyIntolerance Validate |
Example TestPlan for resource AllergyIntolerance read and profile validation |
HL7 FHIR R4 US Core Capabilities |
Example TestPlan to verify a FHIR server’s CapabilityStatement conformance to the US Core 4.0.0 IG |
These test definitions are available to FHIR test engines to verify systems are conforming to this implementation guide
HL7 FHIR R4 TestScript Dynamic Read Validate US Core AllergyIntolerance JSON |
TestScript to test USCoreAllergyIntolerance resource read and profile validation using #json format |
HL7 FHIR R4 TestScript Dynamic Read Validate US Core AllergyIntolerance XML |
TestScript to test USCoreAllergyIntolerance resource read and profile validation using #xml format |
HL7 FHIR R4 TestScript Read Validate US Core AllergyIntolerance JSON |
TestScript to test USCoreAllergyIntolerance resource read and profile validation using #json format |
HL7 FHIR R4 TestScript Read Validate US Core AllergyIntolerance XML |
TestScript to test USCoreAllergyIntolerance resource read and profile validation using #xml format |
Tests for CapabilityStatement using the FHIR CapabilityStatement Resource JSON |
Tests for CapabilityStatement using the FHIR CapabilityStatement Resource using JSON format. |
Tests for CapabilityStatement using the FHIR CapabilityStatement Resource XML |
Tests for CapabilityStatement using the FHIR CapabilityStatement Resource using XML format. |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
AllergyIntolerance Example 1 |
AllergyIntolerance Example 1 |
Patient Example 1 |
Patient Example 1 |