Back to work

HEALTHCARE OPERATIONS

Clinical Productivity

Daily productivity for registered dietitians, inside Elevra, the hospital operations platform at Compass Healthcare Digital.

Role
Lead Product Designer
Scope
Workflow, role and state behavior
Engineering
Production RBAC implementation
Status
Shipped to production

The turning point

The daily record got one owner.

I was the lead product designer on the module, accountable for its requirements and design from the first workbook review to production handoff.

Daily productivity lived in shared workbooks that managers rebuilt by hand at month end. A workbook can record who changed a cell. It cannot say whose day it was, or which of two entries should govern, so the edit trail alone never settled who was allowed to correct it.

I built the record around the dietitian who owns the day, with manager approval and authorship kept as separate permissions. Submit and lock shipped. The correction path was proposed before pilot: the manager authorises a reopen, the dietitian changes the values, and both versions are kept. Day-level detail costs a wider table and careful handling of weekends and leave.

Edits collided

Concurrent edits overwrote entries, and the file could not say whose day it was.

The day was split

Dietitians covering several units logged in separate workbooks, so their full day never showed.

Managers reconciled

Managers merged and checked each workbook by hand, every month, for hours.

Gaps stayed hidden

A missing entry stayed invisible until someone opened the file and looked.

The problem

The workbook recorded a value. It could not tell the manager who owned the day.

Daily productivity lived in shared Excel files, one per cost center and month, edited in circulating copies. Excel can record who changed a cell. Nothing in the workbook said whose day it was, or which entry should govern it. History alone did not establish who could correct the record.

Registered dietitian: "I logged my activity for the day. Who changed my numbers?"

Operating model reconstructed

Shared workbookTwo writers, one cell, one file per cost center

productivity-tracker-august.xlsx
RDDateHoursR. DempseyAug 133.5 hrsK. SimmonsAug 134.5 hrsB. NwosuAug 142.0 hrsM. VegaAug 144.0 hrs

2:02K. Simmonsoverwritten4.5 hrs

2:41R. Dempseythe file keeps this one2.5 hrs

Cell C13 holds 4.5 hours, entered by one dietitian, until a second entry of 2.5 hours from a circulating copy replaces it. The sheet keeps no revision mark, no author, and no trace of the first value.

Owned recordTwo RDs, two records, one writer each

ElevraSubmitted, locked

Kayla SimmonsRD, Inpatient adult

Day
Thu, 13 August 2026
Hours
4.5
Care setting
Acute medical, 4 East

Revisions

  1. 5:10 PMSubmitted by K. Simmons, ownerLocked at submit.
  2. 2:41 PMR. Dempsey’s entry went to her own record
  3. 2:02 PMDraft created by K. Simmons

See it

Managers needed the missing day, not another percentage.

Recreated from the shipped workflow, not screenshotted. Switch surfaces, then expand either one full screen.

Bo is guidingStep 1 of 16

Elevra

Sacred Heart Medical

Clinical productivityWeekly submissions

Weekly submissions

Mar 2–6, 202614 team membersDemo data

DietitianMonMar 2TueMar 3WedMar 4ThuMar 5FriMar 6Last reminder
2+ days missing6
Blessing Nwosu2
Ian McAllister2
Kayla Simmons2
Luis Navarro4
Marisol Vega2
Vanessa Rhodes3
1 day missing5
Katie Holbrook1
Lindsey Barker1
Nicole Hartsell1
Rachel Dempsey1
Thiago Carvalho1
11 people with missing submissions

Where it came from

These are real screens from the shipped product, reconstructed for this site. Every dietitian, site and record shown is demo data.

From workbook to roster

A shared spreadsheet, then a day grid, then a roster ordered by what is missing.

My role

I defined the module and designed it end to end.

My responsibility

I worked out what a dietitian's day holds, who may change it once it is submitted, and what a manager sees when a day is missing.

I wrote the requirements and designed the dietitian and manager views.

RecordOwnerState
Day enteredDietitianSubmitted
Day missingManagerFollow-up

How I worked

  • Started from the workbooks. The requirements came from how dietitians actually logged their days and how managers reconciled them by hand at month end.

  • Designed in two tracks. One version inside Elevra's existing design library for this release, and an unconstrained version showing where the module could go next.

  • Scoped the first release. It sat on Elevra's existing assessment forms, with census integration, leadership dashboards and AI-assisted entry held for later. The module went through stakeholder review and reached production.

Outside my remit

Engineering build
Implementation on Elevra's assessment infrastructure and the production release.

Elevra / Daily record

Rachel Dempsey

Registered dietitian, record owner

Date of service12 March 2026
Care settingOutpatient adult
StatusSubmitted
Submitted4:40 PM
Manager view, same record

Give each day an owner.

The RD owns the daily submission. Managers inspect the same record.

Patient care setting

Start with the care setting

Inpatient adultOutpatient adult

Outpatient adult

Nutrition clinic

Comprehensive1
Limited3
Save draft

Show the relevant fields.

Selected care settings determine which activity fields appear.

Rachel Dempsey / This week

Tuesday is missing

MonTueWedThuFri
ReasonNothing logged
FlaggedNext morning
View record

Make missing days visible.

Day-level exceptions show where a manager needs to look.

Evolution

One record supported different responsibilities.

The RD still owned the daily record. Managers could inspect its state and exceptions, but did not author the work on the RD’s behalf. Manager approval and RD authorship were deliberately separate permissions.

Design precedent

Access control standards and health information research describe separation of duties: authority is split so a restricted action cannot be carried out by one person alone.

Bo is guiding

The RD authors the dayA registered dietitian logs one day’s work here.

Productivity log

