Administration
Roles and permissions in Remote Patient Monitoring
Each role in Remote Patient Monitoring: what it sees, does and cannot do, its approvals, and a permissions matrix.
Applies to Remote Patient Monitoring as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.
On this page
Who can see and do what in Remote Patient Monitoring. These roles are the starting point; your administrators set them up to match your teams. Platform roles are assigned in Vivify as part of the managed service.
Roles
Medical director
Medical director, clinical program lead, director of care management. Owns the clinical design of the program and approves what the platform asks of patients and when it alerts the care team.
- Sees: All patients in the program and their readings; Care pathways, thresholds and their change history; Program reporting on enrollment, engagement and alerts
- Does: Approves care pathways, questions and education content; Approves default thresholds and the protocol for responding to alerts; Approves patient-specific threshold changes or delegates them to named clinicians; Decides which conditions and patient groups the program covers; Reviews program results in the service review
- Cannot: Apply configuration changes in the platform directly; Approve a change they requested themselves when a second approver is named
- Approvals: Approves pathways, thresholds and protocols; their own requests go to a named second clinical approver.
- Notified about: Changes awaiting approval, the monthly service report, and platform incidents that affect monitoring.
Care manager
Registered nurse care manager, health coach, care coordinator with clinical license. Reviews readings and alerts for their patients and acts on them under the approved protocol.
- Sees: Patients assigned to them, with readings, alerts, answers and trends; Missed-reading flags for their patients; Their own record of actions and time
- Does: Reviews out-of-range and missed readings on the dashboard; Contacts patients by phone, message or video; Escalates to the patient's clinician under the protocol; Records actions and time spent; Proposes patient-specific threshold changes for approval
- Cannot: Change a pathway or default thresholds; See patients outside their assignment unless their role allows; Discharge a patient without the clinician's decision
- Approvals: Patient-specific threshold changes they propose are approved by the medical director or a named clinician.
- Notified about: New alerts for their patients, patients with missed readings, and patients newly assigned to them.
Program coordinator
RPM program coordinator, enrollment specialist, medical assistant. Gets patients onto the program and keeps track of every kit.
- Sees: Referrals waiting for enrollment; Enrollment and consent status; Kit shipment, setup and return status
- Does: Confirms eligibility and records consent; Enrolls patients on the pathway the clinician selected; Orders kits and tracks shipment and setup; Contacts patients who have not sent a first reading; Arranges kit returns on discharge
- Cannot: Change pathways or thresholds; Review clinical alerts or record clinical actions
- Approvals: Enrollment on a pathway follows the clinician's order; nothing they do needs separate approval.
- Notified about: New referrals, kits delivered but not set up, and kits not returned.
Revenue cycle lead
Revenue cycle manager, coding and billing lead, compliance auditor for billing. Checks that the records behind each remote monitoring claim are complete before it is submitted.
- Sees: Monthly records of enrollment, consent, reading days and care time per patient; Patients whose records are incomplete for the month; Program reporting needed for billing review
- Does: Reviews monthly billing support reports; Returns incomplete records to the program team; Decides which services are billed, under your billing policies; Samples records for internal billing audit
- Cannot: Change clinical records or recorded time; Change pathways, thresholds or patient enrollment
- Approvals: Billing decisions follow your organization's coding and compliance policies; Moraph does not decide what is billed.
- Notified about: Monthly billing support reports when they are ready.
IT or EHR analyst
EHR interface analyst, clinical applications analyst, IT security lead. Connects the platform to your EHR and identity systems and manages access to the service.
- Sees: Interface status and error queues; User accounts and roles; Change requests affecting integration
- Does: Works with Moraph on the EHR interface and its testing; Approves Moraph administrator access; Creates and removes staff users, or asks Moraph to; Coordinates EHR upgrades and retesting; Handles first-line staff support
- Cannot: Change clinical pathways or thresholds; See patient readings unless their role allows
- Approvals: Changes to the EHR interface are approved through your change process and the medical director where clinical content is affected.
- Notified about: Interface errors that Moraph cannot resolve, planned platform changes, and Vivify service notices.
Moraph RPM platform engineer
Moraph remote monitoring engineer, integration engineer. Configures and supports the platform, devices and data feeds under changes your organization has approved.
- Sees: The platform's administration settings within the service's scope; Device and transmission status; Interface error queues, tickets and the change record
- Does: Builds pathways, questions and thresholds as approved; Configures devices and kit types; Monitors transmission and interface errors and fixes them; Supports patients and staff with technical problems; Escalates platform defects to Vivify
- Cannot: Approve pathways, thresholds or a change they will apply; Review readings for clinical purposes or contact patients about their health; Grant themselves additional administrator rights
- Approvals: Every configuration change they apply has an approved request; emergency actions follow the agreed procedure and are reported straight away.
- Notified about: Interface errors, devices not transmitting, approvals granted, and Vivify service notices.
Moraph service manager
Moraph service delivery manager. Runs the service, reports on it and makes sure requests, kit issues and escalations reach the right people.
- Sees: Service reporting, tickets, changes and escalations; Kit inventory and logistics status; Licence use and renewal dates
- Does: Prepares and runs the monthly service review; Tracks requests, changes and escalations to closure; Coordinates kit logistics with the fulfilment arrangement; Coordinates with Vivify on platform incidents and service notices
- Cannot: Apply configuration changes; Make clinical or billing decisions
- Approvals: Recommendations on pathways, kits and staffing go to the medical director for a decision.
- Notified about: Escalations, overdue requests, kit shortages and platform incidents.
Permissions at a glance
| Action | Med director | Care manager | Coordinator | Revenue cycle | IT analyst | Moraph eng. | Moraph service |
|---|---|---|---|---|---|---|---|
| Approve care pathways and default thresholds | Approves | – | – | – | – | – | View |
| Change a patient's thresholds | Approves | Own work | – | – | – | – | – |
| Apply a configuration change | Approves | – | – | – | – | Full | – |
| Enroll and discharge patients | Approves | Own work | Full | – | – | – | – |
| Review readings and alerts | Full | Own work | – | – | – | – | – |
| Record actions and care time | Full | Own work | – | View | – | – | – |
| Order, track and return kits | View | View | Full | – | – | Full | Full |
| Resolve device and interface errors | – | – | View | – | Full | Full | View |
| View billing support reports | View | Own work | – | Full | – | – | View |
| Manage staff users and roles | Approves | – | – | – | Full | Full | – |
| View change history | View | – | – | View | View | View | View |
"Own work" means only records or items assigned to that person; "Approves" means the role signs off the action.
How access is controlled
- Clinical decisions stay with your clinicians. The platform flags readings against thresholds your clinicians approved; care managers and clinicians decide what to do.
- Moraph engineers apply changes; your organization approves them. Changes to pathways and thresholds always have a clinical approver, and nobody approves a change they requested themselves when a second approver is named.
- Moraph staff see patient information only as far as technical support and data feed work require, using named individual accounts with the least rights the service needs.
- Roles are agreed during implementation and can be limited by clinic, program or care team. Patients use the patient app or tablet and never see staff screens.
Was this page helpful?
Report a problem with this page
Need help with your own setup rather than this page? Raise a support ticket.