Skip to content

Supported integration architecture

Connects with the systems you already run.

Cure sits on top of your hospital systems through a dedicated integration layer. Nothing is replaced — your systems stay the source of truth, and patients get one clear experience.

Discuss your environmentSecurity
  • HIS
  • HMIS
  • EMR
  • EHR
  • ERP
  • ERPNext
  • LIS
  • RIS
  • PACS
  • Pharmacy
  • Billing
  • Insurance
  • Payment Gateways
  • SMS
  • WhatsApp
  • Email
  • Call Center
  • Queue Management

Architecture

Four layers, one patient experience.

Data flows from the systems of record, through the Cure integration layer, into the patient experience on web and mobile.

  1. 01

    Hospital Systems

    Systems of record in each provider environment

    • HIS / HMIS
    • EMR / EHR
    • LIS
    • RIS / PACS
    • Billing
    • Pharmacy

  2. Cure Integration Layer

    Secure APIs, data mapping and events

    • Secure APIs
    • Data mapping
    • Event triggers
    • Access control
  3. 03

    Patient Experience Layer

    Services, records and notifications

    • Appointments
    • Results
    • Records
    • Payments
    • Notifications

  4. Web / Mobile

    Where patients use Cure

    • iOS
    • Android
    • Web portal

Messaging & payments

  • SMS
  • WhatsApp
  • Email
  • Payment gateways

System categories

What Cure is designed to connect with.

Supported integration architecture — the connections enabled in each deployment depend on the provider's environment and the systems in place.

Hospital & clinical

  • HIS

    Patient registration, visits and services.

    Integration-ready

  • HMIS

    Hospital management and administration data.

    Integration-ready

  • EMR

    Clinical records, diagnoses and notes.

    Integration-ready

  • EHR

    Longitudinal patient health records.

    Integration-ready

  • ERP

    Enterprise resources, finance and operations.

    Integration-ready

  • ERPNext

    Open-source ERP, including healthcare modules.

    Integration-ready

Diagnostics

  • LIS

    Laboratory orders and released results.

    Integration-ready

  • RIS

    Radiology scheduling and reports.

    Integration-ready

  • PACS

    Medical image access for patients.

    Depends on provider environment

Pharmacy & finance

  • Pharmacy

    Prescriptions and dispensing.

    Integration-ready

  • Billing

    Invoices, balances and receipts.

    Integration-ready

  • Insurance

    Coverage and approval information.

    Depends on provider environment

  • Payment Gateways

    Online payment of patient bills.

    Depends on provider environment

Communication & operations

  • SMS

    Reminders and one-time codes.

    Integration-ready

  • WhatsApp

    Notifications through business messaging.

    Depends on provider environment

  • Email

    Notifications and documents by email.

    Integration-ready

  • Call Center

    Shared context for patient support teams.

    Depends on provider environment

  • Queue Management

    Visit check-in and queue status.

    Depends on provider environment

Integration availability depends on each provider's systems, vendors and approvals. Cure does not claim that any specific integration is active until it is configured for a deployment.

Integration principles

Designed to fit your environment.

  • No replacement

    Your systems remain the source of truth.

  • Secure APIs

    Authenticated, scoped endpoints between systems.

  • Event-driven

    Released results and bookings trigger patient updates.

  • Provider-controlled

    You decide which services are exposed to patients.

Connects with the systems you already run.

A dedicated integration layer connects hospital systems to the patient experience — so going digital doesn't mean replacing anything.

Discuss your environmentProviders