Details
-
Change Request
-
Resolution: Persuasive
-
Medium
-
FHIR Core (FHIR)
-
R5
-
Modeling & Methodology
-
Datatypes
-
2.3.0
-
-
Grahame Grieve / Ron Shapiro: 4-0-0
-
Clarification
-
Compatible, substantive
-
R5
Description
It is not entirely clear from the specification how constraining the child elements of a CodeableReference should work As an example, let's say I wanted to constrain CarePlan.activitiy.detail.reason (a CodeableReference) to only be able to reference Condition. I can see that if I wanted to do this, I could change the targetProfiles array on CarePlan.activity.detail.reason. But would it be legal if instead I applied the constraint by changing targetProfiles on CarePlan.activity.detail.reason.reference? How do you handle cases where the CodeableReference and the Reference it contains both have constraints? It seems like a misuse of the CodeableReference type to do this, but I don't see anything saying I can't do this.
Attachments
Issue Links
- mentioned in
-
Page Loading...