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
- Device enrollment
Device enrollment
Link a monitoring device and its metric to the right patient.
OverviewDevice enrollments×
Remote Patient Monitoring · Device enrollment
New
Device enrollments
Device enrollments
| Patient | Device identifier | Metric type | Enrolled at | Ended at | |
|---|---|---|---|---|---|
| PTN-18119 | DI-594 | MT-269 | 06 Oct | 08 Oct | |
| PTN-51811 | DI-594 | MT-621 | 10 Oct | 14 Oct | |
| PTN-47583 | DI-774 | MT-363 | 10 Oct | 14 Oct | |
| PTN-92361 | DI-105 | MT-503 | 03 Oct | 08 Oct | |
| PTN-51207 | DI-812 | MT-650 | 08 Oct | 13 Oct |
6 of 6 records
DI-594Device enrollments · DE-53716
PatientPTN-18119
Metric typeMT-269
Enrolled at06 Oct
Ended at08 Oct
What you can do
Give each device a patient and a purpose
Device enrollment records the patient, device identifier, metric type, enrollment date and ending date. It forms the bridge between the patient record and the readings that arrive later. Device Coordinator should select the patient from the roster and check the device identifier against the physical or source-system label before submitting the enrollment. A reading associated with the wrong enrollment can appear beside the wrong patient even when its value and time are correct.
The capture workflow checks the linked patient, encounter and acting clinician. It requires a current verified clinical privilege covering the action and event date, together with an active care team assignment for the patient and access purpose. Treat those checks as part of the enrollment handoff. A staff member who can open the enrollment screen is not thereby authorized to enroll any device for any patient.
How the work is organized
- Patient link. Each enrollment points to one patient whose identity has been checked.
- Device link. The identifier distinguishes the device that sent or will send readings.
- Care authority. The clinician’s privilege and care assignment are checked for the enrollment action.
What to agree during setup
Choose the source of device identifiers and the procedure for a replacement device. Decide which metric names staff enter and how those names relate to the incoming device feed. Determine when enrollment begins and who records its end. A patient changing devices should retain the older enrollment and its readings so a clinician can understand which source produced a past value. Keep the source-system mapping and any device provisioning handoff explicit.
Agree who checks the care team assignment at setup. The assignment has a purpose and effective dates; the privilege has a type, verification state and effective dates. The implementation team should rehearse an expired privilege, an ended assignment and a device submitted for the wrong patient. Each should stop before the new enrollment is accepted. Then repeat the valid request and reconcile any duplicate association before the device feed is connected.
Check the handoff on an actual case
Care Coordinator confirms a patient’s signed consent and assigns the clinician. Device Coordinator checks the device identifier, selects the metric and records the enrollment date. The clinician’s privilege and care assignment cover the event. The first transmitted reading then points back through this enrollment to the patient. If the device is later replaced, the coordinator ends the original enrollment and creates the new association. The clinician can still read prior measurements in the context of their original device.
What your team sees
- Device enrollments — Check the patient, device identifier, metric and enrollment dates.
- Active care assignments — Check the responsible clinician and purpose for the enrollment.
Follow the work through
Follow device to reading, then reading to follow-up. See implementation for a first-device rehearsal.
What it keeps track of
Data model- Device enrollments
- Remote monitoring devices provisioned to a patient.
- Patients
- Patients enrolled in the remote monitoring program.
- Clinical privileges
- Verified professional privileges held by a clinician.
- Care team assignments
- Purpose-scoped care team access to a patient.
- People
- Care team members and staff referenced across the monitoring program.
Who uses it
Permissions- Device Coordinator
- , Care Coordinator, Monitoring Clinician.
- The device coordinator records the association; the care coordinator confirms patient and consent context; the clinician holds the required care authority.
Set up Remote Patient Monitoring your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.