Migrate from Artera to Oracle Health.
2 documentation-derived translation patterns — what carries over and what to watch for. Cited to the Feature Parity Map; the audit tells you whether the move is worth it.
Artera ScheduleCare and Oracle Health both let patients self-book online against real provider availability and re-book from past visits, so a practice on Oracle can drop the standalone Artera ScheduleCare add-on and move scheduling into the Oracle Health Patient Portal Cloud Service: turn on portal self-service online scheduling plus 'Book again' from past appointments/favorites, with scheduled/rescheduled/canceled notifications and confirmation links via the patient's preferred contact method. Keep Oracle Health (the system of record where a self-booked slot becomes a real encounter and flows straight into pre-registration, intake, and check-in); cut Artera. Because the booking writes to the EHR's own scheduling, there is no external sync to maintain the way a third-party widget would need.
- Warning: Self-service online scheduling and 'Book again'/'Ask Oracle' navigation are tied to recent Patient Portal release trains (e.g. March 2026); confirm your org's portal version exposes them before retiring Artera.
- Warning: Oracle portal scheduling is login-first; confirm the path for new/unknown patients Artera could book so net-new self-scheduling volume is not lost.
- Warning: Re-create Artera's automated waitlist/earlier-slot backfill behavior in the Oracle workflow (or accept its loss) and verify slot availability and confirmation links fire before cancelling Artera.
- Warning: Move any branded ScheduleCare booking link on the practice website to the Oracle portal scheduling entry point so external scheduling traffic is not stranded.
Artera and Oracle Health both run secure, two-way patient messaging, so a practice on Oracle can retire the standalone Artera Harmony contract and move conversations into the Oracle Health Patient Portal Cloud Service (HealtheLife successor): patients message from the portal and inbound messages route to the specific provider or message pool by encounter relationship, where staff handle them in the EHR's message workflow on the same chart. Keep Oracle Health (the system of record where an inbound message can be reconciled into the chart and trigger orders or scheduling); cut Artera. The portal's Conversational Messaging, file attachments, conversation search, and send/receipt status cover the day-to-day texting Artera previously handled.
- Warning: Artera reaches patients over SMS/text/voice/email in their preferred channel including patients who never log in; the Oracle portal is login-first, so confirm portal enrollment and a notification path before cutting Artera or some patients lose contact.
- Warning: Conversational Messaging and the routing/pool features cited are tied to recent Patient Portal release trains (e.g. March 2026) — confirm your org is on a portal version that includes them before retiring Artera.
- Warning: Artera is multilingual (100+ languages); validate the Oracle portal's language coverage for your patient population before the cutover.
- Warning: Re-point EHR-triggered outreach (appointment prep, care-gap, follow-up) Artera fired via API/FHIR/HL7v2 onto Oracle-native portal messaging/notifications so those sends do not silently stop.