Interoperability · APIs · Developer platform
Connect to everything. Without the usual pain.
careos is interoperable by default. FHIR-aligned canonical model, contract-first APIs, a broad adapter catalogue, and a developer platform built for regulated environments. Integration is a product surface, not a services project.
FHIR-aligned canonical model
One model. The standard vocabulary.
Canonical model
Core clinical concepts mapped to FHIR R4. Patients, episodes, plans, medications, observations, documents — all aligned to the standard vocabulary.
Imports
CSV, NDJSON, and FHIR bundle imports with schema validation, dry-run, and idempotent replay for migrations.
Exports
Structured, validated, schema-versioned exports. Data leaves careos in formats downstream systems can consume without custom glue.
Terminology services
Managed terminology for medications (dm+d / RxNorm), observations (LOINC), and organisations (ODS / NPI).
SMART on FHIR
SMART-ready patterns for app launch, scoped OAuth, and context passing — so partner apps plug into the canonical model without custom glue.
Mapping services
Versioned terminology and concept mappings across markets, with reconciliation reports for imports and row-level validation errors.
API surface
Contract-first. Deterministic. Auditable.
Every endpoint follows the same rules. Every mutation produces both a domain event and an audit event. Integration code should be boring.
OpenAPI 3.1
Contract-first specification. The API surface is defined before code, reviewed by design partners, and versioned as a product.
Deterministic SDKs
SDKs generated directly from the contract. Same guarantees across languages. No hand-maintained client drift.
Cursor pagination
Every list endpoint supports cursor pagination and structured filters. No offset hacks, no unbounded queries.
Idempotency keys
Every mutation and transition supports idempotency keys. Safe retries, safe reprocessing, safe distributed work.
Events + audit
Every mutation emits domain events to subscribers and an audit event to the Evidence Ledger. No silent writes.
Rate limiting
Tenant-aware rate limits with burst, quota and fair-share controls. Structured 429 responses carry retry hints and correlation IDs.
Standards supported
The acronyms auditors ask about.
Adapter catalogue
Pre-built integrations across six domains.
Identity
- Azure AD
- Okta
- Google Workspace
- NHS login
- SAML 2.0
- OIDC
Messaging
- NHS Notify
- Twilio
- SendGrid
- Voice providers
- Letter printing
Telephony
- Queue integration
- Call disposition
- Transcript storage
- Callback handling
Devices
- RPM vendors
- Wearables
- Home monitoring equipment
- Device enrolment
Finance
- Payer integrations
- Claims gateways
- Invoicing
- Payment providers
Documents
- E-signature providers
- OCR
- Document storage
- Redaction pipelines
Developer experience
Built for the people who integrate things.
Sandbox environments
Per-tenant sandboxes with synthetic data that mirrors the shape of production. Safe to build against, safe to break.
Tenant-scoped API keys
Keys are always scoped to a tenant and a role. Rotate, revoke, and audit from the admin surface.
Webhook replay
Delivered webhooks are retained and replayable. Debugging an integration does not require reproducing the source event.
Contract tests
Published contract test suites so partners can verify compatibility before shipping. No hand-rolled fixtures.
Marketplace workflow
A submission workflow for partner apps: review, certification, publication, and revenue share.
CLI tooling
A first-party CLI for tenant scaffolding, config diff, webhook replay, data import dry-runs, and SDK generation — built on the same contract as production.
Developer platform
Get sandbox access. Build on the contract.
We open sandboxes for design partners, integrators, and marketplace applicants. Talk to the platform team to request access.