OpTally · Admin

← Back to app

Program-level oversight. You can see who's signed up and how much they're using it — but never anyone's actual cases (those are end-to-end encrypted and unreadable to the server).

This month

—

Residents signed up

—

Parses this month

—

Per-resident cap / mo

Pilot metrics

—

Total cases logged

—

Cases logged · 7 days

—

Active residents · 7 days

—

App opens · 7 days

—

ACGME syncs · 7 days

—

Median operation → logged (pilot)

—

Median operation → in ACGME (pilot)

—

Baseline operation → entry (own ACGME history)

—

Capture proxy · 4 wks (logged ÷ performed)

—

Median log → sync (queue time)

—

Median signup → first case

Per resident · median days from operation to log. Baseline = their own ACGME history (created − procedure date); pilot = cases logged in OpTally / marked submitted. Grade: A ≤1 · B ≤3 · C ≤7 · D ≤14 · F >14.

Resident	Baseline	Pilot → logged	Pilot → ACGME	Change

Log→sync = days from logging a case to marking it in ACGME.

Program view

What a program director would see. Built only from each resident's daily progress snapshot (category counts and totals, never a case) and the pilot events. "Projected" = current major total + pace over the last 90 days × months to a June 30 graduation for their PGY. Residents can turn the snapshot off in Settings.

Residents

Name	Email	Cases	Parses (mo)	Last login	Last active	Joined

Bug reports & feedback

When	Type	From	Message	Shot

Pilot mode

Collect no patient identifiers — applies to every account. The MRN field is not shown, dictation does not ask for it, and the ACGME queue carries an empty Case ID, so residents type that one field into ACGME themselves.
Enforced in the app, not on the server — case data is end-to-end encrypted, so the server cannot inspect a payload to reject one. Turning this on changes what OpTally collects; it does not remove identifiers already stored.

Pilot surveys

Open the post-pilot survey to residents — turn on near the end of the 4 weeks (residents get prompted on next open).

When	Type	From	Answers

Access control

Require an invite code to sign up

When on, new residents need a code from you to create an account. Great for testing with a few people; turn it off (or add domain restriction) for a wider rollout.

Max uses

Program (optional)

Program director

Names an existing account as the director for a program. They sign in at /program with their normal password and see the Program view for residents whose invite carried that program name. Leave the program blank to remove the role.

Account email

Program

Invite code	Used	Created

Model for everyone

Parsing model (applies to all residents; overrides their local choice)

Anthropic API key

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

Set / rotate key (leave blank to keep current)