Foundation as Chronic Care Engine

RPM would turn Foundation from a point solution for visits, labs, and scripts into the system that runs the whole chronic care loop. A health system could enroll a hypertension or diabetes patient, ship a blood pressure cuff or glucose device, watch readings flow in, trigger outreach when values drift, order labs, route the patient to an async doctor review, and fill or adjust medication without staff stitching vendors together by hand.

• Foundation already has the key downstream pieces. Its APIs connect telehealth, diagnostics, and pharmacy workflows, and its automation layer handles benefits checks, prior auth, refill outreach, adherence follow up, and side effect monitoring. RPM adds the missing upstream signal, which is the live patient data that tells the system when to act.
  1 sacra
• Virta shows what this looks like in practice for metabolic disease. Patients use connected devices, coaches and physicians monitor readings, medications get adjusted quickly, and the company sells that as an ongoing employer and payer benefit. Foundation could provide the infrastructure layer for similar programs without owning the care brand itself.
  2 sacra
• The closest analog on the health system side is Commure and Athelas, which used patient monitoring as one module inside a broader hospital software bundle. That matters because hospitals usually buy more software from vendors that can plug monitoring into billing, messaging, and clinical operations, not from standalone device dashboards.
  3 sacra 4 sacra

The next step is for healthcare infrastructure platforms to move from transaction processing to continuous care orchestration. If Foundation adds RPM cleanly, it can sell health systems a chronic care engine for diabetes, hypertension, obesity, and post discharge follow up, which raises revenue per customer and makes the platform harder to replace.