Architecture

Your hospital should keep running even when the internet doesn’t.

Indian hospitals do not get to pause admissions because a fibre line is cut. Nexus OneHealth is built on-premise first — the cloud is there for backup and reach, never as a single point of failure.

Deployment topology

Where everything actually sits.

Inside the hospital network: web and desktop clients talk to application services, which use an on-premise PostgreSQL database and an imaging and document store. Lab systems over HL7 or FHIR, PACS and DICOM, WhatsApp messaging and staff attendance integrate at the edge. An optional encrypted delta sync connects outward to off-site backup, disaster recovery and remote access for consultants.

Hospital network

Runs with the internet down

  1. Web & desktop clientsHospital network and approved devices
  2. Application servicesClinical, pharmacy, billing, reporting
  3. Operational databasePostgreSQL, on your server
  4. Imaging & documentsDICOM store, casesheets, PDFs

Integrations at the edge

  • Lab systems — HL7 / FHIR
  • PACS / DICOM
  • WhatsApp messaging
  • Staff attendance

Keep the systems you are happy with. We integrate rather than insist.

Cloud services — if you want them

  • Off-site backupEncrypted delta, to your chosen location
  • Disaster recoveryRestores verified, not assumed
  • Remote accessFor consultants working off-site

Switch it off and nothing leaves the premises.

Why it is built this way

Local-first. Cloud optional.

  • Works when the internet does not

    The database and application run inside the hospital. A broken link to the outside world does not stop admissions, dispensing or billing.

  • Cloud sync is a choice, not a condition

    Optional encrypted delta sync gives you off-site backup and remote access for consultants. Switch it off and nothing leaves the premises.

  • Your data stays yours

    On-premise PostgreSQL with scheduled, verifiable backups. No lock-in to a vendor cloud, and no per-record hostage-taking on exit.

  • The server is your capital asset

    You own the hardware and it sits on your balance sheet, rather than renting capacity by the month. It is configured for disaster recovery and to meet the compliance requirements your auditors check.

  • No variable cloud costs

    Nothing is metered. A busy month does not produce a larger bill, and your running cost is known in advance instead of moving with usage.

Access control, audit logging, backups and what happens if we cease trading are covered in detail for technical evaluation.

Security & infrastructure

Standards & controls

What your IT head will ask about.

We publish only what we can evidence, and say plainly which items are still in progress.

Standards & interoperability

  • HL7 / FHIRSupported

    Interoperability with labs, PACS and external systems.

  • DPDP Act 2023Supported

    Audit trails, access control and data export on demand — built to meet your obligations as data fiduciary.

  • ABDM / ABHAAwaiting approval

    ABHA number capture is live today. ABDM sandbox registration is submitted and awaiting approval from NHA; integration certification and production onboarding follow after that.

  • NABH documentationSupported

    Records, consent and audit trails structured to supply the evidence NABH assessors ask for.

These describe what the software supports. They are not certifications, and we do not claim to hold any.

Controls in the product

  • Role-based access13 roles, 47+ granular permissions
  • Audit loggingReads, writes, prints and exports
  • Encryption in transitAnd for any sync that leaves the building
  • Data residencyYour server, your hospital, your hardware
  • Break-glass accessNever blocks a clinician — always recorded
  • Verified backupsRestores tested, not assumed

Send this page to your IT head.

If something here is not specific enough for your assessment, ask and we will answer directly rather than send a brochure.

Request the technical packTalk to us — +91 73969 94314