Stream: implementers
Topic: Orders
Mat Coolidge (Apr 14 2016 at 13:25):
Would there be any problem with a DiagnosticReport sharing a primary ID with a Diagnostic Order?
Grahame Grieve (Apr 14 2016 at 13:30):
logical id?
Mat Coolidge (Apr 14 2016 at 13:32):
yes
Grahame Grieve (Apr 14 2016 at 13:32):
then thats fine
Grahame Grieve (Apr 14 2016 at 13:32):
unusual in terms of business - it's almost always a many:many relationship between order and report, but it's legal in FHIR terms
Mat Coolidge (Apr 14 2016 at 13:43):
Our order results are stored on the original order record, so once they become resulted I need to render a report with the observations
Mat Coolidge (Apr 14 2016 at 13:43):
the easiest way for us to map to our backend is to have them share logical ID's
Mat Coolidge (Apr 14 2016 at 13:44):
and I know its a little wierd, you could query for the report with the same value for identifier= and request.identifer=
Eric Haas (Apr 15 2016 at 23:56):
You could have both - the order Id can repeat and you could differentiate the DiagnosticOrder ID vs the DiagnosticReport ID with type. Like OB2-2 and OBR-3 in a V2 ORU message if you are familiar with those.
Jeremy Chapman (Sep 13 2019 at 15:59):
How do HL7v2 ORM messages map to FHIR? I've seen old (may 2015) Order resources which don't seem to e listed in current documentation.
Jeremy Chapman (Sep 13 2019 at 16:30):
ServiceRequest. Found it.
René Spronk (Sep 16 2019 at 14:29):
Y - http://ringholm.com/docs/04350_mapping_HL7v2_FHIR.htm is DSTU2 and dates from 2015. The thinking in the FHIR community as to how one should support orders & order workflows has changed since then. Have a look at the 'workflow' documentation and Task. A summary can be found in the first video mentioned here: http://www.ringholm.com/column/FHIR_HL7_IHE_XDS_year_in_review.htm
Craig Newman (Sep 16 2019 at 15:28):
The v2-to-FHIR project will be including ORM to ServiceRequest mappings as part of the initial scope. We are just about to start out on it if you want to join the conversation. Seek out Hans if you are in Atlanta as ask about it.
https://confluence.hl7.org/display/OO/2-To-FHIR+Project
Vassil Peytchev (Sep 17 2019 at 18:58):
I hope that mapping the whole message will involve more than just the ServiceRequest Resource - e.g. the ORC segment maps to Task, and OBR to ServiveRequest
Craig Newman (Sep 18 2019 at 19:29):
We've documented a few thoughts on the creation of tasks at https://confluence.hl7.org/display/OO/v2-to-FHIR+Tasks but it's not a topic we've spent much time on yet. If you have thoughts, please add them on the Confluence page.
Vassil Peytchev (Sep 18 2019 at 20:00):
I added a few things in the summary, but I feel the rest of the page needs more work. As a starting point, if the assumption is that you are transforming an H7 v2 message into a FHIR message bundle, then most OO message types will have Task as the focus of the message header.
Last updated: Apr 12 2022 at 19:14 UTC
