-
Type:
Change Request
-
Resolution: Not Persuasive
-
Priority:
Medium
-
FHIR Core (FHIR)
-
DSTU1 [deprecated]
-
FHIR Infrastructure
-
StructureDefinition
-
-
Ewout Kramer/Yunwei Wang: 8-0-1
-
Enhancement
Currently, profiles may NOT exclude data that is required in the base. While this makes sense for validation, it limits the utility of profiles for display and authorization use cases.
Consider:
1. A display profile for a small subset of the resource. Basically codifying the _elements query into a profile. This could be indicated as a SUBSETTED profile to relax the conformant with base requirement.
2. Use of targetted profiles for security authorization (for PATCH). Allow a client to update ONLY the elements included in the profile (which may not include a required element). Again, SUBSETTED could be used.
Validation would be limited - only included elements could be validated, so there would need to be some caveats there. The behavior here could be implementer specific, but at least storing the profile would be standard conformant.