Stream: implementers
Topic: DiagnosticOrder and OBR-13
James Butler (Aug 15 2016 at 02:19):
Looking at the mapping from OBR to DiagnosticReport and friends, I see the suggestion that OBR-13 should be mapped to DiagnosticOrder.supportingInformation: https://www.hl7.org/fhir/diagnosticorder-mappings.html#v2. Has anyone implemented this? I'm thinking a reference to an Observation with a valueString and some hardcoded code makes most sense, but is there a particular LOINC code which is suitable?
Eric Haas (Aug 15 2016 at 07:02):
Those mappings have not undergone a QA review. There are two elements in DiagnosticOrder (newly reminted as DiagnosticRequest in STU3) supportinginformation which is a reference and used to provide additional clinical context for the filler and reason which is a coded element and useful for reimbursement. I think that OBR-13 should be mapped to reason
Eric Haas (Aug 15 2016 at 07:06):
Then there is no reason to conjure up a loinc for supporting information.
James Butler (Aug 15 2016 at 21:06):
Thanks, that's an excellent plan.
Last updated: Apr 12 2022 at 19:14 UTC
