On-Kare
    Log inDemo
    Interoperability

    A platform that speaks your ecosystem's language

    84 exchange, API and patient-identity capabilities connecting On-Kare to your labs, pharmacies, public payers and existing systems.

    HL7 FHIRClinical exchange
    84interoperability capabilities
    RESTAPI
    Standards

    Supported exchange standards

    Each standard answers a concrete need: talking to a modern EHR, a legacy hospital system, an imaging platform or a connected device.

    HL7 FHIR clinical exchange

    HL7 FHIR

    FHIR resources for patients, appointments, observations, prescriptions and clinical documents, exposed through a REST API and consumable by third-party EHRs.

    Legacy HL7 v2 flow messaging

    HL7 v2

    Inbound and outbound ADT, ORU and ORM messages to talk to existing hospital systems without a disruptive migration.

    Imaging interoperability

    DICOM

    Connectivity with imaging platforms and integration of reports into the patient record for imaging-dependent specialties (ophthalmology, radiology).

    Remote monitoring device connectivity

    RPM / IoT

    Ingestion of readings from remote-monitoring devices (blood pressure monitors, sensors) feeding remote follow-up and risk triage.

    API

    An API control plane for your integrations

    Secure access to FHIR resources, real-time events and a test environment before going live.

    API authentication

    Access tokens and per-application permission control securing every call to the platform control plane.

    Event-driven notifications

    Webhooks triggered on business events (appointment, lab result, claim status) to keep your tools in sync in real time.

    API control plane

    Application access management, quotas and integration lifecycle for the technical teams of a multi-site network.

    Sandbox provisioning

    Provisioning of an isolated test environment to validate an integration before it goes live.

    api-example.ts
    // On-Kare REST API — Patient resource
    const response = await fetch(
      'https://api.on-kare.org/v1/patients',
      {
        method: 'GET',
        headers: {
          'Authorization': 'Bearer ${ACCESS_TOKEN}',
          'Accept': 'application/fhir+json',
        },
      }
    );
    const bundle = await response.json();
    Connectors

    Business connector families

    From patient identity to public payers, each connector covers one link of the care journey.

    Patient record and identity

    A single patient identity and identity federation (MPI) to match the same patient across multiple facilities or countries.

    Scheduling and capacity

    Slot and capacity synchronisation across sites for consistent appointment steering.

    Public payers and health insurance

    Dedicated connectors to national claims systems — for example the health-insurance gateways used across several Asia-Pacific markets.

    Lab result exchange

    Structured intake of lab results with automatic matching to the originating order.

    Pharmacy and prescribing

    Prescription exchange and dispensing follow-up with pharmacy circuits and controlled-medication registries.

    National health registries

    Feeding public-health registries and national health records where local regulation requires it.

    Data

    Portability and exchange governance

    Interoperability comes with controls: nothing moves without respecting residency and traceability rules. Details on the Security page.

    Portability and migration

    Migration tooling to bring over the history of an existing system without manual re-entry.

    Data transfer compliance

    Controls applied to inter-system exchanges to respect data residency and transfer rules.

    Access logging

    Every API call and exchange is logged for audit and traceability.

    Frequently asked questions

    Can On-Kare coexist with an existing EHR?

    Yes. FHIR/HL7 connectors and webhooks let you exchange patient data, appointments and results with an existing system during a gradual migration.

    Which standards are supported?

    HL7 FHIR for modern clinical exchange, HL7 v2 for legacy hospital systems, DICOM for imaging, plus dedicated connectors to public payers in several countries.

    How are API calls secured?

    Each application accesses the API through its own token, with granular permissions and full access logging, detailed on the Security page.

    Is there a test environment before going live?

    Yes, an isolated sandbox lets you validate an integration (data formats, webhooks, connectors) before activation.

    The platform as a whole

    Interoperability is only one of On-Kare’s eight functional domains.

    2,156
    product capabilities
    8
    business domains
    343
    AI-augmented capabilities
    25
    specialties covered
    7
    care settings
    Functional scope

    One platform, eight domains, a single patient record

    Care doesn't stop at the consultation. On-Kare covers the whole chain — from booking to reimbursement, from triage to compliance — so nothing falls between tools.

    Clinical operations

    1099 capabilities

    Intake, triage, clinical documentation, care pathways, prescribing, imaging, telehealth and remote monitoring.

    General Clinical Ops
    Ai Automation
    Triage & Risk Stratification
    Clinical Docs
    Pathway Orchestration
    286 AI-augmented

    Growth & access to care

    374 capabilities

    Online booking, no-show reduction, reminders, reputation, patient journeys and retention.

    Digital Intake
    Patient Comms
    Scheduling Core
    Scheduling & Capacity
    General Clinical Ops
    19 AI-augmented

    Revenue & finance

    237 capabilities

    Quotes, payments, third-party billing, revenue cycle, collections, denial control and financial reporting.

    RCM & Claims Integrity
    Billing Payments
    Appeals & Legal Recovery
    General Clinical Ops
    Pathway Orchestration
    9 AI-augmented

    Analytics & performance

    148 capabilities

    Multi-site steering, clinical and financial KPIs, internal benchmarks, quality and productivity.

    Analytics Reporting
    Clinical analytics warehouse
    Lab & Diagnostics
    Pathway Compliance Analytics
    9 AI-augmented

    Governance & compliance

    137 capabilities

    Consent, traceability, health-data hosting, access rights, audit trails and risk management.

    Consent & Data Governance
    General Clinical Ops
    Identity Consent
    Intake & Identity
    Security & Trust Controls
    13 AI-augmented

    Platform & interoperability

    84 capabilities

    APIs, FHIR/HL7, lab, pharmacy and EHR connectors, patient identity and real-time synchronisation.

    Interoperability & Ecosystem
    Transversal
    Interop Api
    Triage & Risk Stratification
    Imaging & Diagnostics
    2 AI-augmented

    Workforce operations

    39 capabilities

    Team scheduling, capacity, task delegation, onboarding and clinician administrative load.

    General Clinical Ops
    Workforce & Labor
    Scheduling & Capacity
    Triage & Risk Stratification
    Intake & Identity
    5 AI-augmented

    Public health & community

    38 capabilities

    Prevention, screening, public-health campaigns, regional coordination and access to care.

    Pathway Orchestration
    Pharmacy & Medication
    Public Health & Humanitarian
    Triage & Risk Stratification
    Pediatrics & Education Health

    Let's discuss your existing ecosystem

    Our technical teams review with you which connectors your migration needs.

    Open standards and integration surface

    860 capabilities declare an explicit interoperability requirement in their technical specification.

    Open REST APIs & webhooks586
    HL7 FHIR164
    Payment & payer connectors90
    DICOM imaging80
    Procedure & billing codes76
    E-prescription57
    ICD coding51
    Health information exchange25
    HL7 v224
    SNOMED CT22
    LOINC13
    Identity federation7