Developer Satisfaction
0.1.0 - ci-build
Developer Satisfaction
0.1.0 - ci-build
Developer Satisfaction - Local Development build (v0.1.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 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 Developer Satisfaction Provider Capability Statement |
CapabilityStatement describing the minimal required capabilities of a FHIR Client supporting the Developer Satisfaction Provider functionality. |
| R4 Developer Satisfaction Requestor Capability Statement |
CapabilityStatement describing the minimal required capabilities of a FHIR Client supporting the Developer Satisfaction Requestor functionality. |
| R4 Developer Satisfaction Responder Capability Statement |
CapabilityStatement describing the minimal required capabilities of a FHIR Server supporting the Developer Satisfaction Responder functionality. |
These are custom operations that can be supported by and/or invoked by systems conforming to this implementation guide.
| Get Satisfaction Operation |
This operation is used to get the satisfaction measurement based on the stored satisfaction observations. |
These define constraints on FHIR resources for systems conforming to this implementation guide.
| Developer Satisfaction Goal Profile - Required Data |
Profile for defining the required data for a Developer Satisfaction Goal. |
| Developer Satisfaction Observation Profile - Required Data |
Profile for defining the required data for a Developer Satisfaction Observation. |
These define constraints on FHIR data types for systems conforming to this implementation guide.
| Testing Scope Canonical Value |
The canonical value of the conformance resource that is tested. |
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 DEVSAT-Goal JSON |
Example TestScript to test DEVSAT-Goal resource read and profile validation using #json format |
| HL7 FHIR R4 TestScript Dynamic Read Validate DEVSAT-Goal XML |
Example TestScript to test DEVSAT-Goal resource read and profile validation using #xml format |
| HL7 FHIR R4 TestScript Dynamic Read Validate DEVSAT-Observation JSON |
Example TestScript to test DEVSAT-Observation resource read and profile validation using #json format |
| HL7 FHIR R4 TestScript Dynamic Read Validate DEVSAT-Observation XML |
Example TestScript to test DEVSAT-Observation resource read and profile validation using #xml format |
| HL7 FHIR R4 TestScript Observation $get-satisfaction JSON |
Example TestScript to test the Developer Satisfaction Observation $get-satisfaction operation |
| HL7 FHIR R4 TestScript Observation $get-satisfaction XML |
Example TestScript to test the Developer Satisfaction Observation $get-satisfaction operation |
| HL7 FHIR R4 TestScript Read Validate DEVSAT-Goal JSON |
Example TestScript to test DEVSAT-Goal resource read and profile validation using #json format |
| HL7 FHIR R4 TestScript Read Validate DEVSAT-Goal XML |
Example TestScript to test DEVSAT-Goal resource read and profile validation using #xml format |
| HL7 FHIR R4 TestScript Read Validate DEVSAT-Observation JSON |
Example TestScript to test DEVSAT-Observation resource read and profile validation using #json format |
| HL7 FHIR R4 TestScript Read Validate DEVSAT-Observation XML |
Example TestScript to test DEVSAT-Observation resource read and profile validation using #xml format |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| Goal Example 1 |
Goal Example 1 |
| Observation Example 1 |
Observation Example 1 |
| Observation Example 2 |
Observation Example 2 |