Core Infrastructure

Built to connect healthcare systems, not replace them all.

OpesCare allows approved systems to push and pull patient data through secure APIs, SDKs, widgets, bridge agents, and webhooks — working with whatever infrastructure a facility already has in place.

Developer Docs Request Integration Call

Bi-directional push and pull architecture

OpesCare is not a one-way data store. The platform supports a fully bi-directional model so facilities can contribute information to the patient's timeline (push) and retrieve approved information from it (pull) — all within the bounds of consent and role-based access.

Push

A facility sends new patient data — visits, diagnoses, prescriptions, lab results, referrals — to OpesCare to update the patient's global medical timeline.

Pull

A facility requests approved patient information from OpesCare to inform clinical care — seeing only what the patient has consented to share for the stated purpose.

Interop Flow

Hospital / Clinic

Authorized Provider

Push →

← Pull

OpesCare

Consent + Audit Layer

Laboratory

Pharmacy

Insurer

Five integration pathways — one for every facility type

From enterprise API integrations to zero-install browser portals, OpesCare has a pathway for every technology maturity level.

Connect API

Enterprise

Direct RESTful API integration for modern hospital information systems and enterprise health vendors. OAuth 2.0, versioned endpoints, full sandbox access.

Learn more →

Connect SDK

Developer

Pre-built client libraries for PHP, JavaScript, and Python. Typed request/response objects, full test coverage, Composer/npm/pip distribution.

Learn more →

Connect Widget

Web-Embed

A secure, sandboxed web component for facilities with an existing web portal. Embed patient search, consent, and pull in a single script tag.

Learn more →

Bridge Agent

Legacy

A lightweight local service for facilities running legacy EMR systems, on-premise databases, or file-based record exports. Works offline with encrypted sync queues.

Learn more →

OpesCare Lite

No-Code

A fully hosted browser portal for facilities that do not yet have their own digital system. Staff log in from any modern browser — zero installation.

Learn more →

Standards and data model

OpesCare data structures align with internationally recognised healthcare information standards.

HL7 FHIR R4

Patient, Encounter, Observation, MedicationRequest, DiagnosticReport resources mapped to the FHIR R4 standard.

RESTful JSON

All API endpoints return structured JSON. OpenAPI 3.0 specification available to registered partners.

ISO 8583 for Billing

Financial transaction messages for insurance claims and billing reconciliation follow ISO messaging standards.

HL7 v2 Import

The Bridge Agent can parse and translate legacy HL7 v2.x message files from older EMR systems into FHIR-compatible records.

Connect your facility to the OpesCare network

Our integration team will help you choose the right pathway and guide you through the onboarding process.