Artera HL7 Integration Specification - Orders - ORM
- Get Started
- Troubleshooting and FAQ
- Release Notes
- Patient Channel
- Triggers
- Technical Specifications
- Patient Facesheet
- Insights & Analytics
- Conversation Flows
- Campaigns
- SMS Basics
- Inbox
- Lines & Resources Requests
- Lines, Events, Resources
- Referrals
- AI Agents
- Add-Ons
- Users and Groups
- Platform Settings and Configuration
- Self-Rescheduling
- Recalls
- Artera Harmony Federal Edition
- Marketplace
Patient Matching
Due to the variability of patient spellings and risk of mistyping, Artera performs patient mapping based on the external application’s patient identifier sent over the interface. Artera will store this identifier upon patient creation and use it as matching criteria for any future messages.
This information should be placed according to HL7 2.3 standards and will be accepted in either the PID.2 or PID.3 segment of the message.
Incoming Integration (to Artera)
ORM – Order Messages
ORM messages keep Artera synchronized when important order changes occur within your EMR.