Troubleshooting HL7 connections
Fix a disconnected agent, a patient that receives nothing, rejected messages and duplicates.
Find the symptom, then follow the fix.
| Symptom | Likely cause | Fix |
|---|---|---|
| The agent shows disconnected | The agent is stopped, or the host cannot reach Ovok. | Restart the agent. Check outbound HTTPS (443) to api.sandbox.ovok.com. |
| Nothing arrives for a patient | The patient has no MRN in the hospital's system. | Add the identifier, then resend. |
| The hospital rejects messages | The hospital answers AE or AR. | Read the reason with their analyst and fix the mapping. |
| Duplicates | A retry after a lost acknowledgement. | Drop a repeated control id. |
The agent shows disconnected
- Check that the agent is running on the hospital's host, and restart it.
- Check that the four values match the connection:
baseUrl,clientId,clientSecret,agentId. - Check that the host reaches
api.sandbox.ovok.comon port 443, and that no proxy blocks WebSockets. - If the connection was deleted or remade, use the new credentials. Old ones stop working.
- If the receiver is unreachable from the agent, read the agent's own log on the host.
Nothing arrives for a patient
The Patient needs an identifier whose system is the MRN system of the connection. Add it, then resend the missed Observations.
Also check that the Observation has a numeric value coded in MDC, LOINC or SNOMED CT, and that it matches the connection's criteria.
The hospital rejects messages
An AE or AR answer means the hospital's system refused the message. A retry gets the same answer.
- Ask the hospital's analyst for the reason.
- Compare the message with the reference: codes, units, identifiers.
- Send a test reading again after the hospital changes its side.
Duplicates
A retry after a lost acknowledgement resends the same message. MSH-10 is the Observation id and stays the same, so ask the hospital to drop a message with a control id it has already accepted.
See also
Last updated on