Value Mappings
- 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
Table of Contents
Appointment Statuses Patient Language Patient SexOptional - Portal Enrollment StatusOptional - Patient EthnicityOptional - Patient RaceEpic Only - Visit ModesAppointment Statuses
Technical Importance
Appointment Statuses are used as filters and triggers for different Automations.
A client value can only be mapped to one Artera value. By default, Artera looks for Appointment Statuses in SCH25.1.
Patient Language
Technical Importance
Patient Language Preferences allow Artera to deliver Automations in the patient’s preferred language if the Automation has been translated to that language.
A client value can only be mapped to one Artera value. By default, Artera looks for language preference in PID15.1. For any languages that Artera does not support, or in which the Automation has been translated to, the patient will receive their communication in English.
Patient Sex
Technical Importance
Patient Sex can be used as a filter for different Automations. This allows for specific patient populations to receive more targeted messaging based on sex.
A client value can only be mapped to one Artera value. By default, Artera looks for Patient Sex in PID8.1.
Optional - Portal Enrollment Status
Technical Importance
Patient Portal Enrollment Status can be used as a filter for different Automations. This allows for specific patient populations to receive more targeted messaging and direct them to your Patient Portal for information, or encourage them to sign up for a Portal account.
A client value can only be mapped one Artera value. How Artera captures Portal Enrollment Status is unique to the EMR and depends on your Statement of Work (SOW). Connect with your Artera Technical Project Lead for any questions.
Optional - Patient Ethnicity
Technical Importance
Patient Ethnicity is not currently used in Artera and therefore is an optional field to send. However, future product development may include features that utilize a patient’s ethnicity to support population-based messaging.
Please provide all potential patient ethnicity values in your EMR. A client value can only be mapped one Artera value. By default, Artera looks for Patient Ethnicity in PID22.1.
Optional - Patient Race
Technical Importance
Patient Race is not currently used in Artera and therefore is an optional field to send. However, future product development may include features that utilize a patient’s race to support population-based messaging.
Please provide all potential patient race values in your EMR. A client value can only be mapped one Artera value. By default, Artera looks for Patient Race in PID10.1.
Epic Only - Visit Modes
Technical Importance
In recent versions of Epic, Visit Types no longer specify the Mode (In-Person, Telehealth, or video) in which the patient's visit will occur. The Mode of the visit is captured separately from the Visit Type (New Person, Follow Up, etc).
In order for Artera to provide targeted patient messaging for the different Modes in which a visit could take place, this information must be sent in an OBX segment. Please provide all potential Visit Mode values. An Epic value can only be mapped to one Artera value. By default, Artera looks for the Visit Mode value in OBX5.1 when the OBX segment has a 'TELEHEALTH MODE OF VISIT' tag in OBX3.2.