Orders or Recalls HL7 Specifications
If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.
- Get Started
- Patient Channel
- Patient Facesheet
- Collaborative Inbox
- Lines & Resources Requests
- Lines, Events, Resources
- Platform Settings and Configuration
- Users and Groups
- SMS Basics
- Troubleshooting and FAQ
- Conversation Builder
- Release Notes
- Technical Specifications
Table of ContentsIntroduction VPN and Communication Protocol Patient MatchingIncoming Integration (to Artera)
This document defines the specifications for full integration with the Artera application using HL7 interface standards. Please note that Artera supports a wide range of integration methodologies depending on your Practice Management (PM) and Electronic Medical Record (EMR) system. For more information on HL7, please refer to the Health Level Seven website: http://www.hl7.org
Phase 1: Patient Recalls to Artera
Establish VPN Tunnel
- Connect interface engines
Live Data Feeds to Artera from Customer
- One-Way Recalls (HL7 ORM)
VPN & Communication Protocol
Artera will provide all prospective clients with the Artera VPN Template. Please fill this out as soon as your team is able. A completed form is required before moving forward with any significant integration discussions.
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 - Orders, also known as Recall Messages
ORM messages keep Artera synchronized when important order changes occur within your EMR. Artera will consume messages for new, modified, completed and canceled orders/recalls.
Artera’s core system will only accept ORM messages for orders/Recalls whose location(s) are properly mapped to an Artera Practice. If only a subset of departments, providers, or locations are using Artera, only messages for those resources will be processed through the interface. Any other message received will be filtered and ignored.
Artera is typically configured to use the following ORM messages, any other messages transferred might be filtered and ignored unless otherwise specified during the integration process.
ORM^O01 - Transmit information about an order.
Complex Data Elements