HL7 messages to BDI with PDF file path

[Jennifer Higbie]

The engine is receiving HL7 messages with a file location that I’m forwarding to Horizon Patient Folder.  However, the HL7 message is processed before Phillips actually writes the image that the HL7 message is referencing.  Is there a way to slow down or delay the message so that the image can be written?

Thank you for your help!!

Jennifer

Topic

[Jerry Tilsley]

I have had to handle this type of transaction myself.  My approach is to write the message off to a SQLite database that contains a column indicating if the message has been sent or not.

Then I use a UPoC protocol thread to query the database for messages that have not been sent.  I loop through these messages and check to see if their associated image is present.  If the image is present I send the message on to the destination and update the table indicating it has been sent.  If the image is not present I simple skip over that record and process it again the next time around.

You can have this UPoC check as frequently or infrequently as you desire.

Thanks,

Jerry

[James Cobane]

It seems like the Philips system shouldn’t be sending out the HL7 with the file location information until it actually writes the file; is there configuration on the Philips side to control this?  

Jim Cobane

Henry Ford Health

[Jennifer Higbie]

Apparently if multiple studies are acknowledged at the same time by the techs on the Philips system, the delay only applies to the first message in the batch and not individual studies.

My original search criteria wasn’t finding any hits, but I’ve since found multiple posts regarding this issue and have decided to use a tps proc with a sleep time in it .  I have isolated the thread in it’s own process and will see if that resolves the issue without holding up other messages and other systems.

Thanks for your responses!

[Author]

Replies