These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- OT / Surgery Scheduling
- Features
- Consent and privileges
Consent and privileges
Keep patient permission and clinician verification visible before care.
OverviewConsent review×
OT / Surgery Scheduling · Consent and privileges
New
Consent review
Approval conditions
| Id | Patient | Purpose | Version | Signed at | Expires at | |
|---|---|---|---|---|---|---|
| IDD-221 | PTN-33640 | PRP-242 | Rev A | 03 Oct | 07 Oct | |
| IDD-501 | PTN-35694 | PRP-220 | Rev B | 03 Oct | 06 Oct | |
| IDD-659 | PTN-55187 | PRP-574 | Rev C | 07 Oct | 12 Oct | |
| IDD-314 | PTN-53149 | PRP-145 | Rev D | 26 Oct | 31 Oct | |
| IDD-524 | PTN-37621 | PRP-467 | Rev E | 20 Oct | 23 Oct |
6 of 6 records
IDD-221Consents · CNS-32713
PendingPatientPTN-33640
PurposePRP-242
VersionRev A
Signed at03 Oct
Expires at07 Oct
What you can do
Check the authority behind the visit
A purpose-specific consent record links a patient to the purpose, version, signed date, expiry date, document and current status. The Clinical Coordinator can prepare that record. Licensed Clinician can capture the signed document while working with the patient. The team can distinguish Pending, Signed, Withdrawn and Expired consent during preparation and review.
Clinician privileges are separate records tied to People. They carry a privilege type, license number, issuing authority, verification evidence, effective dates and status. Clinical Governance Administrator maintains them and makes the verification decision. A clinician can have several privilege records for different activities, so the team should inspect the relevant privilege and its effective period for the visit.
How the work is organized
- Consent preparation. Clinical Coordinator records the purpose and version for the patient before care.
- Signed evidence. Licensed Clinician attaches the signed document and date when the patient has signed.
- Privilege decision. Clinical Governance Administrator checks the clinician’s evidence and records Verified only after review.
The patient record’s broader consent state remains useful for intake, while each consent record answers whether a particular purpose has its own signed document. A withdrawn or expired consent needs review before it is relied upon again. Privilege status can be Pending, Verified, Suspended or Expired; staff should use the current status and effective dates rather than relying on an old verification alone.
What to agree during setup
Define the local consent purposes and who is responsible for keeping versions current. Decide where a patient-signed document is obtained and who checks that the signed date and expiry date are correct. Set the point in the visit preparation when the clinician’s privilege evidence is checked, the person who performs verification, and what happens when a record is suspended or expires.
Rehearse access: Clinical Governance Administrator manages privilege records, Clinical Coordinator manages consent records, and Licensed Clinician can manage consent while documenting care. Clinical Reviewer can read the relevant records for review. Avoid treating a pending record as a completed decision merely because a document is attached.
Check the handoff on an actual case
A coordinator schedules an encounter and opens the patient’s consent for the stated purpose. The consent is Pending until the signed document and signed date are recorded. The governance administrator opens the assigned clinician’s privilege, checks the issuing authority, evidence and effective dates, then marks the relevant privilege Verified. During the visit, the clinician documents care against the encounter. Later, if the patient withdraws consent, the team updates that consent record and reviews any future visit before using it.
If the privilege evidence is still pending, the coordinator and governance administrator resolve it before the team relies on that verification. The status is a useful handoff signal because it records the decision made on the privilege record.
What your team sees
- Consent review — Patient consents awaiting signed evidence or decision.
- Privilege verification inbox — Clinician privileges awaiting governance verification.
Follow the work through
See encounter preparation and care documentation. Review the roles guide with the people who decide verification.
What it keeps track of
Data model- Consents
- Purpose-specific patient consent
- Clinical privileges
- Verified clinician privileges
- Patients
- Patient identity and consent status
- People
- OT staff and clinicians
Who uses it
Permissions- Clinical Coordinator
- Prepares consent; Licensed Clinician captures signed evidence; Clinical Governance Administrator verifies privileges; Clinical Reviewer reads the evidence; Admin supports access.
Set up OT / Surgery Scheduling your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.