Medicolegal Death Investigation (MDI) FHIR Implementation Guide, published by HL7 International / Public Health. This guide is not an authorized publication; it is the continuous build for version 2.0.0-ballot2 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-mdi-ig/ and changes regularly. See the Directory of published versions

MDI Use Cases

The use cases described here do not make any assumptions about whether implementing systems are using FHIR Messaging or FHIR RESTful API. Implementations of this MDI FHIR IG will vary, and some may use a FHIR API rather than FHIR Messaging. In those cases, a MessageHeader and a Document Bundle can be exchanged without a Message Bundle wrapper. For more information, see Relationship between Messaging and REST and FHIR Exchange Module. Document Bundles may be exchanged between systems and persisted in document storage and management systems. See FHIR Documents and FHIR Bundles for additional guidance.

Death Case Record Creation and Update for Death Certificate

Death data for a case record can be exchanged bidirectionally between an MDI case management system (CMS) and an EDRS via a document bundle. This is the base use case for gathering information needed to develop a death certificate.

Scenario A:

1. Case record originates in the MDI CMS
2. MDI CMS sends data to EDRS in Document Bundle
3. EDRS completes death certificate with information from other sources (funeral home, etc.)

Scenario B:

1. Case record originates in EDRS
2. EDRS sends data to MDI CMS in Document Bundle
3. MDI CMS updates case record with MDI information
4. MDI CMS sends updated case record in new Document Bundle to EDRS
5. EDRS completes death certificate

FHIR Resources listed on Artifacts, MDI Profiles for Death Certificate:

• Bundle - Document MDI and EDRS: Document bundle profile providing a FHIR “wrapper” to contain a composition document.
• Composition - MDI and EDRS: Composition profile representing a data document exchanged between an MDI CMS and an EDRS that includes death investigation findings, such as:
  • Circumstances of death
  • Death date and certification of death
  • Cause and manner of death
  • Additional information, such as autopsy results, medical history, etc.
• MDI Cause Of Death Part 1

The Composition - MDI and EDRS provides the Tracking Number Extension for including case or file numbers used by various systems to identify the case. One Composition can have multiple tracking numbers with additional tracking numbers added over time, e.g., MDI CMS case number added to a file with an EDRS record number.

The Composition - MDI and EDRS uses many of the same profiles as (i.e., references) the VRDR & VRCL FHIR IGs. One exception is the MDI Cause Of Death Part 1 profile, which is based on the VRDR Cause Of Death Part 1 profile, but requires a performer, which is the cause of death certifier (coroner or medical examiner). The rationale for the heavier constraint here is to preserve the chain of cause-of-death determination and who made the determination.

Examples listed on Artifacts, MDI-defined Resource Examples for Death Certificate:

• Bundle - MDI and EDRS - Freeman: Document bundle for the Freeman example case.
• MDI and EDRS Composition - Freeman: Completed data document composition for the Freeman example case record.
• MDI and EDRS Composition - draft: Draft data document, with status = preliminary, and author and attester = "Temporarily Unknown", using the data-absent-reason extension.
• MDI Cause of Death Part 1 – Freeman: Observation with practitioner, who is the Cause of Death certifier (coroner or medical examiner)

Transmission of Forensic Toxicology Diagnostic Findings from LIMS to MDI CMS

Data from a forensic toxicology laboratory information management system (LIMS) can be sent to an MDI CMS via a diagnostic report and message bundle.

FHIR Resources listed on Artifacts, Forensic Toxicology Profiles:

• Bundle - Message Toxicology to MDI: Message bundle profile providing a FHIR “wrapper” to contain a message header and a diagnostic report from a forensic toxicology laboratory.
• MessageHeader - Toxicology to MDI: Message header profile indicating that a diagnostic report is the focus of the message.
• DiagnosticReport - Toxicology Lab Result to MDI: Diagnostic report profile providing forensic toxicology findings
• Specimen - Toxicology Lab
• Observation - Toxicology Lab Result: Analysis of specimen

Examples listed on Artifacts, MDI-defined Resource Examples for Forensic Toxicology:

• Bundle - Message Toxicology to MDI - Freeman: Message bundle for the Freeman example case.
• MessageHeader - Toxicology to MDI - Freeman: Message header specifying the focus of the message and providing source and endpoint example information.
• DiagnosticReport - Toxicology Lab Result to MDI - Freeman: Diagnostic report for the Freeman example case.
• Specimen & lab result observation examples (many))

Exchange of a PDF Report within the MDI Community

