EHR Integration Information

Unidirectional Integration

Purpose

The Stat HL7 Integration allows health centers to track patient flow at a patientand appointment-specific level of detail, allowing staff to know where patients are throughout the clinic, which patients have arrived, and how long those patients have been waiting. The integration allows analytics to review a specific patient visit based on the Patient ID, breakdown of cycle times by appointment type, and additional workflow analysis. The integration minimizes additional steps required from staff.

Narrative Description of Integration

At patient check-in, the health center's Interface Engine sends an HL7 message indicating the patient has arrived. This message is parsed and mapped to the appropriate department in the Stat system and the patient is placed in the "waiting room" of the Stat system. Staff are alerted that the patient has arrived via desktop & audible notifications. The patient visit is then tracked through the Stat system. Upon completion of the visit, the entire visit is logged to Stat reporting database, with the Appointment Id, Appointment Type, and Patient ID as identifying fields.

Required Fields

• Patient Name
• Practice/Facility ID
• DOB
• Patient ID
• Provider ID
• Resource ID
• Appointment Time
• Appointment Type/Description
• Appointment Status
• Appointment Id

Triggers & Filters

The health center's interface engine should trigger to send the message on patient arrival. The messages should be further filtered to only send when the following criteria are met:

• Appointment is in applicable departments
• Patient has arrived
• Appointment is in person (not a telephonic visit)

Stat Filtering & Mapping

Stat further filters and maps the messages as follows:

• Ignore messages where department or provider are not in the Stat system
• Ignore messages with an existing appointment ID currently in the Stat system
• Maps to Provider and Department in Stat system

Transport Method & Network Connectivity

Health centers typically communicate with Stat Interface Engine through a TCP/IP connection or SFTP connection.

Stat provides health center with whitelisted IP addresses for its Interface Engine.

Bidirectional Integration

Purpose

The Stat HL7 Integration allows health centers to track patient flow at a patient- and appointment-specific level of detail, allowing staff to know where patients are throughout the clinic, which patients have arrived, and how long those patients have been waiting. The integration allows analytics to review a specific patient visit based on the Patient ID, breakdown of cycle times by appointment type, and additional workflow analysis. The integration minimizes additional steps required from staff.

Narrative Description of Integration

At patient check-in, the health center's Interface Engine sends an HL7 message indicating the patient has arrived. This message is parsed and mapped to the appropriate department in the Stat system and the patient is placed in the "waiting room" of the Stat system. Staff are alerted that the patient has arrived via desktop & audible notifications. The patient visit is then tracked through the Stat system, which updates the patient location and appointment status in the EHR. Upon completion of the visit, the entire visit is logged to Stat reporting database, with the Appointment Id, Appointment Type, and Patient ID as identifying fields.

Typical HL7 Message Types

SIU S12 (appointment creation), S14 (appointment update), S15, (appointment cancellation), including the below fields:

• Patient Name
• Facility ID
• DOB
• Patient ID
• Resource ID
• Appointment Time
• Appointment Type/Description
• Appointment Status
• Appointment ID

Stat Filtering & Mapping

Stat filters and maps the messages based on the following fields:

• Appointment Status
• Facility ID
• Appointment Type
• Resource ID

Transport Method & Network Connectivity

Health centers typically communicate with Stat Interface Engine through a TCP/IP connection or SFTP connection.

Stat provides health center with whitelisted IP addresses for its Interface Engine.