1. Patient Referral Management
  2. Features
  3. Clinical documentation
Feature · Clinical documentation

Clinical documentation

Keep signed notes, observations and purpose-specific consent with care records.

OverviewSigned Consents
Patient Referral Management · Clinical documentation

Signed Consents

All consents

New
IdPatientPurposeVersionSigned atExpires at
IDD-840PTN-93758PRP-641Rev A12 Oct18 Oct
IDD-403PTN-65548PRP-502Rev B19 Oct21 Oct
IDD-739PTN-20596PRP-117Rev C18 Oct24 Oct
IDD-147PTN-23233PRP-406Rev D16 Oct24 Oct
IDD-433PTN-39082PRP-803Rev E08 Oct14 Oct
6 of 6 records
IDD-840All consents · AC-20792
Signed
PatientPTN-93758
PurposePRP-641
VersionRev A
Signed at12 Oct
Expires at18 Oct
Example screen with sample data

What you can do

Preserve who recorded the visit

A clinical note links to an encounter and an author. It contains a note type, narrative text, signed date and status. A draft can be worked before signature; a signed note should show that its author completed the documentation. An amended state distinguishes later correction from the original signed state. The author and encounter links let the team read the note in the context of the actual visit.

Observations also belong to encounters. Each observation records a metric, value, unit, observation date and recorder. That structure lets a clinician distinguish a measured value from the narrative note. The team should agree on clear units and metric names so the same measurement can be interpreted consistently across visits.

How the work is organized

  • Prepare. The Clinician opens the encounter and records observations against that visit.
  • Document. The author writes a Draft note, checks the patient and encounter context, and signs it when ready.
  • Review. The care team checks the signed note and applicable consent before marking the encounter complete.

What to agree during setup

Decide which note types the team uses and who may sign or amend a note. Agree what an amendment should explain, and preserve the signed date so later readers can understand the sequence. Review the role access for notes and observations together; they contain patient care information even when staff reach them from different screens.

Consent records are purpose-specific. Each one has a purpose, version, document, signed date, expiry date and status. A signed record should be matched to the work being done and its date. An expired or withdrawn record calls for a fresh care team decision. The patient’s overall consent status is useful context, while the individual document carries the purpose and version.

Check the handoff on an actual case

A patient arrives for a specialty encounter. The clinician records an observation with its value and unit, then prepares a Draft note attributed to themselves. Before signing, they check that the note belongs to the correct encounter. After signing, the signed date and author remain visible. The next reviewer opens the encounter and sees both the note and observation without having to infer which visit they belong to.

For a second case, compare a Signed consent with a Withdrawn one for the same patient. The team should choose the record that matches the purpose and date of the intended work. Rehearse a note amendment so staff know how to distinguish a correction from an unfinished draft.

What your team sees

  • Draft Clinical Notes — Notes still being prepared, with encounter and author visible.
  • Signed Consents — Consent records available for purpose and date review.

What it keeps track of

Data model
Clinical notes
Attributed clinical documentation for encounters.
Observations
Measured values captured during encounters.
Encounters
Scheduled and completed patient visits.
All consents
Purpose-specific patient consent records.
Patients
Patient identity and consent status records.

Who uses it

Permissions
Clinician
, Care Operations Manager, Referral Reviewer

Set up Patient Referral Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started