Visit Methods Automation Filters
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 ContentsVisit Methods in ArteraSetting Up Visit MethodsIntegrationAutomationsDefault AutomationsPractice Automations
Organizations that have enabled Epic Visit Modes can use this Visit Mode information within Artera to send unique Automations, filter patient lists, and even display the Visit Method on the Patient Facesheet.
This minimizes the total number of visit types, making it easier for Artera admins to build and maintain provider schedules. Depending on your visit type build and how you have configured Artera Automations, this can drastically reduce the amount of time needed to set up and maintain Automations for Telehealth and video visits.
Visit Methods in Artera
Once your Visit Methods have been mapped into Artera, you will be able to:
Use Visit Method as an Appointment Automation Restriction.
See the Visit Method as a tag on the upcoming Appointments tile in the Patient Facesheet.
Use Visit Method as a Filter on the Scheduled Patients view to refine the list of patient appointments displayed.
Setting Up Visit Methods
Setup requires additional integration work to ingest Visit Mode data from Epic to Artera in an HL7 OBX segment. Important: Please connect with your Customer Success Representative for additional informaiton.
Today, Artera supports mapping the different Epic Visit Modes to three standard Visit Methods:
It is likely that multiple Visit Modes in Epic will be mapped to the same Visit Method in Artera.
Implementing Visit Methods will likely allow you to reduce the overall number of Appoint Automations you have running at any one time, also reducing the required maintenance effort. You may find it easier to reimagine your existing Automation set up and start the build fresh, or you could simply add the Visit Mode option to an existing Automation and pause the Automations you will no longer need.
When creating Default Automations, Visit Method is set as a restriction within the Default Automation build. All other restrictions are configured at the Practice-level.
Configuring at the Practice-Level
When configuring your Default Automation at the Practice-level, you will add your Restrictions and your Restriction Statement will include the Visit Method details. Any changes to the Visit Method selected would need to be made at the Default-level.
When building Practice Automations, Visit Method is set as a Restrictions just like any other available within the build.