Stream: implementers
Topic: Observations with both string and code value[x]
Kirstine Rosenbeck Gøeg (Sep 18 2020 at 12:32):
I have an Observation, which always has a string-value, but sometimes also have a structured result (CodeableConcept).
Right now I have profiled using two observations with a hasMember attribute pointing from the string-valued observation to the structured observation.
It would simplify my model if I design one Observation, with value[x] datatype CodableConcept - using CodableConcept.text for the text-based result and CodableConcept.coding for the structured result. However, is this design an unintended use of the FHIR-standard? (You might argue that since the data is primarily text-based it should be represented as a string - not a text in a CodableConcept datatype)
If you are interested, you can see an example (of the first design) here: http://build.fhir.org/ig/Kirstinerosenbeck/FKInfo/branches/master/StructureDefinition-KLCommonCareSocialEvaluation.html (where hasMember references a structured evaluation)
What are your thoughts on this?
Lloyd McKenzie (Sep 18 2020 at 13:08):
@Eric Haas
Michele Mottini (Sep 18 2020 at 13:15):
If the string and the code are expressing the same concept / idea it is appropriate to the just put the string in CodeableConcept.text
Michele Mottini (Sep 18 2020 at 13:15):
Otherwise I would go for a main observation containing two components with the code and string values
Last updated: Apr 12 2022 at 19:14 UTC
