Stream: implementers
Topic: mapping Transcription R03 to FHIR Resource
Jennifer Starling (Aug 21 2020 at 16:33):
We are implementing a new FHIR database and I'm having trouble with the R03 mapping to the Diagnostic Report or for the content. If the R03 is a transcription pathology report and the documented result is coming from the OBX:5 value repeated, would those values be in the Diagnostic Result result tag, or should they be in the Observation resource text tag?
Vassil Peytchev (Aug 21 2020 at 17:43):
The September ballot contains some information on HL7 to FHIR mapping, specifically of the ORU^R01 message (what is R03, BTW?)
There is also the #v2 to FHIR stream, where you may get better responses.
Jennifer Starling (Aug 21 2020 at 18:10):
An ORU^R03 is an hl7 message is a transcription report dictation by a provider so it looks like:
Incoming hl7 message has:
OBX|1||||This is the start of|||||
OBX|2||||the report that I want to store|||||
....
Vassil Peytchev (Aug 21 2020 at 18:39):
I've never seen an ORU^R03 message defined by HL7 (all the way back to version 2.2), although version 2.2 and 2.3 have an example for a micro result that uses ORU^R03, but that is likely a typo...
I think the ORU^R01 mapping I mentioned above might be a good starting point...
René Spronk (Aug 22 2020 at 10:19):
I've never seen R03 implemented either, but that's beside the point. DiagnosticReport.presentedForm.Attachment might be an option (less likely in my opinion), or DiagnosticReport.result.valueString/valueAttachment. Note that text in a FHIR resource is a 'summary' / additional kind of thing, so one would value that in addition to the 'observed value'. DiagnosticReport probably has other data/references besides the actual textual report, so the text in the Diagnostic report resource would be a textual summary of all of that, plus the text of the actual observation.
Last updated: Apr 12 2022 at 19:14 UTC
