Skip to content

Add Epic EHI Tables to CLIF mapping guide#2

Open
clifford-clif wants to merge 2 commits intoCommon-Longitudinal-ICU-data-Format:mainfrom
clifford-clif:epic-ehi-mapping-guide
Open

Add Epic EHI Tables to CLIF mapping guide#2
clifford-clif wants to merge 2 commits intoCommon-Longitudinal-ICU-data-Format:mainfrom
clifford-clif:epic-ehi-mapping-guide

Conversation

@clifford-clif
Copy link

Summary

This PR adds comprehensive documentation for mapping Epic EHR data to CLIF format, leveraging the publicly accessible Epic EHI Export Schema.

Key Resources Documented

Credit to Wan-Ting for sharing the open.epic.com link in the weekly call.

Files Added

  • *\Epic/README.md* - Comprehensive mapping guide covering all CLIF tables
  • *\Epic/epic_ehi_clif_mapping.csv* - Field-level mappings (68 mappings across 14 CLIF tables)
  • *\Epic/common_flowsheet_rows.csv* - Common flowsheet row names for vitals, respiratory, position, CRRT

CLIF Tables Covered

Table Mapping Status
patient
hospitalization
adt
vitals
labs
medication_orders
medication_admin_continuous
medication_admin_intermittent
respiratory_support
crrt_therapy
microbiology_culture
sensitivity
position
code_status
hospital_diagnosis

Why This Matters

Previously, Epic sites needed UserWeb access to discover table mappings. This guide provides:

  1. A public starting point for Epic → CLIF ETL
  2. Field-level documentation for each CLIF table
  3. Flowsheet row references (the most site-specific part of Epic ETL)

Notes

  • Flowsheet row IDs (FLO_MEAS_ID) are site-specific - this guide provides common names to search for
  • Some mappings require joins to ZC reference tables
  • Medication categorization requires mapping therapeutic classes to mCIDE

cc: @08wparker

- Document publicly accessible Epic EHI Export Schema (open.epic.com)
- Create comprehensive table-by-table mapping from Epic to CLIF
- Include field-level mappings in CSV format
- Add common flowsheet row reference for vitals, respiratory, position, CRRT
- Reference both EHI tables and Clarity Data Handbook resources

This enables Epic sites to build their CLIF instances without requiring
Epic UserWeb access for initial table discovery.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant