Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Handling ORU^R31 and ORU^R32 #86

Open
PPFH opened this issue Jul 21, 2022 · 0 comments
Open

Handling ORU^R31 and ORU^R32 #86

PPFH opened this issue Jul 21, 2022 · 0 comments

Comments

@PPFH
Copy link

PPFH commented Jul 21, 2022

Hello,
In our project we encountered a device sending ORU messages with Event Triggers R31 and R32. The device also expects from the HL7 Server a default ACK in response to ORU message and then a ACK^R33 message.

Example of Server<->Device communication:

LIS-HL7 Server      -----    Device
                    <----    ORU^R32
 ACK (ORU^R32)      ---->
 ACK^R33            ---->  
                    <----    ACK (ACK^R33)

I'm not a HL7 expert but I read that triggers R31, R32, R33 have been introduced in v2.5 or later.
The device ORU message's MSH declares HL7 v2.4: clearly this is an "out of standard" protocol implementation.

We are using Hapi HL7 v2.3. Unforntunately I see that those event triggers are not handled by your library yet.
Is there an easy way to handle those messages and to send a message (ACK from HL7 Server to device) without expecting any response?

Note: I must say that I actually found a way to do part of the job (handling ORU^R31 and ORU^R32), however it's far to be a clean solution (it's just a workaround but it works).

Thank you very much,
Andrea

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant