Has anyone seen unpredictable results displaying messages from SMATDB?
I have a test interface that’s storing ADT in one DB and corresponding ACKs in another.
When I display all messages (in time saved order) with both DBs selected, I expect to see each message displayed followed by its corresponding ACK.
But – sometimes – I’ll see several hundred messages listed with no corresponding ACKs. Those several hundred messages might span 10-15 minutes.
I’m certain that I’m sending ACKs for each received ADT message, so this behavior is confusing and concerning at the same time.
We’re currently running 19.1 on RHEL.
Jeff Dinsmore
Chesapeake Regional Healthcare