Hospital-at-home admits a patient to their own bedroom for conditions that have traditionally required an inpatient stay, delivering acute, hospital-level care in the home. The model combines continuous remote patient monitoring (RPM), daily clinician touchpoints both in person and over video, rapid-response logistics for when a patient deteriorates, and a central command center coordinating it all. The patient gets a hospital level of attention without the hospital bed, and the program takes on the obligation to detect and respond to acute changes as reliably as a ward would.
In the United States the program runs largely on the CMS Acute Hospital Care at Home waiver, which is what lets hospitals bill for inpatient-level care delivered at home. That waiver has been extended by Congress in increments rather than made permanent, which means its regulatory runway is genuinely a product planning input — the timeline over which you can count on reimbursement is set by legislation, not by your roadmap, and teams building here have to watch the extension cycle.
The build is coordination-heavy in a way that distinguishes it from a simple telehealth product. Monitoring, visit scheduling, supply and equipment logistics, and escalation all have to behave as one integrated system with inpatient-grade reliability, because a missed signal at home does not have a nurse three steps away to catch it. The common mistake is underestimating the operational and reliability bar — treating it as RPM plus video calls, when in reality the escalation pathway (how fast and how surely a deteriorating patient gets a clinician or transport) is the part that determines whether the program is safe.
