mimic-eicu-mapping

Map equivalent clinical concepts between MIMIC-IV and eICU databases.

40|17|Updated Oct 27, 2025
One-click install
npx skills add https://github.com/hannesill/m4 --skill mimic-eicu-mapping
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mimic-eicu-mapping
Source: https://github.com/hannesill/m4/tree/main/src/m4/skills/system/mimic-eicu-mapping
Command: npx skills add https://github.com/hannesill/m4 --skill mimic-eicu-mapping

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill enables researchers to map equivalent concepts between MIMIC-IV and eICU databases, enabling cross-database research and easier external validation.

Core Features & Use Cases

  • Align tables, columns, and concepts across MIMIC-IV and eICU to support cross-dataset queries
  • Provide a consistent semantic layer for multi-center studies and model validation
  • Validate mapping accuracy by cross-checking core domains like Patients, Admissions, and ICU Stays

Quick Start

Map a MIMIC-IV concept to its eICU equivalent and confirm aligned semantics.

Frequently Asked Questions about mimic-eicu-mapping

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map MIMIC-IV concepts to eICU for cross-database research?

Yes, you can align MIMIC-IV and eICU schemas for cross-dataset queries by mapping equivalent tables, columns, and domain concepts. This semantic alignment supports multi-center studies and model validation across datasets with differing structures.

What is the best way to validate clinical model accuracy across MIMIC-IV and eICU?

Validating clinical models across MIMIC-IV and eICU involves mapping equivalent clinical concepts to create a consistent semantic layer. This allows you to translate queries across datasets and perform external validation by cross-checking core domains like Patients and Admissions.

Does mapping MIMIC-IV to eICU support structured outputs for research pipelines?

Mapping MIMIC-IV to eICU supports structured outputs designed for integration into research pipelines. It translates table and column mappings with aligned domain concepts, enabling automated multi-center studies and external validation across differing database schemas.

Can I cross-check core clinical domains like ICU stays when mapping eICU to MIMIC-IV?

You can cross-check core clinical domains like ICU Stays, Patients, and Admissions when mapping between eICU and MIMIC-IV. This validates mapping accuracy by ensuring aligned semantics and equivalent concepts across both clinical datasets.

Why translate clinical queries across MIMIC-IV and eICU datasets with differing schemas?

Translating clinical queries across MIMIC-IV and eICU datasets with differing schemas enables cross-database research and external validation. It establishes a consistent semantic layer, allowing queries built for one dataset to function on the other.