EHR and PMS Integrations

Connect appointment, attendance, and revenue outcomes from your EHR or practice-management system (PMS) to the same patient journey data you collect on your website. Once the data arrives in Ours Privacy, you can use it for attribution, funnels, conversion analysis, and approved downstream destinations.

Each EHR and PMS exposes data differently. We choose the connection path that fits your system, map the selected activity to Standard Healthcare Events, and connect the outcomes to the patient's web journey.

Why Connect EHR and PMS Data

• Measure the outcomes that matter. Connect booked appointments, attendance, cancellations, and revenue to the campaigns and pages that drove them.
• Use one event model across your stack. Standard event names keep your EHR, website, reporting, and destinations aligned.
• Make lower-funnel data useful. Use EHR and PMS outcomes in Attribution, Web Analytics, and your data warehouse.
• Control downstream delivery. Use event allow lists and mappings to decide which approved signals reach each destination.

How an EHR Connection Works

1. Choose the connection path. Depending on the interfaces your system exposes, this may be a FHIR or HL7 connection, a webhook, your backend using the Ingest API, or a workflow automation platform.
2. Map the activity that matters. Translate appointments, attendance, cancellations, and revenue into Standard Healthcare Events.
3. Match the outcome to the journey. Use a stable patient or lead identifier so server-side outcomes connect to the same person as their website activity.
4. Use and govern the data. Analyze the events in Ours Privacy, then allow-list and map only the signals you want to forward downstream.

FHIR and HL7 Connections

The primary path for EHR and PMS data is a connection to the interfaces your system already exposes: a FHIR API, an HL7 v2 feed, or a vendor API your organization can authorize. Ours Privacy reads the appointment, attendance, and revenue activity you approve, using standard healthcare interoperability tooling for the EHR-facing work, and maps it to standard events.

This lets each organization's EHR data model map to the same reporting contract. What you can measure depends on your EHR deployment, the resources and message types it exposes, the events you need, and the data you authorize for the connection.

Important: Connecting an EHR for measurement does not automatically include writing data back to that EHR. Write-back is a separate use case that is scoped with its own data flow and permissions.

Other Connection Paths

Systems can also send activity through webhooks, your own backend, or workflow automation. See Choose an EHR or PMS Connection Path for when each option fits and what information to prepare.

What You Can Measure

Once your EHR or PMS activity uses the standard schema, you can:

• Measure which sources, campaigns, and landing pages lead to booked and completed appointments.
• Build funnels from inquiry through booking, attendance, cancellation, or no-show.
• Compare conversion rate and revenue across campaigns, locations, providers, and service lines.
• Attribute revenue to the marketing journey that preceded it.
• Forward approved conversion signals to advertising, analytics, CRM, and warehouse destinations.

The Standard Healthcare Events reference defines the appointment lifecycle and revenue events. Attribution and Conversions and Funnels explain the reports that use those events.

Find the Right Connection Path

Start with the EHR and PMS Support Matrix to find your system and its typical connection mechanism, including Epic, Oracle Health (Cerner), athenahealth, eClinicalWorks, and specialty platforms. Choose an EHR or PMS Connection Path then covers the routes in detail and what to bring to an integration assessment.

If your system is not listed, that usually means no customer has asked for it yet rather than that it cannot connect. The support matrix includes an integration request path with the details that make a request actionable.

Key Resources

• EHR and PMS Support Matrix: find your system and how it connects, or request one that is not listed.
• Choose an EHR or PMS Connection Path: compare FHIR and HL7, webhook, Ingest API, and workflow automation routes.
• Send EHR Data From Your Data Warehouse: use Snowflake, Databricks, or BigQuery as the source.
• Connect Any Patient Scheduling Platform: connect the booking surface patients touch.
• Standard Healthcare Events: the event and property contract for the patient journey.
• Visitor Identity and Matching: connect server-side outcomes to website activity.
• Allow Listing Events: control which events can reach a destination.
• Data Mapping: transform approved data for each destination.

Need Help?

Contact support@oursprivacy.com for help with your existing connection, or contact your account representative to assess a new EHR or PMS.