Medical examiner and coroner case management systems

Reference article · 5 min read

A medicolegal death investigation office produces a record that has to satisfy several audiences at once: a family that wants to know what happened, a prosecutor who may try the case years later, a state registrar that will not accept an incomplete death certificate, and a public health agency waiting on overdose data. Many offices run on a shared drive, a spreadsheet case log, and a word processing template. That arrangement works until case volume, photograph storage, or the number of people needing simultaneous access crosses some threshold. Then it fails in familiar ways: two investigators editing the same log, images filed under a name that was later corrected, a toxicology result that arrived by fax and never reached the file, a certificate amended in the registry but not in the office copy.

This is a description of what a case management system for a coroner or medical examiner office has to hold and connect, written for the administrator or county IT director who has to scope the replacement.

The case record from notification to disposition

The record begins before anyone knows who the decedent is. Intake has to accept a call from law enforcement, a hospital, or a hospice at any hour, capture the reporting party and circumstances, and support a jurisdiction decision: accept, decline, or accept for external examination only. From there the system carries scene documentation, investigator narrative, photographs taken at the scene, next of kin identification and notification attempts, and the transport record.

Two structural points matter more than any feature list. First, the case number must be assigned at notification and never change, with all later identity corrections handled as attributes of that case rather than as renaming. Second, the record has to tolerate an unidentified decedent for an extended period, which means every field keyed to a name needs a path that works without one.

Identification, NamUs, and external reporting

Identification work spans fingerprints, dental comparison, radiographic comparison, DNA submission, and visual identification by family. The system should record the method used, who made the determination, and the supporting documents, because that chain gets questioned later.

• NamUs. The National Missing and Unidentified Persons System, administered through the National Institute of Justice, accepts unidentified and unclaimed decedent cases. A number of states have enacted reporting requirements with their own timelines and triggers. Confirm your state's current requirement with your counsel or state office rather than relying on a vendor's summary.
• Overdose surveillance. CDC-funded programs collect detailed medical examiner and coroner data on drug overdose deaths, typically through a state health department abstracting from your case files and toxicology reports. Violent deaths feed a separate national system. Both work far better when narrative, scene findings, and toxicology are structured and exportable.
• Law enforcement and missing persons. Fingerprint and DNA submissions go to separate state and federal systems, each with its own forms and timelines.

Evidence, personal effects, and morgue operations

Chain of custody is the part most often underbuilt in homemade systems. Evidence, biological specimens, and personal effects need individual item records with barcode or RFID identifiers, every transfer logged with person and timestamp, and a reason code for release or destruction. Personal effects returned to family should generate a signed receipt tied to the item record.

Body tracking is the same discipline applied to the decedent: cooler, rack, and tray location, movement history, and release to the funeral home or transport service with signature. Systems that make location a free-text field produce the search-the-cooler problem that prompted the procurement in the first place.

Imaging, autopsy, and laboratory results

Photograph and radiograph volumes grow faster than administrators expect, and postmortem CT pushes storage substantially higher. Plan capacity for the retention period your state requires, not for current year volume. Require that images stay linked to the case and to the body region or item they document, that originals are preserved unaltered, and that access to images is governed separately from access to the report text.

Toxicology and histology usually come from outside laboratories. Ask for a real interface rather than PDF attachment: structured results reduce transcription error and make surveillance reporting possible. Pending-result tracking with automatic aging is what keeps cases from sitting open after the lab has responded.

Certification, records release, and reporting

Cause and manner determination feeds the state electronic death registration system. An interface that prefills demographic and certifier data, supports pending certificates, and handles amendments cleanly saves substantial rekeying. Cremation authorizations, fee tracking, and unclaimed decedent disposition often live in the same workflow.

Release of records is governed by state law, and the rules commonly differ for autopsy reports, photographs, and investigative narratives, and by requester type. Build the exemption logic into redaction and release workflows rather than leaving it to individual judgment, and log every disclosure. Confirm current requirements with counsel, since these statutes are amended frequently.

Accreditation bodies for medical examiner and coroner offices set expectations around report turnaround, caseload per pathologist, documentation, and facility practice. Choose a system that reports the metrics your accrediting body actually inspects: pending cases by age, autopsy-to-report interval, certification backlog, and workload by staff member.

What to ask before you buy

1. Show the chain of custody audit trail for a single item, including a correction made after the fact.
2. Demonstrate a live death registry interface and a live toxicology interface in a state or laboratory you already serve, not a slide.
3. State the image storage architecture, retention handling, and the cost of storage growth over the contract term.
4. Describe how records requests, redaction, and disclosure logging are handled.
5. Require in the contract that the agency owns its data, that a full export including images and audit logs is available on demand in documented formats, and that export is not an additional charge at termination.

HQT builds and integrates case management and records systems for state and local agencies, including interface work between operational systems and state and federal reporting programs.

Frequently asked questions