Multi-location EHR configuration is less about how many sites a platform can list and more about which objects the software actually scopes to a location. Cerbo's help documentation describes a toggle model in which users pick a location at login and switch between sites afterward, with inventory, financial reports and outgoing form contact details following that selection [1]. AdvancedMD and eCareHealth describe centralized calendars, cross-location reporting and role-based access at the enterprise level [2][3]. The gap between those descriptions matters: a practice that assumes patient charts or portal behavior follow the location toggle will plan the wrong work. This article reads the primary documents for what they state, what they leave open, and how a configuration team can test the boundary before go-live.

What the Location Toggle Actually Controls

Cerbo's documentation is unusually specific about the mechanics. Locations are added under system settings with a name, website, email, address, phone, fax and EIN, and there is no stated cost for adding secondary locations, though functionality beyond the listed items is assessed case by case and may carry custom development charges [1]. Users select a location at the login screen and can switch by hovering over their initials and choosing another site [1]. That toggle is the unit of analysis for everything else in the article: the question for any object is whether it reads the toggle or ignores it.

The same document draws a firm line around what the toggle does not reach. User profiles are not assigned to a location, and all users can see any information their permission level allows regardless of site [1]. Patient charts are not assignable by location, and the vendor recommends tags to separate patient sets for reporting [1]. The patient portal can be styled to match only one website, all patients use the same portal URL, and portal functionality such as available tabs, scheduling access and secure messaging cannot be limited by location [1]. Logos on outgoing emails, faxes and other documents also do not differentiate by site [1].

Inventory and Financial Reporting as Location-Scoped Objects

Inventory is the clearest example of a location-scoped object in Cerbo's documentation. When multi-location configuration is enabled, the add-item window in the inventory manager includes a dropdown to designate an item's location, and the manager can be filtered to one site or both [1]. When prescribing inventory items, users can only dispense items assigned to the location they are currently logged into [1]. For a practice dispensing supplies or medications at more than one site, that constraint is a design decision rather than a preference: stock assigned to the wrong location becomes undispensable from the other site until it is corrected.

Financial reporting follows the same pattern. Cerbo states that common reports, including end-of-day, income, allocation, revenue per patient and the charges-added check, can be filtered by location [1]. The documentation also notes that the location of the adding user becomes the default in at least one context [1]. What the document does not describe is a consolidated roll-up view across all sites in a single report, so a group needing combined totals should confirm that behavior directly rather than infer it from the filter language.

Practical detail: build the exclusion list first

Before mapping any location in a new EHR, write two columns: objects the vendor documents as location-scoped, and objects the vendor documents as global. For Cerbo, the global column already contains user profiles, patient charts, portal styling, portal functionality and document logos, each stated explicitly [1]. The scoped column contains location contact details on outgoing faxes and forms, inventory assignment and dispensing, and filtered financial reports [1]. Any object that appears in neither column becomes a written question to the vendor, with the answer recorded alongside the configuration decision so the next site added inherits the same understanding.

How Enterprise Vendors Frame the Same Problem

AdvancedMD frames multi-site configuration around centralized management, describing a cloud platform hosted on AWS with uniform access and updates across sites, standardized clinical software spanning specialties, a centralized calendar covering all locations, and cross-location reporting and analytics [2]. The vendor also names interoperability between sites and among software systems as a starting point for enterprise practices [2]. These are vendor claims about capability rather than independent findings, and the page does not enumerate which configuration objects are location-specific versus global.

eCareHealth describes location-specific scheduling with each site holding its own calendar, providers and exam rooms, cross-location patient transfers, one accounts receivable workflow with per-location and rolled-up reporting, and role-based permissions spanning providers, billers, administrators and regional managers [3]. The vendor states that patient records are centralized while access is governed by role-based permissions, and that multi-state HIPAA boundaries are configurable [3]. It also states that groups typically roll out two to three locations per month with migration support [3]. Those statements are the vendor's own and are not verified here.

Where the Documentation Stops

The three vendor documents answer different questions. Cerbo's article is a feature inventory with explicit exclusions, which makes it the most useful for planning because a reader can see the boundary of the toggle [1]. AdvancedMD and eCareHealth describe outcomes and scale, including support for groups from two to fifty or more locations in one case and two to two hundred or more in another, but neither page lists the objects that remain global [2][3]. A practice comparing them cannot conclude from these pages alone that either platform scopes patient charts, portal appearance or document branding by site.

That asymmetry is the practical lesson. Absence of a stated exclusion is not evidence of location-level control, and absence of a stated inclusion is not evidence of its opposite. The Cerbo document shows why the distinction matters: a group that assumed portal styling or chart assignment followed the location toggle would discover the gap during rollout rather than during contract review. Buyers evaluating the other two platforms should request the equivalent exclusion list in writing.

A Suggested Evaluation Walkthrough

Consider a hypothetical two-site group preparing configuration, offered here as a suggestion rather than a report of testing. The team lists five objects it believes are location-scoped: clinic fax header, inventory stock, end-of-day report, patient chart assignment and portal appearance. Mapping those against Cerbo's documentation, the first three are supported, since contact information on outgoing faxes and forms defaults to the logged-in location and can be changed by toggling, inventory is assigned per location, and end-of-day reporting can be filtered by site [1]. The last two are explicitly excluded: charts are not assignable by location and portal styling is single-site [1].

The walkthrough produces a concrete configuration task list. Charts need a tagging convention agreed before migration so reporting can separate patient sets [1]. Portal appearance needs a single decision acceptable to both sites, because it cannot vary [1]. Fax and form headers need verification that each site's contact details are entered correctly, since the default follows the logged-in location [1]. Inventory needs an assignment rule for shared stock, because items assigned elsewhere cannot be dispensed from the current site [1]. None of this requires new software; it requires reading the exclusion list before the build.

Technical Readiness Beyond the Toggle

Location configuration sits inside a wider readiness problem that public-sector guidance treats at the facility level. The Indian Health Service readiness guide asks organizations to inventory third-party interfaces with system and vendor name, interface type such as HL7, FHIR or DICOM, ports, protocols and direction of data flow, and to inventory devices with model number, firmware version, connection type and physical location in the facility [4]. It also directs sites to test wireless connectivity at various facility locations using devices meant for EHR functions, noting signal strength, latency and packet loss [4].

The SAFER System Configuration guide, published by the Office of the National Coordinator for Health IT, states that EHRs are profoundly influenced by their configuration and that a multi-disciplinary configuration team should include practicing clinicians so technical components align with clinical workflows [5]. It adds that beyond initial configuration, a continuous and reliable review and maintenance process must be developed and followed [5]. For a multi-site group, that maintenance process is where location drift appears: a new site added without its fax details, inventory or report filters configured will behave inconsistently from day one.

What the Evidence Cannot Establish

Nothing in these documents supports a claim about which platform performs better across locations, and no source here reports independent testing, customer outcomes or comparative pricing. The Cerbo article is a help-center page modified in June 2025 and describes one product's behavior at that time [1]. The AdvancedMD and eCareHealth pages are marketing descriptions of capability [2][3]. The IHS and SAFER documents address readiness and configuration practice generally, not any named commercial product [4][5].

A reader should also treat scale figures cautiously. eCareHealth's statement that it supports groups from two to two hundred or more locations, and its separate statement that it is designed for groups operating two to fifty or more, are vendor claims that appear on the same page without further definition [3]. AdvancedMD's description of centralized calendars and cross-location analytics does not specify how conflicts between site schedules are resolved [2]. These are open questions for a structured demo, not settled facts.