What it does
The case analytics workbench answers guided questions about case-log activity — requirement progress, diagnoses and procedures seen, requirement gaps — at the institution, program, or personal level, with privacy suppression for small groups. Case logs can also be downloaded as CSV or Excel files with date, rotation, and status filters, and every download is audited.
Who it's for
Program administrators and directors use the program lens, institution administrators use the institution lens, and learners get a personal progress lens on their own logs from My Cases.
How it works
Access. The Analytics tab on My Cases only appears when the selected program has an active membership for that person; admin-only access without membership hides the tab. Export permissions are separate from viewing permissions.
Personal progress lens. On My Cases (/my-cases?tab=analytics), learners see one question at a time, a compact status strip, and results — without the admin recipe rail, report-controls inspector, export/saved actions, or locked legacy previews. Program and institution analytics keep the full workbench.
Guided recipes. Instead of a free-form query builder, the workbench offers named questions ("recipes"): individual requirement progress, procedures seen, diagnoses seen, procedure requirement gaps, and diagnosis requirement gaps. On program and institution lenses, each recipe can deep-link into the compliance dashboard for remediation; on the personal lens, CTAs stay inside My Cases (Summary or Diagnoses/Procedures Seen). Further recipes — group log summary, procedure volume matrix, cases completed by learner, case duration by rotation, review throughput, and a full source-row download — appear as locked previews for staff and cannot run yet; learners don't see locked recipes.
Privacy suppression. Aggregates covering fewer than five people are suppressed rather than displayed, and complementary values that would reveal a suppressed number are hidden too. Suppressed cells display as "Suppressed", never as zero.
Analytics exports (planned). The staff workbench shows an export panel describing the planned audited export path — background jobs with expiring downloads and permission rechecks at queue, processing, and download time. It's not enabled yet: CSV generation stays disabled until the export engine ships, so the export action stays unavailable. The personal lens shows no export or saved-report controls.
Case log file export. From Logs, program staff filter the list by date range, rotation, and status, then select Export to download a CSV summary of the filtered view — one row per case log. The export never includes the encrypted patient reference, and each successful export is logged in the audit trail with its row count. Learners don't have an export control on My Cases.
Before you start
You need case-management permission for the program whose logs you're exporting.
Apply the filters you want first — date range, rotation, status — since the export downloads the current filtered view, not the whole program.
The file is a CSV summary, one row per log; it does not include diagnoses, procedures, or the patient reference field.
Do this
Open Logs (
/cases/logs) → you should see the list with status cards for Total Cases, Pending Review, Approved, and Rejected.Apply the filters you want on date range, rotation, or status in the filters panel → the list updates to match.
Select the Export button → you should see it switch to an "Exporting..." state, then a CSV file with the filtered rows.
You're done when
✓ You have a CSV file matching the filters you set, with one row per case log.
✓ The export shows up in the audit trail with its row count.
✓ No patient reference values appear anywhere in the file.
Boundaries and limits
Locked-preview recipes are visible to staff but can't be run until their backing ships; learners on My Cases Analytics only see live progress questions.
Exporting directly from the analytics workbench isn't available yet — the staff export panel is informational and marked as planned. Case log file export from the log workspace is the working export path today.
Small-group suppression (fewer than 5) applies to analytics aggregates and can't be switched off; personal cohort benchmarks aren't exported.
Analytics access is permission-gated per lens and scope; forged scopes are rejected on the server and show a "denied" state instead of data. Personal progress is owner-scoped.
The organization portal has no case analytics surface; lenses stop at institution, program, and personal.
Case log file export from Logs is CSV summary only, one row per log, and never includes the patient reference field. A detailed layout with each log's diagnoses and procedures, and an Excel format, aren't available in the current app.
Approval actions aren't available inside analytics; review happens in the review workflow, which analytics only summarizes and links to.
Common questions
Q: Why does a cell say "Suppressed"? A: The group behind that number has fewer than five people, so it's hidden along with any totals that would let it be derived.
Q: Can I export the diagnoses and procedures on each log, not just the log list? A: Not yet. Today's export from Logs is a CSV summary, one row per log.
Q: Can learners export their own logs? A: Not directly. My Cases has no export control — ask your program administrator to export from Logs.
Q: Why is a report I need shown as locked? A: It's staged behind an export engine that hasn't shipped yet. Staff analytics show it as a locked preview; learners don't see locked previews at all.
Q: How is My Cases Analytics different from Summary? A: Summary is your status cards and remaining-items list. Analytics asks one guided progress question and shows the answer as a visual or table, linking back into Summary or Seen for the full list.
Related articles