Remote Patient Monitoring Services

The vendor required to provide remote patient monitoring (RPM) program to enhance care for oncology patients across the continuum of treatment.
- Leverage digital health tools and connected devices to:
•    Improve early detection of complications.
•    Enhance patient experience by supporting care at home.
•    Reduce avoidable ed visits and readmissions.
•    Strengthen alignment with value-based care models and payer partnerships.
- Objectives
•    Understand the range of RPM solutions available (clinical focus, devices, platforms, workflows). 
•    Identify best practices and pitfalls in implementing RPM in oncology. 
•    Explore options for integration with altera sunrise (and possible future epic migration). 
•    Estimate resources, costs, and ROI models.
- Technology and devices
•    Devices provisioned by vendor, patient-owned, or BYOD (bring your own device)
•    Connectivity models (cellular, Bluetooth, wi-fi).
•    The data frequency, accuracy, and FDA clearances.
- Platform and integration
•    Outline the integration capabilities with altera SCM (current) and other major EHR’S such as epic.
•    List the FHIR/hl7/API capabilities.
•    The patient-facing apps or portals—ease of use, language support, and accessibility.
•    The alerting logic and clinician dashboards.
- Clinical workflow and staffing
•    The typical care team model (nurses, apps, central monitoring, outsourced options).
•    The escalation pathways—alerts triaged and routed
- Compliance, security and privacy
•    Security frameworks.
•    Your data storage location and retention policies.
- Reimbursement and financial models
•    List your experience supporting RPM CPT codes (99453, 99454, 99457, 99458).
•    support do you provide for value-based contracting arrangements
•    the typical ROI and cost avoidance metrics (readmissions, los, ed visits) and how your system measures these.
•    describe your pricing model: per patient, per device, per provider, enterprise license, etc.
- Implementation and support
•    The average implementation timeline.
•    The ongoing vendor support (technical + clinical).
•    The scalability—the program expands from pilot to enterprise
- Future platform considerations
•    The anticipated impact of AI on RPM model.