Design principles
What Neriant is built to be — and what it refuses to become.
A short, non-negotiable set of principles that shape every architectural decision, every module, and every deployment.
Principles
Eight commitments we hold the platform to.
Standards-first, always
FHIR R4/R5, SNOMED CT, LOINC, HL7 v2, X12, NCPDP, IHE profiles and national programme specifications are first-class — never bolted on. If a standard exists, we conform.
Vendor-neutral by construction
Identity providers, AI models, cloud regions and downstream connectors are pluggable. The platform never becomes permanently dependent on a single vendor in any layer.
Sovereign by default
The same codebase ships as multi-tenant SaaS, single-tenant private cloud, sovereign region, or edge deployment. Data residency, key custody and routing are configurable per deployment.
Clinically safe
Every clinical workflow is designed against DCB0129/DCB0160-style hazard analysis. Safety case artefacts are produced as the product is built — not retro-fitted before audits.
Auditable end-to-end
Every read, write, override, AI invocation and cross-organisation share is recorded with provenance. The audit ledger is part of the product, not an add-on log file.
Modular domain services
Patient, encounter, orders, medications, results, documentation, RCM and analytics are separate services with stable contracts — so deployments can adopt incrementally and migrate safely.
Coexist before you replace
Neriant runs next to Epic, Oracle Health, MEDITECH, InterSystems, Dedalus and Altera. Replacement is optional; orderly coexistence is the default migration posture.
Human oversight on AI
Counsel AI never acts unsupervised on patient data. Every model invocation is governed, attributable, region-locked where required, and visible in audit.