Remote Patient Monitoring

Overview

What you are buying

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.

See how it works

A short walkthrough

Illustrative screens of how Moraph runs the service, with fictional sample data. They are not screens of Vivify itself, which belongs to its vendor.

1. Step 1

   The enrollment and kit tracker

   Every referred patient has a row from consent to first reading, so nobody is left with a kit they never set up.

   Remote Patient Monitoring · Enrollment trackerSample data

   Patient	Pathway	Consent	Kit	First reading	Status
   Patient 40217	Heart failure	Recorded	Delivered	Received	Active
   Patient 40231	Hypertension	Recorded	Delivered	Received	Active
   Patient 40248	COPD	Recorded	Delivered	None	Setup call needed
   Patient 40252	Heart failure	Recorded	Shipped	None	Awaiting delivery
   Patient 40266	Diabetes	Pending	Not ordered	None	Awaiting consent

2. Step 2

   The pathway approval

   Each pathway's devices, questions and thresholds are written down and approved by a named clinician before they go live.

   Remote Patient Monitoring · Pathway reviewSample data

   Heart failure pathway v3 · Example Health System (fictional)

   Status

   Awaiting approval

   Prepared by

   Moraph RPM platform engineer

   Approver

   Medical director

   Devices

   Scale, blood pressure cuff, pulse oximeter

   Changes from v2

   Weight-gain threshold changed

   Default thresholds proposed

   • Weight gain over the amount set in your protocol over 1 day or 1 week
   • Systolic blood pressure above or below protocol limits
   • Oxygen saturation below protocol limit
   • No reading for the number of days set in your protocol

   Approve pathwayReturn with comments

3. Step 3

   A device that stopped sending

   Moraph spots patients whose readings have stopped and follows up until data is flowing again.

   Remote Patient Monitoring · Ticket TX-1182Sample data

   Ticket TX-1182 · Patient 40217, no readings

   1. No readings flagged in daily transmission checkMoraph engineer
   2. Tablet found offline; patient calledProgram coordinator
   3. Home internet changed; patient helped to reconnectMoraph support
   4. Test reading receivedMoraph engineer
   5. Care manager told monitoring has resumedMoraph engineer

4. Step 4

   An interface error

   Failed messages to the EHR are found, explained and resent, with the record kept.

   Remote Patient Monitoring · Interface errorSample data

   Interface error IE-3307 · Reading not filed

   Message

   Blood pressure reading, Patient 40231

   Error

   Patient not matched in EHR

   Cause found

   Identifier changed after patient record merge

   Resolution

   Identifier updated, message resent

   Status

   Awaiting EHR team confirmation

   Checks made

   • Other messages for the patient reviewed
   • No other patients affected
   • Merge process noted for the service review

   Resend messageClose error

5. Step 5

   The billing support report

   Each month, the records behind remote monitoring services are laid out for your revenue cycle team to review.

   Remote Patient Monitoring · Billing supportSample data

   Patient	Pathway	Consent on file	Days with readings	Care time recorded	Record
   Patient 40217	Heart failure	Yes	24	42 min	Complete
   Patient 40231	Hypertension	Yes	19	25 min	Complete
   Patient 40248	COPD	Yes	6	10 min	Complete
   Patient 40252	Heart failure	Missing	0	0 min	Incomplete

6. Step 6

   The monthly service review

   Enrollment, engagement, kits, data feeds and support for the month, reviewed with your leads and turned into actions.

   Remote Patient Monitoring · Service reviewSample data

   Monthly service review · Example Health System (fictional)

   Period

   Sample month

   Patients active

   312

   Kits shipped

   48

   Transmission tickets

   21

   Interface errors resolved

   9 of 10

   Actions agreed

   • Add cellular kits for patients without home internet
   • Clinic B to confirm consent process
   • Review weight threshold with medical director
   • Retest interface after planned EHR upgrade

   Approve reportAdd action

Roles and permissions

Who does what in the product

Each role below is a starting point. During implementation we set them up to match your teams, and every action anyone takes is recorded in the audit trail.

Permissions at a glance

• ● Full
• ◐ Own work only
• ✓ Approves
• ○ View only
• – No access

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.

Integrations

How it connects to your systems

Each integration is confirmed in discovery and specified in the design. See how an engagement progresses.

Reporting

What you can report on

11 standard reports, grouped by who uses them. Each shows who it is for, how it can be broken down, how it is delivered and what it is used for. The data behind them is also available to your own reporting tools.

Program

Operations

Billing support

Governance

Exports, access and evidence

• Reports are produced by Moraph from the platform's program data and from Moraph's ticket, kit and change records, and reviewed with you each month.
• Billing support reports show the records behind each month. Your revenue cycle team decides what is billed and checks it against current payer rules.
• Reports respect each viewer's role: care managers see their own patients, and summary reports for leadership can be produced without patient identifiers.
• Reports can be exported to CSV, and summary reports to PDF, for committees, internal audit and payer reviews.
• Report contents and frequency are agreed during implementation; additional views can be requested through the service review.

Implementation

What a rollout involves

The general phases are on Working with Moraph. For this product, they involve the following.

Evaluation checklist

What to test in a demonstration or pilot

Questions worth putting to us, and to any other vendor you are considering.

1. Walk a sample patient from referral through consent, kit delivery and first reading
2. Review the proposed pathway and thresholds with the clinicians who will approve them
3. Check how a device that stops sending is detected and who follows up
4. Test the EHR interface with fictional patients and confirm where readings appear
5. Review a sample billing support report with your revenue cycle team
6. Confirm the split of responsibilities between your care team, Moraph and Vivify

Next steps

Evaluate Remote Patient Monitoring

Buying through a formal procurement? See How to buy for purchasing routes, accessibility conformance reports and company information. Documentation: Remote Patient Monitoring guides on docs.moraph.com (getting started and security guides are public; setup, administration and integration guides are for client accounts). Support: Remote Patient Monitoring support guide.