MPPS Status update to HL7 Forward Tasks not working

[toufic...@gmail.com]

Dears,

ver 5.24.2

I am not able to initiate HL7 Forward Task for MPPS status update.

I have configured as per the documentation:

HL7 Procedure Status Update Delay is empty

HL7 Procedure Status Update Timeout is set to PT1M

HL7 Procedure Status Update On Timeout is set to True

HL7 Procedure Status Update Task Polling Interval is set PT1M

The MPPS is working normally, and it is using the same study UID, and on the monitoring page the MWL and MPPS tabs are updated accordingly (In PROGRESS . DISCOUNTED etc...), but noting appears in the "HL7 Forward Tasks".

PS: The "on Study received" notification works fine (when HL7 Procedure Status Update Delay is set to PT1M), but I need to make it work for MPPS.

Kindly advise what am I missing...

Thank you,

Toufic

[Vrinda Nayak]

I'm assuming you have also configured HL7 Procedure Status Update Sending Application and HL7 Procedure Status Update Receiving Application(s) for MPPS case. Additionally, note that HL7 Procedure Status Update message is sent on MPPS triggers only if the MPPS dataset coming into archive also contains Placer Order Number Imaging Service Request and Filler Order Number Imaging Service Request in Scheduled Step Attributes Sequence as this information is required in ORC-2 and ORC-3 fields in the outgoing Procedure Status Update messages from archive

[toufic...@gmail.com]

Dear Vrinda,

Thanks for quick feedback.

Yes, the HL7 Procedure Status Update Sending Application and HL7 Procedure Status Update Receiving Application(s) are configured, as I am receiving succesfully notifications for study availability when HL7 Procedure Status Update Delay is set to PT1M, but when I keep this setting empty to receive the notifications by MPPS it doesn't work.

I am sending the ORC-2 and ORC-3 but still I am not able to get notifications for MPPS (at least I need the DISCONTINUED and COMPLETED).

Attached a sample ORM sent to the Archive that creates the MWL:

MSH|^~\&|xxxxxxxxx|xxxxxxxxxxxxxxxxx|||||ORM^O01|bb867c1c-9e61-4504-afb2-063b998fce73||2.5||||||UTF-8

PV1||||||||916^xxx^xxx^xxx|||||||||||2346453q

PID|||1231238||xxx^xxxx^xxxx||19561118|M

ORC|NW|210063574202111120844|210063574202111120844||SC||^^^20211210121212|||||||||||TTT

OBR||||^^^^Chest X-Ray|||||||||||||||210063574202111120844|81351||||DX||||||||||||||||||||81351^Chest X-Ray

Waiting your feedback.

Thank you!
Toufic

[Vrinda Nayak]

No, you understood it wrong - "I am sending the ORC-2 and ORC-3 but still I am not able to get notifications for MPPS (at least I need the DISCONTINUED and COMPLETED)."

Archive can send out HL7 Procedure Status Update message OMG^O19 when it receives MPPS - which is explained in the wiki - Synchronize external HL7 receivers on receive of Requested Procedures. What I mentioned in the last post was to check if the MPPS received by the archive contains the required attributes - Placer Order Number Imaging Service Request and Filler Order Number Imaging Service Request in Scheduled Step Attributes Sequence - because these 2 attributes from the MPPS incoming to archive are used in HL7 message going out from the archive

[Vrinda Nayak]

Alternatively, to test and understand how HL7 messages are sent out from archive on receive of MPPS - you can use mppsscu tool (using -s option to set Placer Order Number Imaging Service Request and Filler Order Number Imaging Service Request in Scheduled Step Attributes Sequence) to send MPPS to archive. On the other end, you may use hl7rcv tool which acts as an HL7 receiver where you can see the HL7 message it received from the archive (Note - if you choose to use hl7rcv tool, you would need to change HL7 Procedure Status Update Receiving Application and Facility and also configure device for HL7 receiver).

[Toufic N. MOKBEL]

Dear Vrinda,

