For programs
ACGME data matters. Capnolog helps programs complement it with a clearer view of case activity, unresolved gaps, and the workflow behind the numbers.
Program workflows and data connections may vary by implementation.
The console
A chief or a coordinator signs in at console.capnolog.com, pastes next week's OR schedule, settles every name against the program's resident list, and publishes it. It is a separate sign-in from the resident app, and it never opens a resident's case log.
Paste the cells straight out of your scheduling export, or hand the console a CSV, an Excel file or a PDF. The file is read on your own computer and never uploaded, you tell it once which column is which, and one publish covers up to fourteen days.
Every cell is editable — room, start, procedure, attending, surgeon, residents, site, note. Each name is matched against your resident list as you type, and publishing stays off until every one of them resolves. A cell that looks like patient information stops the draft saving at all.
The console says what travels before you send it: the dates, how many residents the week reaches, and that names, rooms and procedures are the whole of it. Publishing writes the program's OR board — the same board a resident's phone reads — and what a resident sees there depends on their program's setup.
One card answers the question a chief opens the console with: is the schedule my residents see the current one? Version, row count, dates covered, and whether today falls inside the published window. Every publish is kept — correcting a week makes the next version rather than rewriting the last one.
A resident flags one of their own cases — research, a case report, an M and M, teaching — and separately chooses which of those to offer the program. The queue is three words wide: new, seen, closed. It carries no ranking, no count and nothing about the patient. The console side is built; the phone's half of sharing is not switched on yet, so nothing arrives in it today.
Capnolog sets a program up before its first sign-in, so what your program can connect depends on where your schedule lives. Tell us what you run. Ask about your program.
Three layers
Programs rely on ACGME data for formal reporting. Manual reports and program-management tools help organize the work. Capnolog adds a third layer: a resident-facing logging and review workflow that helps programs see case activity before it becomes a reporting problem.
Formal case-log data is essential, but it often reflects what has already been submitted—not what is still unresolved in the day-to-day workflow.
Strengths
Limitations
Many programs use broader tools for evaluations, scheduling, or reporting. These tools can be valuable, but case logging is often one feature among many rather than the center of the workflow.
Strengths
Limitations
Capnolog focuses on the moment the case happens: fast logging, clear review, and visibility into what still needs attention—so programs can complement formal data with earlier signals.
Strengths
Limitations
Not built yet
| What changes | ACGME data alone | Other program-management tools | Capnolog |
|---|---|---|---|
| Daily case capture | Not the primary purpose | Depends on implementation | Central workflow |
| Resident feedback | Limited | Varies by platform | Built into the logging workflow |
| Missing or unresolved cases | Often visible after reporting | Depends on manual review | Designed to surface earlier |
| Program visibility | Formal and authoritative | Broad administrative views | Case-centered visibility |
| Data timing | Typically after submission | Varies | Closer to when the case happens |
| Resident ownership | Limited | Varies | Designed for the resident's daily workflow |
| Implementation | Already required | Already in place for many programs | Program-specific |
| Privacy and scope | Formal reporting data | Varies | Designed to avoid unnecessary individual exposure |
Daily case capture
Resident feedback
Missing or unresolved cases
Program visibility
Data timing
Resident ownership
Implementation
Privacy and scope
Hedged, category-level comparison — not a feature audit of any product.
Program value
Programs do not need more dashboards. They need earlier clarity about whether residents are logging cases, whether progress is on track, and where support is needed.
See case activity and gaps closer to when they happen, rather than waiting for the next reporting cycle. Requirement progress moves with the reviewed record, so a category running short shows up while there is still time to rotate through it.
A faster logging workflow can improve the quality and consistency of the case record. Support, not surveillance: the workflow is built for the resident first, and the resident owns their own log.
Unresolved entries and progress gaps are easier to act on when they are visible in context. Program-level aggregates are not available yet.
In developmentCapnolog does not replace ACGME data. It helps programs understand the workflow that produces it, and what a program can connect and see is configured per program.
Program-specificThe path
The resident logs the case quickly.
The record is confirmed or corrected.
Requirement progress reflects the reviewed record.
Programs can see broader patterns without needing individual case detail.
Gaps and stalls become visible before the next formal report.
What a program can connect, and which views it gets, depends on the program. There is no program-level aggregate of case activity yet.
Data connections
Capnolog can read a program's existing OR board or scheduling source so the day's assignments arrive as draft cases on the resident's phone. It runs with one program today, and what can be connected depends on where a program's schedule lives.
Your program's existing schedule
Room, time, attending, procedure type only
Pilot — one programNo patient identifiers cross this line
The day's cases, pre-filled
Nothing is logged without the resident
De-identified, program-level — in development
ConceptWorkforce scheduling, not patient data: room, procedure text, clock time, anesthesia type, and staff assignments. Patient identifiers are neither requested nor stored.
The rooms they were assigned to, as draft cases with the site, room, attending, and procedure already filled in. Nothing is logged without the resident.
Read access to the schedule source, a conversation with whoever owns it, and a short pilot with a handful of residents. We build and maintain the connector.
Quoted per program, because the work depends entirely on the system being connected. Tell us what you run and we will tell you what it takes.
Programs should. ACGME data is the formal record. Capnolog is designed to complement it by improving the workflow that happens before submission:
Program data connections and reporting workflows vary. Capnolog does not replace formal ACGME requirements or reporting, and it does not pull a program's data out of ACGME.
For programs
Five questions. We reply by email with what a program engagement looks like for your specialty and where it stands today.
Capnolog complements ACGME data with earlier, clearer visibility into the case workflow. Program features vary by implementation.
Logging is free for every resident. Program access is priced per program. See pricing · How the data works · What the research says about case-log accuracy