Good morning! I’m in a bit of a pickle and I’m hoping there’s a way out.
I have an interface that sends hundreds of thousands of messages a day, many of them duplicative information related to aperiodic vitals ORUs into our EMR. Basically, the machine from the vendor sends out the first message, let’s say at 05:00 and then resends the same value over and over again every minute, as different messages until the vitals are taken again, and then that value is resent again and again. It essentially makes aperiodic vitals values into periodic, which is clogging up our EMR with processing junk data.
The vendor can’t help, but I have an idea that may. I just don’t know how to implement it.
Basically, when the inbound ORU comes in from the vendor, I want to pull the vitals timestamp and the visit number from their respective fields and store them paired in a database. Then send the original ORU down it’s respective path to the EMR. Then when the next message comes in, compare the Visit Number on the database and then compare the timestamp. If it’s the same, suppress the message; if the timestamp is different, update the database with the new timestamp and then send the message to the EMR. I’d also need to clean up the visit numbers as time goes on so the database doesn’t get too full.
Any ideas? Or maybe a better way to handle the problem I’m not thinking of? Thanks!