← All selected work
CASE STUDY 01 — QUALITY & PATIENT FLOW

Hospitalist & provider performance scorecards

Built the hospitalist dashboard within Epic, developing the individual Reporting Workbench reports and SlicerDicer content behind its patient-flow and quality measures. Brought those measures together for the quality team, hospitalist leaders, and nursing / operational stakeholders.

Audience & decisionsQuality team · Hospitalist leaders · Nursing & operational teams
Tools & strengthsEpic · Reporting Workbench · SlicerDicer · Radar dashboards
The business questions

Several questions. One reporting foundation.

My contribution

From source records to decision support.

Owned the metric-level reporting development behind the Epic hospitalist dashboard, building each requested measure through Reporting Workbench and SlicerDicer rather than simply assembling an existing set of results. Translated quality-team requirements into report criteria, defined patient populations, date parameters, groupings, and summary measures for patient status, observation duration, length of stay, discharge timing, and sepsis reporting. Brought the resulting reporting content together as Epic dashboard components so stakeholders could review related measures in a shared clinical context.

What made the work demanding

Each measure required its own reporting logic and validation: which encounters qualified, which status and event timestamps applied, how results were grouped, and what calculation answered the business question. Combining Reporting Workbench report content and SlicerDicer sessions in one dashboard also required consistent definitions and reporting periods across the underlying sources.

What the work enabled

Gave the quality team and clinical leaders a shared reporting view inside Epic for reviewing prolonged stays, discharge milestones, and sepsis measures. Supported focused follow-up with nursing, physician, and operational teams. Worked collaboratively with Community Connect partners to validate reporting content and support release readiness, keeping stakeholder review connected to the reporting build.

Epic reporting development

Built measure by measure. Delivered inside Epic.

Reporting Workbench · Report criteria & results

Developed the operational report content behind the requested measures, aligning the patient population, filters, output columns, and summary logic with the quality team’s questions.

SlicerDicer · Populations, slices & measures

Built the SlicerDicer reporting content used to summarize and compare the relevant patient populations, with criteria and groupings tied to the measure being evaluated.

Epic dashboards · Radar components

Combined the reporting content into dashboard components within Epic, giving users a consolidated view of related patient-flow and quality measures.

Community Connect · Collaborative validation

Worked with Community Connect partners on reporting validation and release readiness, connecting the metric build with stakeholder review and a shared understanding of the results.

What the reporting covered.

AreaReporting scopeDecision context
Patient statusInpatient and observation populationsDistinguish the groups before comparing throughput.
Observation duration<24 hours · 24–48 hours · >48 hoursIdentify the distribution of shorter and prolonged observation stays.
Length of stayAverage LOS · Average excess days per dischargeSupport review of stay duration and potential discharge barriers.
Discharge timingDischarge order by 10:00 · Patient discharge by 12:00 / 14:00Compare ordering and departure milestones.
SepsisVolume · Order-set utilizationSupport quality review of use patterns and the relevant patient population.
Validation & analytical judgment

Numbers that can be explained.

These checks make the analytical approach concrete. Where original validation artifacts are unavailable, this section describes the relevant checks rather than implying a published audit trail.

Validate before comparing

Confirm encounter grain, department attribution, status history, and the eligible population for each measure.

Check timing boundaries

Test observation duration bins at 24 and 48 hours; define whether times refer to order entry, patient departure, or another event.

Reconcile to operational evidence

Compare period totals and selected encounters with source reporting and the quality team’s expected activity.

Validate the Epic reporting content

Check the Reporting Workbench criteria and result columns, SlicerDicer populations and summary measures, and the dashboard components against the intended metric definitions. Confirm that report content and dashboard summaries use the expected periods and populations.

Keep unresolved definitions visible

The discharge-order-to-discharge interval needs the source report open to confirm direction and units; it is not presented here as a finalized metric.

Built in Epic using Reporting Workbench and SlicerDicer, with dashboard content organized in Epic’s Radar reporting framework. The original dashboard image and precise definition of the discharge-order interval are not included.
← Selected workNext: Baby-Friendly maternity quality reporting ↗