What is a house-call EHR?
A house-call EHR is an electronic health record designed for medical care delivered in the patient's home, where the travel between visits is part of the clinical day rather than an inconvenience outside the system. A conventional clinic EHR assumes patients come to the provider, so it models the day as a calendar and treats distance as irrelevant. A house-call EHR inverts that assumption: appointment slots are ranked by how much driving each one adds, the day is planned and displayed as a route rather than a list, documentation is built for a laptop in someone's living room instead of a fixed workstation, and patients waiting at home are given a live arrival estimate. The category is used by house-call physicians, mobile medical practices, home-based primary care programs, and health systems running home-visit lines of service.
How a house-call EHR differs from a clinic EHR
The differences are not cosmetic. Every row below describes an assumption a clinic EHR makes that stops being true once the clinician is the one travelling, and each one has to be reworked rather than configured around.
| Dimension | Clinic EHR | House-call EHR |
|---|---|---|
| Scheduling model | Open slots on a calendar; distance is not a factor | Slots ranked by drive time from the previous stop |
| The provider's day | A list of appointments in one location | A route across many locations, with per-leg distance and time |
| Where charting happens | A fixed workstation between patients | A laptop in the patient's home, often offline-tolerant |
| Patient wait experience | Patient waits in a room with staff present | Patient waits at home; needs a live arrival estimate |
| Order signing | Signed on-site by the treating provider | Often needs dual signature — visiting plus attending physician |
| Referral direction | Mostly outbound to specialists | Two-way with home-health agencies and discharge planners |
| Billing capture | Coded by back-office staff after the encounter | Coded at the point of care, before leaving the home |
What a house-call EHR has to handle
Five capabilities separate a genuine house-call EHR from a clinic system with a mobile view bolted on. Drive-time scheduling ranks appointment slots by the travel each adds, so the schedule reflects what a day can physically contain. Route-based day planning renders those visits as a sequence with distance and duration per leg, and turn-by-turn navigation between homes. In-home documentation supplies visit templates for the encounter types a home-based practice bills — Annual Wellness Visits, Face-to-Face encounters, POLST discussions, follow-ups — and captures signatures on-site. Dual-signature orders handle the common arrangement where a visiting clinician's order requires a supervising physician's co-signature. Two-way referrals let home-health agencies send patients in, not just receive them.
Privacy considerations specific to home visits
Home-based care creates a privacy problem clinic software never faces: the patient's home address becomes clinical data. Any system that routes a provider between homes is processing protected health information the moment it geocodes those addresses, which means the mapping layer falls inside the same HIPAA boundary as the chart. Practices evaluating a house-call EHR should ask specifically where geocoding and routing run. A vendor passing patient addresses to a consumer maps API is moving PHI to a processor that will not sign a Business Associate Agreement. Services such as Amazon Location Service are BAA-eligible and exist for exactly this reason.
How to evaluate a house-call EHR
Thirteen questions that separate purpose-built systems from clinic software with a mobile skin. A vendor who cannot answer the scheduling, signing and coding questions concretely is describing a clinic EHR.
- Does scheduling account for travel time, or is it a calendar with addresses attached?
- Can the provider see the whole day as one route, with distance and time per leg?
- Is documentation usable on a laptop in someone's living room, without a second monitor?
- Are visit templates available for the encounter types the practice actually bills?
- Can orders carry a dual signature when a supervising physician must co-sign?
- Do referrals flow in from home-health partners, not just out to specialists?
- Are billing codes captured during the visit rather than reconstructed days later?
- Does the system know the home-visit E&M families (99341–99345, 99347–99350) and suggest from them?
- Are frequency limits enforced, so a once-per-lifetime code cannot be billed twice?
- Can payer eligibility be checked before the drive, and claims submitted without a second portal?
- Can patients see an arrival estimate without installing an app?
- Is the vendor willing to sign a Business Associate Agreement (BAA)?
- Does geolocation run on BAA-eligible infrastructure, or on a consumer maps API?
How VizzitMD approaches it
VizzitMD is a HIPAA-compliant CRM and EHR built for house-call and mobile medical practices, designed around the constraints above rather than adapted from a clinic product. Scheduling ranks slots by drive time from the previous stop, and the day renders as one live route map with distance and time per leg. Visit templates cover 12 encounter types — including Annual Wellness Visits, Welcome to Medicare (IPPE), Home Health Certification and Recertification, Transitional Care Management and monthly Chronic Care Management — with ICD-10 diagnoses coded in the home and signatures captured on-site. Medication, DME, laboratory, diet and supply orders draw on an FDA National Drug Code catalog, require a supervising physician's co-signature for nurse practitioner and physician assistant encounters, and produce pharmacy-ready PDFs. On the revenue side, a suggestion engine proposes CPT and HCPCS codes from a rules table of 52 home-visit codes with frequency limits attached, payer eligibility is checked before the visit, and completed claims are submitted electronically. Geocoding and routing run on Amazon Location Service, and VizzitMD generates a filled California POLST form directly from visit data.
Read the full FAQ · Why we built it this way · Request a VizzitMD demo