01 / PLATFORM
Curova is composed of an experience layer, a governed intelligence layer, and a trust substrate. The same data model and the same event bus run across all three — which is what lets a single triage event become a claim, a follow-up, and a longitudinal signal.
02/COMPOSITION
03/ARCHITECTURE
Surfaces talk to substrate through the IQ Engine. Every read and write passes through the policy and consent gates. The event bus is the contract every module shares.
Experience surfaces
Value rails
Curova IQ Engine
Care data substrate
Trust substrate
Integration kits
04/INTEGRATION SURFACES
Curova is built to integrate, not to replace. Every edge surface is documented, versioned, and conformant.
Native FHIR resources for encounters, observations, medications, claims, consents, and more — with versioned profiles and documented extensions.
ABHA-linked accounts, ABDM-compliant consent flows, and HCX-ready claim envelopes designed for India’s national rails.
Consent receipts, purpose binding, and an append-only audit stream — all cryptographically chained and queryable per patient.
Sample chains, prescription delivery, and home-collection routing through pluggable adapters — quality and tracking events flow back into the record.
Card, UPI, and provider-payout rails with structured receipts that feed claims, reconciliation, and price discovery.
Continuous clinical-eval and red-team rails attach signed evaluation artefacts to model versions and decision-trail nodes.
05/EVENT STREAM
A small slice of the governed event stream that runs under a single patient encounter. Every event carries consent state, provenance, and clinician sign-off.
06/TOPOLOGIES
Default for hospital networks and lab groups: an isolated tenant, region-pinned data residency, and direct integration kits.
For independent providers and small networks adopting Node, Axis, Detect, or Dose individually — shared substrate, isolated org boundaries.
For regulators and large insurers who require a sovereign control plane: substrate runs in-region; intelligence runs federated.
07/GOVERNANCE POSTURE
Curova’s governance posture is structural, not editorial. Every layer is built to be reviewable by clinicians, regulators, and patients.
Every AI output is assistive. No clinical recommendation moves without a named clinician sign-off.
Reads bind to purpose at the call site. Same role, different data — depending on what the request is for.
Outputs ship with sources, model identity, confidence band, and dissenting signals attached.
Every decision-trail node is replayable. Patients, clinicians, and regulators can audit the same record at different scopes.
08/STAKEHOLDERS
Curova is built for the people who actually move care. Each surface is designed for the work, not the demo.
Curova Node turns the phone into a coordinated care companion — triage, appointments, reports, medicines, and reminders all backed by the same consented record.
PARTNER
We work with hospital, lab, and pharmacy networks; payers; and integration partners ready to put care on a structured event stream.