Skip to content

Integrate and harmonize waveform related concepts #27

@briangow

Description

@briangow

In waveform-reference-mapping-3 @p-talapova has been adding waveform concepts for the MIMIC-IV data.

In many cases the new concept does not exist in the Athena or other _delta tables (e.g. WAVEFORM). This is the case for the FAP (Femoral Arterial Pressure) signal for example. For this reason, it would be great to have thewaveform-reference-mapping-3 concepts integrated into released _delta tables.

In some cases a similar concept already appears in other delta tables or even Athena. For example for aVR I see these:

source table concept_id concept_name domain_id vocabulary_id concept_class_id standard_concept concept_code valid_start_date valid_end_date
MIMIC/Ontology/concept_delta 2061506642 aVR Measurement MIMIC4 mimic4wdb S AVR 5/7/25 12/31/99
WAVEFORM/Ontology/concept_delta 2082499989 aVR Waveform Metadata WAVEFORM WFE Lead S WF100009 12/5/25 12/31/99
Athena 1031335 Lead AVR Observation LOINC LOINC System LP7385-0 1/1/70 12/31/99
Athena 37544008 LEAD aVR Spec Anatomic Site CDISC Body Structure C90362

Given this, we may want to perform a harmonization step across libraries prior to integration (at least across the _delta tables, if none of the Athena concepts are standard).

I would assume that if the waveform concept will generally apply across datasets, that we'd lean towards adding the concept to the WAVEFORM _delta table as opposed to the MIMIC _delta table.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions