SQL for Revenue Cycle Analysts: Denials, A/R, and Underpayment Queries SQL for revenue cycle analysts answers one question over and over: where is the money stuck, and why? Charges, claims, remittances, and adjustments live in separate tables with separate owners. This article shows the query patterns that connect them: days in A/R, charge lag, denial
SQL for Revenue Cycle Analysts Read Post »
SQL for Financial Reporting: Trial Balance, Period Close, and Reconciliation Queries SQL for financial reporting differs from general analytics in one way that matters: every number must tie to something. A dashboard that is 2 percent off is a curiosity. A trial balance that is off by one cent is a failed control. This article
SQL for Financial Reporting Read Post »
SQL for Healthcare QA Analysts: Data Validation Queries for EHR Testing SQL for healthcare QA analysts is the skill that proves what an EHR build did to the data. A screen shows only part of that. A screen can display the right value while the table underneath holds a duplicate, a null, or a code
SQL for Healthcare QA Analysts: Data Validation for EHR Testing Read Post »
HIPAA-Safe Clarity SQL: How to Query Epic Data Without Exposing PHI HIPAA-safe Clarity SQL means every query returns only the data its purpose requires. You run it from an authorized source, and the output limits re-identification. Most privacy incidents in analytics do not come from attackers. They come from a well-meaning analyst who exports patient-level
HIPAA-Safe Clarity SQL Read Post »
Clarity LOS Calculation with DATEDIFF: Admit-to-Discharge Logic for Epic Analysts A Clarity LOS calculation looks like one line of SQL: DATEDIFF between admit and discharge. It is also the most common reason two Epic reports show different length-of-stay numbers for the same patients. The function counts calendar boundaries, not elapsed days, and the definition you
Clarity LOS Calculation with DATEDIFF Read Post »
Epic Clarity PAT_ENC Table: Columns, Joins, and Query Patterns for Analysts The Epic Clarity PAT_ENC table holds one row per patient encounter contact, and almost every visit-level report you will validate starts there. It also hides the most common reconciliation trap in Epic reporting: a row in PAT_ENC is not always a visit. This article
Epic Clarity PAT_ENC Table Read Post »
Epic Clarity SQL for Analysts: Common Tables, Query Patterns, and Data Validation A build validation that relies only on clicking through Hyperspace catches what’s visible on screen and misses everything underneath it — a diagnosis code mapped to the wrong category, an order type missing from a report’s underlying filter, a duplicate encounter inflating a
Epic Clarity SQL for Analysts: Common Tables, Query Patterns, and Data Validation Read Post »