Where can I check what is received by the archive inside the MPPS message? (In the log I don't see the HL7 message, only a notification of MPPS).

And, shall I select OMG? Not ORM as HL7 notification?

Thanks,

Toufic

--
You received this message because you are subscribed to a topic in the Google Groups "dcm4che" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dcm4che/dwUzE577FWw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to dcm4che+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/e7e6b1fa-37b6-4576-a786-4c088699ffe2n%40googlegroups.com.

[Vrinda Nayak]

- Where can I check what is received by the archive inside the MPPS message? (In the log I don't see the HL7 message, only a notification of MPPS).

You may enable DEBUG logging for org.dcm4che3.net in wildfly configuration. The incoming MPPS with the request dataset to archive and HL7 message going out of archive in server.log is then seen as indicated in attached snippet of server.log

- And, shall I select OMG? Not ORM as HL7 notification?

Procedure Status Update notification from Image Manager / Image Archive to DSS / Order Filler is defined only in IHE's Eyecare Technical Framework - Procedure Status Update [EYECARE-22] transaction. There is no such corresponding transaction in IHE's Radiology framework. Hence, only OMG^O19 order message can be sent out of the archive - https://github.com/dcm4che/dcm4chee-arc-light/issues/500.

Much later, archive also started supporting notification of imaging results to external HL7 receivers described in Encounter Based Imaging Workflow - Notify of Imaging Results [RAD-132] - https://github.com/dcm4che/dcm4chee-arc-light/issues/2407. This required ORU^R01 as outgoing message type.

This implies, you can currently select either OMG^O19 or ORU^R01 for messages going out of archive on receive of MPPS or Study (with(-out) associated MWL)

[Toufic N. MOKBEL]

Dear Vrinda,

Could you please specify where I can change the log level to DEBUG?

Can find somewhere the mppsscu.exe ?

To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/4731a28c-abef-4979-bac6-ddf9ca991ec1n%40googlegroups.com.

[Vrinda Nayak]

mppsscu and all other dcm4che tools are always available in the library releases.

For enabling org.dcm4che3.net as DEBUG, see attached screenshots

[Toufic N. MOKBEL]

Dear Vrinda,

I thank your quick support, I tried the mppsscu with DISCONTINUED including the siuid+requested procedure id + scheduled procedure id, the MWL was successfully processed and changed to MPPS DISCONTINUED on the archive UI... But didn't get an HL7 Notification.

(I am only getting the HL7 notification on Study Availability, not by MPPS).

My configuration is exactly as mentioned in the documentation (because it is successfully working for Study Availability)

Please assist!

Thanks!

Toufic

To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/6f828b59-62c8-4a13-9cea-9f934eff7b91n%40googlegroups.com.

[Vrinda Nayak]

Please show how exactly did you run the mppsscu tool and what flags you set when using it. You need to set Placer Order Number Imaging Service Request and Filler Order Service Imaging Request in Scheduled Step Attributes Sequence!

[Toufic N. MOKBEL]

Hi Vrinda,

You are right! The mpps was missing the Placer Order Number Imaging Service Request and Filler Order Service Imaging Request...

Do the modalities always send them with their MPPS? Can we have a workaround if they don't?

The notification works only on DISCONTINUED and COMPLETED? It doesn't work on IN PROGRESS?

Thanks!!!!

Toufic

To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/f5d0aab9-8989-4e7b-9ddc-918dbf78ceffn%40googlegroups.com.

[Vrinda Nayak]

Currently, we are not aware of any use case wherein HL7 receivers are interested in IN PROGRESS update messages. If you know of any use case, then please elaborate a little.

Normally, in a Scheduled Workflow the modality would always first query for a worklist (RAD-5) and use the information present in worklist when it sends out MPPS. Although Placer and Filler Order Numbers are optional in MPPS, these are required in worklist.

[Toufic N. MOKBEL]

Dear Vrinda,

Usually RIS Systems are interested to know when the Imaging Study starts, especially for long studies such as CT, MR, PT, NM, US...

The MPPS IN PROGRESS will allow the Administrator or Front Desk to be aware on live basis what is the status of the patients/orders and whether patients are in progress in the Imaging Rooms.

This is in addition to the analytics and statics that the IN PROGRESS can provide, such as Imaging Procedure Times, Patient Waiting times, ...

Regards,

Toufic

To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/80a9aee9-0366-40ee-9415-6bb606a37887n%40googlegroups.com.

[Johnson F]

Agreed fully, it was important for me too but i gave up on ar v5.24.2 since it arc version of dcm4chee doesnt send all these updates. as of now i have difference solution, does my job.............

[Toufic N. MOKBEL]

The IN PROGRESS is usually a SC_IP in the HL7 notification ORC

To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/aec19d3b-a889-485b-ae7d-3d2f2d7a5bfen%40googlegroups.com.

[Vrinda Nayak]

Opened Notify HL7 Receivers and/or update MWL status to STARTED also on receive of MPPS with IN PROGRESS status.

[Johnson F]

Very much appreciated Vrinda....