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.
- Remote Patient Monitoring
- Features
- Clinical notes and privileges
Clinical notes and privileges
Attribute clinical documentation and check current clinician authority.
OverviewDraft clinical notes×
Remote Patient Monitoring · Clinical notes and privileges
New
Draft clinical notes
Signed waits for the monitoring clinician
| Encounter | Author | Note type | Signed at | Status | |
|---|---|---|---|---|---|
| ENC-1381 | NT-597 | 13 Oct | Draft | ||
| ENC-5101 | NT-314 | 23 Oct | Draft | ||
| ENC-5668 | NT-659 | 21 Oct | Draft | ||
| ENC-2545 | NT-522 | 20 Oct | Draft | ||
| ENC-2019 | NT-352 | 22 Oct | Draft |
6 of 6 records
NT-597Clinical notes · CN-76144
DraftEncounterENC-1381
Signed at13 Oct
What you can do
Give the note a known author
A clinical note belongs to an encounter and an author. It records note type, narrative, signed time and status. Draft identifies work still being written; Signed identifies the attested version; Amended signals a later correction. The signed time matters because the encounter’s completion depends on actual documentation, not simply a label in a work queue. Keep the author linked to the staff record used for clinical access.
Clinical privileges hold the clinician, privilege type, license number, issuing authority, verification evidence, effective dates and verification status. A current verified privilege is checked for protected actions. The workflow also checks a current care team assignment for the patient and purpose. A verified privilege alone is not a patient assignment; a patient assignment alone is not professional authorization.
How the work is organized
- Draft. Monitoring Clinician writes the note against the encounter being documented.
- Verify. Admin checks the clinician’s privilege evidence and effective dates.
- Sign. The author attests to the note and records the signed time before closure.
What to agree during setup
Set the privilege types needed for documentation and review, and decide who verifies the underlying evidence. Agree when a suspended or expired privilege takes effect in the operating process. Staff names in People link to user identities; check that the right person is acting before any privileged step. The care team assignment should state the patient, clinician, access purpose and dates used by the workflow.
Define how a signed note is corrected. Agree how to retain the earlier signed document outside the note status when a correction is made, and attribute the correction to its author. Decide who reviews a note awaiting signature and when the encounter may be completed. Pilot a draft note, a signed note and an amendment so the team knows which status to use. Rehearse an expired privilege and an ended care assignment as denial cases, not merely as dashboard filters.
Check the handoff on an actual case
A clinician documents a scheduled encounter after confirming the patient’s signed consent. The observation has already been recorded. The clinician drafts the note; the reviewer checks that the visit and measurement agree. The author signs it with the actual signed time. If a factual correction is found later, the clinician records an amendment in the note lifecycle. The encounter retains its linked note and responsible people. Staff use the agreed document-retention procedure to inspect the earlier signed version.
What your team sees
- Draft clinical notes — Find encounter notes awaiting an author’s signature.
- Pending privileges — Find clinician credentials awaiting verification.
- Encounters awaiting review — Check which visits still depend on documentation.
Follow the work through
Use encounter to signed note for the care handoff and roles for access rehearsal.
What it keeps track of
Data model- Clinical notes
- Attributed clinical documentation attached to an encounter.
- Clinical privileges
- Verified professional privileges held by a clinician.
- Encounters
- Scheduled and completed care encounters for monitored patients.
- People
- Care team members and staff referenced across the monitoring program.
- Care team assignments
- Purpose-scoped care team access to a patient.
Who uses it
Permissions- Monitoring Clinician
- , Clinical Reviewer, Admin.
- The author owns the note; the reviewer checks the documentation; Admin maintains staff identity and privilege verification.
Set up Remote Patient Monitoring your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.