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
This page defines how CapabilityStatements are used and the expectations for mandatory and must support elements. A conformant system SHALL support the resources as profiled by this guide.
Note that the conformance verbs - SHALL, SHOULD, MAY - used in this guide are defined by the FHIR Conformance Rules.
In order to claim conformance with this guide, a client and server implementation must adhere to the defined requirements in this guide.
Profile Support refers to the support of the profiles defined in this guide in a system exposing FHIR resources. Specifically, a conformant server:
CapabilityStatement.instantiates
element: http://touchstone.aegis.net/touchstone/fhir/dev-satisfaction/CapabilityStatement/dev-satisfaction-server-r4
.CapabilityStatement.rest.resource.supportedProfile
element for the Observation resource type: http://touchstone.aegis.net/touchstone/fhir/dev-satisfaction/StructureDefinition/DEV-SAT-Observation
** declaring support for the Developer Satisfaction Goal Profile by including its official URL in the server’s CapabilityStatement.rest.resource.supportedProfile
element for the Goal resource type: http://touchstone.aegis.net/touchstone/fhir/dev-satisfaction/StructureDefinition/DEV-SAT-Goal
In this guide, no elements are currently marked as Must Support. In the future those elements that are flagged as MS will be enumerated below, with details on what must support means.