Contact Us

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.

Please fill out the contact form below and we will reply as soon as possible.

  • WEBINARS
  • ARTERA ACADEMY
  • SUPPORT
  • RELEASES
  • STATUS PAGE
  • Home
  • Technical Specifications
  • Artera-Specific Features

Artera HL7 Integration Specification - Orders - ORM

Contact Us

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.

Please fill out the contact form below and we will reply as soon as possible.

  • Get Started
    Getting Help Post-Implementation
  • Release Notes
  • Triggers
  • Patient Channel
    Managing Appointments
  • Troubleshooting and FAQ
  • Patient Facesheet
  • Technical Specifications
    Artera Foundation Artera-Specific Features EMR Specifications
  • Insights & Analytics
    Insights Analytics Plus Self Service Analytics
  • Collaborative Inbox
  • Conversation Flows
  • Campaigns
  • Lines & Resources Requests
  • Lines, Events, Resources
  • SMS Basics
  • Automations
    Appointment Automations Inbound Message Automations Recall Automations Referral Automations
  • Referrals
  • Add-Ons
    Call-To-Text/Abandoned Calls Community Outreach
  • Users and Groups
  • Platform Settings and Configuration
    Settings Forms
  • Self-Rescheduling
  • Recalls
  • Marketplace
+ More

Table of Contents

Patient Matching Incoming Integration (to Artera) ORM Field Breakdown (to Artera)

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. 

ORM Field Breakdown (to Artera)

Legend

Field

Requirement

Notes

HL7 Field

Patient ID

Required

Used to uniquely identify patient

PID.2 or PID.3

First Name

Required


PID.5.2

Last Name

Required


PID.5.1

Middle Name

Optional


PID.5.3

Home Phone / Cell Phone

Required

Repeatable Segments Allowed

PID.13.1

Phone Identifier

Recommended

Repeatable Segments Allowed

PID.13.3

Alt Phone

Recommended

Used if patients home phone is landline (non-text enabled)

PID.14.1

Gender

Required


PID.8

Date of Birth

Required

Used for patient to access secure messages

PID.7

Email Address

Recommended


PID.13.4

SSN

Recommended

Used for patient to access Secure Messages

PID.19

Address Line 1

Recommended


PID.11.1

Address Line 2

Recommended


PID.11.2

City

Recommended


PID.11.3

State

Recommended


PID.11.4

Zip

Recommended


PID.11.5

Primary Language

Recommended

Used to identify which language to send messages in for patients

PID.15.1

Order ID

Required

Used to identify an Order

OBR.2.1

Order Event Type ID

Required


OBR.4.1

Order Event Type Name

Required


OBR.4.2

Order Location ID

Required


PV1.3.1

Order Location Name

Required


PV1.3.2

Order Creation Date/Time

Recommended


OBR.6.1

Order Due Date/Time

Required


OBR.27.4

Provider ID

Required


OBR.16.1

Provider First Name

Required


OBR.16.2

Provider Last Name

Required


OBR.16.3

Provider Degree

Recommended


OBR.16.4

Order Status

Required


ORC.5.1

orders hl7 orm

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Technical Specification Downloadable Templates
  • Orders or Recalls HL7 Specifications
  • Artera HL7 Integration Specification - Inbound ADT & SIU
© 2024 Artera. All Rights Reserved.
Privacy Policy | Terms of Service | Cookie Policy | Do Not Sell My Personal Information

Knowledge Base Software powered by Helpjuice

Expand