-
Type:
Change Request
-
Resolution: Persuasive
-
Priority:
Medium
-
FHIR Core (FHIR)
-
STU3
-
FHIR Infrastructure
-
CapabilityStatement (Conformance)
-
-
Grahame Grieve/Michael Donnelly: 14-0-1
-
Enhancement
-
Non-substantive
-
STU3
CapabilityStatement is super-complex. How documents are defined (whether by StructureDefinition or GraphDefinition) isn't totally landed yet. It's not obvious how the resource is going to evolve in the face of our new "storage" paradigm or where SMART stuff will fit or even CDSHooks stuff will fit. It seems like some sort of parameterized/configurable approach is going to be needed here - we just haven't had the time to figure it out. I think that if we lock down the current representation, we're going to be kicking ourselves in 2-5 years time.
- is voted on by
-
BALLOT-3622 Negative - Melva Peters : 2018-Jan-FHIR R1
- Balloted