Stream: implementers
Topic: Conditional requirement in Forge profile
Brian Reinhold (Apr 12 2017 at 09:13):
I have a requirement on the Observation.code element which is easy to specify in text but I am not sure how to do it in Forge. The Observation.code is a [1..*] where one coding element is required to be that of IEEE 11073-10101. So I have used slicing to handle that. Now I have a codingIEEE element with a [1..1] cardinality. However, if the measurement happens to be a vital sign, FHIR requires the use of LOINC. So I need to make a second slice called codingLOINC but its cardinality is [0..1] because not all PHD measurements are vital signs. So somehow I need to indicate that the element is required when a vital sign but optional otherwise. I can put such information in the edit boxes. Is that the best I can do?
Sunanda Veeraganti (Apr 12 2017 at 10:11):
@Brian Reinhold there are some examples in this page https://www.hl7.org/fhir/profiling-examples.html which are very similar to the scenario you have
Brian Reinhold (Apr 12 2017 at 10:29):
Thanks. It looks like what I have done is correct.
Last updated: Apr 12 2022 at 19:14 UTC
