Tools built for healthcare interoperability.
Connect your hospital, clinic, lab, or pharmacy to the OpesCare network using the integration method that fits your existing infrastructure.
RESTful API — direct system-to-system integration
The Connect API gives authorized health systems full programmatic access to the OpesCare platform — patient identity, consent, clinical timelines, medication availability, and more. All endpoints are JSON-based and authenticated via OAuth 2.0 client credentials.
- OAuth 2.0 client credentials flow
- Versioned endpoints — current stable: v1
- Sandbox environment for safe pre-production testing
- Full audit trail — every API call is logged
"health_id": "CM-HID-7KQ9-MP42-X8D1",
"consent_ref": "CNS-789",
"data": [...]
Pre-built libraries in PHP, JavaScript, Python and more
The SDK wraps the Connect API into idiomatic clients so your development team can integrate in days rather than weeks.
PHP
StableLaravel/Symfony compatible. Install via Composer. Full typed request/response objects.
composer require opes-health-systems/opescare-php
JavaScript
StableNode.js and browser-compatible. Works with Axios and Fetch. TypeScript definitions included.
npm install @opes-health-systems/opescare-js
Python
BetaAsync and sync clients. Pydantic models for type safety. FastAPI and Django ready.
pip install opescare-python
.NET / Java
Roadmap.NET 6+ and Java 17+ clients are currently in development. Register to be notified at launch.
Coming soon — register interest
Embed patient search and consent in your web application
The Connect Widget is a secure, sandboxed web component you can embed inside your existing hospital information system or web portal. It handles patient lookup, consent request, and record pull without requiring a custom API integration.
- Single script tag embed — no build pipeline required
- Scoped iFrame — zero access to your parent app state
- Customizable theme and label strings
- postMessage API for result callbacks into your app
Connecting legacy systems, local databases, and offline environments
Not every facility has a modern API-ready system. The Bridge Agent is a lightweight local service that can connect to on-premise databases, file-export systems, or semi-offline environments, and sync records securely with OpesCare on a scheduled or event-driven basis.
Local Database Connector
Reads from MySQL, PostgreSQL, MSSQL, or SQLite databases on your local network and maps records to the OpesCare data model.
File Export Parser
Ingests CSV, HL7, or structured PDF exports from legacy EMR systems and translates them into FHIR-compatible records.
Offline Sync Queue
Records are queued locally when the facility is offline, then synced automatically when the connection is restored.
Encrypted Local Storage
All queued data is encrypted at rest on the local machine using AES-256. Credentials are stored in secure OS keychains.
A full browser portal for facilities without their own digital system
OpesCare Lite is a secure, hosted web portal that lets smaller clinics, pharmacies, and health posts access the OpesCare network without building any integration. Staff log in from any modern browser and work directly with patient records through a guided interface.
- Zero installation — fully browser-based
- Role-based access — doctors, nurses, pharmacists, admins
- Works on tablets and low-bandwidth connections
- Same security and audit standards as API integrations
Stay in sync with real-time platform events
Subscribe your endpoint to OpesCare events and keep your local system updated without polling the API.
Available event topics
visit.recorded
A new clinical visit has been pushed to the timeline.
consent.granted
A patient has approved a consent request.
consent.revoked
A patient has revoked an active consent grant.
lab.result.released
A validated lab result has been released.
prescription.dispensed
A pharmacy has marked a prescription as dispensed.
emergency.access
An emergency access event has been recorded.
sync.failed
A record push or pull sync has failed.
Example webhook payload
"timestamp": "2026-05-18T08:42:00Z",
"facility_id": "FAC-001",
"health_id": "CM-HID-7KQ9-MP42-X8D1",
"consent_ref": "CNS-789",
"data": {...}
Signature verification
Every webhook delivery includes an HMAC-SHA256 signature over the raw request body using your endpoint secret. Always verify before processing.
Ready to connect your system?
Submit a developer or integration request and our interoperability team will review your use case and access scopes.