Build vs buy: when a healthcare organization should develop its own software
How to decide between writing a system in house, buying a vendor's product, or combining the two, and the mistakes that make the decision expensive.
What are the options besides build and buy?
- Build: the organization's own developers (or a contractor working to its design) write the software, and the organization owns and supports it.
- Buy (commercial off-the-shelf, COTS): a vendor's product, installed on the organization's servers or hosted by the vendor, configured to local needs.
- Subscribe (software as a service, SaaS): the vendor runs the software in its cloud and charges a subscription; the organization configures it but manages no servers.
- Hybrid: buy the core and build around it, for example an app or a report on top of the vendor's APIs, or an open-source product adapted and supported in house.
In project management this is a make-or-buy analysis: a decision made early, during planning, because it shapes the budget, the schedule and the procurement.
How do building and buying compare?
| Build | Buy | |
|---|---|---|
| Fit to the need | Exactly what is specified | What the product does; gaps are closed by configuration, workarounds or changed processes |
| Time to use | Long: design, develop, test | Shorter: select, configure, test, train |
| Cost up front | Development staff and time | Licence or subscription, implementation services |
| Cost over the life | All support, fixes, security updates and changes in regulation, by the organization | Maintenance or subscription fees; the vendor keeps the product current |
| Risk | Delivery risk, and dependence on the few people who know the code | Dependence on the vendor (its roadmap, prices, survival), lock-in |
| Control | Full control of features and timing | Features and timing set by the vendor's roadmap |
| Usually fits | A unique, strategic need with no product on the market | Common needs met by mature products: EHR, LIS, RIS/PACS, billing, ERP |
Which factors decide between building and buying?
- Fit: a gap analysis of the requirements against the products. If several mature products meet most of the needs, buying is hard to beat.
- Strategic value: software that gives the organization a real advantage, or supports a way of working that is its own, is a candidate for building; software for common processes is not.
- Capability: skilled developers, testers, security and support staff, not only for the project but for the whole life of the system.
- Time: a hard deadline usually favours buying.
- Regulation and certification: in the United States, CMS's Promoting Interoperability programs require certified EHR technology (ONC's Health IT Certification Program) for participation, and not meeting them brings Medicare payment reductions; a home-built system would have to be certified itself. Privacy, security and medical device rules apply either way.
- Interoperability: how well the option exchanges data with the systems around it, through standards such as HL7 v2 and FHIR.
- Vendor viability: the vendor's finances, customer base, roadmap and support record.
- Total cost of ownership over the system's expected life (below).
What goes into the total cost of ownership?
The total cost of ownership (TCO) is every cost of the option over its life, not only the purchase: licences or subscriptions, hardware and hosting, implementation and data conversion, interfaces, training, staff to run and support it, maintenance and upgrades, security, downtime procedures and, at the end, retirement and data migration. Building has no licence fee but carries all of the development, maintenance and support; buying has fees but shares the cost of keeping the product current with the vendor's other customers. Only a TCO over the same number of years compares the two fairly.
What is the difference between configuring and customizing a vendor product?
Configuration uses the settings, tables and tools the vendor provides (order sets, templates, rules, workflows): it is supported, and it survives upgrades. Customization changes the product's code or works around it in ways the vendor does not support: it may close a gap, but it makes every upgrade harder and costlier, and it can leave the organization on an old version. Heavily customizing a bought product often brings the costs of building without its control. The usual advice is to configure, to adapt local processes to the product where the product follows good practice, and to customize only where there is a strong reason.
How is a vendor product selected?
- Requirements agreed with the users, ranked (must have, should have, nice to have).
- Request for information (RFI): a broad question to the market, to learn which products exist and narrow the list.
- Request for proposal (RFP): the detailed requirements sent to the shortlisted vendors, who answer with a proposal and a price.
- Scripted demonstrations: each vendor shows the same real scenarios, written by the organization, so the products can be compared fairly.
- Reference checks and site visits with organizations of a similar size and type already using the product.
- Evaluation with a weighted scoring matrix, then contract negotiation: scope, service levels, support, data ownership, exit terms.
What do candidates get wrong?
- "Building is cheaper because there is no licence." Support, security updates and regulatory changes for the system's whole life usually cost more than the licence saved.
- Building for a common need that mature products already meet.
- Forgetting long-term support: having developers for the project is not having them for ten years.
- Treating customization as free. It raises the cost of every upgrade.
- Letting money already spent decide. What a failed in-house effort has cost is a sunk cost; only future costs and benefits count.
Summary for revision
- Buy for common needs met by mature products; build for a unique strategic need, with the skills to support it long term.
- Hybrid: buy the core, build around it through APIs.
- Decide on TCO over the system's life, not on the licence.
- Configure rather than customize: customizations make upgrades harder.
- Selection: requirements, RFI, RFP, scripted demos, references, scoring, contract.
Sources
- Project Management Institute, A Guide to the Project Management Body of Knowledge (PMBOK Guide): make-or-buy analysis and procurement management.
- Centers for Medicare & Medicaid Services (CMS), Promoting Interoperability Programs: the certified EHR technology requirement.
- Office of the National Coordinator for Health IT (ONC), Health IT Certification Program.
Related free practice questions
The site files this concept under the domain Management and Leadership.
Try exam-style questions
A 20-question trial exam with an explanation for every option and a score per domain, drawn from 40 free questions. No payment method needed.
Start the trial examQuestions about the exam: CPHIMS guide · What is CPHIMS? · Exam cost · Eligibility · Passing score · Renewal · Exam day · How long to study · Is it worth it? · What is CAHIMS?
Concepts explained: HL7 v2 vs FHIR · Capitation vs fee-for-service · Safe Harbor vs Expert Determination · Incident vs problem vs change · Backup types, RTO and RPO · Privacy Rule vs Security Rule · CDS five rights · Lewin vs Kotter · SDLC and go-live strategies · Testing types · Earned value (SPI, CPI) · Structure, process, outcome · HIE models · Six Sigma vs Lean · Levels of interoperability · Bandwidth vs latency · EMTALA · Risk responses · RACI matrix · Sunk vs opportunity cost · Data governance
The four domains: Healthcare and Technology Environments · Clinical Informatics · Healthcare Information and Systems Management · Management and Leadership
Written by Adel Moustafa, About us
Written and checked against the sources above on 22 October 2026. An independent site, not affiliated with or endorsed by HIMSS. CPHIMS® is a registered trademark of HIMSS.