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.
- IVF / Fertility Clinic Mgmt
- Features
- Consent and privileges
Consent and privileges
Record purpose-specific consent and verified clinician privileges.
OverviewPrivileges awaiting verification×
IVF / Fertility Clinic Mgmt · Consent and privileges
New
Privileges awaiting verification
Verified waits for the clinical governance administrator
| Id | Clinician | Privilege type | License number | Issuing authority | Verification evidence | |
|---|---|---|---|---|---|---|
| IDD-596 | Document | CP-28093 | IA-914 | VE-563 | ||
| IDD-191 | Prescribe | CP-35231 | IA-941 | VE-485 | ||
| IDD-619 | Review | CP-43865 | IA-241 | VE-492 | ||
| IDD-314 | Study investigator | CP-16063 | IA-609 | VE-224 | ||
| IDD-974 | Document | CP-51633 | IA-766 | VE-196 |
6 of 6 records
IDD-596Clinical privileges · CP-28093
DocumentIssuing authorityIA-914
Verification evidenceVE-563
StatusPending
What you can do
Consent and privileges
A consent belongs to a patient and records its purpose, version, signed date, expiration date and document. Its state can be pending, signed, withdrawn or expired. The clinic can inspect the exact consent record relevant to a visit rather than relying on a general patient status alone. The patient record carries a separate consent status for quick orientation.
How the work is organized
- Anchor the record. Match each consent purpose and version to the patient before care begins.
- Capture the evidence. Keep signed dates, expiration dates and documents together on the consent record.
- Check the handoff. Let the Clinical Governance Administrator examine license evidence and effective dates before changing a privilege from Pending to Verified.
The governance administrator maintains each clinician’s privilege type, license number, issuing authority, verification evidence and effective dates. A pending privilege becomes verified only after a human has examined the evidence. Suspended or expired states remain visible to staff reviewing who should perform a particular kind of clinical work.
What to agree during setup
Agree the purposes and versions used for consent, where signed documents are stored, and who checks expiration before care. Decide who can verify a clinician’s privilege and which evidence is sufficient for that decision. Keep effective dates current when a license changes. Record the decision in the privilege record rather than treating a job title as proof of eligibility.
Check the handoff on an actual case
Take a patient with a pending consent and a clinician with a pending privilege. Attach the signed consent document, record its version and date, and move it to signed. The governance administrator opens the clinician record, checks the license and evidence, then marks the privilege verified. Have the reviewer inspect both records in the context of the planned encounter. Repeat with a withdrawn consent and an expired privilege so the team can see the states clearly.
When a patient returns, the team should check the current purpose-specific consent and the clinician’s effective privilege dates again. A prior signed document or verification may no longer cover the planned visit.
What your team sees
- Privileges awaiting verification — Examine pending privilege evidence and record the governance decision.
- Consent awaiting signature — Find patient consents that still need a signed document and date.
Follow the work through
Follow the connected records in the operating process and agree the decision points before the first live visit. Use implementation to prepare sample cases with the team. Return to the data model when mapping existing patient and encounter records. The team should confirm that each role can reach the records needed for its own part of the handoff.
What it keeps track of
Data model- Consents
- Purpose-specific patient consent
- Clinical privileges
- Verified clinician privileges
- Patients
- Patient identity and consent status
- People
- Clinic staff and clinicians
- Encounters
- Patient visits and care episodes
Who uses it
Permissions- Clinical Governance Administrator
- Verifies privileges; Clinical Coordinator and Licensed Clinician handle consent; Clinical Reviewer inspects both.
Set up IVF / Fertility Clinic Mgmt your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.