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
- Encounters and observations
Encounters and observations
Move scheduled care through arrival, measurement, review and completion.
OverviewUpcoming encounters×
Remote Patient Monitoring · Encounters and observations
New
Upcoming encounters
Encounters
| Patient | Clinician | Scheduled at | Started at | Ended at | Status | |
|---|---|---|---|---|---|---|
| PTN-46654 | 19 Oct | 23 Oct | 26 Oct | Scheduled | ||
| PTN-67893 | 05 Oct | 14 Oct | 19 Oct | Scheduled | ||
| PTN-12020 | 11 Oct | 18 Oct | 20 Oct | Scheduled | ||
| PTN-54684 | 10 Oct | 13 Oct | 17 Oct | Scheduled | ||
| PTN-74068 | 25 Oct | 03 Nov | 08 Nov | Scheduled |
6 of 6 records
PTN-46654Encounters · ENC-77901
ScheduledScheduled at19 Oct
Started at23 Oct
Ended at26 Oct
What you can do
Make the visit state reflect actual care
An encounter ties a patient and clinician to a scheduled time, visit type, start time, end time and working status. The schedule lets the care team see what is planned. Arrival means staff have verified patient identity and current purpose-specific consent. In progress means the team is documenting care. Awaiting review identifies a handoff before completion. Completed requires an actual end time and the necessary documentation and follow-up checks.
Observations hold point-in-time measurements taken during the encounter. Each observation records the metric, value, unit, observed time, encounter and person who recorded it. Keep these separate from transmitted device readings: an observation belongs to a care encounter, while a remote reading belongs to a device enrollment. A clinician can compare them in context without turning one into the other.
How the work is organized
- Schedule. Care Coordinator selects the patient, clinician, visit type and planned time.
- Document. Monitoring Clinician records arrival, observations and the clinical note.
- Close. The clinician resolves outstanding care tasks and records when the encounter ended.
What to agree during setup
Choose how visits are scheduled and who verifies identity at arrival. Define which purpose-specific consent applies to each visit type, and what evidence staff must see before recording arrival. Decide which observations the team captures during the visit and which units they use. Make the distinction between a device transmission and an encounter measurement clear in training, especially when both occur on the same day.
Agree who handles an encounter awaiting review, how an unsigned note is returned to its author, and how a care task is resolved before completion. A cancelled appointment should remain distinguishable from a completed one. A visit that started but lacks its actual end time should remain open for correction by the right clinician. These are ordinary operating decisions to rehearse with a scheduled, cancelled and completed example.
Check the handoff on an actual case
A patient with an assigned clinician arrives for a scheduled review. Care Coordinator confirms identity and signed consent, then records arrival. Monitoring Clinician begins the encounter, measures a value and records it as an observation with unit and time. The clinician drafts a note, assigns a care task and sends the encounter for review. Once the note is signed and the task is resolved, the clinician records the actual end time and completes the encounter. Anyone reading the chart can distinguish the visit measurement from the earlier transmitted readings.
What your team sees
- Encounter workboard — See scheduled, arrived, active and awaiting-review visits by status.
- Upcoming encounters — Check the patient, clinician and planned time before the visit.
- Encounters awaiting review — Find visits whose documentation still needs attention.
Follow the work through
Read consent to encounter and encounter to signed note. Use the data model to plan source mapping.
What it keeps track of
Data model- Encounters
- Scheduled and completed care encounters for monitored patients.
- Observations
- Point-in-time measurements captured during an encounter.
- Patients
- Patients enrolled in the remote monitoring program.
- Consents
- Purpose-specific patient consent records and their lifecycle.
- Clinical notes
- Attributed clinical documentation attached to an encounter.
- Care tasks
- Follow-up work assigned to a responsible clinician.
Who uses it
Permissions- Care Coordinator
- , Monitoring Clinician, Clinical Reviewer.
- The coordinator prepares arrival; the clinician documents and completes care; the reviewer checks the handoff.
Set up Remote Patient Monitoring your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.