NefraOne
Sign inRequest early accessSign in

Trust

Boring where it matters.
Only the stamps move.

The rest of the site shows the product in depth. This page stays flat: what the clinic is bound to, how its data is kept, and what is written down when something happens. The one motion is a stamp coming down.

eNRR and MDTRLHDN e-InvoicePDPAISO/IEC 27001 · underway

What the clinic is bound to

Return ready

eNRR annual return

Registry fields are captured at the chair during the session. The annual return is built from the record, checked for gaps, and entered into eNRR from inside NefraOne.

Validated

LHDN e-Invoice

Validated e-Invoices from sessions and orders, for patients and funders. The validation QR prints on the receipt when the clinic wants it there.

Logged

Full audit log

Every change, every actor, every timestamp. Edits to a finished session wait for approval; imports record who ran them; every AskNefra question is logged.

Scoped

Roles and capabilities

Nurses see their patients, outlet admins their outlet, owners everything. Capabilities add stock or finance duties without handing out a bigger role.

Underway

ISO/IEC 27001

Information security management built to the standard. Certification is underway; the controls are already how we work.

Touch first

Built for gloved hands

44 px targets, guided steps, camera scanning for the MyKad and the machine display. The floor runs on a tablet; the heads-up fits a phone.

How a clinic's data is kept

Six plain statements. Each one is how the system is built, not a promise about intentions.

  1. 01Each clinic's rows are locked in the databaseRow-level security policies run inside Postgres with the signed-in clinic's id. One clinic can never read another's rows, whatever a line of code forgets.
  2. 02Encrypted in transit and at restTLS everywhere; records, documents and receipts encrypted where they sleep. Private files are served by signed links, never by a public address.
  3. 03Least privilege, by role and by capabilityA nurse's phone shows her patients. A sponsor's panel shows the patients its letters cover and nothing else. Access is granted, scoped and revocable from Users.
  4. 04AskNefra is read-only and names stay homeThe assistant can open pages and read what you may read; it never changes a record. Patient access is a switch the clinic turns on; until then it works with aliases. Every question is audited.
  5. 05Imports and migrations are silentBringing a clinic across from its existing system or a spreadsheet sends no invites, receipts or notifications. The clinic decides when its people hear from the system.
  6. 06Continuous backups, controlled releasesPoint-in-time recovery on managed infrastructure, health monitoring, and database changes applied before the code that needs them is released.

What gets written down

A sample of the audit log, as an admin sees it. Every row names the person, the time and the thing.

Audit logToday7 daysCustomPHMP Batu Muda
WhenWhoWhatOn
9:43amHashimah binti Mustamin · nurseReceipt issued · QR payment · RM40.00JP-RC-20261021-0002
9:51amNurul · nurseSession edited · medicines · Recormon to own supply · awaiting reviewSession 17 Oct
10:02amQurratu · outlet adminSession edit approved · the order was brought in stepOR-PHMPBMD-2610-0172
10:15amDr Nirmala · doctorAskNefra asked · "which patients are below Kt/V 1.2 this month" · 3 rows readQuality
10:40amAien · tenant adminCapability granted · inventory.count · to a nurseUsers

Questions about data, access or the registry return?

Write to us and a person answers. We will show you the audit log, the role matrix and the database policy, not a slide.

Contact us Back to the overview