Allscripts Integration
- Get Started
- Release Notes
- Triggers
- Patient Channel
- Troubleshooting and FAQ
- Patient Facesheet
- Technical Specifications
- Insights & Analytics
- Collaborative Inbox
- Conversation Flows
- Campaigns
- Lines & Resources Requests
- Lines, Events, Resources
- SMS Basics
- Automations
- Referrals
- Add-Ons
- Users and Groups
- Platform Settings and Configuration
- Self-Rescheduling
- Recalls
- Marketplace
SIU Sample
MSH|^~\&|Enterprise|Enterprise|HL7ADT_OUT||20231124153153-0700||SIU^S12|3829961503310|P|2.3.1
SCH||2062957||||FU|FU|Follow Up Pulmonary|20|||||||Curley^Moe|||FAMILY MEDICINE|Curley^Moe||FAMILY MEDICINE|||Booked
PID|||410311^^^MRN||Test^Patient^R||19811112|Male|||||(999)6450000^^^^^999^6450000^^Mobile|||||6760455^^^Visit Number|553132132
PV1||Ambulatory|INTMED^^^HCC|Elective|||||||||||||||6760455^^^Visit Number|||||||||||||||||||||||||20231124102000-0700
AIS|||1998^IMPUL2^^^Follow Up Pulmonary|20231124102000-0700|||20
AIP|||703^Smith^Doc|Physician||20231124102000-0700|||20
Appointment Identifier: The appointment identifier sent in the SIU message should be the Allscripts Appointment ID.
Patient Identifier: The MRN sent in the SIU and ADT messages should be the Allscripts Patient ID.
NOTE: Artera requires the Allscripts Appointment ID and Patient ID. This is because the Allscripts SetAppointmentStatus API for appointment status writebacks requires these values. Allscripts' values of Patient Number and Encounter Number are not compatible with the API and should not be used. Even if your organization is not currently implementing writebacks, Appointment ID and Patient ID are still recommended in the event that writebacks are implemented in the future.