Ingest: Parse ADT Messages

[chanskw]

Investigate parsing of ADT messages.
Do we want to parse the entire set of ADT? If not, what ADT information is useful in a Streams application?

[chanskw]

Initially, we should focus on the following messages for clinical monitoring:

ADT-A01 – patient admit
ADT-A02 – patient transfer
ADT-A03 – patient discharge
ADT-A04 -- Register a patient
ADT-A06 -- Change an outpatient to an inpatient
ADT-A07 -- Change an inpatient to an outpatient
ADT-A08 – patient information update
ADT-A10 -- Patient Arriving
ADT-A16 -- Pending Discharge
ADT-A28 -- Add person informaton

[chanskw]

We are using the ADT_XXX super structure from Hapi to parse any ADT message. For each ADT message, information from the following segments are extracted:

MSH
PID
PV1
EVN

ADT messages will be published as AdtEvent. This is the definition of AdtEvent:

type MessageInfo = rstring receivingApp, rstring messageType, rstring receivingFacility, rstring sendingFacility, rstring messageTs, rstring sendingApp;

type EventDetails = rstring eventType, rstring recordTs, rstring eventTs;

type Patient = list<rstring> alternateNames, list<rstring> alternateIds, rstring gender, rstring name, rstring dateOfBirth, rstring id, rstring status;

type Clinician = rstring name, rstring id;

type PatientVisit = rstring patientClass, rstring visitNumber, rstring priorLocation, rstring location, list<Clinician> attendingDoctors, list<Clinician> consultingDoctors;

type AdtEvent = MessageInfo msg, EventDetails evt, Patient patient, PatientVisit pv;

Is this sufficient to map patient to certain location and their clinicians? What other information maybe be needed?

[chanskw]

If you want to try out the service, information is here: https://github.com/IBMStreams/streamsx.health/tree/develop/ingest/hl7

[chanskw]

This is completed.