Details
-
Change Request
-
Resolution: Not Persuasive
-
Very High
-
FHIR Core (FHIR)
-
STU3
-
FHIR Infrastructure
-
ImplementationGuide
-
Profiling
-
-
Grahame Grieve/Rick Giemer: 8-0-0
Description
The mustSupport element clearly differentiates which elements in a profile implementers are expected to support - and which they don't. However, we don't currently have language that says that the flags in the profile actually have to jive with the ad-hoc documentation in the profile. I.e. there's nothing that stops an author from flagging Patient.deceasedDate as "false", while elsewhere adding language that indicates that Patient.deceasedDate "SHALL" be supported in some way. We need to make explicit - probably in the profiling page - that doing this isn't permitted. The ad-hoc language in narrative and surrounding text can't conflict with the formal documentation expressed in the StructureDefinition.