OHDSI / OHDSI/CommonDataModel

Multiple Death Records Due to Death_type or Cause - Version 5.4

Open
#758 6 comments 1 reaction 1 assignee View on GitHub

@RogerJCarlson is already working on this.

Since Sep 6, 2023.

Dominant language
HTML
Stars
1.1k
Forks
508
Avg merge
1h 30m
Merged PRs (30d)
3

Description

Issue Name: Multiple Death Records Due to Death_type_concept or Cause_concept Version 5.4

Issue Type: Duplicate records caused by multiple standard concept_ids for death cause or death type (provenance)

Description: http://ohdsi.github.io/CommonDataModel/cdm54.html#DEATH
The table description for the Death table has the following: "A person can have up to one record if the source system contains evidence about the Death". However, an ICD diagnosis code may map to multiple SNOMED codes:

ICD10: J96.21 (Acute on chronic respiratory failure with hypoxia (HCC))
maps to
SNOMED: 389086002 (Hypoxia) and 67905004 (Acute-on-chronic respiratory failure)
This results in two records with the same death date.

Similarly, a person may have death records from multiple systems (provenance), i.e. EHR and death registry.

Suggested Solution: For OMOP version 5.4, allow multiple records in the Death table caused by either the death_type_concept_id and/or cause_concept_id. However the Death_Date(s) must match.

Possible Implications:

  • CDM documentation will need to be modified.
  • The rules of the DQD (Data Quality Dashboard) will have to be adjusted to match.
  • Others?

Related forum post: https://forums.ohdsi.org/t/multiple-death-records-due-to-snomed-mapping/19517

Reported By: Roger Carlson

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.