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.
- Community Health Worker App
- Features
- Consent and privileges
Consent and privileges
Review patient consent and clinician privileges before eligible care decisions.
OverviewPrivilege verification×
Community Health Worker App · Consent and privileges
New
Privilege verification
Verified waits for the clinical governance administrator
| Assigned worker | Privilege type | License number | Issuing authority | Effective to | Status | |
|---|---|---|---|---|---|---|
| Document | CP-92972 | IA-107 | 27 Oct | Pending | ||
| Prescribe | CP-34992 | IA-887 | 19 Oct | Pending | ||
| Review | CP-66955 | IA-693 | 25 Oct | Pending | ||
| Study investigator | CP-23753 | IA-811 | 17 Oct | Pending | ||
| Document | CP-46988 | IA-731 | 10 Oct | Pending |
6 of 6 records
IA-107Clinical privileges · CP-92972
DocumentEffective to27 Oct
StatusPending
What you can do
Keep authority visible
The household record shows a current consent state. A separate consent record carries its purpose, version, document, signed date, expiry date and status. This lets the team ask a specific question: does the consent for this purpose still apply to this household? The Clinical Coordinator and Licensed Clinician can manage consents, while the Clinical Reviewer can inspect them with the encounter evidence.
Clinician authority has its own record. A Clinical Governance Administrator maintains the privilege type, license number, issuing authority, verification evidence and effective dates for an assigned worker. Privileges may be pending, verified, suspended or expired. The record helps the team check whether a worker’s documented authority covers the task under review.
How the work is organized
- Household consent. The current household state gives an immediate signal during intake.
- Purpose-specific consent. The signed document and expiry date provide the detail behind the state.
- Professional privilege. Verification evidence and effective dates support the governance administrator’s verification decision.
A household may have more than one consent purpose. Review the record for the relevant purpose rather than treating a general active state as a substitute for the signed document. A privilege also needs a type and effective period; a verified status alone should be read with its dates.
What to agree during setup
List the consent purposes and versions the team will use. Name who checks an expiring consent and who updates the household’s current consent state after a withdrawal. Define which privilege types are required for documentation, prescribing, review or study investigator activity. Agree which governance administrator verifies evidence and how the team handles an expired or suspended privilege on an already planned visit.
For the first operating cycle, enter one signed consent and one pending consent for separate households. Add a pending clinician privilege with its supporting document, then review the verification queue. The team should be able to find the person, date range and status without searching external files.
Check the handoff on an actual case
A coordinator prepares a visit for a household whose consent state is active. They inspect the purpose-specific consent, including version and expiry date, before proceeding. The assigned clinician has a verified documentation privilege with an effective period covering the encounter. If the consent was withdrawn or the privilege suspended, the team sends the case to the responsible coordinator or governance administrator for a decision before the care record is treated as eligible.
What your team sees
- Consent follow-up — Find pending, expired or withdrawn consents by household and purpose.
- Privilege verification — See pending professional records with worker, type and dates.
- Encounter review inbox — Inspect consent and authority alongside the encounter.
Follow the work through
What it keeps track of
Data model- Consents
- Purpose-specific patient consent
- Clinical privileges
- Verified clinician privileges
- Households
- Patient identity and consent status
- People
- Clinic staff and clinicians
- Care team assignments
- Care team access assignments
Who uses it
Permissions- Clinical Coordinator
- , Licensed Clinician, Clinical Governance Administrator, Clinical Reviewer and Admin.
Set up Community Health Worker App your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.