Healthcare API

The Unified Healthcare API enables developers and product managers to access clinical and scheduling data from electronic health record (EHR) and practice management systems through a single, standardized interface. Retrieve patients, practitioners, locations, appointments, open slots, encounters, conditions, allergies, medications, observations, and immunizations from Epic, Oracle Health, athenahealth, MEDITECH, NextGen Healthcare, Veradigm, DrChrono, Elation Health, Tebra, Cliniko, Halaxy, EMIS, and other healthcare platforms — all with one API.

What is the Unified Healthcare API?

EHR and practice management platforms like Epic, Oracle Health, and athenahealth each have unique APIs with different authentication methods, data models, and endpoints. Many expose HL7 FHIR R4, but each vendor implements a different subset of resources, search parameters, and extensions, and many smaller practice management systems use their own REST APIs entirely. The Unified Healthcare API normalizes these differences into a simplified model mapped from FHIR R4, allowing you to build once and support the systems your healthcare customers already use, without maintaining separate integrations for each provider.

Healthcare integrations represent people as patients and practitioners, places of care as locations, scheduling as appointments and bookable slots, and the clinical record as encounters, conditions, allergies, medications, observations, and immunizations, each linked back to its patient.

Key Benefits for Developers

• Single Integration: Write code once to support multiple EHR and practice management platforms — no need to learn each vendor's FHIR profile or proprietary API
• Normalized Data Models: Work with consistent patient, appointment, and clinical-record structures across all platforms, with standard code systems (LOINC, SNOMED CT, RxNorm, ICD-10, CVX) preserved as codings
• Real-Time Data Access: Every request hits the source API live with no caching, ensuring you always have up-to-date schedules and records
• Zero Maintenance: No need to track API version changes or deprecations across multiple healthcare platforms
• Faster Development: Ship healthcare integration features in days instead of months of integration work

Benefits for Product Managers

• Multi-Platform Support: Let clinics, practices, and health systems connect the EHR they already use without custom development
• Competitive Advantage: Launch with support for major EHR platforms while competitors build integrations one at a time
• Customer Flexibility: Read patient records and book appointments from a single interface regardless of the practice's software
• Reduced Time-to-Market: Get patient-facing and scheduling features to market quickly without waiting for engineering to build multiple integrations
• Scalable Product Strategy: Easily add new healthcare platforms as customers request them without significant engineering resources

Healthcare Data Objects

The Healthcare API provides access to the following standardized objects:

• Patients: Demographics with name, gender, birthdate, deceased status, emails, telephones, address, preferred language, business identifiers such as an MRN, and primary care practitioners (practitioner_ids).
• Practitioners: Doctors, nurses, and other providers with name, title, gender, contact details, identifiers such as an NPI, specialties, qualifications, languages, and the locations where they provide care (location_ids).
• Locations: Clinics, hospitals, departments, and other places of care with name, description, managing organization, address, telephones, coordinates, identifiers, and a parent_id for locations nested within another.
• Appointments: Booked visits with patient, practitioners, location, occupied slots, status (proposed, pending, booked, arrived, checked in, fulfilled, cancelled, no-show, waitlist), start and end times, service types, reasons, and cancellation reason.
• Slots: Bookable availability on a practitioner's schedule at a location, with status (free, busy, busy-unavailable, busy-tentative), start and end times, service types, and whether the slot is overbooked.
• Encounters: Visits and admissions with patient, practitioners, location, the appointment that scheduled them, conditions addressed, status, class (ambulatory, emergency, inpatient, observation, home health, virtual), reasons, and start and end times.
• Conditions: Problems, diagnoses, and health concerns with codings, clinical status, category, and onset, resolution, and recorded dates.
• Allergies: Allergies and intolerances with substance codings, clinical status, category (food, medication, environment, biologic), criticality, reaction manifestations, and onset date.
• Medications: Medication orders and prescriptions with codings, status, dosage instructions, refill count, and authored, start, and end dates.
• Observations: Lab results, vital signs, and other measurements with codings, status, category, numeric or text value and unit, interpretation, reference range, and components such as systolic and diastolic blood pressure.
• Immunizations: Administered vaccines with codings, status, administration date, lot number, and expiration date.

Clinical records link to their patient through patient_id, and to the encounter and practitioner that recorded them through encounter_id and practitioner_id. Each integration supports the objects and write operations its vendor documents; see the integration's support matrix for details.

Common Use Cases

Online Appointment Booking

Build patient-facing scheduling tools that list practitioners and locations, show open slots, and book, reschedule, or cancel appointments directly in the practice's EHR — without staff re-keying bookings into each system.

Patient-Facing Health Apps

Create patient portals and companion apps that display a patient's conditions, allergies, medications, lab results, and immunizations, using standard codings so the same app works across every connected EHR.

Care Coordination & Referrals

Share a patient's clinical summary between providers. Pull encounters, active problems, and current medications to prepare referrals, care plans, and handoffs across organizations that use different systems.

AI Clinical Assistants

Build AI agents that read encounters, observations, and medication lists to summarize patient history, prepare visit notes, flag abnormal results, and answer questions about a patient's record.

Remote Patient Monitoring

Write vital signs and device readings back to the EHR as observations where the platform supports it, and read the patient's existing results and reference ranges to put new measurements in context.

Healthcare Analytics & Reporting

Pull scheduling and clinical data into analytics dashboards and data warehouses. Report on appointment volume, no-show rates, provider utilization, and population health across practices and platforms.

Why Use a Unified Healthcare API?

Traditional Approach:

• Build separate integrations for each EHR and practice management platform
• Learn multiple authentication systems, including SMART on FHIR launch flows and vendor-specific OAuth
• Map each vendor's FHIR profile or proprietary schema to your own model
• Monitor and update integrations when any platform deprecates or changes their API
• Handle platform-specific rate limits, pagination, and search parameters

With Unified Healthcare API:

• Integrate once with a single API that works across healthcare platforms
• Use one authentication flow for all platforms
• Work with normalized patient, scheduling, and clinical-record objects
• Automatic handling of API changes, rate limits, and platform-specific differences
• Consistent list filters such as patient_id, practitioner_id, and location_id across platforms

Integration Scenarios

For Digital Health SaaS Applications

Add "Connect Your EHR" features that work with supported healthcare platforms. Build scheduling, intake, patient engagement, or telehealth products without building separate integrations for each provider.

For AI & Automation Tools

Create AI-powered assistants that read patient, encounter, and clinical data, then summarize records, prepare documentation, and automate routine work across platforms using a single, consistent API interface.

For Analytics & Population Health Platforms

Pull scheduling and clinical data from connected platforms into your data warehouse or analytics tool. Create unified utilization and outcomes reports without building multiple data pipelines.

For Remote Monitoring & Device Platforms

Connect device readings and patient-reported data to the patient's record. Keep clinicians working in their own EHR while your platform supplies the measurements.

Real-Time, Live Data

Unlike other integration platforms that cache data or run periodic sync jobs, the Unified Healthcare API provides real-time access to healthcare data. Every API request hits the source platform directly, ensuring you always have the most current schedules, appointments, and clinical records.

This real-time architecture is ideal for:

• Booking flows that need current slot availability
• Front-desk and check-in tools that rely on today's appointment status
• Clinical dashboards displaying the latest results and vitals
• AI applications that need fresh data for analysis and recommendations

Privacy & Security

Unified.to never stores your customers' healthcare data. All requests are stateless and pass through to the healthcare platforms directly. Traffic is regionalized (US/EU/AU) to comply with data residency requirements.