For questions about this archive, please contact webmaster@hl7.org.
I Butt (Mar 05 2019 at 02:50):I am looking for HL7 Message specification for Request & Response to Get all the orders related with Radiology / Xray from HIS. Query will be based on Patient ID / MRN
I reached with the following:-
Request:
For Example:-
Request:-
--> Sample Request Message
MSH Segment, MSH-9 Field for Pharmacy Query QRY^Q26 (I am looking this field for Radiology Order Query)
QRD Segment will send about Patient MRN and Order Type
Response:
Sample Response message for all the Radiology Orders
For Example:
(MSH-9 Field)
PID Segment
ORC (I am not sure)
OBR ( I am not Sure)
Thanks
Lloyd McKenzie (Mar 05 2019 at 04:29):Support for v2 queries is highly variable. Have you reached out to the administrators of the systems you're trying to query data from to find out what they support?
I Butt (Mar 05 2019 at 04:38):Support for v2 queries is highly variable. Have you reached out to the administrators of the systems you're trying to query data from to find out what they support?
Unfortunately the team told us you send us the HL7 specification we will prepare accordingly. Due to this I am looking for it.
Lloyd McKenzie (Mar 05 2019 at 05:22):@Elliot Silver ?
I Butt (Mar 05 2019 at 05:35):Elliot Silver ?
I am here for solution not for argument and reasons. This is HL7 forum, I should find solution from here.
Elliot Silver (Mar 05 2019 at 05:36):I’ve never heard of someone doing this; systems that I’m aware of simply listen for the orders and keep a record.
The original question seems to suggest that there is a pharmacy-specific way of doing this, and by extension expects a radiology-specific variant. I’m not sure this is true.
I don’t know V2 query well enough to know if such a query is even possible, let alone how to populate it.
I Butt (Mar 05 2019 at 05:38):I’ve never heard of someone doing this; systems that I’m aware of simply listen for the orders and keep a record.
The original question seems to suggest that there is a pharmacy-specific way of doing this, and by extension expects a radiology-specific variant. I’m not sure this is true.
I don’t know V2 query well enough to know if such a query is even possible, let alone how to populate it.
Thanks For reply.
But there should be some way to get all orders (Pharmacy, Lab & Radiology) for a specific patient by Patient ID or MRN. Pharmacy example i present here because I got this easily and provide them the HL7 specification they implemented and its working fine. Request Message QRY^Q26 with QRD Segment. Response Message: ROR^ROR With ORC and RXC Segment.
Alternate Is: Can you please specify the trigger Message for Radiology Orders? So in this case when patient have any order (New, change or cancel) we receive message.
Lloyd McKenzie (Mar 05 2019 at 05:50):"Should be" and "is" are not necessarily the same. As Elliot says, a lot of v2 systems don't do queries at all. HL7 only defines standard queries where the community has asked us to do so. There are no standard queries defined in the radiology space. If you need one, you're going to have to define one of your own. Chapter 5 explains how to do that. The good news is that your communication partner has said they'll do whatever you tell them to - so define a query that takes the parameters you need and returns the data you need and you're good to go. Just don't expect anyone that you haven't specifically negotiated with to support it.
Lloyd McKenzie (Mar 05 2019 at 05:52):O23 is the trigger for radiology orders. You'll need to look at all of the other triggers for changes though. Those can all be found in the HL7 spec.
I Butt (Mar 05 2019 at 05:56):O23 is the trigger for radiology orders. You'll need to look at all of the other triggers for changes though. Those can all be found in the HL7 spec.
Thanks and I understood what Mr. Elliot said and I agree with you and his response.
If you help in Message Type (MSH-9) and Segments It will be big support.
Thanks
Lloyd McKenzie (Mar 05 2019 at 06:00):Have you read chapter 5 of the specification about creating custom queries? The segments can be whatever ones you find useful - which will depend on your business case. You can take a look at the radiology message structures to see which ones could theoretically be present in a notification and subset from there.
I Butt (Mar 05 2019 at 06:04):Have you read chapter 5 of the specification about creating custom queries? The segments can be whatever ones you find useful - which will depend on your business case. You can take a look at the radiology message structures to see which ones could theoretically be present in a notification and subset from there.
Before After Long struggle I provide them HL7 specification for two interfaces 1. Patient Demographic Information 2. Pharmacy Orders
3. Now I am looking for radiology Orders, I though from here I can find quick solution.
Can you provide the URL for so I can download HL7 chapter 5.
Let me check and get back to you.
Elliot Silver (Mar 05 2019 at 06:08):For clarity on what @Lloyd McKenzie said, O23 is the OMI^O23 message, although many systems are still using older ORM messages.
As well as checking out chapter 5 of the V2 spec, I suggest digging into chapter 4 on orders.
I’m not sure which version of V2 you need,, but I think they’re all downloadable here: https://www.hl7.org/implement/standards/product_brief.cfm?product_id=185
I Butt (Mar 05 2019 at 09:41):I come up with following option.
Request:
MSH|^~\&|QS||RAD||199910180900-0700||QBP^Q61^QBP_Q11|7777|P|2.4|
QPD|Q61^Radiology Order|Q98|01111111^^^^MR| --> Patient ID
RCP|I|
Response:
MSH|^~\&|RAD||QS||||RSP^K61^RSP_K61|5555|P|2.4|
MSA|AA|7777|
QAK|Q98|OK|Q61^Radiology Order|
QPD|Q61^Radiology Order|Q98|01111111^^^^MR|
PID|||01111111^^^^MR|
ORC
OBR
OBR
OBR
OBR
Please check is it fine?
Lloyd McKenzie (Mar 05 2019 at 15:14):That's not really the purpose of this discussion forum. You're free to ask quick questions that other members of the community (i.e. volunteers) who might have past experience that allows them to give you a quick answer. However, no one here is paid. Doing a review of a draft specification (or even a draft instance) to make sure it's valid is the sort of thing you'd probably need to pay someone to do if you can't do it yourself. (That said, tha bare ORC and OBRs look odd - normally if you have nothing to send for a segment you omit it. Also, I think you're missing at least some required elements. Make sure you read through the spec for every segment and data type you're sending.
I Butt (Mar 06 2019 at 01:40):For clarity on what Lloyd McKenzie said, O23 is the OMI^O23 message, although many systems are still using older ORM messages.
As well as checking out chapter 5 of the V2 spec, I suggest digging into chapter 4 on orders.
I’m not sure which version of V2 you need,, but I think they’re all downloadable here: https://www.hl7.org/implement/standards/product_brief.cfm?product_id=185
Thanks for Help, Can you please help for the Orders Segment Name for order details OBC & OBR is fine?
Lloyd McKenzie (Mar 06 2019 at 03:32):I'm not understanding the question
I Butt (Mar 06 2019 at 05:39):I'm not understanding the question
OMI^O23 is the Message Type with O23 trigger.
Which segment have Order detail by Physician / Doctor For example chest Xray etc., Currently focus radiology only.
Lloyd McKenzie (Mar 06 2019 at 06:10):You've looked at the segment definitions in the spec?
I Butt (Mar 06 2019 at 07:16):Yes I checked.
ORC Common Order, Which is required. TQ1 (Timing / Quantity) also required. OBR -- Observation Request.
Is segments are OK?, and OBR is repeatable?
Remaining Segment definition / detail i will check from spec. This is Understandable for me.
Last updated: Mar 23 2020 at 00:02 UTC