bi-directional interfaces

[Kevin Crist]

i am getting ready to set up an interface that will do patient scheduling. our HIS has been doing this but this new interface will take over. we will be sending adt’s from new interface to the HIS to get acct numbers and send it back. is there anything i should look for. any directions would be great. thanks

Topic

[Jim Kosloskey]

Kevin,

What I would do is to send the ADT over one connection (getting an acknowledgment back) and receive the Account Numbers over another connection (acknowlidging the account # message).

I would then route and reformat (if necessary) the Acct # message to the format needed by the ADT source.

I would keep this as asynchronous as possible.

Now if it is important that the source system not send another message until it has received the account number, that is another issue altogether.

email: jim.kosloskey@jim-kosloskey.com

[Vince Angulo]

We do something close to this in two connections like Jim describes, so it’s not what I’d call truly bidirectional.

Most of the logic is handled by the vendors for both systems.  Here’s how it works:

The Practice Management-Scheduling system has a unique pool of patient account numbers assigned so that we can instantly differentiate the PM encounters from our acute care visits in the HIS.

Nothing happens at scheduling, but at check-in the PM system generates an A04 with a patient account number from the assigned pool.

The HIS receives the A04 and creates a visit with PM-generated account number.

The HIS immediately echoes out an A08 that returns the HIS’ internal guarantor and subscriber ID #s, which we reformat in an xlate to comform to the PM system’s numbering convention.

The PM system files the HIS internal ID#’s as external ID#s for PM so that we can update Guarantor and Coverage information in both directions.  We don’t maintain visit info in both directions so the patient account number isn’t cross-referenced in this way.

Hope this helps.

[Author]

Replies