What this is, and who it is for
The casebook is a grid of the study: one row for each participant, one column for each visit, and in each cell the state of the forms of that visit: how many are complete, in progress or not started, whether the visit was missed, how many queries are open, how far source verification has got and whether anything is locked. It answers "where do we stand?" without opening a form. A participant also has a casebook of their own.
| You need | To |
|---|---|
subject.read | See the casebook (a site person sees their own site) |
clinical.query.read | See the open-query counts (without it the grid says Open-query counts are not shown — you don't have access to this study's queries. Every other column is complete.) |
Held by: Organization Admin, Project Manager, Clinical Research Associate, Data Manager, Medical Officer, Sponsor Manager, Sponsor Supply Manager, Auditor, Principal Investigator, Clinical Research Coordinator, Pharmacy, Site Monitor, Clinical Data Coordinator (subject.read).
Where to find it
In a workspace: Casebook (Every subject's data-capture status across all visits — completion, queries, source verification, and lock. Click a cell to see its forms.), with the counts of Subjects and Visits, a search (Search subject / ID…), a Legend and a Fullscreen view (Exit to leave it). On a participant's page, the Visits & forms tab shows the same for one participant.
What you can do
- Search for a participant by number or screening ID and page through the rows (50 at a time).
- Read a cell. Its bar has one segment for each place the forms stand: locked, complete, in progress, not started (red when the visit was missed). The cell shows the open queries, a source verification mark and a lock.
- Click a cell to open its forms: each form is listed by code and name with its own status (Complete, In progress, Not started, Missed, Locked), its queries and its source verification (SDV, SDV partial, SDV discrepancy). Open visit → goes to the participant's visit. A visit held remotely is marked, and the forms that need the person in the room.
- Go full screen to read a large study.
Every option
What the cell counts
The forms a cell counts are those the design binds to the visit (any binding that is not Inactive, including Conditional ones, which the system does not apply: Binding a form to visits). A participant sees the forms of the version they follow. A form is:
| Status | When |
|---|---|
| Not started | The visit is scheduled or in window and there is no complete record |
| In progress | There is a record that is not complete |
| Complete | The record is complete |
| Missed | The visit was missed |
| Locked | The record is signed and locked, or the binding was set to Locked in the design (then it shows Locked whatever the data) |
Source verification mark
A complete form shows how far verification has got: none, partial, done or discrepancy (Monitor and verify data).
What the system records
Reading the casebook leaves no record of its own; the counts are derived from the records, queries and verifications each time. API reads are in the request log. See Audit events.
What you cannot do, and why
- Edit from the grid. It reads; click through to the form.
- See participants of another site if you are site staff, or of the other workspace.
- See open-query counts without query access.
- Rely on a Locked mark as a signature. A cell shows Locked for a signed record, but also when the design's binding is locked; the E-Signatures register is the authority on what is signed (Sign records).
Compliance Q&A
Yes. The casebook is computed from the records, queries and verifications each time it is read, so it cannot drift from them.
Evidence: server/src/modules/study/casebook/application/derive-cells.ts (cells derived on read from records, queries and verifications)
Related
Run a visit · Use the reports and the dashboard · Monitor and verify data · Work with queries