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.
- Public Health Surveillance
- Features
- Consent and authority
Consent and authority
Follow consent and authority through its source records and decisions.
OverviewSigned Consents×
Public Health Surveillance · Consent and authority
New
Signed Consents
Consents
| Patient | Purpose | Version | Signed at | Expires at | Status | |
|---|---|---|---|---|---|---|
| PTN-94652 | PRP-229 | Rev A | 17 Oct | 20 Oct | Signed | |
| PTN-98415 | PRP-165 | Rev B | 24 Oct | 26 Oct | Signed | |
| PTN-40900 | PRP-874 | Rev C | 17 Oct | 25 Oct | Signed | |
| PTN-73033 | PRP-992 | Rev D | 21 Oct | 25 Oct | Signed | |
| PTN-80449 | PRP-228 | Rev E | 11 Oct | 14 Oct | Signed |
6 of 6 records
PRP-229Consents · CNS-96259
SignedPatientPTN-94652
VersionRev A
Signed at17 Oct
Expires at20 Oct
What you can do
Work from the source record
Patient consent, care-team assignment and professional privilege answer separate questions. The Clinical Coordinator captures the patient’s signed consent for a stated purpose and version. The Clinical Governance Administrator maintains the clinician’s patient assignment and verified privilege, each with effective dates. A Signed consent alone does not grant professional authority, and an Active assignment alone does not cover every purpose. The Licensed Clinician checks all three records for the date of the intended action.
Consider a clinician assigned to a patient for one access purpose. Before signing a note, compare that purpose with the consent purpose and the clinician’s Document privilege on the action date. If the assignment has ended, the governance administrator updates the access record; a coordinator cannot grant privilege by changing the patient record. The clinician waits until each source supports the action.
How the work is organized
- Source. Keep consent purpose and version, signed and expiry dates, access purpose, effective dates and verification evidence on the record that owns the work.
- Responsibility. Clinical Governance Administrator starts from the relevant list and checks the linked record before acting.
- Handoff. Use the status and dates to decide what the next person should inspect.
What to agree during setup
Agree the consent purposes and versions used by the program, the access purposes attached to care-team assignments and which privilege types cover each clinical action. The coordinator owns consent capture; the governance administrator owns assignment and privilege evidence. Review effective and expiry dates at the action date. Decide who investigates a mismatch between the staff person and linked user account.
Check the handoff on an actual case
Choose one patient and a clinician linked to a user. The coordinator records a Signed consent with purpose, version and dates. The governance administrator checks an Active care-team assignment and a Verified privilege whose dates cover the action. Have the clinician repeat the checks before a note signature. End the assignment, then try the same action again; the team should stop and identify the governance record that needs resolution.
Use the signed date and expiry date for consent, and the effective window for assignment and privilege. A record may carry a favorable status but fall outside the date of care. Keep the patient, clinician and purpose visible while resolving that mismatch. The governance administrator can correct authority records; the coordinator can correct the consent record with the patient’s documented decision.
What your team sees
- Signed Consents — Check the patient’s documented purpose and validity dates.
- Active Care Team Assignments — Check clinician, patient, access purpose and effective window.
- Verified Clinical Privileges — Check the privilege type and verification window.
Follow the work through
Use the process walkthrough to rehearse the decision and the data model to check record links. The roles page explains the access responsibilities.
What it keeps track of
Data model- Consents
- Purpose-specific patient consent records with version and validity window.
- Care team assignments
- Active care-team access assignments scoping a clinician to a patient.
- Clinical privileges
- Verified professional privileges covering a clinician and effective window.
- Patients
- Individuals under surveillance or care, with consent status and assigned clinician.
- People
- Clinicians, coordinators, reviewers and governance staff who act in the surveillance program.
- Users
- Users
Who uses it
Permissions- Clinical Governance Administrator
- , Clinical Coordinator, Licensed Clinician, Clinical Reviewer.
Set up Public Health Surveillance your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.