dcm4chee arc light - Sending HL7 after receiving study

978 views
Skip to first unread message

Michał Kuchta

unread,
Sep 18, 2018, 5:44:04 AM9/18/18
to dcm4che
Hello. I need help. 
Added HL7 Receiver (mirth channel), and updating MWL status as in https://github.com/dcm4che/dcm4chee-arc-light/wiki/Update-MWL-status-to-COMPLETED-for-received-studies.

I send modality worklist entry, read it by modality (USG - GE Voluson e). I do some screens, end study.
On PACS I see that Study was send,  MWL entry is updated.

Yet mirth don't receive any notification.

I tried with synchronization done  on mpps trigger, and study receive trigger. No success.

What am I missing? 
How can I check where is problem? 
Is it logged somewhere? Can I debug it?

vrinda...@j4care.com

unread,
Sep 18, 2018, 11:58:40 AM9/18/18
to dcm4che
Hello,

Can you verify it by checking in the HL7 Forward Queue (Go to Monitoring Page -> Queues tab -> select HL7 Forward Tasks). What do you see?

Michał Kuchta

unread,
Sep 19, 2018, 3:31:10 AM9/19/18
to dcm4che
Can you verify it by checking in the HL7 Forward Queue (Go to Monitoring Page -> Queues tab -> select HL7 Forward Tasks). What do you see?

Queue is empty. Count 0. Submit loads no results.

vrinda...@j4care.com

unread,
Sep 19, 2018, 4:30:00 AM9/19/18
to dcm4che
- Verify if the study instance UID in the MWL message matches with that of study instance UID present in study/MPPS.
- If you are using MPPS trigger, ensure the MPPS attributes have ScheduledStepAttributesSequence (which should also contain PlacerOrderNumberImagingServiceRequest and FillerOrderNumberImagingServiceRequest) and PerformedProcedureStepStartDateAndTime
- Check in your database, if at all there are any entries in the hl7psu_task table.
- If there are no entries in this table, then it means you have incorrect LDAP configurations.
- If your configurations are correct, entries present in database table hl7psu_task and also attributes present in MPPS as mentioned above, then check your wildfly logs, if there are any errors

Michał Kuchta

unread,
Sep 20, 2018, 9:47:22 AM9/20/18
to dcm4che
- Study instance uid matches
- Not using MPPS trigger (now)
- There are no entries. But when study is recived, entry is created, and then deleted after some time.
- In wildfly log I got:
2018-09-20 13:45:09,088 INFO  [org.dcm4chee.arc.hl7.psu.HL7PSUScheduler] (EE-ManagedScheduledExecutorService-default-Thread-8) Schedule HL7PSUTask[pk=12, deviceName=dcm4chee-arc, studyInstanceUID=STUDY.386, scheduledTime=2018-09-20 13:45:03.588]
2018-09-20 13:45:09,122 WARN  [org.dcm4chee.arc.hl7.psu.HL7PSUEJB] (EE-ManagedScheduledExecutorService-default-Thread-8) Failed to schedule HL7 Procedure Status Update to Mirth-HL7:
: org.dcm4che3.conf.api.ConfigurationNotFoundException: Unknown HL7 Application: Mirth-HL7|
at org.dcm4che3.conf.api.hl7.HL7ApplicationCache.findHL7Application(HL7ApplicationCache.java:67)

Mirth-HL7 is name of Hl7 Applications of device Mirth-Device added according to https://github.com/dcm4che/dcm4chee-arc-light/wiki/HL7-Receiver

Johnson F

unread,
Oct 17, 2021, 5:10:14 AM10/17/21
to dcm4che
Hello Miku,

is it working? https://github.com/dcm4che/dcm4chee-arc-light/wiki/Requested-Procedures link has fields which are not even available on settings page....

Vrinda Nayak

unread,
Oct 18, 2021, 4:54:56 AM10/18/21
to dcm4che
Which fields are not available? Where exactly are you trying to configure when you say "settings page"?

Vrinda Nayak

unread,
Oct 18, 2021, 4:56:13 AM10/18/21
to dcm4che
Have you configured HL7 receiver for Mirth-HL7? See HL7 Receiver

Johnson F

unread,
Oct 18, 2021, 9:08:10 AM10/18/21
to dcm4che
These settings what you mentioned in document is not available in arch 5.24.2

Using Archive UI
  1. Go to Menu->Configuration, then on Devices page, Edit the dcm4chee-arcdevice.Go to Extensions and Edit extension of Device Extension. Again go to its Extensions and Edit extension of Archive Device.

  2. Enter values in fields HL7 Procedure Status Update Task Polling Interval, HL7 Procedure Status Update Tasks Fetch Size, HL7 Procedure Status Update Sending Application and HL7 Procedure Status Update Receiving Application as shown below.

  3. As explained above, if one wants this synchronization to be done on :

    a. MPPS trigger : Set values for fields HL7 Procedure Status Update Timeout and HL7 Procedure Status Update On Timeout.

    b. Study Receive trigger : Set value for field HL7 Procedure Status Update Delay

Johnson F

unread,
Oct 18, 2021, 9:26:53 AM10/18/21
to dcm4che

Yes

kamlesh....@hops.healthcare

unread,
Oct 5, 2022, 5:40:05 AM10/5/22
to dcm4che
Setting is not get. Please provide other way for it.
Reply all
Reply to author
Forward
0 new messages