EHR software cost has no single reliable market average. The most defensible public figures come from ONC-cited studies estimating $15,000 to $70,000 per provider for purchase and installation, and from vendor pricing pages listing ambulatory subscriptions between $199 and $599 per provider per month [1][8]. Those numbers measure different things: one captures implementation and capital outlay, the other a recurring license. A practice evaluating cost therefore needs to separate the software subscription from hardware, training, interfaces, and ongoing maintenance. The HealthIT.gov five-component framework and the Michigan Center for Effective IT Adoption five-year TCO table remain the clearest starting points for building a defensible budget [1]. Vendor cost disclosures under the ONC Certification Program add a second layer: they identify where fees exist without publishing a detailed fee schedule [4][6].
The Two Deployment Models Produce Different Cost Profiles
HealthIT.gov distinguishes on-site deployment from web-based SaaS deployment. On-site systems typically require ongoing costs to support and manage data servers, while SaaS systems usually require a fixed monthly subscription [1]. The Michigan Center for Effective IT Adoption table, based on Regional Extension Center field experience, estimates an average $33,000 upfront cost and $4,000 yearly cost for in-office deployment, producing a $48,000 five-year TCO. The SaaS estimate is $26,000 upfront and $8,000 yearly, producing a $58,000 five-year TCO [1]. The lower upfront SaaS figure does not automatically mean lower total cost.
The AMA STEPS Forward module repeats the same ONC range and the same Michigan Center figures, framing them as averages for self-hosted and cloud-hosted servers [5]. Cloud-based EHRs can reduce upfront hardware and software costs and ongoing maintenance costs, and they allow an organization to start small and increase IT allocations as needed [2]. But the Health IT Playbook also warns that organizations should establish legal contracts, service level agreements, and ongoing monitoring with a cloud vendor [2]. The deployment decision is therefore a cash-flow and control decision, not a simple price comparison.
Five Cost Components Shape the Real Budget
HealthIT.gov identifies five main components of EHR implementation for ambulatory primary care settings: hardware, software, implementation assistance, training, and ongoing network fees and maintenance [1]. Hardware may include database servers, desktop computers, tablets or laptops, printers, and scanners [1]. Training must cover physicians, nurses, and office staff before and during implementation, including how the EHR will create new workflows [1]. Ongoing costs can include hardware and software license maintenance agreements, staff education, telecom fees, IT support fees, and new hires such as IT operations staff, clinical data analysts, or application analysts [1].
The AMA module adds physician and staff time and materials needed to learn new system features, plus the expense of an implementation support provider [5]. A vendor's published subscription price does not necessarily include these items. PrognoCIS, for example, states that setup and training carry a cost discussed at the time of purchase, and that data migration cost varies by volume and type of data [7]. EPCS verification and clearinghouse fees are the customer's responsibility and not part of the EMR price [7]. A budget built only from the monthly subscription will undercount the first-year cash requirement.
Build a Five-Year TCO Worksheet Before Requesting Quotes
Start with the Michigan Center table as a reference point: $33,000 upfront and $4,000 yearly for in-office, or $26,000 upfront and $8,000 yearly for SaaS [1]. Then replace those averages with vendor-specific written answers for hardware, software, implementation assistance, training, and ongoing network fees and maintenance [1]. Add the AMA items that vendors rarely quote: physician and staff time for training and workflow redesign, and any implementation support provider expense [5]. Request the vendor's ONC cost disclosure and ask for a written explanation of every fee category it lists, since disclosures notify rather than price [4][6]. Finally, have an attorney review exit clauses and regulatory update cost language before signing [5][6].
Published Ambulatory Prices Are Specific, Not Universal
Nirmitee.io's October 2026 guide reports that the eClinicalWorks pricing page lists $499 per provider per month for the EHR and $599 with practice management, with no start-up costs, free data migration, and initial training for practices of 1 to 9 providers, plus airfare billed separately. The Practice Fusion pricing page starts at $199 per provider per month with an annual commitment [8]. PrognoCIS publishes a starting price of $280 per provider per month, with setup and training costs discussed at purchase [7]. These are vendor-published list prices, not negotiated contract values.
The same guide cautions that hospital figures cover different scopes and years and should be compared as scale, not as prices [8]. A measured study by Fleming et al. in Health Affairs found an average five-physician practice spent about $162,000 to implement an EHR, plus $85,500 in first-year maintenance, in 2011 dollars [8]. That study predates current subscription pricing and certification requirements, so it cannot be treated as a current benchmark. The defensible conclusion is that small-practice software prices are public while hospital system prices are quoted, not published [8].
Certification Cost Disclosures Identify Fees Without Publishing Schedules
ONC certification transparency requirements require vendors to publicly disclose certain information about limitations and types of costs [6]. The Sightview EHR 5.0 cost disclosure states explicitly that the fees described are intended to provide notification of the existence of a fee where one exists and not a detailed fee schedule [4]. Sightview notes that establishing a connection to each third-party HISP with which it has no existing relationship may be charged, and that the cost of establishing connections can be substantial and may exceed the annual licensing and subscription fee in some cases [4]. Its standardized Patient API requires Blue Button Pro, and predictive decision support interventions require a third-party DSI vendor [4].
Oracle Health's certified cost information similarly identifies required costs for specific certified capabilities. For example, patient health information capture requires software licenses for PowerChart or PowerChart Ambulatory or PowerChart ASP and Advanced Care Documentation, while the Messaging REST service is embedded with Oracle Health Millennium at no additional cost [3]. Configuration of interfaces, exports, or outputs beyond certification-tested specifications is considered outside the CommunityWorks, Ambulatory ASP, and Continuum offerings and may be subject to a fee [3]. These disclosures help a buyer ask targeted questions but do not replace a written quote.
A Hypothetical Evaluation for a Three-Provider Specialty Practice
Consider a three-provider ophthalmology practice evaluating Sightview EHR 5.0 against a general ambulatory SaaS product. The practice would first request written confirmation of the monthly subscription, setup, training, and data migration fees, since Sightview's disclosure does not publish a fee schedule [4]. It would then ask which certified capabilities require additional modules: the standardized Patient API requires Blue Button Pro, and predictive decision support requires a third-party DSI vendor [4]. If the practice sends Direct messages to referring optometrists, it should ask whether its existing HISP relationships avoid new connection charges [4].
For the general SaaS alternative, the practice would compare the published per-provider subscription against the same five components. HealthIT.gov's framework directs the practice to estimate hardware, software, implementation assistance, training, and ongoing network fees and maintenance [1]. The AMA module adds the cost of physician and staff time for learning new workflows [5]. This hypothetical comparison does not produce a winner from the source documents; it produces a list of written questions that must be answered before any contract is signed. The practice should also confirm whether regulatory updates requiring significant new features may trigger additional charges [6].
Sources & references
- How much is this going to cost me? | HealthIT.gov · www.healthit.gov
- Electronic Health Records - Health IT Playbook · healthit.gov
- Oracle Health Certified Health IT Costs Information · www.oracle.com
- Cost disclosure · www.sightview.com
- EHR Software Selection and Purchase: Understand Practice Needs and Evaluate Readiness for Selection and Purchase | Electronic Health Records | AMA STEPS Forward | AMA Ed Hub · edhub.ama-assn.org
- EHR Contracts Untangled · Office of the National Coordinator for Health Information Technology
- EHR Software Cost $280 | EHR Pricing & Plans Explained · prognocis.com
- EHR Implementation Cost 2026: Real Budgets and Prices · nirmitee.io