This resource describes expected capabilities of an MDI CMS Server which is responsible for providing responses to the queries submitted by a Client. It lists FHIR profiles and search parameters that, at a minimum, should be supported by MDI CMS Servers. MDI CMS Clients have the option of choosing from this list to access necessary data.

This resource describes the expected capabilities of the Electronic Death Registration System (EDRS) Server actor, which is responsible for providing responses to the queries submitted by the EDRS Requestors. The complete list of FHIR profiles, RESTful operations, and search parameters supported by EDRS Servers are defined. EDRS Clients have the option of choosing from this list to access necessary data based on their local use cases and other contextual requirements.

This resource describes the expected capabilities of the toxicology lab Server actor which is responsible for providing responses to the queries submitted by toxicology lab Requestors. The complete list of FHIR profiles, RESTful operations, and search parameters supported by toxicology lab Servers are defined. toxicology lab Clients have the option of choosing from this list to access necessary data based on their local use cases and other contextual requirements.

This Bundle profile represents a Document Bundle exchanged between an MDI CMS and EDRS. It can be used for bi-directional exchange. It contains a Composition - MDI and EDRS.

This Composition profile represents data exchanged between an MDI CMS and an EDRS.

The Observation - Cause of Death Part 1 profile reflects the ordered causes of death asserted by the death certifier. The cause of death is initially specified with text. The MDI Observation - Cause of Death Part 1 artifact overlaps with the VRDR Cause Of Death Part 1 artifact.

The Observation - Contributing Cause of Death Part 2 profile is used to identify factors contributing to the cause of death as asserted by the death certifier. The MDI Observation – Contributing Cause of Death Part 2 artifact overlaps with the VRDR Cause of Death Part 2 artifact.

This Observation provides the death date and date pronounced dead. If the actual date of death is known, set value to type dateTime. If the date of death is not known, and a range is known, set value to type Period. The MDI Observation - Death Date artifact overlaps with the VRDR Death Date artifact.

This Observation provides the certified explanation of how the injury leading to death occurred. The MDI Observation - How Death Injury Occurred artifact overlaps with the VRDR Injury Incident artifact.

This Observation provides the conclusion arrived at upon completion of death investigation regarding the manner of death (e.g., natural, homicide, suicide, accident). The MDI Observation - Manner of Death artifact overlaps with the VRDR Manner of Death artifact.

This Observation provides an indication of the pregnancy status of the decedent. The MDI Observation - Decedent Pregnancy artifact overlaps with the VRDR Decedent Pregnancy Status artifact.

This Observation provides the conclusion arrived at during death investigation regarding the extent to which tobacco use contributed to the death of the decedent. The MDI Observation - Tobacco Use Contributed to Death artifact overlaps with the VRDR Tobacco Use Contributed To Death artifact.

This Observation records if an autopsy was performed, if autopsy findings are available, and the autopsy Performer (US Core Practitioner). The MDI Observation - Autopsy Performed Indicator artifact overlaps with the VRDR Autopsy Performed Indicator artifact.

This Procedure records the certification of death by the certifier. The MDI Procedure - Death Certification artifact overlaps with the VRDR Death Certification Procedure artifact.

This Location records the location of death. It is based on US Core Location and further constrains the type element location of death. The MDI Location - Death artifact overlaps with the VRDR Death Location artifact.

This Location records the location of an injury. It is based on US Core Location and further constrains the type element to location of injury. The MDI Location – Injury artifact overlaps with the VRDR Injury Location artifact.

This Bundle profile represents a Message Bundle from a forensic toxicology laboratory to an MDI CMS. It contains a Message Header and a DiagnosticReport - Toxicology Lab Result to MDI.

This MessageHeader identifies the DiagnosticReport being sent from a forensic toxicology LIMS to an MDI CMS.

This resource defines the characteristics of a message that can be shared between a forensic toxicology system and an MDI CMS. This resource is used by CapabilityStatement resources and defines Toxicology Lab Results as the the type of event that initiates the message.

This profile contains constraints to the US Core Diagnostic Report Profile to address the use case for sending data from a forensic toxicology LIMS to an MDI CMS. Each analyzed specimen, represented by a Specimen - Toxicology Lab resource, must be referenced by at least one Observation - Toxicology Lab Result and may be referenced by more than one Observation - Toxicology Lab Result. For specimens received but not analyzed, the laboratory should provide a reason for no analysis in the DiagnosticReport.conclusion and/or each unanalyzed specimen’s Specimen - Toxicology Lab Specimen.note.

This Specimen profile identifies and describes the specimen sent by a medical examiner, coroner, or autopsy performer to a toxicology lab for analysis. For specimens received but not analyzed, the laboratory should provide a reason for no analysis in the DiagnosticReport.conclusion and/or each unanalyzed specimen’s Specimen - Toxicology Lab Specimen.note. The laboratory may use the Specimen.condition to describe the state of the specimen via codes from the extensible value set hl7VS-specimenCondition and/or use the Specimen.note to describe details or issues about the specimen.

This Observation profile describes forensic toxicology laboratory test results from analysis of a specimen sent by a medical examiner, coroner, or autopsy performer to the laboratory.

This DocumentReference profile constrains the US Core DocumentReference Profile to support exchanging death investigation documents, such as an Autopsy Report or Investigator’s Narrative. The content may be included as inline base64 encoded data or be provided by direct reference (e.g., URL). 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’.

Bundle - MDI and EDRS: Freeman example

MDI and EDRS Composition: Freeman example

Composition - MDI and EDRS: draft example with status=preliminary, author & attester using data-absent-reason extension

Observation - Cause of Death Part 1: Freeman example

