1. Remote Patient Monitoring
  2. Data model and migration order
Reference

The tables behind Remote Patient Monitoring

Remote Patient Monitoring ships with 14 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.

Tables
14
Features
7, plus shared settings
Change it
Add fields and tables in Proto

How the model is organised

Patient and access:

Patients, Consents, care team assignments, clinical privileges, People, Users. Identity, consent, clinician authority and purpose-scoped patient access.

Remote monitoring:

Device enrollments, remote readings. A device association and its observed measurements.

Clinical care:

Encounters, Observations, clinical notes, care tasks. Visit progress, measurements, attributed documentation and follow-up.

Financial handoff:

Charges, Payments. Service charges linked to encounters and confirmed receipts linked to patients.

Every table, by feature

Device enrollment

5 tablesAbout this feature
  • Device enrollments

    Remote monitoring devices provisioned to a patient.

    Linked to Patients
  • Patients

    Patients enrolled in the remote monitoring program.

    Linked to People
  • Clinical privileges

    Verified professional privileges held by a clinician.

    Linked to People
  • Care team assignments

    Purpose-scoped care team access to a patient.

    Linked to Patients, People
  • People

    Care team members and staff referenced across the monitoring program.

    Linked to Users

Remote readings

6 tablesAbout this feature
  • Remote readings

    Transmitted device readings awaiting or completing review.

    Linked to Device enrollments, People
  • Device enrollments

    Remote monitoring devices provisioned to a patient.

    Linked to Patients
  • Patients

    Patients enrolled in the remote monitoring program.

    Linked to People
  • People

    Care team members and staff referenced across the monitoring program.

    Linked to Users
  • Clinical privileges

    Verified professional privileges held by a clinician.

    Linked to People
  • Care team assignments

    Purpose-scoped care team access to a patient.

    Linked to Patients, People

Encounters and observations

6 tablesAbout this feature
  • Encounters

    Scheduled and completed care encounters for monitored patients.

    Linked to Patients, People
  • Observations

    Point-in-time measurements captured during an encounter.

    Linked to Encounters, People
  • Patients

    Patients enrolled in the remote monitoring program.

    Linked to People
  • Consents

    Purpose-specific patient consent records and their lifecycle.

    Linked to Patients
  • Clinical notes

    Attributed clinical documentation attached to an encounter.

    Linked to Encounters, People
  • Care tasks

    Follow-up work assigned to a responsible clinician.

    Linked to Patients, People

Clinical notes and privileges

5 tablesAbout this feature
  • Clinical notes

    Attributed clinical documentation attached to an encounter.

    Linked to Encounters, People
  • Clinical privileges

    Verified professional privileges held by a clinician.

    Linked to People
  • Encounters

    Scheduled and completed care encounters for monitored patients.

    Linked to Patients, People
  • People

    Care team members and staff referenced across the monitoring program.

    Linked to Users
  • Care team assignments

    Purpose-scoped care team access to a patient.

    Linked to Patients, People

Care coordination

6 tablesAbout this feature
  • Care tasks

    Follow-up work assigned to a responsible clinician.

    Linked to Patients, People
  • Patients

    Patients enrolled in the remote monitoring program.

    Linked to People
  • People

    Care team members and staff referenced across the monitoring program.

    Linked to Users
  • Care team assignments

    Purpose-scoped care team access to a patient.

    Linked to Patients, People
  • Clinical privileges

    Verified professional privileges held by a clinician.

    Linked to People
  • Encounters

    Scheduled and completed care encounters for monitored patients.

    Linked to Patients, People

Charges and payments

5 tablesAbout this feature
  • Charges

    Billable care services derived from an encounter.

    Linked to Encounters
  • Payments

    Confirmed payments received against patient services.

    Linked to Patients
  • Encounters

    Scheduled and completed care encounters for monitored patients.

    Linked to Patients, People
  • Patients

    Patients enrolled in the remote monitoring program.

    Linked to People
  • People

    Care team members and staff referenced across the monitoring program.

    Linked to Users

Shared and settings

1 table
  • Users

    Users

    Linked to Users

Keys and references

Patients uses patient number for the program identifier. People links to Users and Patients points to its assigned clinician. Consents and care team assignments point to Patients; the assignment and clinical privileges point to People. Device enrollments points to Patients and remote readings points to device enrollments. Encounters points to Patients and the responsible clinician; Observations and clinical notes point to Encounters and their recorder or author. Care tasks points to the patient and assignee. Charges points to Encounters; Payments points to Patients. Keep source identifiers and device identifiers stable when importing.

Migration order

  1. Load Users and People with the correct staff-to-user links.
  2. Load Patients with their patient numbers and assigned clinicians.
  3. Load current Consents, clinical privileges and care team assignments with effective dates and evidence.
  4. Load device enrollments, then remote readings against the correct enrollment.
  5. Load active Encounters, Observations, clinical notes and care tasks.
  6. Load Charges and Payments after reconciling encounter and patient links; rehearse the complete care path before release.

Set up Remote Patient Monitoring your way.

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

How to get started