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.
- Emergency Department System
- Features
- Consent and clinical privileges
Consent and clinical privileges
Review patient consent and clinician privilege evidence before the relevant care action.
OverviewConsents pending signature×
Emergency Department System · Consent and clinical privileges
New
Consents pending signature
Approval conditions
| Id | Patient | Purpose | Version | Expires at | Status | |
|---|---|---|---|---|---|---|
| IDD-266 | PTN-34516 | PRP-240 | Rev A | 20 Oct | Pending | |
| IDD-839 | PTN-69382 | PRP-428 | Rev B | 26 Oct | Pending | |
| IDD-988 | PTN-63389 | PRP-121 | Rev C | 16 Oct | Pending | |
| IDD-551 | PTN-73703 | PRP-740 | Rev D | 17 Oct | Pending | |
| IDD-841 | PTN-22578 | PRP-750 | Rev E | 22 Oct | Pending |
6 of 6 records
IDD-266Consents · CNS-36134
PendingPatientPTN-34516
PurposePRP-240
VersionRev A
Expires at20 Oct
What you can do
Keep authority visible in the record
A patient consent names its purpose and version, carries a document, and records a signed and expiry date. Its state can be Pending, Signed, Withdrawn or Expired. The patient record also has a consent-status field for an overall view. A clinician privilege names the person and privilege type, license number, issuing authority, verification evidence, effective period and status. The Clinical Governance Administrator maintains verified professional privileges and care-team assignments.
These are distinct records. A patient may have a signed consent for one purpose while another purpose remains pending. A clinician may have a verified privilege for documentation while a prescribing privilege still needs review. The team should check the relevant consent and privilege for the action at hand, rather than treating either as a general approval for every activity. The status and effective dates give the next person a way to identify what needs attention.
How the work is organized
- Purpose-specific consent. Each consent belongs to a patient and records the signed document, purpose, version and dates.
- Professional privilege. Each privilege belongs to a clinician and records the type, evidence, effective dates and verification state.
- Care-team access. A dated assignment identifies which clinician has access to the patient’s care record for a stated purpose.
What to agree during setup
List the consent purposes and document versions used in the first pilot. Agree who enters the signed date, how withdrawals are recorded and how an expired consent is reviewed before another action. For professional privileges, identify the person who checks license evidence, the expected effective period and the meaning of each privilege type. Decide when a Pending privilege may become Verified, and when Suspended or Expired requires a new review.
The Clinical Governance Administrator can manage privileges and care-team assignments. Licensed Clinicians can manage consent records and read privileges. Clinical Reviewers can read both forms of evidence. Use a representative case where the clinician has one verified privilege and another pending privilege so the handoff does not rely on a single broad status.
Check the handoff on an actual case
Start with a patient consent marked Pending. Enter its purpose and version, attach the document and record the signed date when the patient signs. Confirm that the item leaves the pending-consent list when its status becomes Signed. Then mark a separate consent Withdrawn and ask the pilot team how that decision changes the next care step. The record should retain the patient and purpose that the withdrawal concerns.
Add a clinician’s privilege with license and issuing authority, verification evidence and effective dates. Keep it Pending while the administrator checks the evidence, then move it to Verified under the agreed policy. Review it near its end date and exercise the Suspended or Expired path. The clinical reader should be able to see which exact privilege was reviewed, not merely the person’s name.
What your team sees
- Consents pending signature — Patient and purpose-specific documents still awaiting signature.
- Privileges pending verification — Clinician evidence that the governance administrator needs to check.
Follow the work through
What it keeps track of
Data model- Consents
- Purpose-specific patient consent
- Clinical privileges
- Verified clinician privileges
- Care team assignments
- Care team access assignments
- Patients
- Patient identity and consent status
- People
- Clinic staff and clinicians
Who uses it
Permissions- Clinical Governance Administrator
- Verifies professional privileges; Licensed Clinician records consent; Clinical Reviewer reads the resulting evidence.
Set up Emergency Department System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.