Observation - Cause of Death Part 1: Freeman example, specifying interval quantity (days)

Observation - Contributing Cause of Death Part 2: Freeman example

Observation - Death Date: Freeman death date & location example

Observation - Death Date: period example

Observation - Death Date: partial date/time example

Observation - How Death Injury Occurred: Freeman Medication Ingestion (fentanyl) example

Observation - Manner of Death: Freeman, accidental example

Observation - Decedent Pregnancy: Freeman example

Observation - Tobacco Use: Freeman example

Observation - Autopsy Performed Indicator: Freeman example

Procedure - Death Certification: Freeman example

Location - Death: Atlanta GA Freeman example

Location - Death: address as string example

Location - Death: latitude & longitude example

Location - Injury: Atlanta GA Freeman example

Bundle - Message Toxicology to MDI: Freeman example

MessageHeader - Toxicology to MDI: Freeman example

DiagnosticReport - Toxicology Lab Result to MDI: Freeman example

Specimen - Toxicology Lab: Freeman Blood examples

Observation - Toxicology Lab Result: Freeman Ethanol Blood example

Observation - Toxicology Lab Result: Freeman 4-anpp Blood example

Observation - Toxicology Lab Result: Freeman Acetylfentanyl Blood example

Observation - Toxicology Lab Result: Freeman Fentanyl Blood example

Specimen - Toxicology Lab: Freeman Urine example

Observation - Toxicology Lab Result: Freeman Ethanol Urine example

Observation - Toxicology Lab Result: Freeman 4-anpp Urine example

Observation - Toxicology Lab Result: Freeman Acetylfentanyl Urine example

Observation - Toxicology Lab Result: Freeman Fentanyl Urine example

Observation - Toxicology Lab Result: Freeman Norfentanyl Urine example

Observation - Toxicology Lab Result: Freeman Xylazine Urine example

Specimen - Toxicology Lab: Freeman Vitreous Humor example

Observation - Toxicology Lab Result: Freeman Ethanol Vitreous Humor example

Specimen - Toxicology Lab: Freeman Bile example

Specimen - Toxicology Lab: Freeman Liver example

Specimen - Toxicology Lab: Freeman Stomach Contents example

Example of US Core Organization - UF Health Pathology Labs, Forensic Toxicology Laboratory

Example of US Core Patient - Alice J. Freeman, decedent

US Core Patient: Unknown Name - Decedent where there is no information known about the patient. Assume that the system will assign a tracking number (e.g., medical record number, case number, or other). Uses Extension: Data Absent Reason.

Example of US Core Practitioner - Dr. Bruce Goldberger, toxicologist

Example of US Core Practitioner - Dr. Sam Jones, medical examiner, death certifier

Example of US Core Practitioner - Dr. J.M. Lehz, autopsy performer

DocumentReference - MDI Report: Autopsy Report example

DocumentReference - MDI Report: Investigator’s Narrative example

This Extension contains a tracking number, such as a case number or file number assigned by an MDI organization, EDRS, or other involved organization to facilitate recognition of common case records across disparate systems and over time.

A set of codes indicating the type of certifier (medical examiner/coroner, certifying physician, etc.) The MDI ValueSet - Certifier Types artifact overlaps with the VRDR Certifier Types VS artifact.

A set of codes that reflect the extent to which tobacco use contributed to the person’s death. Based on Contributory Tobacco Use (NCHS)[2.16.840.1.114222.4.11.6004]. The MDI ValueSet - Contributory Tobacco Use artifact overlaps with the VRDR Contributory Tobacco Use VS artifact.

This value set contains codes that describe the approach to establishing a date. The MDI ValueSet - Date Establishment Approach artifact overlaps with the VRDR Date of Death Determination Methods Value Set artifact.

A set of codes that reflect whether the decedent was pregnant at or around the time of death. Based on Pregnancy Status (NCHS)[2.16.840.1.114222.4.11.6003]. The MDI ValueSet - Death Pregnancy Status artifact overlaps with the VRDR Pregnancy Status artifact.

A set of codes to reflect the manner that a person died. The MDI ValueSet - Manner of Death artifact overlaps with the VRDR Manner of Death VS artifact.

Code values reflecting the death location of the decedent (e.g., hospital, home, hospice). The MDI ValueSet - Place of Death artifact overlaps with the VRDR Place of Death VS – PHVS_PlaceOfDeath_NCHS artifact.

This value set contains codes to that identify the type of tracking number.

Role of the decedent in a transportation incident resulting in a death-related injury. The MDI ValueSet - Transportation Incident Role artifact overlaps with the VRDR Transportation Incident Role artifact.

Value set with Yes, No and Unknown. The MDI ValueSet - Yes No Unknown artifact overlaps with the VRDR Yes No Unknown artifact.

Valueset with Yes, No, Unknown, and Not Applicable. The MDI ValueSet - Yes No Unknown NotApplicable artifact overlaps with the VRDR Yes No Unknown NotApplicable artifact.

Codes that reflect whether the decedent was pregnant at or around the time of death. Includes the concepts defined in Pregnancy Status (NCHS)[2.16.840.1.114222.4.11.6003] which are from the PHIN VS (CDC Local Coding System)[2.16.840.1.114222.4.5.274] The MDI CodeSystem - Death Pregnancy Status artifact overlaps with the VRDR Pregnancy Status Codes artifact.

Local Component Codes for observation components that lack an appropriate LOINC code. The MDI CodeSystem - Local Component Codes artifact overlaps with the VRDR Local Component Codes artifact.

This code system contains codes for use in MDI CMS.

Parameters - SNOMED US Version