Remote Patient Monitoring

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.

The problem it solves

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.

Who it’s for

• 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

1. EnrollPatients are referred, consented and enrolled on the care pathway their clinician selects, and a kit with the right devices is sent or handed over.
2. MonitorReadings from home devices reach the care team's dashboard, where Vivify applies the pathway's thresholds and surfaces readings outside range for clinical review.
3. Keep data flowingMoraph watches the technical side: devices that have stopped sending, failed EHR messages and connection problems, and works with patients and your team to fix them.
4. Close and reportPatients are discharged from the program when the clinician decides, kits are returned, and the records needed for reporting and billing are complete.

Connected home devices

Vivify receives readings from supported Bluetooth devices such as weight scales, blood pressure cuffs, pulse oximeters, thermometers and glucometers, through a tablet or the patient's own phone.

Care pathways

Condition-specific pathways combine device readings with daily questions and education, configured to protocols your clinicians approve.

Clinician-approved thresholds

Alert thresholds for each pathway, and any patient-specific changes, are set and recorded with the approving clinician.

Care team dashboard

Vivify shows the care team which patients have readings out of range or missed readings, so they can work the highest-priority patients first.

Video and messaging

Care managers can contact patients through the platform's video visits and messaging where your program uses them.

EHR integration

Readings, alerts and program summaries are sent to your EHR through the interface agreed during implementation.

Kit logistics

Moraph coordinates kit orders, shipping, setup support, returns and device replacement with the fulfilment arrangement agreed for your program.

Transmission monitoring

Moraph checks daily for patients and devices that have stopped sending readings and starts follow-up.

Enrollment and consent records

Each patient's enrollment, consent, pathway and discharge are recorded, ready for audit and billing review.

Time and reading records

Reading days and care team time are recorded per patient per month, to support your revenue cycle team's billing review.

Patient technical support

Patients get help with device setup and connection problems from Moraph support or your team, as agreed.

Controlled changes

Changes to pathways, thresholds and settings each have a request, a clinical approver and a record.

Medical director

Approves care pathways, thresholds and protocols, and owns the clinical program

Care manager

Reviews readings and alerts, contacts patients and records actions and time

Program coordinator

Enrolls patients, records consent and tracks kits from shipment to return

Revenue cycle lead

Reviews monthly records of readings and care time before claims are submitted

Moraph RPM platform engineer

Configures the platform, devices and EHR interface under approved changes, and fixes data feed problems

Moraph service manager

Runs the monthly service review and reports on enrollment, transmission and support

Electronic health record

Readings, alerts and program summaries are sent to your EHR through an HL7 or API interface agreed during implementation.

Home devices

Supported Bluetooth devices pair with the tablet or the patient's phone app and send readings to Vivify.

Single sign-on

Staff sign in through your identity provider where the platform supports it.

Kit fulfilment

Kit orders, shipment tracking and returns are coordinated with the fulfilment arrangement agreed for your program.

Care management system

Where care managers work in a separate care management tool, program enrollment and alerts can be shared with it.

Your service desk

Staff tickets pass between your IT service management tool and Moraph's.

Reporting

Program, transmission and billing support reports are delivered to your teams or data warehouse.

Business associate agreement

Moraph signs a business associate agreement with your organization because the service involves PHI, and Vivify's own agreement covers the platform.

Named Moraph staff

Moraph staff work with individual accounts, the least rights the service needs and multi-factor authentication; there are no shared accounts.

Role-based access

Care teams see their own patients, coordinators see enrollment and kits, and Moraph sees what technical support requires.

Complete audit trail

The platform's access logs and Moraph's change and ticket records show who did what and when.

Encryption and keys

Service records Moraph holds are encrypted, with keys Moraph staff cannot use without explicit, time-bound authorization.

People decide

Thresholds flag readings for review; clinicians decide on care, and Moraph tooling never contacts patients about their health.

Licences through Moraph

Moraph resells the Vivify subscription and runs it as one service, subject to Vivify's terms.

Your existing Vivify program

If you already license Vivify, Moraph reviews pathways, thresholds and integrations and takes over operation.

Co-managed

Your team keeps some tasks, such as enrollment or patient technical support, and Moraph runs the rest; the split is written into the responsibilities for the service.

Program design

We work with your medical director on the conditions in scope, eligibility, patient numbers, care team staffing and the protocol for responding to alerts.

Pathways and thresholds

Pathways, questions, education and default thresholds are drafted from your protocols and approved by your clinicians before build.

Devices and kits

Device types for each pathway and the kit fulfilment, setup and return arrangements are agreed and tested.

EHR integration

The interface to your EHR is built and tested with your analysts, including where readings and summaries appear.

Pilot

A first group of patients is enrolled with extra support, and the protocol, thresholds and kit process are adjusted with your team.

Handover to operations

Change process, approvers, support routes, escalation contacts and reporting are agreed, and the program moves into day-to-day operation.

• Moraph is not Vivify Health. Vivify operates the platform, and Vivify's own service commitments, roadmap, maintenance and outages apply.
• Vivify licences are subject to Vivify's terms. Devices and kits are priced separately.
• Remote monitoring is not an emergency service. Patients must be told how to get urgent help, and readings are reviewed during the hours your program sets.
• Moraph does not review readings for clinical purposes, contact patients about their health or make care decisions; your clinicians do.
• Moraph does not decide what is billed or submit claims. Billing rules for remote monitoring change, and your revenue cycle team checks them.
• Monitoring depends on patients using their devices and on home connectivity. Some patients will need a cellular-connected kit or extra support.
• Only devices the platform supports can send readings automatically; others need manual entry.
• Moraph does not make privacy or breach notification decisions; your privacy officer does.

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