What this is, and who it is for
Inside the Live or UAT workspace, the design that workspace is running is available to read: the forms, the visit schedule and the visit–form mapping, under Configuration. It is the same screens the designers build in, shown read-only. Use them to check what a form asks, which forms a visit expects, or what was tested and signed.
| You need | To |
|---|---|
form.read | See the forms |
visit.read | See the visit schedule |
form.design or study.write | See the mapping (it is the designers' view) |
Held by: Organization Admin, Project Manager, eCRF Designer, Clinical Research Associate, Data Manager, Medical Officer, Sponsor Manager, Sponsor Supply Manager, Auditor, Principal Investigator, Clinical Research Coordinator, Pharmacy, Site Monitor, Clinical Data Coordinator (form.read).
Where to find it
In a workspace's menu: Configuration → Forms, Visit Schedule, Visit ⇄ Form Mapping. Each page carries a fixed notice: Read-only — released design; changes go through an amendment. with the reason beneath it:
| Version in this workspace | The notice says |
|---|---|
| Live | … is the Live design. |
| In UAT | … is under test, so its design is frozen for the cycle. |
| Awaiting sign-off | … passed UAT and is frozen while it is signed. |
| Approved | … is signed off and frozen until it is taken Live. |
| Superseded or withdrawn | … is kept for the record. |
In Build the same pages are editable for the designers (Study → Build; Build a study); a person without a design permission sees them with Your role cannot edit a design.
What you can do
- Open a form to read its fields, checks and logic as a preview, with its version label and status (Preview and testing).
- Read the visit schedule: each visit's day, window, required or optional, whether it can be held remotely.
- Read the mapping: which forms each visit collects, which are required, which need the person in the room.
- Export the design as a data dictionary or ODM-XML from Exports at the study level (Importing and exporting a design).
- Compare versions on Study → Versions: a version's page lists its changes against the Live design.
- The fixed notice: released design, changes go through an amendment.
- The fixed notice: released design, changes go through an amendment.
- The preview is a read-only render; nothing entered in it is saved.
- The same notice on every page of the design.
- The same notice on every page of the design.
Every option
Which version
A workspace shows the version it is running: UAT shows the version under test (and a closed cycle's own snapshot, read-only); Live shows the Live version. A participant follows the version they were created under until they are moved, so a participant may be on an older version than the one a Live page shows (Amend a live study).
What the system records
Reading the design leaves no record of its own. The design itself, with its content hash, is the snapshot recorded when the version was submitted.
What you cannot do, and why
- Edit a form, visit or mapping here. The design is sealed once released: a change is an amendment that is tested and signed.
- See the design of a version in Build from a workspace. Build is the designers' area.
Compliance Q&A
Yes. Each version's frozen snapshot is kept with its hash, each participant's records carry the version they were captured under, and the design can be exported as a data dictionary or ODM-XML carrying that hash.
Evidence: server versions snapshot (content hash)participants follow their versiondesign exports carry the snapshot hash
Related
Build a study · Review and release a study · Importing and exporting a design · Auditor