Conformance FHIR Resource Proposal
- 1 Conformance
- 1.1 Owning committee name
- 1.2 Contributing or Reviewing Work Groups
- 1.3 FHIR Resource Development Project Insight ID
- 1.4 Scope of coverage
- 1.5 RIM scope
- 1.6 Resource appropriateness
- 1.7 Expected implementations
- 1.8 Content sources
- 1.9 Examples
- 1.10 Resource Relationships
- 1.11 Timelines
- 1.12 gForge Users
- 1.13 Issues
Owning committee name
- Temporarily owned by the FHIR Core Team
Contributing or Reviewing Work Groups
FHIR Resource Development Project Insight ID
Scope of coverage
The resource is used to represent all conformance declarations with FHIR that fall within the scope of the FHIR specification. Specifically:
- It covers conformance declarations across the messaging, document and services paradigms
- It covers conformance declarations of installed, designed and proposed systems (whether composed of multiple components or stand-alone)
- It covers both "full" conformance and any specification-recognized "partial" conformance within the scope of use
Systems cannot legitimately declare conformance with FHIR unless they are accompanied by a valid instance of this resource.
Note: This resources does not cover conformance declarations for out-of-scope uses. E.g. FHIR as an internal database model, FHIR as an internal model for decision-support purposes, etc.
This resource operates outside of the space covered by the RIM as "meta" information about FHIR-conformant systems. It will have mappings to the v2 conformance model and portions of the v3 MIF.
Conformance declaration has been identified as important in v2 and relevant in v3. It is particularly important for discoverability in RESTful solutions. Conformance statements represent distinct installations, software systems and software requirement statements and thus meet the requirement of independence. The number of data elements is on the high side due to the need to capture information on a variety of different interoperability types, however the types need to be combined because the overall conformance statement acts as a single unit.
All implementations declaring conformance to FHIR will need to implement this resource.
- HL7 v2 conformance profiles
- HL7 v3 MIF conformance statement
- IHE Implementation guides
- One instance each from an RFP perspective describing document requirements
- A configurable application describing RESTful, document and messaging capabilities
- An installed application describing a document configuration
No resources are expected to reference Conformance statements, at least not within the 80%.
Conformance will reference the Profile resource to allow identification of the constraints and packaging expectations supported for messaging and documents
This is a core resource that will be part of the initial DSTU
- Do we need a PSS for this?
- Should this resource be used for declaration of conformance for SOA FHIR solutions as well, and if so, what would that look like?
- Are there additional sources we can/should look to for examples of Conformance
- should clarify the relation between conformance and profile