Hospital at home technology has to do something most remote care software never attempts: support inpatient-level care in a patient's living room, with the same accountability as a hospital bed. Monitoring, staffing, logistics and documentation all have to work together, every hour of the day.
This guide breaks the technology into its working parts, from the kit that goes into the home to the command center that watches it, and explains how each part ties back to the EHR and to Medicare's Acute Hospital Care at Home waiver.
What technology does a hospital at home program need?
Building a hospital at home program?
Agnotic builds hospital at home platforms for clients, from monitoring and command center tools to EHR integration.
A hospital at home program needs five kinds of technology: a monitoring kit in the home, a virtual command center that watches patients and escalates, tools that schedule and route in-person visits, EHR integration that keeps the inpatient record complete, and communication links that work when the home network does not.
The difference from ordinary remote monitoring is the level of care. These patients would otherwise be in a hospital bed, so response times, escalation paths and documentation have to meet inpatient expectations, not outpatient ones.
What do the CMS waiver rules mean for the system?
The CMS waiver rules decide which hospitals can run the program and on what terms, so the system has to support them from day one. The Consolidated Appropriations Act, 2026 extended Medicare's Acute Hospital Care at Home waiver through 30 September 2030.
That date gives programs a planning horizon, and the software should still treat it as a dated rule. Store the waiver end date in configuration, and plan how the system would support discharging or returning patients to the hospital if the waiver lapsed without further action.
CMS QualityNet states that each hospital requests its own waiver under its CMS Certification Number, with an expedited review for hospitals that have treated at least 25 patients in an at-home acute setting and a more detailed review for others. A health system running several hospitals needs the platform to track which hospital and waiver each patient is admitted under.
The waiver also sets patient safety requirements covering how patients are selected, in-person visits, monitoring and emergency response. Encode the current version published on QualityNet as checklists and timers in the platform, owned by the clinical lead, rather than relying on staff memory or an old slide deck.
How should monitoring kits be chosen and managed?
Monitoring kits should be chosen for reliability in an untrained home, not for the longest feature list, and managed as tracked hospital equipment. A kit that fails at 2 a.m. with no one to fix it is a safety problem, not a support ticket.
- Connectivity: use a cellular hub or a kit with its own data connection, so monitoring does not depend on the household's Wi-Fi.
- Devices: choose vital sign devices the clinical team specifies, such as blood pressure, pulse oximetry, temperature and, where needed, continuous wearable sensors, with a defined data path for each.
- Communication: include a tablet or similar device for video visits and an always-available way to reach the command center, with large controls for patients who are unwell.
- Power and backup: plan for power cuts with battery backup and a phone fallback, and alert the command center when a device goes offline.
- Asset tracking: record which kit, serial numbers and firmware went to which patient, for recall, cleaning and swap logistics.
Provision kits before they leave the hospital. Each device should be paired to the patient's record, tested end to end with a reading that appears in the command center, and labeled so a visiting nurse can swap a faulty unit quickly.
When the patient is discharged, the kit comes back through a return workflow: collection, cleaning, data wipe where devices store readings, inspection and restocking. Track kits through each step so the program always knows how many are ready.
What does the virtual command center do?
The virtual command center is the nursing station of a hospital at home program. It shows every patient's status, receives device alerts, runs scheduled virtual check-ins and decides when to send someone to the home or bring the patient back to the hospital.
Its main screen is a census view: each patient with their latest vitals, alert state, next scheduled visit, assigned clinicians and any open tasks. Sorting and filtering should put the patients who need attention first, with stale data flagged as clearly as abnormal data.
Alerts need clinical thresholds set per patient by the care team, with acknowledgment and escalation timers. An alert that no one acknowledges within the set time should move to the next person automatically, and every step should be logged.
Shift handoff is easy to overlook. Give the incoming team a summary of each patient's events, pending tasks and concerns since the last shift, generated from the record rather than typed from memory.
Coordinating in-person care in the home
In-person care at home needs dispatch software, not just a calendar. Nurses, paramedics, therapists, phlebotomists and couriers each visit on their own schedule, and the system has to plan routes, track arrival and confirm each visit was completed.
Treat each visit as a task with a required window, a role, a location and a checklist. The scheduler assigns it to a qualified person, the mobile app shows the route and patient details, and the command center sees the visit status change from planned to en route to on site to complete.
Supplies and medications are part of the same plan. Deliveries of medications, oxygen or equipment should be linked to orders in the EHR and confirmed on receipt, so the command center knows what is in the home.
Field staff can lose signal in a home, so the mobile app should save work offline and sync when connected, without letting two people edit the same record at once. Visit notes should land in the EHR, not only in the dispatch tool.
How does documentation stay in the EHR?
Documentation stays in the EHR when every hospital at home patient is admitted there as an inpatient, and every other tool writes back to that encounter. The EHR is the legal record and the source for billing, quality measures and handoffs back to the hospital.
Device readings should reach flowsheets through an interface the EHR supports, such as HL7 v2 ORU messages or FHIR Observation writes where the vendor allows them. Validate readings before filing, and file them with the device identifier so a clinician can see the source.
An EHR can represent hospital at home as a virtual unit or location. Work with the EHR team on how beds, census and transfers are represented, so a return to the physical hospital is a transfer within one admission, not a discharge and a new admission.
Orders and medication administration should follow the same rules as in the hospital. If the command center, the dispatch tool or the mobile app shows orders, they should read them from the EHR rather than keep their own copy.
How should escalation work when a patient worsens?
Escalation should follow written pathways that the platform enforces: who is alerted, who decides, how quickly someone reaches the home and how the patient gets back to the hospital. The pathway must work at any hour and when a device or network fails.
Build the pathways as configurable steps with timers. A worsening reading triggers a virtual assessment, which can trigger an urgent in-person visit, which can trigger transport back to the hospital or an emergency call. Each step records who acted and when.
Silence is a signal too. When a device stops sending data or the patient does not answer a scheduled check-in, the platform should treat it as an event with its own escalation, not wait for the next reading.
A readiness checklist for hospital at home technology
Use this checklist before the first patient is admitted. Each item has a clear test, and a failed test is a reason to delay launch.
- 1. Waiver tracking: each patient is linked to the admitting hospital and its waiver, and the waiver end date sits in configuration.
- 2. Kit test: a provisioned kit sends readings to the command center over cellular with the household Wi-Fi off.
- 3. Offline alert: unplugging a device raises an offline alert in the command center within the time the clinical team set.
- 4. Alert escalation: an unacknowledged alert moves to the next person on schedule, and the log shows each step.
- 5. Visit dispatch: a scheduled visit appears in a field app, runs offline, syncs and files a note to the EHR encounter.
- 6. EHR filing: device readings appear in the right flowsheet rows with source and time, and a transfer back to the hospital stays in one admission.
- 7. Escalation drill: a simulated deterioration runs from alert to virtual assessment to in-person visit to transport, within the times in the pathway.
- 8. Kit return: a discharged patient's kit goes through collection, cleaning, wipe and restock, and inventory updates.
How Agnotic can help
Hospital at home programs stand or fall on the joins between monitoring, people in the field and the inpatient record. Agnotic Technologies builds hospital at home platforms for clients: kit provisioning and device data pipelines, command center census and alerting, visit dispatch with offline field apps, and EHR integration that keeps every reading and note in the admission.
Agnotic does not run care or staff programs. It builds the software the clinical team specifies and tests it against the program's own pathways before launch.
Build your hospital at home platform with Agnotic
Explore Agnotic's hospital at home platform work, or browse the remote care articles hub.
Related reading on Agnotic
Continue with RPM programs, alert fatigue, clinician dashboards and telehealth in home health care.
