Our application has the ability to share data with the American Association of Orthopedic Executives (AAOE) Empower platform. This facilities the sending of appointment data to trigger patient outcome surveys. In future iterations, this will also allow quality data and other practice statistics to be shared.
In order for the AAOE Empower integration to work, a few things must be pre-configured. This article describes these requirements.
Product Setup
The AAOE Empower Integration product must be added to the practice. This must be completed by an Administrator at iSalus Healthcare.
Company Settings
The AAOE Empower Integration requires that the practice supply their AAOE Practice ID. This can be obtained by contacting your AAOE representative. Once you have the ID...
- Follow these steps to locate and update Company Settings.
- Locate the AAOE Empower Practice ID company setting.
- Set the value to the one provided by AAOE.
- Save
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 Name | Survey Type Sent Out |
|---|---|
| Surgery - Lt Arm | Patient Outcome |
| Surgery - Lt Elbow | Patient 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 - Back | Patient Outcome |
| Surgery - Neck | Patient Outcome |
| New Patient | Patient Satisfaction |
| New Complaint | Patient 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 Event | SIU HL7 Message Type | Notes |
|---|---|---|
| New appointment created | S12 | |
| Appointment rescheduled | S13 | Date/Time changed |
| Appointment cancelled | S15 | Status = Cancelled |
| Appointment Deleted | S17 | |
| Patient is a No Show | S26 |
SIU HL7 Message Format
Message Header
| MSH | Field | Value Notes |
|---|---|---|
| 1 | Field Separator | |
| 2 | Encoding Characters | ^~\& |
| 3 | Sending Application | OfficeEMR |
| 4 | Sending Facility | Company Setting: AAOE Practice ID |
| 5 | Receiving Application | AAOE Empower |
| 6 | Receiving Facility | AAOE |
| 7 | Date/Time of Message | Timestamp when message was triggered |
| 8 | Security | Blank |
| 9 | Event Type | See above trigger notes |
| 10 | Message Control ID | GUID for this message |
| 11 | Processing ID | Blank |
| 12 | Version ID | 2.3 |
| 13 | Sequence Number | Blank |
| 14 | Continuation Pointer | Blank |
| 15 | Accept Acknowledgement Type | AL |
| 16 | Application Acknowledgement Type | AL |
| 17-25 | Blank | Blank |
Scheduling Data
| SCH | Field | Value Notes |
|---|---|---|
| 1 | Appointment ID | iSalus unique appointment ID |
| 2 | Filler Appointment ID | Blank |
| 3 | Occurrence Number | 1 |
| 4 | Blank | Blank |
| 5 | Schedule | Resource ID ^ Resource Name |
| 6 | Event Reason | Blank |
| 7 | Appointment Reason | Blank ^ Chief Complaint |
| 8 | Appointment Type | Appointment Type ID^ Appointment Type Description |
| 9 | Appointment Duration | Appointment duration in minutes |
| 10 | Appointment Duration Units | "Mins" |
| 11-27 | Blank | Blank |
Patient Data
| PID | Field | Value Notes |
|---|---|---|
| 1 | Set ID | 1 |
| 2 | Patient ID | iSalus chart number |
| 3 | Patient ID | iSalus chart Number |
| 4 | Alternate ID | Old Patient ID |
| 5 | Patinet Name | Last^First^Middle |
| 6 | Maiden Name | Blank |
| 7 | Date of Birth | YYYYMMDD |
| 8 | Gender | M, F, or U |
| 9 | Ailias | Nick Name |
| 10 | Race | Code^Description |
| 11 | Address | Street^City^State^Zip Code |
| 12 | Country Code | USA |
| 13 | Phone and Email | Home Phone^^^Email Address |
| 14-40 | Blank | Blank |
Provider Data
| PV1 | Field | Value Notes |
|---|---|---|
| 1 | Set ID | 1 |
| 2 | Patient Class | N |
| 3 | Assigned Patient Location | Blank |
| 4 | Admission Type | Blank |
| 5 | Preadmit Number | Blank |
| 6 | Prior Patient Location | Blank |
| 7 | Attending Doctor | If a resource is connected to a provider… ProviderNPI^ProviderLast^ProviderFirst If a resource is not connected to a provider ResourceID^ResourceLast^ResoruceFirst |
| 8 | Referring Doctor | Referring NPI ^ Last ^ First |
| 9-54 | Blank | Blank |
Resource Group Data
| RGS | Field | Value Notes |
|---|---|---|
| 1 | Set ID | 1 |
| 2 | Segment Action Code | U |
| 3 | Resource Group ID | Blank |
Appointment Resource Data
| AIG | Field | Value Notes |
|---|---|---|
| 1 | Set ID | 1 |
| 2 | Segment Action Code | U |
| 3 | Resource ID | Resource ID ^ Resource Name |
| 4 | Resource Type | Blank |
| 5 | Resource Group | Blank |
| 6 | Resource Quantity | Blank |
| 7 | Resource Quantity Units | Blank |
| 8 | Start Date/Time | Appointment Date/Time (YYYYMMDDHHMMSS) |
| 9 | Offset | Blank |
| 10 | Offset Units | Blank |
| 11-14 | Blank | Blank |
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.
