FHIR Chat · ServiceRequest.intent value from ORU_R01 and OUL_R22 message · v2 to FHIR

Stream: v2 to FHIR

Topic: ServiceRequest.intent value from ORU_R01 and OUL_R22 message


view this post on Zulip Eli-Jean Leyssens (Nov 02 2021 at 16:31):

Mapping ORU_R01 and OUL_R22 messages to a Bundle with a MessageHeader, ServiceRequest and DiagnosticReport. Unfortunately the ServiceRequest attribute "intent" is mandatory, but there is no mapping listed at: https://www.hl7.org/fhir/servicerequest-mappings.html#v2
So, what would be the most approriate value to set for intent, "order" or "original-order"? Or maybe even one of the other RequestIntent values?

view this post on Zulip Riki Merrick (Nov 02 2021 at 17:52):

Hi Eli,

view this post on Zulip Riki Merrick (Nov 02 2021 at 17:59):

I think this needs some thought - for the OML message It would probably be at least 'order', but if this is from the original provider I would use 'original-order' as you suggest - I guess that doesn't change in FHIR for the report back like the order control code does in v2, so then it would just represent that, UNLESS an additional ServiceRequest is included to represent a filler-order or reflex-order... (and we may need to look at add-on, etc - see here for discussion specifically around how these order types should be handled in FHIR: https://confluence.hl7.org/pages/viewpage.action?pageId=79504418

view this post on Zulip Eli-Jean Leyssens (Nov 04 2021 at 14:47):

Even though the servicerequest-mappings.html didn't list anything for intent, I just saw that there is a mapping for OBR.0 at https://build.fhir.org/ig/HL7/v2-to-fhir/ConceptMap-segment-obr-to-servicerequest.html
So, here it says to set the intent to "order".


Last updated: Apr 12 2022 at 19:14 UTC