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.
- Medical Coding System
- Features
- Patients and consent
Patients and consent
Keep patient identity and purpose-specific consent close to the visit.
OverviewPatients Needing Consent×
Medical Coding System · Patients and consent
New
Patients Needing Consent
Confirmed waits for the clinical coordinator
| Id | Patient number | Display name | Consent status | Assigned clinician | |
|---|---|---|---|---|---|
| IDD-243 | PTN-44308 | Display 283 | Pending | ||
| IDD-673 | PTN-77432 | Display 661 | Pending | ||
| IDD-235 | PTN-53248 | Display 138 | Pending | ||
| IDD-370 | PTN-10625 | Display 365 | Pending | ||
| IDD-990 | PTN-54245 | Display 302 | Pending |
6 of 6 records
IDD-243Patients · PTN-44308
PendingDisplay nameDisplay 283
What you can do
Begin with an identifiable patient
The Clinical Coordinator creates the patient record before scheduling a visit. The patient number gives staff a stable reference when names are similar. The assigned clinician makes the expected care owner visible. Contact and birth details help the coordinator check that the next encounter belongs to the right person. A second name match alone is a poor reason to attach notes or a charge to an existing patient.
Patient consent status gives the team a quick current-state signal. A purpose-specific consent holds its own version, signed date, expiry date and document. Staff can therefore distinguish a patient’s broad status from the particular consent relevant to a service. A signed form for one purpose should not be treated as permission for every future activity.
How the work is organized
- Identity. The coordinator checks patient number and displayed name before attaching a new encounter.
- Purpose. The consent record says which activity was discussed and which version the patient signed.
- Current state. Pending, Signed, Withdrawn and Expired remain separate consent outcomes for review.
What to agree during setup
Agree how patient numbers are assigned and who resolves apparent duplicates. Choose the language used for each consent purpose and where the signed document comes from. Decide how staff will check an expiry date before relying on an earlier signature. The Clinical Coordinator manages patient and consent records; the Licensed Clinician can work with consent evidence during care. The Clinical Governance Administrator can inspect patient identity while maintaining care-team access.
The team should also agree when a patient-level consent status changes. It is a useful summary, but the purpose-specific record carries the signed document and its dates. During a handoff, the receiving clinician should examine the purpose and version of the consent that applies to the planned visit.
Check the handoff on an actual case
Suppose a returning patient is scheduled for a new visit. The coordinator looks up the patient number, checks the assigned clinician and reviews the consent for the planned activity. If that consent is still Pending, the coordinator keeps it visible for completion. When the document is signed, the record moves to Signed with its date and version. If the patient later withdraws consent, the Withdrawn state must remain visible to anyone reviewing the encounter.
The encounter can then point to the existing patient instead of a duplicate identity. The team should test that a clinician sees the correct patient and that a different patient’s record is not pulled into the visit by a similar display name. Follow-up care tasks can stay with the patient when the visit ends.
What your team sees
- Patients Needing Consent — Find patient records whose consent status still needs attention.
- Consent Review — Open purpose-specific consent records waiting for a signed outcome.
Follow the work through
See patient intake and encounter documentation. Set the identity and consent rules in implementation.
What it keeps track of
Data model- Patients
- Patient identity and consent status
- Consents
- Purpose-specific patient consent
- Encounters
- Patient visits and care episodes
- Care tasks
- Follow-up care tasks
Who uses it
Permissions- Clinical Coordinator
- , Licensed Clinician, Clinical Governance Administrator
Set up Medical Coding System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.