Details
-
Change Request
-
Resolution: Persuasive with Modification
-
Highest
-
FHIR Core (FHIR)
-
R4
-
Terminology Infrastructure
-
ConceptMap
-
-
Rob Hausam/Reuben Daniels: 4-0-0
-
Enhancement
-
Compatible, substantive
-
R5
Description
Right now, the element referenced by a dependency needs to have a specific value. What if it needs to be one of a set of values? E.g. "This mapping applies if body site falls in this set of codes" In that circumstance, you couldn't have a single value. I'm ok with saying that this circumstance needs an extension, but in that case, we couldn't make value mandatory. (Note that adding valueSet might create an issue using the same structure for 'product' because obviously when populating other elements, you need to pick a specific value
(Comment 111 - imported by: Ron G. Parker)
Attachments
Issue Links
- is voted on by
-
BALLOT-17586 Negative - Ron G. Parker : 2021-May-FHIR R5 Comment
- Closed
-
BALLOT-18213 Negative - Joel Francis : 2021-May-FHIR R5 Comment
- Closed
-
BALLOT-18435 Negative - Cindy Jiang : 2021-May-FHIR R5 Comment
- Closed
- relates to
-
FHIR-32540 Why are element.code and target.code 0..1?
- Published
-
FHIR-15687 ConceptMaps should be able to map to/from a ValueSet
- Published
-
FHIR-28284 Improve modelling for ConceptMap's dependsOn and product fields
- Published