Appointment HL7 Interface to Trigger Outcome Surveys

Our application has the ability to send appointment and demographic information to the AAOE Empower platform based on activities taking place in the iScheduler.  As appointments are added, changed, deleted, etc... our application will generate a SIU HL7 File that will be sent to the AAOE Empower Platform automatically.

Appointment Type Setup

The AAOE Empower Outcome Survey Integration requires that the practice use specific types of appointments when scheduling.  These appointment types dictate which surveys are sent out.

Follow the steps found here to add the Appointment Types described below.

Appointment Type NameSurvey Type Sent Out
Surgery - Lt ArmPatient Outcome
Surgery - Lt ElbowPatient Outcome
Surgery - Lt Shoulder
Patient Outcome
Surgery - Lt Hip
Patient Outcome
Surgery - Lt Knee
Patient Outcome
Surgery - Lt Ankle
Patient Outcome
Surgery - Lt Foot
Patient Outcome
Surgery - Lt Hand
Patient Outcome
Surgery - Rt Arm
Patient Outcome
Surgery - Rt Elbow
Patient Outcome
Surgery - Rt Shoulder
Patient Outcome
Surgery - Rt Hip
Patient Outcome
Surgery - Rt Knee
Patient Outcome
Surgery - Rt Ankle
Patient Outcome
Surgery - Rt Foot
Patient Outcome
Surgery - Rt Hand
Patient Outcome
Surgery - BackPatient Outcome
Surgery - NeckPatient Outcome
New PatientPatient Satisfaction
New ComplaintPatient Satisfaction

Events that Trigger an HL7 Message

Within the iScheduler, if any of the following activities take place, a new SIU HL7 Message will be generated. 

iScheduler EventSIU HL7 Message TypeNotes
New appointment createdS12
Appointment rescheduledS13Date/Time changed
Appointment cancelledS15Status = Cancelled
Appointment DeletedS17
Patient is a No ShowS26

SIU HL7 Message Format

Message Header

MSHFieldValue Notes
1Field Separator
2Encoding Characters^~\&
3Sending ApplicationOfficeEMR
4Sending FacilityCompany Setting:  AAOE Practice ID
5Receiving ApplicationAAOE Empower
6Receiving FacilityAAOE
7Date/Time of MessageTimestamp when message was triggered
9Event TypeSee above trigger notes
10Message Control IDGUID for this message
11Processing IDBlank
12Version ID 2.3
13Sequence NumberBlank
14Continuation PointerBlank
15Accept Acknowledgement TypeAL
16Application Acknowledgement TypeAL

Scheduling Data

SCHField Value Notes
1Appointment IDiSalus unique appointment ID
2Filler Appointment IDBlank
3Occurrence Number1
5ScheduleResource ID ^ Resource Name
6Event ReasonBlank
7Appointment ReasonBlank ^ Chief Complaint
8Appointment TypeAppointment Type ID^ Appointment Type Description
9Appointment DurationAppointment duration in minutes
10Appointment Duration Units"Mins"

Patient Data

PIDFieldValue Notes
1Set ID1
2Patient IDiSalus chart number
3Patient IDiSalus chart Number
4Alternate IDOld Patient ID
5Patinet NameLast^First^Middle
6Maiden NameBlank
7Date of BirthYYYYMMDD
8GenderM, F, or U
9AiliasNick Name
11AddressStreet^City^State^Zip Code
12Country CodeUSA
13Phone and EmailHome Phone^^^Email Address

Provider Data

PV1FieldValue Notes
1Set ID1
2Patient ClassN
3Assigned Patient LocationBlank
4Admission TypeBlank
5Preadmit NumberBlank
6Prior Patient LocationBlank
7Attending Doctor

If a resource is connected to a provider…


If a resource is not connected to a provider


8Referring DoctorReferring NPI ^ Last ^ First

Resource Group Data

RGSFieldValue Notes
1Set ID1
2Segment Action CodeU
3Resource Group IDBlank

Appointment Resource Data

AIGFieldValue Notes
1Set ID1
2Segment Action CodeU
3Resource IDResource ID ^ Resource Name
4Resource TypeBlank
5Resource GroupBlank
6Resource Quantity Blank
7Resource Quantity UnitsBlank
8Start Date/TimeAppointment Date/Time (YYYYMMDDHHMMSS)
10Offset UnitsBlank

File Timing and Details

Timing:  Every 10 minutes, the application will check for new triggering events and generate a file as needed.

File Naming Convention: iSalus Database ID – AAOE Practice ID – Appointment ID – Unique ID.HL7

File Destination:  The file will be transmitted to AAOE via SFTP.