Choose an EHR or PMS Connection Path

Compare FHIR and HL7, scheduling platform, data warehouse, webhook, and Ingest API paths for sending appointment and revenue outcomes from an EHR, PMS, or scheduling tool to Ours Privacy.

Use this page to choose how your EHR, practice-management system, or patient scheduling platform sends appointment, attendance, and revenue outcomes to Ours Privacy.

Where the data comes from matters less than you might expect. Whether the record starts in an EHR, a scheduling platform, or a table in your data warehouse, every path maps the selected activity to the same Standard Healthcare Events and identifies it against the same patient journey. Pick the path with the interfaces and access you already have.

Choose a Connection Path

The paths below are listed in the order we usually evaluate them. Start with a direct connection to the EHR or PMS, and move down the list only when the interfaces or your team's capacity rule it out.

FHIR or HL7 Connection

Start here when your EHR or PMS exposes a FHIR API, an HL7 v2 feed, or a vendor API that your organization can grant access to. This is the primary path for EHR and PMS data, and it is how most healthcare systems connect.

Ours Privacy reads the appointment, attendance, and revenue activity you authorize, using standard healthcare interoperability tooling for the EHR-facing work, and maps it to standard events. What you can measure depends on the resources and message types your deployment exposes, such as appointment resources, encounter or visit status, and billing or claim activity.

Patient Scheduling Platform

Many organizations book through a dedicated scheduling platform rather than the EHR itself. If bookings originate there, connect the scheduling platform instead of, or alongside, the EHR. See Connect a Patient Scheduling Platform.

Webhook Source

Use a webhook source when your system can send appointment, patient, or status-change notifications as they happen. Ours Privacy receives the payload and maps it to an event and visitor identity.

Data Warehouse or Data Lake

If appointment, attendance, and revenue data already lands in Snowflake, Databricks, BigQuery, or a data lake, use that as your source of record instead of building a second EHR integration. This is often the fastest path, because the modeling and cleanup work is already done, and it is a good fit for attendance and revenue that settle late.

See Send EHR Data From Your Data Warehouse for how to schedule the send, handle late-arriving revenue, and avoid double-counting.

Ingest API

Use the Ingest API when your engineering team controls a backend service or integration layer around the EHR or PMS. Your service sends selected outcomes directly to Ours Privacy.

Workflow Automation

Use workflow automation when your operational tools are already connected through an automation platform. The workflow forwards selected activity to Ours Privacy without adding tracking code to each tool.

Important: An EHR name alone does not determine the connection method. Two organizations using the same EHR can expose different interfaces, fields, event types, and access permissions.

Map EHR Activity to Standard Events

Your system's raw records and status values become a small, consistent set of patient-journey events:

Confirmed appointment: map to appointment_booked for booking conversion and campaign measurement.
Appointment confirmation: map to appointment_confirmed when you need another booking-funnel step.
Completed visit or intake: map to appointment_completed for attendance and show-rate analysis.
Missed or cancelled appointment: map to appointment_no_show or appointment_cancelled for leakage analysis and operational reporting.
Rescheduled appointment: map to appointment_rescheduled to keep one lifecycle connected without double-counting.
Payment or recognized revenue: map to purchase or revenue_recognized for revenue and attribution reporting.

Use the Standard Healthcare Events reference for the recommended properties, including appointment ID, service line, provider, location, and revenue value.

Prepare for an Integration Assessment

Bring these details when you evaluate a new EHR, PMS, or scheduling platform connection:

The system name, deployment, and available integration method, such as HL7, FHIR, API, or webhook.
Whether the data you need already lands in a warehouse or data lake, and who owns those tables.
The appointment, attendance, revenue, and other outcomes you want to measure.
The stable patient or lead identifier that can connect backend outcomes to website activity.
The data fields that should be available for reporting and the destinations that should receive approved signals.
Whether you need EHR write-back. This is separate from bringing EHR data into Ours Privacy for measurement.

Use the Data After It Arrives

Standard events give the same lower-funnel outcomes a consistent meaning across Ours Privacy:

Attribution connects conversions and revenue to marketing sources and campaigns.
Conversions and Funnels shows booking and attendance drop-off.
Visitor Identity and Matching explains how server-side outcomes connect to website activity.
Allow Listing Events and Data Mapping control what reaches each downstream destination.

Next Steps

EHR and PMS Integrations: overview of the patient-journey measurement flow.
Standard Healthcare Events: event names and properties to send.
Webhooks: configure a webhook source.
Ingest API Integration: send events from your backend.
Keragon: use workflow automation to send healthcare-system activity.