Electronic death registration and vital records systems

Reference article · 5 min read

A vital records system holds the legal record of births, deaths, and fetal deaths, and in many jurisdictions marriages and divorces. Registration is usually statewide under a state registrar, while local registrars and county clerks accept filings and issue certified copies at the counter. The same system serves hospitals, funeral homes, clinicians, medical examiners and coroners, and the federal statistical system.

Electronic death registration is often the first piece an agency replaces, because it involves the most outside participants and the tightest time pressure. Birth registration, amendments, issuance, and statistical reporting either live in the same platform or exchange data with it. Understanding how a record moves is the fastest way to write requirements that hold up in practice.

How a death record moves

The funeral director enters the decedent's personal information, from name and place of death to Social Security number and veteran status. The medical certifier, an attending clinician where state law allows, or a medical examiner or coroner in reportable cases, completes cause and manner of death and signs electronically. The local registrar registers the record once both halves reconcile, and burial, cremation, and transit permits follow.

Case routing. A funeral home opens a case and refers it to a certifier. Lookup that depends on staff typing a name correctly produces duplicates and stalled cases.
Reportable referral. Deaths falling to the medical examiner or coroner need a clean path out of the clinician queue and back, including dropping a record to pending.
Deadlines. Filing and certification windows are set by state law and vary. Build reminders and supervisor escalation into the system instead of relying on phone calls.

Birth registration and what depends on it

Birth registration starts with a hospital birth clerk working from a parent worksheet, and with midwives or parents for out-of-facility births. Attachments change the legal record: acknowledgment of paternity, court orders establishing parentage, and the request for a Social Security number at birth. Delayed registration, adoption, and foundling cases need their own workflows, and records sealed by statute or court order need a separate, tightly controlled path.

Coding, national reporting, and amendments

Certifiers enter cause of death as free text in a causal sequence, not as codes. Those literals become ICD codes, and jurisdictions differ in how much coding they do locally versus through the automated systems used by the National Center for Health Statistics. Data reaches NCHS under cooperative agreements, generally through the NAPHSIS inter-jurisdictional exchange record layout and, increasingly, the HL7 FHIR implementation guide for vital records death reporting. When a medical examiner awaits toxicology or autopsy findings, the record registers with cause pending and is updated later by supplemental report. Ask how a system ages that pending queue and reports backlog by certifier and office.

Amendments follow different evidence standards depending on what changes: a typographical correction, parent information, a court-ordered name change, a gender marker change, an adoption, or cause of death. Require full version history: the original record, each amendment, the evidence accepted, the approver, and the date. What a certified copy must show about an amendment is jurisdiction specific, so confirm the rule with counsel before configuring it.

Issuance, security paper, and online ordering

Certified copies are the public-facing half of the program and the part most exposed to fraud. Most states restrict who may obtain one, and eligibility must be checked in every channel.

Security stock. Track paper by serial number from receipt to issuance to void, and reconcile inventory by drawer and printer. Distributed printing in county offices multiplies the problem.
Identity proofing. Remote ordering needs an assurance approach matched to the risk: documentary verification, knowledge-based methods, or a state credential. Federal digital identity guidance is a useful reference.
Order channels. Many jurisdictions use a third-party ordering service alongside their own portal. Confirm who holds the data, how fees and refunds work, and how suspected fraud is escalated.
Verification instead of copies. Requesters who only need to confirm an event can use the NAPHSIS electronic verification services, which cover birth verification and fact of death.

Exchange, access control, and surge planning

Records often belong to more than one jurisdiction, as when a resident of one state dies in another. The State and Territorial Exchange of Vital Events, operated by NAPHSIS, is the standing channel between jurisdictions, and a replacement system should participate natively rather than through re-keying.

External accounts at funeral homes, hospitals, and medical practices turn over continuously. Require role-based permissions, an accountable approver for each account, deactivation on inactivity, logging of every search and view, and alerting on searches of employee or high-profile records. Mass fatality events and prolonged emergencies raise volume and add temporary certifiers, so test capacity deliberately and keep a continuity plan that includes offline filing forms and a path for entering those records afterward.

What to ask before you buy

Which jurisdictions run this product, and may we speak with their registrars and IT staff without the vendor present?
Is jurisdiction-specific law handled by configuration, by scripting, or by custom code that becomes our upgrade problem?
Can you demonstrate NCHS transmission, interjurisdictional exchange, and verification interfaces working rather than described?
What is the migration plan for legacy records, images, and indexes, and who validates the result?
What must hospitals and funeral homes do to integrate, and what supports certification from an electronic health record?

In the contract, pin down data ownership and export, support terms matched to statutory filing deadlines, security and audit requirements, and the price of future rule changes and interfaces. Plan external user training early, because adoption by funeral homes and certifiers usually decides whether a rollout works.

HQT builds and modernizes records systems for state and local agencies, including data migration, integration, and public-facing ordering workflows.

Frequently asked questions

What is the difference between STEVE and EVVE?

Both are services of NAPHSIS, the association of state and territorial vital records jurisdictions. STEVE, the State and Territorial Exchange of Vital Events, moves registration data between jurisdictions when an event crosses state lines. EVVE supports electronic verification of vital events, letting authorized requesters confirm a birth record or a fact of death instead of relying on a paper certificate. Participation terms and the agencies eligible to use each service are set by NAPHSIS and the jurisdictions, so confirm current details with your state registrar.

Can a county buy its own electronic death registration system?

In most states, death registration itself is a statewide function, and counties participate in the state system rather than procuring a separate registration platform. Counties more often buy systems around it, such as imaging and indexing of historical records, counter queuing, cashiering, and local online ordering. Before starting a procurement, confirm with the state registrar what the state system covers and what interfaces it makes available to local registrars.

How should a system handle cause of death cases that are still pending?

When a medical examiner or coroner is waiting on toxicology or autopsy results, the record is normally registered with the cause listed as pending so that disposition and benefits are not held up. The cause is completed later through a supplemental report, and that update has to flow to the state file and on to NCHS. Require a pending queue with aging, reminders to the certifying office, and backlog reporting by certifier and office.

What should we require before turning on online ordering for certified copies?

Require eligibility checks that match your state's rules on who may receive a certified copy, an identity proofing method appropriate to the risk, and full audit logging of every order and search. Settle who holds the applicant data, how fees, refunds, and chargebacks are handled, and how suspected fraud is escalated and to whom. Also decide where copies are printed, because distributed printing spreads security paper inventory control across more offices.

What matters most when migrating from a legacy EDRS?

Historical data is usually the hardest part: decades of records in older formats, scanned images of varying quality, and indexes that staff rely on to find records at the counter. Require a written migration plan with validation by your own staff, not only by the vendor, and a defined approach for records that cannot be matched cleanly. Plan for a period when both systems are readable, and train funeral homes, hospitals, and certifiers before cutover, since their adoption sets the pace.