WildFHIR R4 Enterprise Edition Implementation Guide
1.0.0 - current
WildFHIR R4 Enterprise Edition Implementation Guide
1.0.0 - current
WildFHIR R4 Enterprise Edition Implementation Guide - Local Development build (v1.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. 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.
| WildFHIR R4 Requestor |
WildFHIR R4 Requestor actor |
| WildFHIR R4 Responder |
WildFHIR R4 Responder actor |
The following artifacts describe the specific requirements to be met by systems compliant with the implementation guide.
| WildFHIR R4 Requirements for Responder support of the Patient Purge operation |
WildFHIR R4 Requirements for Responder support of the Patient Purge operation |
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.
| WildFHIR R4 Server Capability Statement |
CapabilityStatement describing the minimal required capabilities of a FHIR Server supporting the WildFHIR custom operations functionality. |
These are custom operations that can be supported by and/or invoked by systems conforming to this implementation guide.
| AEGIS WildFHIR R4 Convert Format |
This is the WildFHIR R4 Global Convert Format operation. It provides a standardized mechanism to convert a posted FHIR resource instance to a specific FHIR syntax format. The operation simply returns the FHIR resource instance in the format specified by the request HTTP Accept Header. |
| AEGIS WildFHIR R4 Load Examples |
This is the WildFHIR R4 Global Load Examples operation. It provides a standardized mechanism to process all files in the specified directory folder in ascending alphanumeric order by filename and create/update them on the target WildFHIR server. |
| AEGIS WildFHIR R4 Patient Purge |
This is the WildFHIR R4 Patient Purge operation. It provides a standardized mechanism to force a hard delete or purge of all referenced FHIR resources to a specific Patient. The operation behaves similar to the Patient $everything operation where the Patient Compartment definition is used to discover all related Patient data. |
| AEGIS WildFHIR R4 Purge All |
This is the WildFHIR R4 Purge All operation. It provides a standardized mechanism to force a hard delete or purge of ALL FHIR resources (and their version history). |
These test definitions are available to FHIR test engines to verify systems are conforming to this implementation guide
| WildFHIR R4 TestScript Global $purge-all Usage Example JSON |
Example TestScript to illustrate the use of the WildFHIR R4 Global $purge-all operation using JSON Format. All WildFHIR data is purged in the setup followed by a single test that recreates a known Patient 'wildfhir-patient-purge' via a PUT update/create operation. |
| WildFHIR R4 TestScript Global $purge-all Usage Example XML |
Example TestScript to illustrate the use of the WildFHIR R4 Global $purge-all operation using XML Format. All WildFHIR data is purged in the setup followed by a single test that recreates a known Patient 'wildfhir-patient-purge' via a PUT update/create operation. |
| WildFHIR R4 TestScript Patient/[id]/$purge Usage Example JSON |
Example TestScript to illustrate the use of the WildFHIR R4 Patient/[id]/$purge operation using JSON Format. Data for the known Patient id 'wildfhir-patient-purge' is purged in the setup followed by a single test that recreates the original data via PUT update/create operations. |
| WildFHIR R4 TestScript Patient/[id]/$purge Usage Example XML |
Example TestScript to illustrate the use of the WildFHIR R4 Patient/[id]/$purge operation using XML Format. Data for the known Patient id 'wildfhir-patient-purge' is purged in the setup followed by a single test that recreates the original data via PUT update/create operations. |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| Observation for WildFHIR Purge |
Observation for WildFHIR Purge |
| Patient for WildFHIR Purge |
Patient for WildFHIR Purge |