Stream: implementers
Topic: Forge Equivalent of CDA 'such that it' (one value required)
Brian Reinhold (Apr 11 2017 at 14:10):
I want to be able to specify that the Observation.code is required to have a coding element that is populated using a certain coding system, however, additional coding elements are also encouraged expressing the same concept in other coding systems. In CDA implementation guides there is a specified language to express that condition. But in Forge any requirement I make on the selection of a coding system suggests that all elements must use that coding system (which makes no sense).
Michel Rutten (Apr 11 2017 at 14:29):
@Brian Reinhold you can slice the .code element to define several coding options.
Brian Reinhold (Apr 11 2017 at 14:38):
okay ... I was afraid of that. I do remember something about 'slicing' in last November's seminar but I didn't recall enough to remember the reason. The most recent use I saw of slicing was to take an element with a max FHIR cardinality of 1 and make it effectively have a higher cardinality. Illegal in FHIR unless one provided a special URI showing the use case.
Michel Rutten (Apr 11 2017 at 14:58):
Slicing allows you to define specific constraints on "slots" in a list of items. In you case, you could slice Observation.code to define several options for the code. The first slice could e.g. define a mandatory coding from a specific code system. Following slices could e.g. define optional additional codings from alternative systems. Check the fhir spec for examples on slicing.
Grahame Grieve (Apr 15 2017 at 21:13):
I
Grahame Grieve (Apr 15 2017 at 21:14):
I'm not sure I follow the underlying desire - what does 'encouraged' mean? Why not just say this in narrative?
Last updated: Apr 12 2022 at 19:14 UTC
