Job Description
We are seeking an experienced Epic Subject Matter Expert (SME) with deep expertise in Epic Clarity to lead the data mapping and extraction efforts for our Revenue Cycle Management (RCM) Semantic Model project. The ideal candidate will bridge the gap between Epic’s complex clinical/financial workflows and our GCP/Data Warehouse environment, ensuring that the critical KPIs (Net Collection Rate, Denial Rates, AR Aging, etc.) are built on accurate, high-integrity data.
Key Responsibilities:
Data Mapping & Lineage: Lead the end-to-end mapping of data elements from Epic Chronicles and Clarity to the target Data Warehouse schema. Identify the correct tables and columns for dimensions such as Patient, Practitioner, Point of Care, and Insurance.
KPI Logic Translation: Translate complex RCM business definitions into technical SQL logic using Epic Clarity tables (e.g., CLARITY_TDL, ARPB_TRANSACTIONS, HSP_TRANSACTIONS).
Database Architecture: Utilize deep knowledge of Epic Clarity database structures to design efficient extraction patterns, specifically focusing on Professional (PB) and Hospital Billing (HB) modules.
Stakeholder Alignment: Collaborate with clinical and financial business owners to validate that data pulled from Clarity accurately reflects the front-end workflows seen in the Epic Hyperspace application.
Required Skills & Experience:
Epic Certification: Active certification in Epic Clarity (Data Model) is highly preferred (specifically Resolute PB, HB, or Prelude/ADT).
SQL Mastery: Expert-level SQL skills for querying massive datasets and performing complex joins across Clarity tables.
Domain Expertise: Comprehensive understanding of Revenue Cycle Management (RCM), Population Health workflows, including charge capture, claim submission, payment posting, and denial management.
- Epic Ecosystem: Familiarity with how data flows from Chronicles (real-time) to Clarity (relational) and Caboodle (dimensional).
Analytical Mindset: Ability to troubleshoot why a number in a dashboard doesn’t match a number in Epic and identify the specific workflow or table discrepancy.
