NexHealth Integration
Discover how to connect NexHealth with Ours Privacy to track patient interactions and clinical events while ensuring HIPAA compliance and data privacy.
Use this page to connect NexHealth to Ours Privacy so booking activity joins the rest of the patient journey. There are two ways to do it, and they answer different questions, so most practices end up using both.
Option 1: Track the Booking Flow in the Browser
NexHealth lets you embed the Ours Privacy Web SDK, or use the Ours Privacy Tag Manager, inside the booking experience it serves. This is what shows you the funnel: how many patients started a booking, where they dropped off, and which campaign brought them.
Because this runs in the patient's browser, it sees what happens on the pages NexHealth renders. It will not see a booking that staff creates directly in NexHealth, or an appointment later marked attended or a no-show.
Option 2: Receive Appointment Outcomes by Webhook
NexHealth can send appointment activity to a webhook source server-side. This is what confirms outcomes: the appointment was booked, the patient attended, or the patient did not show up.
What to know before you start:
- Subscribing to NexHealth webhooks is done through their developer tooling, not a settings screen, so plan on a short setup with someone comfortable at a command line. Your account representative can run this with you.
- You need NexHealth developer access. Confirm with NexHealth which plan this requires for your account.
- Expect the outcome events, not the intermediate ones. The webhook covers the ends of the appointment lifecycle: booked, attended, and no-show. The steps in between are what Option 1 is for.
Map the incoming activity to Standard Healthcare Events so it reports alongside every other source.
Which to Use
- Measuring campaign performance and booking drop-off: Option 1.
- Reporting attendance, no-shows, or sending appointments back to ad platforms as offline conversions: Option 2, because those outcomes only exist server-side.
- Both: the browser events show where patients fall out of the funnel, and the webhook confirms which appointments were real.
Next Steps
- Webhooks: configure the webhook source.
- Standard Healthcare Events: the event names to map to.
- Connect Any Patient Scheduling Platform: the same pattern for other booking platforms.
- Visitor Identity and Matching: how a webhook booking joins the original web session.
For further assistance, contact support@oursprivacy.com.
How is this guide?