A PDF report, such as an Autopsy Report or Investigator’s Narrative, can be exchanged between an MDI CMS and another FHIR-enabled data system. The content may be included as inline base64 encoded data or be provided by direct reference (e.g., URL).

FHIR Resource listed on Artifacts, MDI Administrative Profiles:

• DocumentReference - MDI Report: The document type is required and is constrained by US Core to a LOINC value whose SCALE is DOC in the LOINC database or is the HL7 v3 Code System NullFlavor concept 'unknown'.

Examples listed on Artifacts, MDI-defined Resource Examples for Administrative Profiles :

• DocumentReference - MDI Report - Autopsy Report example: Example autopsy report included as a base-64 encoded PDF.
• DocumentReference - MDI Report - Investigator's Narrative example: Example investigator’s narrative referenced by example URL.

Transmission of a Death Certificate for Review

Death certificate information may be exchanged for review in several cases:

• Data Quality Improvement: Querying for information needed to properly code and classify the cause of death for data quality improvement. “Cause-of-death querying is a process by which the State health department contacts the medical certifier who completed the cause-of-death statement and asks for clarification or further information so that resulting mortality statistics may be as complete and accurate as possible.” (From CDC, Instruction Manual Part 20 - ICD-10 Cause-of-Death Querying (2013).)
• Cremation Clearance (also known as "cremation authorization"): Many states and jurisdictions require cremation clearance from a medical examiner / coroner to make sure the physical evidence is not needed for any further inquiries into the death. The rules about when cremation clearance is required vary among jurisdictions, but typically it is needed when the cause and manner of death information for the death certificate is provided by an attending physician or other provider, rather than the jurisdiction's medical examiner / coroner.

Data Quality Improvement Use Case Steps:

1. EDRS sends the death certificate to MDI case management system (CMS) for review.
2. Medical examiner / coroner reviews death certificate information, particularly the cause and manner of death
3. MDI CMS sends response with additional information.

Cremation Clearance Use Case Steps - The cremation clearance workflow starts after the death certificate is largely complete. A typical workflow, at a high level, includes:

1. Next of kin (or other authorized person or organization) requests cremation be the method of disposal and signs a cremation clearance request (CCR).
2. Funeral home provides death certificate information and submits the CCR to the jurisdiction's vital records office (VRO) electronic death record system (EDRS).
3. EDRS sends the CCR with the death certificate to MDI case management system (CMS) for review.
4. Medical examiner / coroner reviews death certificate information, particularly the cause and manner of death, and makes a determination.
5. MDI CMS sends to EDRS a cremation clearance authorization document with the status of the request.

This IG provides FHIR messaging artifacts for exchanging document bundles containing the death certificate information for review and additional information for cremation clearance, if needed.

FHIR Resource listed on Artifacts, Death Certificate Review Profiles:

• Bundle - Message Death Certificate Review: Message bundle profile providing a FHIR “wrapper” to contain a message header and a document bundle for death certificate review workflows.
• MessageHeader - Death Certificate Review: Message header profile indicating that a document bundle is the focus of the message, the reason for the message (e.g., cremation clearance), and additional information about the status of the death certificate.
• Bundle - Document Death Certificate Review: Document bundle profile providing a FHIR “wrapper” to contain a composition document.
• Composition - Death Certificate Review: Composition profile containing Death Certificate components defined in the Vital Records Death Reporting (VRDR) FHIR Implementation Guide as the first sections. Additional sections represent information often used for cremation clearance workflows and data quality reviews.
• Observation - Medical Information Data Quality
• Observation - Personal Information Data Quality
• Observation - Communicable Disease
• Observation - Embalmed
• Organization - Crematorium

This implementation guide does not define FHIR resources for other aspects of the cremation clearance workflow, such as fee payment.

Examples listed on Artifacts, MDI-defined Resource Examples for Death Certificate Review:

• Bundle - Message Death Certificate Review example
• MessageHeader - Death Certificate Review example
• Bundle - Document Death Certificate Review example
• Death Certificate Review Composition example for death data review request (example 1): Death data review request example
• Death Certificate Review Composition example for death data review response (example 2): Death data review response example
• Death Certificate Review Composition example for cremation clearance request (example 3): Cremation clearance request example
• Death Certificate Review Composition example for cremation clearance response (example 4): Cremation clearance response example
• Observation - Medical Information Data Quality example
• Observation - Personal Information Data Quality example
• Observation - Communicable Disease example
• Observation - Embalmed example
• Organization – Crematorium example