Clinical data outlives
the software that made it.
A prescription written today may be read in twenty years by a clinician who has never heard of us. That constrains the architecture more than any feature request ever has.
Not resettable
You can reset a password. A clinical history is a fact about a person's life.
Acted upon
A wrong record is not an inconvenience. Someone prescribes from it.
Not the clinic's risk
The patient bears the consequence of a breach. They were not in the room when the software was chosen.
Outlives vendors
Portability is not a feature request. It is the minimum honest position.
Encrypted, resident, auditable.
Engineered in rather than added — least privilege by default, encryption in transit and at rest, and an append-only audit trail on every access to identified data.
Data residency
Stored in India on empanelled infrastructure. Production data never appears in a lower environment.
Encryption everywhere
In transit and at rest, on device and on server, with managed keys and rotation.
Role separation
Assistants cannot reach clinical narrative beyond what dispensing requires.
Append-only estate
Amendment creates a version. Nothing is overwritten; nothing is hard-deleted.
Immutable audit
Every read and write of identified patient data is logged and attributable.
Device loss
Remote wipe of the local store on revocation, initiated by the clinic administrator.
Stated with its status.
We do not claim certifications we have not been granted. Where something is intended rather than achieved, this page says so.
| Data protection | India's DPDP Act 2023 — lawful basis, granular consent, data-principal rights and breach process. The clinic is the data fiduciary; we process on its behalf under a written agreement. |
| Data residency | India-resident storage on empanelled infrastructure. |
| Clinical terminology | SNOMED CT via NRCeS affiliate registration, LOINC, ICD and ATC under their respective licences, with attribution in the product. |
| Interoperability | HL7 FHIR R4 and DICOM for exchange and imaging. |
| Digital health ecosystem | Works with ABHA identity and the national consent framework. Not currently certified against ABDM milestones. |
| Security assurance | Independent security assessment before any real patient data. Current status shared under NDA. |
Certification status changes. Where this page and a certificate disagree, the certificate governs. Current status is available on request.
Software that records,
not software that decides.
The boundary is between assisting a clinician to record what they decided, and participating in the decision. We are deliberately on one side of it.
In scope
Transcription, terminology retrieval, deterministic mapping, interaction and allergy advisories from a maintained database.
Out of scope
Diagnostic suggestion, treatment recommendation, triage scoring. No autonomous action affecting a patient.
Advisory only
Alerts are inline, non-modal and never block a prescription. Alert fatigue is a certainty, so scope is narrow.
Reversible
Any entry corrected or removed in one action, with the original retained.
Talk to us about security.
We share architecture detail, control mappings and current certification status under NDA.