Medico-legal cases aren't paperwork — they're evidence. Capture them as a first-class EMR feature, not a printout pasted at the end of the shift.
What MLC really is
An Indian emergency department sees medico-legal cases every single shift — road traffic accidents, alleged assault, alleged poisoning, burns, attempt-to-suicide, suspicious deaths, sexual assault, snake bite, drowning. Once a case is flagged as medico-legal, the clinical record becomes potential evidence in a court of law. That changes the rules for what gets captured, how it's stored, who can see it, and what cannot be edited after the fact. Most HMS implementations treat MLC as a printable form. That's how hospitals lose cases — not the clinical ones, the legal ones.
What the law actually expects
- Immediate police intimation in writing — with a copy retained, signed by the duty doctor.
- Panchnama / inquest documentation for unnatural deaths, with witness signatures captured at the time.
- Chain-of-custody for any biological sample sent for forensic analysis — who collected, sealed, handed over, with timestamps and signatures.
- Photographs of injuries with a measurement reference, where the patient consents.
- An audit trail that survives the question 'when was this entry made, and could it have been edited afterwards?'
Why bolted-on MLC fails
A separate paper MLC register at the front desk fails because the resident filling the clinical notes and the receptionist filling the register are different people, working in different rhythms, and the register lags behind by hours. The first time anyone reconciles the two is when the police visit. By then nobody remembers what happened, the OPD card has been misplaced, and the duty doctor has gone home. The clinical record contradicts the register on small details, and a lawyer turns those small details into reasonable doubt.
Built-in MLC: how it should work
- Trigger on chief complaint — RTA, assault, poisoning, burn, attempted self-harm — automatically marks the encounter as MLC and unlocks the legal fields.
- A single MLC form embedded in the ED encounter, not a separate module. Same case ID, same timeline.
- Police intimation drafted automatically from the encounter data — duty doctor only adds case-specific notes and signs.
- Witness fields with name + relationship + signature capture (on-screen or printed and scanned back in).
- Injury photography with measurement scale, stored encrypted, accessible only to authorised roles.
- Tamper-evident log of every edit — what changed, who changed it, when, from which IP.
Tamper-evident audit, in plain English
An MLC entry should be appended to, never silently rewritten. If a doctor corrects a fact, the original remains visible alongside the correction with a reason. Deletes are blocked at the database level — not just hidden from the UI. The audit table is locked down so even a hospital admin cannot rewrite history. That's the only kind of audit a court will accept as evidence.
A small story
A 90-bed hospital lost a wrongful-death case last year not because the clinical care was poor, but because the only record of the police intimation was a photocopy with an illegible date stamp. The court asked whether the intimation had been backdated. The hospital could not prove otherwise — the EMR didn't store it, the register was unsigned for that date, and the duty doctor had since left. The case turned on that single missing audit detail. The clinical correctness never got litigated.
How MyEMR handles it
MLC is part of the ED encounter, not a bolt-on. The chief-complaint trigger lights up the legal fields; the police intimation is drafted from encounter data; the audit log is append-only and lives in a separate table that even the hospital admin cannot rewrite; photographs are stored encrypted with role-gated access. The whole flow is one continuous record from triage to discharge — and to a subpoena, three years later.