Populating historical ADT on new interface

[Mike Strout]

I am turning on an ADT feed to a new system and they want a few weeks of historical ADT messages sent to the system before we go live, to make sure all patients in house have admissions or registrations.

I have historical SMAT files by day and have had no problems resending those messages to the inbound pre-tps side of the interface and limiting the destination thread to the new system.

My question is how do I best handle the last day of data? The best case scenario would be to stop the inbound ADT feed, grab the SMAT file for today, resend it to the new system and then restart the inbound feed. Of course, stopping the entire ADT feed is not a real good solution in a production environment.

My next thought was to simply hold the inbound messages for that particular thread, but if I am submitting the SMAT file pre-tps, won’t it get held too?

My last thought as I typed this up was to process the last SMAT file shortly after it cycles at midnight so the new file is tiny. The resend would be so quick, temporarily stopping the incoming ADT feed probably wouldn’t have major consequences.

What is the best practice for getting all historical messages processed and then the last day of messages, all in the correct order?

Mike

Topic

[Elisha Gould]

Depends on your setup.

Are your messages comming in from the third party system into the thread that you are processing on?

If so then you could change the port number temporarily and bounce the thread so that it wont connect, resend the smat, then change it back.

Otherwise if its from another cloverleaf site, you could hold the outbound of the other site and release once done.

Theres also the ability to resend with higher priority, so they are processed first, but its more prone to user error, if data is not all resent at the same time.

[Robert Kersemakers]

How about creating an extra, temporary thread to send the historical messages to the desired outbound thread? Could make things much easier.

Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

[Author]

Replies