Nightly Discharge Question

[Keith McLeod]

If I create an interim thread in its own process for to direct from the source to this interim thread ADT_A03 messages where I do a disposition of OVER to move the message from the Outbound TPS to the Inbound tps and then route back to the original destination.  The inbound arrow on the monitor to this thread will be red while processing the ADT_A03 nightly discharge messages.  I have a proc in place to regulate the passing of these messages back to the original destination at a rate of 1 per second.  It appears that this allows normal messages to flow without delay.  I do both change the priority of the message and do a 1 second sleep on the tps inbound of this interim thread.  What is the down side to this?  Any one provide some insight? Thanks….

Topic

[Mark Thompson]

We are using a similar set-up for small X12 messages querying a web service.  It is working very well.  If the web service is not available we route the message to a “delay” thread (running in its own process) to be retried later.

There is an easier solution for our HL7 interfaces.  We just write the message to a file and let fileset/local pick it up at the desired rate.  X12 messages track lots of stuff in metadata that gets lost when the message is written to a file.  That’s why we build the delay thread.

- Mark Thompson
HealthPartners

[Author]

Replies