ERP for healthcare: finance and supply beside the EHR
An ERP for healthcare runs finance, purchasing, inventory, and HR beside the electronic health record, and it leaves the chart, clinical orders, and claims coding in the EHR.
An ERP for healthcare runs finance, purchasing, inventory, and HR beside the electronic health record, and it leaves the chart, clinical orders, and claims coding in the EHR. For a clinic group, medical supplier, or device maker of about 30 to 100 staff, Business Central or Odoo is a realistic shortlist. As of October 2026, Business Central Essentials is USD 80 per user per month in the United States on a yearly commitment, and CAD 108.50 in Canada plus tax. ERP Research's analyst range for a Dynamics 365 healthcare deployment is USD 150,000 to more than USD 1,000,000 over 6 to 14 months.
A hospital suite aimed at tens of thousands of users is a different purchase. This page prices the mid-market license, separates it from implementation, and says what the ERP should own for two readers: a clinic or healthcare administrator, and a surgical-supply or device manufacturer.
What the ERP owns when the EHR already holds the chart
Clarity Ventures describes the split this way: "The EHR holds the chart; the ERP holds everything that keeps it supplied." The same guide names Epic, Cerner, and Meditech as the systems that hold the clinical record, and it defines healthcare ERP as the system of record for purchasing, supply chain, finance, HR, payroll, and materials management. Ranking those clinical products as ERP options mixes two budgets and two vendors.
For a clinic group, the ERP should own the general ledger, payables, purchasing, stock, and a payroll import. Business Central finance covers a general ledger and chart of accounts, dimensions, multi-currency, deferrals, item charges, recurring revenue, receivables and payables, bank reconciliation, intercompany transactions, consolidation across companies, and cost accounting. Salary transactions can be imported from a payroll provider. That is the administrative close. It is not a clinical scheduler, and it is not the coding workflow that turns a visit into a claim.
The handoff to ask a bidder to draw is short. Charges, payments, and denial write-offs need a posting path into the ledger. Patient demographics and the designated record set stay in the EHR unless you have a written reason to copy them. If the ERP never stores clinical notes, the privacy scope of the project stays narrower. If purchasing, inventory, or HR will store protected health information, the project has to say so before anyone prices security work.
Two operational facts decide whether a generic small-business ledger is enough. The same guide says "Most providers buy through a group purchasing organisation. The ERP has to hold contract pricing, tiers and rebates, and reconcile them against what was actually invoiced." It also says "The item master is the artifact every implementation underestimates and the one that decides whether the rest works." A 40-person clinic with one entity, one stockroom, and no contract-price reconciliation can often stay on a smaller accounting system. A group that buys on GPO tiers, or a supplier whose item master carries units of measure, lots, and vendor contracts, is already in ERP work.
Clinic groups and device makers need different first phases
Business Central and Odoo can both hold finance and inventory. The first phase still depends on whether you close several entities or build kits.
Track A is a clinic group or healthcare administrator with about 30 to 100 staff. The painful work is a multi-entity close, purchasing, contract price versus invoice, supplies, and a payroll file from the payroll provider. Business Central can consolidate companies and post intercompany transactions, and dimensions plus cost accounting are how you split cost by department or service line. You do not need a manufacturing license for that. You do need an item master the buyers will keep current, and a rule for which vendor contract price is allowed on a purchase order.
If the clinic is a charity or a research shop, the fund and project questions look like the ones in our guide to ERP for nonprofits and associations. Ask the bidder to show dimensions or projects on your own chart of accounts. Do not assume a healthcare label includes a grant ledger.
Track B is a medical supplier or a surgical-supplies manufacturer. The painful work is lot and serial identity, expiration, a bill of materials, and a quote that can become a production order. Distribution without manufacturing can start on inventory and purchasing. The moment you build kits, trays, or finished devices, the license and the phase change, because manufacturing setup is a different scope from buying and reselling.
Infor's healthcare ERP page describes financials, supply chain with group-purchasing integrations and recall automation, human capital and credential tracking, and a connection between ERP and EHR. It publishes no price there. It also tells a customer story of CHRISTUS Health on 35,000 users, with a claim of more than 5,000 hours saved a year. That is Infor's figure, and it describes a health system. A 60-person clinic or a kit manufacturer should not budget as if that story were their project.
What to ask about HIPAA, a BAA, and Canadian privacy law
Treat compliance as questions in the statement of work. Do not treat a logo, a partner tier, or a signed template as the control.
In the United States, Microsoft's HIPAA and HITECH page says HIPAA applies to covered entities (health care providers, health plans, and health care clearinghouses) and to business associates that handle protected health information. Dynamics 365 and Dynamics 365 U.S. Government are listed as in-scope services for Microsoft's business associate agreement. The same page answers its own question in one line: "Does having a Business Associate Agreement with Microsoft ensure my organization's compliance with HIPAA and the HITECH Act? No." Microsoft also says there is no HHS-approved certification that a business associate can use to demonstrate HIPAA compliance, and that a BAA does not by itself make the customer compliant.
Ask four things before you accept a security slide.
- Will this Business Central or Odoo environment store protected health information, or only purchase orders, invoices, item quantities, and payroll imports?
- If Dynamics 365 will store that information, who signs Microsoft's BAA, and which company in a multi-entity group is the covered entity or the business associate?
- Which records stay in the EHR so the ERP does not become the designated record set?
- What will the partner configure (roles, audit trail, retention, environments) versus what Microsoft's agreement covers?
Microsoft's compliance page points readers to Microsoft Cloud for Healthcare as an industry resource. That offering is a different product from Business Central financials. A demo of one is not a demo of the other.
We do not claim a HIPAA certification, and we will not tell you that a BAA closes your program. On a scoping call we will mark whether the first phase stores protected health information and which side of the EHR boundary each record sits on.
Canada is a different statute map. The Office of the Privacy Commissioner of Canada says PIPEDA sets rules for how private-sector organizations collect, use, and disclose personal information in commercial activities across Canada, and that it also covers employee information of federally regulated businesses. Alberta, British Columbia, and Quebec have private-sector laws deemed substantially similar. Ontario, New Brunswick, Nova Scotia, and Newfoundland and Labrador have substantially similar laws for personal health information. Personal information that crosses a provincial or national border in commercial activity is subject to PIPEDA. Municipalities, universities, schools, and hospitals are generally covered by provincial laws.
For an Ontario clinic, the practical question is whether the data stays inside the province under Ontario's health-information statute, or whether a vendor, a payroll bureau, or a shared service sends it across a border and into PIPEDA. Ask each bidder to name the hosting region and the subprocessors in the proposal. Do not accept a single line that says the product is compliant in Canada.
How a covered entity keeps 340B and non-340B stock auditable
340B is a US covered-entity inventory duty. A Canadian clinic and a device manufacturer sit outside that program.
The American Hospital Association's fact sheet, dated from its October 2025 material, says section 340B of the Public Health Service Act requires pharmaceutical manufacturers that participate in Medicaid to sell outpatient drugs at discounted prices to organizations that care for many uninsured and low-income patients. Named eligible hospital types include critical access hospitals, sole community hospitals, rural referral centers, and public and nonprofit disproportionate-share hospitals. Participating hospitals must recertify eligibility annually, take part in HRSA and manufacturer audits, and keep auditable records. The sheet states: "Hospitals must maintain auditable records and inventories of all 340B and non-340B prescription drugs."
The spreadsheet failure mode is specific. Someone keeps a second workbook of which NDCs were purchased at the 340B price, which location they sit in, and which issues were eligible. The workbook drifts from the purchase order and from the shelf. An audit then asks for records the buyer cannot regenerate from the system that created the receipt.
Business Central and Odoo do not ship a 340B module you can turn on. What they can do is track items by location, lot, and quantity so two inventories are not a side file. The design you should make a bidder show on your items is:
- A separate location, bin, or item status for 340B stock and for non-340B stock, so a receipt cannot land in the wrong bucket without a counted transaction.
- Purchase prices that follow the contract, with the invoice matched back to that receipt.
- An issue transaction that names the location the drug left, so eligibility is not retyped at month end.
- A period lock so an auditor can see the inventory as of the recertification date, not a spreadsheet exported and edited later.
If your team cannot walk that chain in a conference room on ten real NDCs, the ERP project has not replaced the spreadsheet. It has added a third list.
Quoting a surgical kit, then building and tracing it
Finished device manufacturers have a quality rule that changed in 2026. FDA says the Quality Management System Regulation became effective on 2 February 2026. It amends device CGMP requirements in 21 CFR Part 820 and incorporates ISO 13485:2016 by reference. It applies to finished device manufacturers who intend to commercially distribute medical devices. Manufacturers of accessories that FDA treats as finished devices are also subject to it.
An ERP can hold bills of materials, lots, serials, and quality steps recorded against those movements. It does not replace a quality management system, and it does not stand in for an FDA inspection. Budget the quality system as its own line if you do not already have one that meets the regulation.
The quoting mechanism Microsoft documents for a manufactured kit is a production order. Production orders convert purchased materials into manufactured items using items, production BOMs, routings, and work or machine centers. A simulated production order can be used for quotes and costing, and it does not affect MPS or MRP. Sales orders can create production orders. For a kit or tray, the quote path a bidder should demonstrate is: configured sales quote, simulated order for cost, then a real production order when the customer accepts. Premium is the license that adds manufacturing.
Traceability is already in the distribution footprint. Microsoft's item tracking design says item tracking covers serial and lot numbers and where items are received, stored, and sold, and that monitoring transaction flow is a legal requirement in medical and chemical supply. Put a recalled lot on the table during selection and ask for every receipt, consumption, and shipment in the system. A report that only shows current on-hand quantity fails that test.
Odoo documents a similar chain. Odoo 19 serial numbers identify a single unit and support expiration dates, location, recalls, and traceability from receipt through manufacturing and delivery. Lots are the other tracking method. Traceability must be turned on, and products can be set to track by unique serial number. Odoo Inventory lists serial numbers, lots, GS1 and barcodes, min-max and make-to-order replenishment, multi-warehouse and multi-company stock, and FIFO, average, LIFO, and standard valuation, and it links to Purchase, Manufacturing, Accounting, and Quality. One marketing line on that page says "Odoo Inventory replaced our legacy spreadsheets which were unable to keep up with our growing business." Treat that as Odoo's own line, then still run the recall test on your items.
Manufacturing and multi-company also change the Odoo plan. On Odoo's pricing card as of October 2026, Custom is the plan that adds multi-company, Odoo.sh or on-premise, Studio, and external API. Standard is Odoo Online and all apps. A device maker with one company can start the license conversation on Standard and still confirm that Manufacturing, Quality, and serial tracking are in the estimate. A group with more than one company should price Custom, and should price Odoo.sh hosting as extra because the pricing page says hosting is not included.
What the licenses cost before anyone quotes a project
List price and project price answer different questions. As of October 2026, Microsoft says its prices are informational and may differ by currency, country, and region. A 30-day Business Central trial is free. The figures below are yearly-commitment list prices.
- Essentials (United States: USD 80.00 per user per month · Canada: CAD 108.50 per user per month, plus applicable tax)
- Premium (Essentials plus service management and manufacturing) (United States: USD 110.00 per user per month · Canada: CAD 149.20 per user per month, plus applicable tax)
- Team Members (United States: USD 8.00 per user per month · Canada: CAD 10.90 per user per month, plus applicable tax)
Sources: US Business Central pricing and Canada Business Central pricing, seen October 2026.
Assume a US clinic group buys 15 Essentials users and no manufacturing. 15 times USD 80 is USD 1,200 per month, or USD 14,400 per year, before Team Members, implementation, integrations, and any added apps. The same 15 seats in Canada are 15 times CAD 108.50, which is CAD 1,627.50 per month and CAD 19,530 per year, plus applicable tax. Ten people who only approve documents, priced as Team Members, add 10 times USD 8, or USD 80 per month, in the United States, and 10 times CAD 10.90, or CAD 109 per month, in Canada before tax. Those approver seats are a separate count from the 15 full users.
Assume a device maker needs manufacturing and prices 12 Premium users. 12 times USD 110 is USD 1,320 per month, or USD 15,840 per year, on the US list. In Canada, 12 times CAD 149.20 is CAD 1,790.40 per month, or CAD 21,484.80 per year, plus tax. Premium is the tier to quote once kits are built in the system. Essentials at USD 80 is the tier to quote for a distributor that buys and sells and does not run production orders. Ask Microsoft, on your tenant, to confirm how Team Members and full users combine. Do not inherit a blended rate from a slide.
Odoo's public card, with yearly and monthly controls rendered together, does not collapse to one number. As of October 2026, the pricing page prints Standard at $24.90 and $31.10 per user per month and also US$31.10 and US$38.90. It prints Custom at $49.00 and $61.10 and also US$61.00 and US$76.20. A footnote says the discount is valid for 12 months for the initial users ordered. A light user is listed at US$8.90 and is quoted with an advisor for limited employee and barcode-operator tasks. One app is free for unlimited users on Odoo Online, and the inventory marketing page describes the first inventory app as free with unlimited users.
Assume 12 full Custom users because you have more than one company. The four printed Custom figures imply monthly license totals of 12 times 49.00 (USD 588), 12 times 61.10 (USD 733.20), 12 times 61.00 (USD 732), and 12 times 76.20 (USD 914.40). Use the pair the order form selects, remember the lower promotional figure is time-limited for the initial users, and add hosting if you use Odoo.sh. Multiplying only the smallest number for a five-year budget understates the renewal.
Odoo publishes implementation packs separately from licenses. Success Packs for new customers are Starter US$493 (4 hours), Basic US$3,060 (25 hours), Standard US$5,950 (50 hours), Custom US$10,625 (100 hours), and Pro US$21,250 (200 hours). A later pack is billed at the returning rate printed beside each hour block: Basic US$3,600, Standard US$7,000, Custom US$12,500, and Pro US$25,000. The lower new-customer figures are a one-time opening purchase. Custom-code maintenance is extra on the Custom pack. Odoo says companies under 50 employees usually buy these packs from Odoo, companies over 50 employees usually use a partner, and companies over 250 employees should contact Odoo. The estimator says 80 percent of projects in that scope go to production in 200 hours or less, and it shows a separate project-cost line of 4,500 euros. Those packs are Odoo's published services for the scopes on that page. They are not a quote for a clinic group with an EHR interface, a GPO price list, or a device quality file. A 70-person organization is already in the band where Odoo says to use a partner, so the Pro pack's 200 hours is a ceiling on a price list, not your project plan.
How published budgets compare with that license math
SoftwareConnect's healthcare ERP roundup says annual cost is often USD 20,000 to USD 75,000 for a small clinic of one or two locations, USD 75,000 to USD 150,000 for a mid-sized or regional provider, USD 150,000 to USD 300,000 or more for a single hospital, and USD 300,000 or more for a multi-facility system. It says implementation is often the largest share and that maintenance is extra. It also lists a Dynamics 365 starting price of USD 80 per user per month, which matches Microsoft's US Essentials list as of October 2026.
Read those bands with the license math in front of you. The USD 14,400 Essentials subscription for 15 users sits below the USD 20,000 floor. The USD 20,000 to USD 75,000 small-clinic range is a reviewer's annual total, and the subscription still does not describe the 15-user project. A 30 to 100 person group with more than one entity is closer to the mid-sized band of USD 75,000 to USD 150,000 a year only as a conversation starter. SoftwareConnect is a review range, not a fixed-fee offer.
ERP Research, updated 27 August 2026, is the analyst page that splits hospitals, clinics, labs, pharma, biotech, and medical devices. For Dynamics 365 in healthcare and life sciences it states a typical total cost of ownership of USD 150,000 to more than USD 1,000,000 and a go-live of 6 to 14 months. It also says lot and serial tracking with expiration dates is part of the distribution footprint, while clinical item masters and regulated quality usually come from partners. The subscription figure to use beside that total is Microsoft's Essentials list of USD 80 per user per month.
The same ERP Research page compiles other healthcare bands: Sage Intacct USD 50,000 to USD 200,000 and 3 to 6 months; NetSuite USD 100,000 to USD 500,000 and 4 to 9 months; Acumatica USD 75,000 to USD 350,000 and 4 to 8 months; SAP S/4HANA Public Cloud USD 150,000 to USD 600,000 and 3 to 6 months; the large hospital-suite rows at USD 300,000 to more than USD 2,000,000 with go-lives inside a 6 to 18 month spread; and a cloud ERP row at USD 400,000 to more than USD 3,000,000 and 9 to 18 months. It also shows a page-level implementation range of USD 50,000 to more than USD 750,000. These are analyst compilations. The hospital-suite rows open at USD 300,000 and USD 400,000, with go-lives inside 6 to 18 months. A clinic group should price a finance, purchasing, and item-master phase against those floors, and should leave the hospital-suite bands for a health system.
For a 30 to 100 person buyer, the useful comparison is license times users, plus a phase you can staff, plus interfaces. A first phase that is only finance, purchasing, and a clean item master should be priced as that phase. Adding 340B inventory design, EHR posting, or device quality records increases the project. It does not change the Essentials list price of USD 80.
How to shortlist Business Central or Odoo
Start from the published list price for the modules you will use (Essentials or Standard for buy-and-resell, Premium or Custom when you manufacture or run more than one company), then test the partner on your data. Our ERP implementation work is scoped that way for organizations in this size band: the clinical system stays, and the first phase is the back office you can run without a side spreadsheet. Platform pages for Business Central and Odoo describe how those rollouts are phased. If you are still comparing products below a healthcare suite, start with the best ERP for small business criteria, then add the healthcare tests on this page.
- One or a few entities, buy and resell supplies, no production (Where to start the shortlist: Business Central Essentials, or Odoo Standard if you are on Odoo Online and do not need multi-company · What the bidder must show: Item master, contract price versus invoice, lot or serial if you ship medical supply)
- Several companies that consolidate (Where to start the shortlist: Business Central companies and consolidation, or Odoo Custom because multi-company is on that plan · What the bidder must show: An intercompany invoice and a consolidated trial balance on your entities)
- Kits, trays, or finished devices (Where to start the shortlist: Business Central Premium, because manufacturing is the Premium addition · What the bidder must show: A simulated production order for the quote, then a real order, with lot or serial through receipt, production, and shipment)
- US covered entity with 340B outpatient drugs (Where to start the shortlist: Either platform, with inventory design, not a 340B module · What the bidder must show: Two auditable inventories and a receipt-to-issue chain on real NDCs)
- Under 50 employees and a small Odoo scope (Where to start the shortlist: A scoped finance and inventory phase · What the bidder must show: A written list of what 4, 25, 50, 100, or 200 hours includes, set against the published pack ceiling of US$493 to US$21,250, and what the EHR and quality work excludes)
- Over 50 employees (Where to start the shortlist: A partner-led project, which is what Odoo states for that size · What the bidder must show: Named consultants, hours by phase, references, and who owns the configuration and code)
The selection tests that matter are people, hours, references, a phase plan, and code ownership. A partner badge does not answer them. Before you sit through a long vendor demo, use this sequence, which is the same discipline as how to choose an ERP implementation partner.
- Write the phase-one workflows on one page: multi-entity close, GPO or contract pricing, 340B versus non-340B stock if it applies, and quote-to-production if you build kits.
- Mark every record that would contain protected health information, and mark everything that stays in the EHR.
- Ask for a fixed list of environments, roles, and the BAA signer when the platform is Dynamics 365. Ask for hosting region and subprocessors in Canada.
- Price licenses from the vendor pages above, and price services as a separate line with hours. Refuse a single blended monthly number.
- Require a data sample: 50 items, 20 vendor contracts or price tiers, and, for a device maker, one BOM with lots. The item master will expose a weak plan faster than a feature checklist.
- Name who configures the system, who can change it after go-live, and whether you receive the customizations.
Bring the fit-check answers, a sample item list, and last quarter's contract-versus-invoice mismatches. That is enough to tell whether phase one is a clinic close, a 340B inventory design, or a kit quote that has to survive a lot recall.
How Flectic can help
Flectic implements ERP on Odoo or Dynamics 365 for companies of 20 to 100 people whose finance, stock and projects run on spreadsheets and disconnected tools. Our ERP implementation service puts those records on one ledger, and each phase has a defined scope and price before it starts. Flectic sends a written proposal with a fixed price for each phase before work starts. Book a free discovery call to check whether a Flectic first phase fits your organization.
Sources
- Dynamics 365 Business Central pricing (United States), Microsoft, October 2026
- Dynamics 365 Business Central pricing (Canada), Microsoft, October 2026
- Financial management - Business Central, Microsoft Learn, October 2026
- Design details - Item tracking - Business Central, Microsoft Learn, October 2026
- About production orders - Business Central, Microsoft Learn, October 2026
- HIPAA and HITECH Act - Microsoft Compliance, Microsoft Learn, October 2026
- PIPEDA requirements in brief, Office of the Privacy Commissioner of Canada, October 2026
- Fact Sheet: The 340B Drug Pricing Program, American Hospital Association, November 2025
- Quality Management System Regulation, U.S. FDA, October 2026
- Odoo Pricing, Odoo, October 2026
- Odoo Success Packs, Odoo, October 2026
- Inventory, Odoo, October 2026
- Serial numbers, Odoo 19.0, Odoo, October 2026
- Healthcare ERP Systems: 12 Options and How to Choose, Clarity Ventures, September 2026
- Healthcare & Life Sciences ERP Market Guide, ERP Research, August 2026
- Best Healthcare ERP Software: 2026 Pricing and Reviews, SoftwareConnect, October 2026
- Healthcare ERP Software System, Infor, October 2026
Frequently asked questions
How do ERP systems work in healthcare?
The ERP posts the administrative side of the organization: purchasing, inventory movements, payables, payroll imports, and the general ledger. The EHR keeps the chart, clinical orders, and the coding path that creates a claim. The two meet where charges, payments, and write-offs need to land in the books, and where supplies consumed in care must match what was purchased.
Can a healthcare ERP integrate with existing clinical systems?
Yes, if you define the messages before you pick modules. A practical interface posts summarized or line-level financial results into the ledger and leaves the chart in Epic, Cerner, Meditech, or your practice system. Ask the bidder to show the posting, the reconciliation, and what happens when a denial changes the receivable. A slide that only says the products can integrate is not a design.
Does a Business Associate Agreement with Microsoft make our organization HIPAA compliant?
No. Microsoft states that a business associate agreement does not by itself make the customer compliant, and that there is no HHS-approved certification a business associate can use to demonstrate HIPAA compliance. Dynamics 365 is listed as an in-scope service for Microsoft's agreement. Your program still has to decide whether the ERP stores protected health information, who signs the agreement, and which safeguards you operate.
Which personal-health-information law applies in Ontario versus PIPEDA when data stays in the province or crosses a border?
The Privacy Commissioner of Canada says Ontario has substantially similar legislation for personal health information, and that hospitals are generally covered by provincial law. PIPEDA applies to private-sector commercial handling of personal information across Canada, and personal information that crosses a provincial or national border in commercial activity is subject to PIPEDA. If a host, payroll bureau, or shared service sends Ontario health information outside the province, ask counsel which statute applies. Name the hosting region in the proposal.
How do we keep auditable 340B and non-340B drug inventories without living in spreadsheets?
Participating hospitals must keep auditable records and inventories of 340B and non-340B drugs, recertify each year, and face HRSA and manufacturer audits. Put the two stocks in separate locations or statuses inside the inventory system, match each receipt to the contract price, and issue from the location that received the drug. Neither Business Central nor Odoo ships a 340B module. If a bidder cannot replay ten real NDCs from receipt to issue, the spreadsheet is still the system of record.
For a surgical-supply or device manufacturer, can Business Central or Odoo quote a configured kit and then build it from a BOM with lot and serial traceability?
Business Central can cost a quote on a simulated production order that does not affect planning, then open a real production order from the sale once the customer accepts. The order uses items, a production BOM, routings, and work or machine centers. Premium is the license that includes manufacturing. Odoo can track a serial or a lot from receipt through manufacturing and delivery when traceability is turned on. From February 2026, finished device manufacturers commercially distributing devices also fall under FDA's Quality Management System Regulation, which an inventory ERP does not replace.
Should we buy Essentials or Premium, and Odoo Standard or Custom, once we have more than one company and need manufacturing?
On Business Central, Essentials is the US list price of USD 80 per user per month for finance and distribution, and Premium at USD 110 adds service management and manufacturing. Price Premium when you build kits or devices. Canada list prices are CAD 108.50 and CAD 149.20 plus tax. On Odoo, multi-company, Studio, external API, and Odoo.sh or on-premise sit on the Custom plan, whose card prints more than one monthly figure, while Standard is Odoo Online and all apps. Companies over 50 employees are in the band where Odoo says to use a partner, so a Success Pack hour cap is not the implementation plan.
What is a sensible way to read a healthcare ERP total cost when the license is only about USD 14,400 a year?
Fifteen US Essentials users at USD 80 each are USD 1,200 a month, or USD 14,400 a year, before approver seats and services. Review sites often quote USD 20,000 to USD 75,000 a year for a one or two location clinic and say implementation is the larger share. Analyst totals for a Dynamics healthcare deployment are often USD 150,000 to more than USD 1,000,000 over 6 to 14 months. Use the license math as the subscription, then ask for hours by phase so a hospital-suite band is not applied to a 40-person back office.