etl-to-omop-cdm

Map coded OpenMed clinical facts into OMOP CDM v5.4 records.

5.0k|615|Updated Oct 4, 2025
One-click install
npx skills add https://github.com/maziyarpanahi/openmed --skill etl-to-omop-cdm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: etl-to-omop-cdm
Source: https://github.com/maziyarpanahi/openmed/tree/main/skills/etl-to-omop-cdm
Command: npx skills add https://github.com/maziyarpanahi/openmed --skill etl-to-omop-cdm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns OpenMed-extracted and terminology-coded clinical facts into validated OMOP CDM v5.4 records, reducing the effort required to integrate clinical note NLP with OHDSI and ATLAS analytics.

Core Features & Use Cases

  • Clinical Event Mapping: Routes conditions, medications, and laboratory measurements into condition_occurrence, drug_exposure, and measurement tables.
  • Vocabulary Standardization: Applies the OHDSI source-to-standard concept pattern using user-supplied ICD-10-CM, SNOMED, RxNorm, LOINC, and Athena vocabulary data.
  • CDM Data Quality: Handles required fields, NLP provenance type concepts, dates, unmapped concepts, de-identified source values, and domain-based routing.
  • Use Case: Convert coded entities from clinical notes into OMOP rows for cohort discovery, quality measurement, observational research, and ATLAS analysis.

Quick Start

Use the etl-to-omop-cdm skill to map my coded OpenMed clinical facts into validated OMOP CDM v5.4 condition, drug, and measurement rows using my licensed OHDSI vocabulary bundle.

Frequently Asked Questions about etl-to-omop-cdm

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

FAQPage Schema
How do I map clinical NLP facts into OMOP CDM v5.4 records?

To map clinical NLP facts into OMOP CDM v5.4, this Skill routes coded OpenMed entities into condition_occurrence, drug_exposure, and measurement tables using your OHDSI vocabulary data for standard concept mappings and domain-based routing.

What vocabulary data do I need for OHDSI ETL workflows with clinical notes?

OHDSI ETL workflows require user-supplied vocabulary data including ICD-10-CM, SNOMED, RxNorm, LOINC, source concepts, standard mappings, NLP provenance type concepts, domains, units, and qualitative values to successfully transform clinical note entities.

Can I use coded clinical note entities for ATLAS cohort analytics?

Yes, coded clinical note entities can be used for ATLAS cohort analytics by converting the extracted NLP facts into validated OMOP CDM rows, which directly support cohort discovery, observational research, and quality measurement.

How does clinical event mapping handle unmapped concepts and data quality?

Clinical event mapping handles unmapped concepts and data quality by applying OHDSI source-to-standard concept patterns, managing de-identified source values, resolving dates, and ensuring required fields and NLP provenance type concepts are accurately populated.

Does this clinical NLP to OMOP mapping require a licensed Athena vocabulary bundle?

Yes, converting coded clinical NLP facts into OMOP CDM rows requires a user-supplied OHDSI vocabulary bundle, utilizing licensed Athena data for ICD-10-CM, SNOMED, RxNorm, and LOINC standard mappings to ensure terminology standardization.

What is the best way to integrate clinical note NLP with OHDSI analytics?

The best way to integrate clinical note NLP with OHDSI analytics is to apply an ETL process that standardizes extracted entities into OMOP CDM v5.4 condition, drug, and measurement records, reducing manual integration effort for ATLAS studies.