Stream: Orders and Observation WG
Topic: OBR with both ED and other data types in OBX
Linda (Oct 05 2020 at 18:52):
Hi all,
We are mapping ORU's to US Core and were wondering how we handle a single OBR that has an Encoded Data value as well as another data type in multiple OBX's.
Example
OBR|...
OBX|1|ED|...
OBX|2|ST|...
OBX|3|NM|...
We noticed R4 does not allow for an attachment value[x] but R5 does - perhaps for this issues. If we are on the right track, what would be the most appropriate way to extend R4 to align with what will happen in R5?
Lloyd McKenzie (Oct 05 2020 at 20:47):
@Eric Haas
Eric Haas (Oct 05 2020 at 22:14):
Since the choice exists in R5 there there is automatically a standard valueAttachment extension to "pre-adopt it"
Eric Haas (Oct 05 2020 at 22:24):
see http://build.fhir.org/versions.html#extensions
Linda (Oct 06 2020 at 14:56):
So where do we find the extension. The link above doesn't have an R4/R5 column
Linda (Oct 06 2020 at 15:19):
I misunderstood I think - this is a pattern we can instantiate - and I also see on another conversation where we name the extension as - http://hl7.org/fhir/5.0/StructureDefinition/extension-Observation.valueAttachment
Last updated: Apr 12 2022 at 19:14 UTC
