Committee Approval Date:
Motion: Rick Geimer/Gino Canessa: 10-0-1
Contributing or Reviewing Work Groups:
Interested Parties: TI, CQI
FHIR Development Project Insight ID:
PSS-2200Getting issue details...
Scope of coverage:
The CapabilityStatement resource and the extensions bound to it.
Proposed IG Title:
FHIR CapabilityStatement Implementation Guide
Proposed IG realm and code:
FHIR Core version(s):
FHIR-I will maintain this IG.
This IG defines profiles and extensions for the CapabilityStatement resource to implement features that were formerly considered for what was known as CapabilityStatement2. This includes a terminology-based approach to managing new assertions around system capabilities, which will allow for feature negotiation.
CapabilityStatement is the largest/most complex of the infrastructure resources, yet there continues to be pressure to add yet more capabilities to describe additional nuances of how systems behave (or are desired to behave). As well, the things people want to say about systems often covers concepts that are outside FHIR proper (e.g. CDS Hooks, SMART) or even outside HL7.
This IG defines a terminology-based approach to managing new assertions around system capabilities to support these needs and will also enable dynamic feature negotiation between various actors.
Grahame Grieve (e.g. tx.fhir.org)
Rick Geimer (Lantana)
Gino Canessa (Microsoft/Argonaut)
Richard Ettema (AEGIS)
Allow querying for messaging features supported by a system
Allow querying for document features supported by a system
Allow a system to dynamically define new features not currently part of the normative content of the CapabilityStatement resource, and allow clients to query for such features without retrieving and parsing the entire CapabilityStatement instance.
Proposing January 2024 for initial Connectathon testing, and May 2024 for first ballot.