OpTally · Console

Sign in

Administrator password instead

Create your program staff account

You will see residents' progress totals and logging speed for your program — never a case, a patient, or a date.

This month

—
Residents signed up
—
Parses this month
—
Per-resident cap / mo

Usage

—
Total cases logged
—
Cases logged · 7 days
—
Active residents · 7 days
—
App opens · 7 days
—
Operation → logged (OpTally median)
—
Operation → entry before OpTally
—
Operation → in ACGME (OpTally median)
—
Capture · 4 wks (logged ÷ performed)
—
ACGME syncs · 7 days
—
Log → sync (queue time)
—
Signup → first case
—
App errors · 7 days
—
Dictations saved without edits
—
Mic press → saved (median)
—
Dictation failures · 7 days
—
Residents with the extension
—
ACGME batch: time per session (median)
Every usage event as one row, for analysis outside the console. No case content.
Per resident · median time from operation to entry. Baseline is their own ACGME history (created − procedure date); OpTally is cases logged here / marked submitted.
ResidentBaselineOpTally → loggedOpTally → ACGMEChange

Scorecard

What OpTally has to show, per resident from their own sign-up: how much gets captured, how fast, and what is captured that ACGME never sees. Own cases only (imports excluded), counted from each resident's sign-up. The comparison line is Firefly's published figure (JSE 2022, three programs): 4.77 cases per resident per week with an OR-schedule feed, 2.85 with the feed paused, 1.44 logging by hand.

—
Cases per resident per week (median)
—
vs Firefly with OR feed (4.77)
—
Mic press → saved (median)
—
Parses accepted as-is
—
Cases logged by voice
—
Cases with a note
—
Attending preferences saved
—
Operation → logged (median)
ResidentDays inOwn casesPer weekVoiceSec/caseAs-isNotesPrefsSent to ACGMEExtension

New program

A program is the unit everything hangs off: it gets one join code residents type at sign-up, and you invite its staff (director, coordinator) from its card below. Staff see only their program's dashboard.

No programs yet — create one above.

Names without a program

These program names sit on invites or accounts but have no program record, so they cannot be opened above. Make one a program to link what already carries the name, or remove the name from everything that has it.

NameCarried by

Program view

—

Major cases · minimum 850

Chief-year cases · minimum 200

ResidentMajor casesChief casesCategories shortProjectedLoggingStatus
Totals and logging habits only — never a case, a patient, or a date. Bars are against the ACGME minimums (850 major, 200 chief). Pace is the resident's cases per month over the last 90 days; projected adds that pace through a June 30 graduation for the PGY. Logging is how long after an operation it gets entered, as the resident's median: same day, within 3 days, within a week, 1–2 weeks, or over 2 weeks. "Before OpTally" comes from the resident's own ACGME history.
No progress snapshots yet — they arrive the first time a resident opens the app or the Progress tab each day.

Residents

NameEmailProgramCasesParsesPlanLast activeJoinedSetup
No residents have signed up yet.

Bug reports & ideas

WhenTypeFromMessageShot
No reports yet.

Surveys

Open or close the follow-up survey for everyone under Settings → Switches.
WhenTypeFromAnswers
No survey responses yet.

App errors

Uncaught errors on residents' devices, reported automatically. Message and location only; long numbers are masked before they leave the device.

WhenWhoMessageWhereBrowser
No errors reported.

Switches

Every on/off setting for this deployment, in one place. Each takes effect on a resident's next sign-in or refresh.

Parsing

The key that pays for everyone's parsing. Stored server-side and never shown back. Current source: —

Usage data

Clean slate: removes every usage event, bug report, survey response and usage counter. Accounts, their cases, programs, staff and settings stay. There is no undo.

One-off codes

Limited-use codes not tied to a program's join code.
CodeProgramUsedCreated
No one-off codes.