Branch Operations
Branch operations refers to running additional home health locations that serve a portion of the parent agency's service area under the parent's Medicare certification and provider number. A branch shares administration, supervision, and services with the parent rather than operating independently. Branches are the standard way to extend geographic reach without certifying a new agency.
How branches differ from a new provider number
A branch is not a separate Medicare provider. It operates under the parent agency's CMS Certification Number, survey history, and Conditions of Participation compliance, and it must be sufficiently close to share administration, supervision, and services with the parent on a daily basis. State definitions of 'sufficiently close' vary, and states approve branch locations through the licensure and certification process. A separately certified agency, by contrast, needs its own provider enrollment, initial survey, and often triggers the 36-month rule considerations on any later sale. Operators weighing expansion typically compare branch approval timelines (often months) against new-agency certification timelines (often a year or more, plus enrollment moratoria history in some markets).
Why branch structure matters financially
Because branches bill under the parent's provider number, their outcomes, OASIS data, and claims roll up into one set of Star Ratings, HHVBP performance scores, and audit exposure. A struggling branch dilutes the whole agency's Care Compare profile, and a compliance failure at a branch is a compliance failure of the certified agency. On the upside, branches share back-office functions: intake, QA review, billing, and scheduling can be centralized, which lowers cost per visit relative to running a standalone entity in each market.
What good branch operations look like
High-performing multi-site agencies standardize the things surveyors and payers see while localizing the things referral sources see:
- One clinical policy set, QA process, and documentation standard across all locations
- Centralized intake, eligibility verification, and billing
- Local clinical managers who own staffing, referral relationships, and case conferences
- Branch-level dashboards for census, SOC timeliness, LUPA rate, and documentation completion
- A defined supervision structure that meets state branch requirements
Common pitfalls
The most common failure mode is drift: each branch develops its own documentation habits, QA shortcuts, and scheduling workarounds, and the agency only discovers the variance during a survey or ADR. The second is stretching the 'sufficiently close' standard until a state surveyor disagrees, which can force an unplanned certification of the location as a separate agency. The third is opening a branch on referral optimism without staffing depth; a branch that cannot admit within 24 to 48 hours trains local discharge planners to refer elsewhere.
Frequently asked questions
Does a branch need its own Medicare survey?
Branches are inspected as part of the parent agency's survey process rather than independently certified. The parent's survey covers branch compliance, and state agencies approve branch locations before they open. A branch that no longer meets the state's criteria for shared supervision can be required to seek its own certification.
Do branch outcomes report separately on Care Compare?
No. Quality measures, Star Ratings, and HHVBP performance aggregate at the CMS Certification Number level, so all branches report as one agency. This is why multi-branch operators watch branch-level internal metrics closely; public reporting will not isolate a weak location for them.
When does it make sense to open a branch versus acquire an agency?
A branch fits when the target market is contiguous to your service area and your constraint is geography, not certification. Acquisition fits when you need a provider number in a non-contiguous market, a certificate-of-need state, or a market with enrollment restrictions. Model both against the 36-month rule and your management bandwidth before committing.