-
Type:
Change Request
-
Resolution: Not Persuasive with Modification
-
Priority:
Medium
-
FHIR Core (FHIR)
-
DSTU1 [deprecated]
-
FHIR Infrastructure
-
Conformance Rules
Profiling -
-
Kai Heitmann / Richard Ettema: 17-1-0
-
Enhancement
-
Compatible, substantive
-
DSTU1 [deprecated]
Comment:
There is currently no way for a profile distinguish between "required but may be empty" (RE) and "optional/don't care" (O) because the multiplicity is not sufficient to distinguish (either 0..1 or 0..*). We need conformance keywords for resource profiles especially when the profile represents the needs of consumer of data (e.g. DAF, QI-core) that have a few mandatory elements (i.e. minoccurs=1) but many RE and O elements.
- is voted on by
-
BALLOT-1385 Negative - Greg Staudenmaier : 2015-May-FHIR R1
- Balloted