Lead Data Engineer

Dice is the leading career destination for tech experts at every stage of their careers. Our client, Business Needs Inc., is seeking the following. Apply via Dice today! Title:- Lead Data Engineer. This is a remote contract role. They MUST have EPIC Operational Data experience. Along with Snowflake, DBT, and SQL. We’d also want them to have Azure Devops experience to win. They need to be able to do the engineering and architecture work. Qual notes below along with the distinction between Billing and operational data in Epic. Need to focus on candidates that come from a Provider (Hospital) background and NOT from the Payer (insurance) side. Candidates could have both but they need the operational side which is the data related to a patient being admitted to the hospital and any associated data throughout their stay to discharge. Notes: In the EPIC EHR system, Operational Data and Billing Data serve different purposes and are used in distinct ways: Operational Data • Purpose: This data is primarily used for the day-to-day operations of healthcare facilities. It includes information that supports clinical workflows, patient care, and administrative processes. • Examples: Patient demographics, clinical notes, lab results, medication records, appointment schedules, and other data related to patient care and hospital operations • Storage: Typically stored in EPIC's Chronicles database for real-time access and in Clarity for reporting and analytics Billing Data • Purpose: This data is focused on the financial aspects of healthcare services. It is used for generating bills, processing insurance claims, and managing revenue cycles. • Examples: Charges for services rendered, insurance information, payment records, coding for procedures and diagnoses (e.g., ICD-10, CPT codes), and other financial transactions • Storage: Often integrated with EPIC's Resolute module, which handles billing and claims processing Qual Template Project Scope (dig into details here): • Looking for someone that understands the patient flows and orders, knows what the data does and the purpose of the data, etc • Building on top of EPIC core clarity data warehouse Why is req open? • Backfilling current CE that lacks EPIC Operational Data experience High-Level Individual Duties: • ETL ingestions and integrations • Build out the Snowflake Enterprise Data Warehouse and optimize data ecosystem • ETL troubleshooting • Work with engineers on business requirements and specs Must-Haves (Concepts & Tools): • Epic Operational Data • Understanding how EPIC ecosystem fits together with Snowflake • Snowflake • DBT • SQL What Will Win (formerly known as “Nice-to-Haves”): • CI/CD pipeline experience • Azure DevOps • Data Modeling Soft Skill Requirements • Strong communication and versatility Screening questions to ask/vet candidates? • Vet candidates on the type of Epic experience they have. • Operational Data: This data is primarily used for the day-to-day operations of healthcare facilities. It includes information that supports clinical workflows, patient care, and administrative processes. • Billing Data: This data is focused on the financial aspects of healthcare services. It is used for generating bills, processing insurance claims, and managing revenue cycles. • This is NOT what they are looking for.