Skip to main content
Request a demo

Feature

Statutory Registers for Hospitals

Five registers Indian hospitals are expected to keep — DPDP Act consent, PCPNDT Form F, the death register with MCCD Form 4, notifiable diseases, and bio-medical waste — live in the same system as the patient record, with entries made as the work is done and each register printed or exported in the format the authority expects, instead of being reconstructed the night before an inspection. These are record-keeping tools: they don’t make a hospital compliant on their own.

Updated
Request a demoAll features

Draft — pending expert review

This page was prepared from the official sources listed below but has not yet been reviewed by a qualified professional. It is general information, not legal or medical advice.

In short

Statutory Registers keeps five registers — DPDP consent, PCPNDT Form F, the death register with MCCD Form 4, notifiable diseases and bio-medical waste — each filled in during normal clinical and admin work, locked once finalised, with a CSV export shaped for the relevant authority.

Who uses it
Reception captures consent; the sonographer or doctor completes Form F; the ward or discharge desk completes the death register; clinicians flag notifiable diseases; admin logs daily bio-medical waste handover.
What it records
Consent events with guardian capture under 18, Form F’s statutory fields, the MCCD cause-of-death chain, notifiable-disease diagnoses with Nikshay IDs for TB, and daily bio-medical waste weights by BMW colour category.
What it prints / exports
A monthly Form F authority CSV, a CRS-ready death-register CSV, general and Nikshay-only TB CSVs, and an annual Form IV bio-medical waste CSV — each downloaded and submitted by your staff, not sent automatically.
Works with
Patient Registration, IPD & Admissions, Reports & Analytics

What you get

  • DPDP consent ledger, with guardian capturePatient consent is recorded by purpose — treatment data, communication, AI processing, research — as an append-only ledger of grant, refuse and withdraw events; for a patient under 18, treatment-data consent requires a guardian’s name and relationship before it can be captured.
  • PCPNDT Form F, draft then finalisedEvery prenatal ultrasound gets a Form F with the patient, referring doctor, indications, procedure and the two mandatory declarations, kept as a locked, immutable record once finalised. The findings field is marked on screen that it must not record or imply the sex of the foetus, and Form F cannot be finalised until both declarations are recorded.
  • Death register with MCCD Form 4Every death is logged with the full medical certificate of cause of death — immediate, antecedent and underlying cause, manner of death, and an MLC flag — printable as MCCD Form 4 once the register entry is finalised.
  • Notifiable diseases, with a Nikshay CSV for TBA hospital-configured list of notifiable diseases can be logged against a patient with a notification status tracked through to acknowledgement, and TB cases carry a Nikshay ID for a ready-to-upload CSV.
  • Bio-medical waste by BMW colour categoryDaily waste handed to your bio-medical waste contractor is logged by colour category — yellow, red, white/sharps, blue and cytotoxic — rolling up into an annual Form IV total.

How it works

  1. Consent is captured at the point of contact

    Reception or clinical staff record a consent event by purpose against the current version of the hospital’s consent notice; for a patient under 18, treatment-data consent needs a guardian’s name and relationship before it can be saved.

  2. A consent gap never blocks care

    An unrecorded or refused consent shows as a gap on the patient record and on the consent screen — it never stops clinical work from happening.

  3. Form F is drafted, then locked

    The sonographer or doctor fills the statutory Form F fields and both declarations, saves it as a draft, and finalises it — once finalised, the form can no longer be edited by anyone.

  4. A death is logged and can print as MCCD Form 4

    The death register can be pre-filled from a death-type discharge, records the full cause-of-death chain, and is finalised the same way as Form F — locked once done — with MCCD Form 4 available to print.

  5. Notifiable diseases move through a status

    A case of a disease on the hospital’s notifiable-disease list is entered in the register and tracked from pending to reported to acknowledged, with TB cases carrying a Nikshay ID.

  6. Waste is logged daily; exports close the loop

    Bio-medical waste is logged once per day by category, and each register offers a CSV shaped for its authority — for staff to download and submit themselves.

Who uses it

  • Reception / ward staffCapture patient consent by purpose, including guardian consent when a patient is under 18, without it ever blocking registration or treatment.
  • Sonographer / doctorComplete and finalise PCPNDT Form F for every prenatal ultrasound, and complete the death register and MCCD Form 4 when a patient dies.
  • CliniciansFlag a notifiable-disease diagnosis against the hospital’s configured list and track it through to acknowledgement, adding a Nikshay ID for TB cases.
  • Admin / compliance ownerLog daily bio-medical waste handover, review the consent-gap list, and export the monthly and annual CSVs each register produces.

In detail

Draft, then permanently locked

Form F and the death register share the same posture: both are editable as a draft, and both become permanently locked the moment they’re finalised — no one, including an admin, can edit a finalised entry afterwards. That’s deliberate: a Form F entry or a death certificate is a legal record, not a working document, and every print of a finalised Form F is logged separately so the record itself is never touched by the act of printing it.

Because of that, it’s worth getting an entry right before finalising it. A correction field is available on a draft Form F for exactly that reason — use it before the record locks, not after.

What the exports are, and aren’t

Every register here produces a CSV — the monthly Form F return, a CRS-ready death-register export, general and Nikshay-only notifiable-disease CSVs, and an annual bio-medical waste Form IV CSV. Each is a file your staff download and submit to the relevant authority themselves; none is a live API connection. The Nikshay export, for instance, is explicitly a file formatted for upload, not a data feed into Nikshay itself — filing it, like the others, is still a step your hospital completes.

DPDP consent doesn’t gate treatment

Consent status is a soft gate by design: an unrecorded, refused or withdrawn consent shows up as a visible gap — on the patient’s record and on a dedicated consent screen — but it never stops a clinician from treating the patient. The one place consent is actually enforced is around the optional AI assistant, which won’t run on a patient’s data after an explicit refusal or withdrawal of consent.

Guardian consent applies specifically to patients under 18, calculated from date of birth: treatment-data consent for a minor requires a guardian’s name and their relationship to the patient before it can be recorded.

Related features

Further reading

Frequently asked questions

Does using these registers make a hospital legally compliant?

No — these are record-keeping tools, not a compliance guarantee. They help a hospital keep its five statutory registers accurate and on time, but meeting every legal obligation around them — filing with the right authority, staff training, physical waste handling and so on — remains the hospital’s responsibility.

Can a finalised Form F or death register entry be corrected later?

No. Once finalised, both are permanently locked against editing, including by an admin. A correction field exists on the draft stage for exactly this reason — check the entry carefully before finalising it.

Does the Nikshay CSV submit TB cases to Nikshay automatically?

No. It produces a CSV file formatted for upload to Nikshay — your staff still download it and submit it through Nikshay’s own process. There’s no live API connection between Trisvio and Nikshay.

What happens if a patient refuses or hasn’t given consent?

It shows up as a visible gap — on the patient record and on the consent screen — but it never blocks clinical care. The one place consent is actually enforced is around the optional AI assistant, which won’t run on a patient’s data after an explicit refusal or withdrawal.

How is guardian consent for a minor handled?

For a patient under 18, calculated from their date of birth, treatment-data consent requires a guardian’s name and their relationship to the patient before it can be captured — it isn’t optional the way it is for an adult patient.

Official references

Rules change. Confirm current requirements with the issuing authority.