EHR appointment status synchronization is best understood as a record ownership problem before it is a transport problem. The systems reviewed here do not share one synchronization model. OnCall Health describes two opposite configurations: the EHR as system of record, where appointment creations and updates flow into OnCall Health, or OnCall Health as system of record, where webhook requests push changes outward [1]. Scope Health documents a read-only sync that pulls the EHR schedule onto its calendar and never creates, moves, or cancels appointments in the EHR [2]. SyncTimes describes both unidirectional and bidirectional HL7 integrations, with the bidirectional variant updating patient location and appointment status in the EHR [3]. NexHealth markets a Synchronizer that reads and writes data directly to patient records without relying on EHR APIs [4]. Twilio's quick deploy app specifies event codes and integration directions for appointment status changes [5]. These are distinct architectural choices, not interchangeable features.
Record Ownership Determines Direction
The first decision is which system owns the appointment record. OnCall Health's guide frames this explicitly: if the EMR or EHR is the system of record, appointment creations and updates should flow from there into OnCall Health [1]. If OnCall Health is the system of record, creations and updates should flow from OnCall Health into the EMR or EHR [1]. This distinction changes which API endpoints and webhook configurations are relevant, and it changes where a status transition such as cancellation is initiated.
Scope Health takes a narrower position. Its documentation states that syncing only reads from the EHR, and that Scope never creates, moves, or cancels appointments in the EHR [2]. Appointments on an EHR-synced schedule cannot be edited in Scope; rescheduling, cancellation, or booking must occur in the EHR and appear in Scope on the next sync [2]. This is a one-way ownership model: the EHR remains authoritative for appointment state, while Scope consumes a read-only projection for scheduling and visit documentation.
Transport and Message Boundaries
Transport choices differ by vendor and integration direction. SyncTimes documents HL7 messages sent by the health center's interface engine at patient check-in, parsed and mapped to the appropriate department in SyncTimes [3]. The integration supports TCP/IP or SFTP connections, with whitelisted IP addresses provided for the SyncTimes interface engine [3]. The bidirectional variant updates patient location and appointment status in the EHR, while the unidirectional variant only places the patient in the SyncTimes waiting room [3].
Twilio's EHR Appointment Management Quick Deploy App specifies appointment events with integration directions. BOOKED flows from EHR to Twilio, CANCEL flows from Twilio to EHR as a patient cancellation request, CANCELED flows from EHR to Twilio as a notification, and RESCHEDULED flows from EHR to Twilio [5]. The guide states that EHR-to-Twilio events must be communicated in near real-time, typically using an HL7 interface engine because HL7 v2 messages are real-time push-based messages [5]. The app is explicitly intended for prototyping and testing purposes only, not production environments [5].
Choosing a Synchronization Pattern
Start by documenting which system owns appointment state. If the EHR is authoritative, a read-only sync like Scope Health's may be sufficient for calendar visibility, but it will not propagate status changes initiated in the secondary system [2]. If bidirectional updates are required, an HL7 interface engine or REST webhook flow must be configured with explicit event directions, as in SyncTimes or Twilio [3][5].
Then define the identifier mapping before any data flows. OnCall Health's metadata recommendation and SyncTimes' field mapping table both show that cross-system matching depends on a stable appointment ID [1][3]. Finally, test failure cases: duplicate messages, unmapped providers, and appointments outside the sync window. Scope Health, for example, only syncs the past 7 days through the next 120 days, so appointments outside that range will not appear [2].
Identifier Mapping and Metadata
Matching records across systems depends on stored identifiers. OnCall Health recommends including a reference to the associated EMR or EHR record in the metadata section of each OnCall Health appointment, and conversely placing the OnCall Health record ID in the EMR or EHR if that system can store metadata [1]. Without such a reference, the guide warns that finding the appointment to update requires less reliable means [1]. This is a practical constraint: status synchronization fails silently when the cross-system identifier is absent or inconsistent.
SyncTimes maps HL7 fields to SyncTimes fields through an input transformation table. Appointment ID from SCH-1.1 maps to EHRAppointmentID, Patient ID from PID-3.1 maps to MRNNumber, and Appointment Start Time from SCH-11.4 is reformatted from yyyyMMddHHmmss [3]. The interface engine ignores messages where department or provider are not in the SyncTimes system and ignores messages with an existing appointment ID currently in the SyncTimes system [3]. These rules prevent duplicate records but also mean that unmapped departments or providers will not appear in SyncTimes.
Deployment Boundaries and Unresolved Questions
Deployment boundaries affect what a synchronization claim can support. NexHealth states that the Synchronizer works independently from the patient software, with no vendor partnership required, and connects directly to the system without going through the vendor [4]. The marketing page lists many supported systems, including AdvancedMD, athenahealth, Tebra, and WebPT [4]. However, the documentation does not specify the mechanism by which the Synchronizer reads and writes data without EHR APIs, nor does it describe how status conflicts are resolved when two systems attempt to update the same appointment.
The SMART Scheduling Links specification addresses a different problem: slot discovery rather than appointment status synchronization. It describes publishers exposing available slots through static web hosting, with directories consuming slots via a bulk publish API and client scheduling applications finding open slots [6]. The specification maintains a separation between static file servers for scheduling links and stateful booking systems for stateful operations, with the booking portal responsible for initiating holds within the scheduling system's source of truth [6]. This architecture does not synchronize appointment status back to an EHR; it publishes availability snapshots.
A Hypothetical Validation Scenario
A useful validation scenario would test cancellation propagation across a bidirectional integration. Suppose a clinic uses an EHR as the system of record and a patient engagement platform as the system of engagement. A staff member cancels an appointment in the EHR. The integration layer should detect the CANCELED event and push it to the engagement platform, following the event direction documented by Twilio [5]. The engagement platform should then update its local appointment record and suppress any pending reminders.
The validation would check three properties. First, the cross-system identifier must match: the EHR appointment ID stored in the engagement platform metadata must equal the ID in the cancellation message [1]. Second, the status transition must be idempotent: sending the same cancellation twice should not create a duplicate record or an error state. Third, the direction must be respected: if the engagement platform is read-only, as in Scope Health's model, a cancellation initiated in the engagement platform should be rejected or ignored rather than written back to the EHR [2]. This scenario is a suggestion for testing, not a claim that any reviewed system has passed such a test.
Sources & references
- Synchronizing appointments between OnCall Health and your EMR/EHR · docs.oncallhealth.io
- Your Schedule and Push to EHR After Connecting | Scope Health · scopehealth.com
- SyncTimes Unidirectional HL7 Integration · help.stat.io
- NexHealth Synchronizer | Real-Time Sync for Practice Management Systems · www.nexhealth.com
- EHR Appointment Management App - EHR Integration Guide · twilio-cms-prod.s3.amazonaws.com
- Specification - SMART Scheduling Links v1.0.0-ballot · build.fhir.org
- NextGen Office Release Notes 2026-07-09 · successcommunity.nextgen.com
- [PDF] Integrated Scheduling Solution User Guide | VA.gov · www.va.gov