Getting started
Getting started with Remote Patient Monitoring
What Remote Patient Monitoring is for, who uses it, what you need before you start, and your first steps.
Applies to Remote Patient Monitoring as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.
Moraph resells, implements and runs the Vivify Health remote patient monitoring platform for health systems, medical groups and health plans. We configure care pathways and alert thresholds your clinicians approve, connect home devices such as scales, blood pressure cuffs and pulse oximeters, and keep readings flowing into the care team's dashboard and your EHR. Your clinicians review readings and decide on care; Moraph runs the platform, the data feeds and the kit logistics behind them.
What it is for
Remote monitoring programs often start well and then struggle with the work around the clinical part. Kits go out without anyone tracking whether they were set up, devices stop sending readings and nobody notices for days, alert thresholds are copied from a vendor default rather than agreed by clinicians, and readings sit in a separate portal instead of the EHR. Billing for monitoring depends on records of enrollment, consent, readings and time spent that are hard to pull together.
- Patients receive kits but some never send a reading
- Devices that stop transmitting are found late, if at all
- Alert thresholds and care pathways are not formally approved by clinicians
- Enrollment, consent, reading days and care time are hard to evidence for billing
Who uses it
- Medical directors and clinical leads for chronic care and post-discharge programs
- Care managers and nurses who review readings and contact patients
- Program coordinators who enroll patients and manage kits
- Revenue cycle teams who bill for remote monitoring services
- IT and EHR teams who connect the platform to clinical systems
Before you start
- Your organization uses Remote Patient Monitoring as a managed platform from Moraph, under an agreement that covers it.
- Licences for Vivify, bought through Moraph or under your own agreement with the vendor.
- A Moraph account in your organization for each person who works with Moraph on the service.
- Named technical and security contacts, recorded in the Moraph Portal.
Steps to get started
Agree the scope of the managed service for Remote Patient Monitoring with Moraph, including which environments and teams it covers.
Name your administrators, technical contact and security contact in the Moraph Portal under People and access.
Review the configuration baseline Moraph proposes for your regulations, and record any changes you need.
Confirm how users will sign in, through your identity provider where the platform supports it.
Agree the pilot group and the cut-over plan with your Moraph delivery lead.
Where to go next
Was this page helpful?
Report a problem with this page
Need help with your own setup rather than this page? Raise a support ticket.