No mechanism in eScription for account/encounter moves?

That’s interesting to hear. We’re just starting an integration with eScription and certainly need the ability to move an account/encounter to a different person.

Here’s an excerpt from their ADT spec.

Trigger Events

Here are the types of HL7 ADT messages that eScription typically receives.

A01 Admit/visit notification

A02 Transfer a patient

A03 Discharge/end visit

A04 Register a patient

A05 Pre-admit a patient

A06 Change an outpatient to an inpatient

A07 Change an inpatient to an outpatient

A08 Update patient information

A11 Cancel Admit

A12 Cancel Transfer

A13 Cancel Discharge

A14 Pending admit for a patient

A17 Swap patient beds

A18 Merge patient information

A24 Link patient info

A28 Add person information

A31 Update person information

A34 Merge patient information

Has anyone investigated whether it would be acceptable to use the A36 or Z44 message to create an A11 Cancel Admit for the erroneous patient record, followed by either an A01 or an A08 to create the account number on the correct patient record?

Carol Gross

Sr. Data Analyst

Oklahoma State University Medical Center

We’ve been using eScription for several years. We currently integrate it with Epic. The list of message types that they “receive” is not necessarily a list of messages that they act upon. Basically for ADTs we’re limited to sending them only A08 and A11 messages.

When designing the integration you need to be aware that eScription will ACK all messsages with AA. They do not send AR or AE. Messages that they encounter that would normally be errored back to the engine are ACKed back with AA and then dropped into the bit bucket.

From the spec, it looks like PV1 is optional and, according to the excerpt below, they’ll be looking for encounter in PID:18.

Note: One of either PID:18 or PV1:19 is used to store the account number representing the patient visit.  eScription prefers that PID.18 be used.