Aug 14, 2026

Draft
Date of serviceAug 14, 2026
Patient care setting
Quick entry
Care settingComp.LimitedTotalGroupRemote
Inpatient adultNo
Filled from quick entry: Comp., Limited, Total, Group

4 of 4 required

The manager reads the same recordThe same entry arrives here. Nothing is retyped.

Team Submissions, August 2026
847Assessments
82%Team compliance
Kayla SimmonsRD, Inpatient adult

Tue, Fri missing3 of 5 days

Mon 10Submitted 9:05 AM
Tue 11No submission
Wed 12Submitted 12:40 PM
Thu 13Submitted 4:40 PM
Fri 14No submission

Recreated from the shipped product with a stand-in roster.

The evidence layer

Three decisions shaped what shipped.

Use the platform that already owns assessments.

Clinical Productivity became a workflow inside Elevra's existing Assessments infrastructure, not a new platform.

The pain was shared files, fragmented records, and manual aggregation.

Elevra, Assessments
Reused from ElevraAlready built, used as isShellnavigation and page frameDesign librarystyled buttons, fields, tablesForm.iodraws forms, checks entriesAssessmentsElevra's existing productClinical ProductivityNew workflow, built insideuses its steps and permissionsBuilt new for itCould not be reusedProduction data modelwhere each record is savedRole-based accesswho can view and approvePower BI datasetsfeeds for managers’ reports
In short. Built inside a product Elevra already had. It reused what existed and built only the three pieces that were missing.

Only show the fields this care setting requires.

Selecting a care setting is what creates its activity fields; an unselected setting has none to fill.

Most of the source schema is irrelevant on any single day.

Design precedent

Public-sector design systems show a related question only when an earlier answer makes it relevant.

What it cost

A shorter-looking form can still be incomplete: fields were missing from the polished interface.

Care setting

Activity records

Inpatient adultAcute medical, 4 East

Unit rule awaiting confirmation

Outpatient adultNutrition clinic, Suite 210

Inpatient pediatrics, Outpatient pediatrics: no fields

Checking a care setting is what creates its activity fields. Nothing is hidden and re-shown: an unchecked setting has no fields to submit, which is why the source schema’s full twelve almost never appear on one day.

Flag only what a rule can explain.

The manager surface uses day-level status, with explicit rules for data-quality exceptions.

Managers were reconciling the monthly result by hand.

Design precedent

Studies of clinical decision support find clinicians override about half or more of system alerts, and some of those overrides dismiss warnings that mattered.

What it cost

Day-level detail creates a wider table and needs careful weekend and PTO handling.

Bo is guidingStep 1 of 3

Submission status

SubmittedMissingReviewDraftUpcoming
Team memberMonTueWedThuFriAction
Rachel DempseyFlags automatically the next morning
Kayla SimmonsStill open for the RD to send
Blessing NwosuHours don't match the logged categories

Rachel Dempsey, Tue

StateNo submitted log on an expected workdayRule that firesAn expected workday closes without a submitted logActionFlagged the next morning, not at month end
A percentage summarizes the month. A day-level grid tells a manager where to act. The sample is reconstructed and contains no employee or facility data.

When a missing day gets seen

Two rules applied to seven reconstructed records, August 2026

Workbook112 days waitingMonth close, 1 SepElevra9 days waiting4 Aug1013141925271 Sep

Tue 4 Aug, nothing submitted

WorkbookSeen at month close, 28 days laterElevraFlagged Wed 5 Aug, the next morningDifferenceSeen 27 days sooner
The workbook rule here is that a gap surfaces when the month is reconciled by hand. Elevra checks each expected workday the next morning. The records are reconstructed and contain no employee or facility data.
A key on a ring with a tag marked KS

Ownership

Submitted records

I defined how submitted records could be corrected without transferring authorship. The manager authorizes reopening; the dietitian changes the values, and both versions remain in history.

Design precedent

Health record rules apply a similar integrity principle: an amendment is appended or linked to the original record rather than replacing it, and earlier versions stay in revision history.

Implementation scope: submit and lock shipped; the correction path was proposed before pilot.

ElevraResubmitted, locked

Kayla SimmonsRD, Inpatient adult

Day
Thu, 13 August 2026
Submitted and corrected values
FieldSubmittedCorrected
Hours worked4.53.5
PTO hours0.01.0

Current submission, K. Simmons, Fri 9:21 AM

Correction history

A desk calendar with one weekday boxed in red

Outcomes

Daily work became attributable and actionable.

What would prove it next.

A reminder sent is an action. A resolved expected submission is the result.

Reconciliation time per exception

FlaggedWed 8:00ResolvedWed 14:20
Daily logKayla Simmons, Thu 13 Aug
Comprehensive
2
Limited
3
Total time
3.5 hrs
  1. Draft
  2. Submitted
  3. Locked

One workflow, start to finish.

Logging, manager review, drill-down, and draft and locked states shipped together in one module.

Weekly submissionsMon 10 to Fri 14 Aug
  • RDRachel Dempsey
  • KSKayla Simmons
  • BNBlessing Nwosu

Tue 11 Aug has no log. Flagged Wed morning.

What the next iteration settles first.

A tool roll with three tools in their pockets and one pocket outlined empty

Field gaps beside the interface

Put the field-gap inventory beside the interface from the first review. A surface can look ready while required fields are still absent.

A try square and a red pencil

Policy before polish

Settle time units, edit windows, correction rights, and role switching before visual polish. The interface can display the answer; it cannot responsibly invent one.

Compare notes

Working on a product that’s still taking shape?

More work

Continue with another case study.

Showing Reframing patient rounding around how sites actually round and FieldWake, set 1 of 3