HealthITPrep
CPHIMS guide Concepts Features Pricing FAQ
Sign in Start free
العربية

The system development life cycle (SDLC): phases and go-live strategies

By Adel Moustafa, CPHIMS® · Updated 22 October 2026

The stages a health information system goes through from the first idea to retirement, what each one produces, how the investment is judged, and the four ways to switch on a new system.

In short: the SDLC is the order of work for a system: planning (the business case, including cost-benefit), analysis (the requirements), design, build or selection, testing, implementation (training, data conversion, go-live), support and maintenance, and evaluation, until the system is retired. Go-live can be big bang, phased, pilot or parallel; each trades speed against risk.
The phases Business case Requirements Design Go-live strategies Waterfall and agile Common mistakes Summary Sources

What are the phases of the SDLC?

PhaseThe question it answersWhat it produces
Planning (initiation)Is this worth doing, and why?Business case, scope, feasibility, cost-benefit, project charter
AnalysisWhat must the system do?Current workflows, gap analysis, requirements
DesignHow will it do it?Architecture, data model, interfaces, screens, security design, future workflows
Build or selectionDo we build it or buy it, and from whom?Built and configured system; or a vendor chosen through a request for proposal (RFP) and a contract
TestingDoes it work as required?Test results from unit to user acceptance testing
ImplementationHow do we switch it on safely?Training, data conversion, go-live, support at go-live
Support and maintenanceHow do we keep it running and up to date?Help desk, fixes, upgrades, controlled changes
EvaluationDid it deliver what the business case promised?Post-implementation review, benefits realisation

At the end of its life, the system is retired: its data is moved or archived according to retention rules, and its media are disposed of securely. Security belongs in every phase, not only at the end. For a purchased system, selection usually follows analysis, and design then covers configuration and the future workflows. The names and number of phases vary from one source to another; this is a common teaching model.

How is the investment judged?

  • Cost-benefit analysis: compares all the costs with all the benefits, including the ones that are hard to put a price on, such as fewer medication errors.
  • Total cost of ownership (TCO): not only the purchase, but licences, hardware, interfaces, staff, training, support and upgrades over the system's whole life.
  • Payback period: how long until the benefits have repaid the investment. It answers "when do we get our money back?".
  • Return on investment (ROI): the net benefit as a share of the cost.
  • Net present value (NPV): future benefits and costs brought back to today's value, because money received later is worth less.

What happens in the analysis phase?

The team studies how work is done today (often by observing it and drawing the workflows), finds the gaps between today and what is needed, and writes the requirements:

  • Functional requirements: what the system must do, such as "check every medication order against the patient's coded allergies".
  • Non-functional requirements: how well it must do it: response time, availability, security, usability, capacity.

Each requirement should later be traced to the test that proves it, often in a requirements traceability matrix. The users who will live with the system, clinicians included, must take part here: a requirement missed in analysis costs far more to fix after go-live.

What does design add, such as compatibility and interoperability?

Design turns requirements into a plan: architecture, data model, screens, interfaces and security. Two design aspects are often confused:

  • Compatibility: the new system can run alongside the existing ones, on the hospital's platforms and network, without conflict.
  • Interoperability: the new system can exchange data with other systems and use what it receives, through standards such as HL7 and shared code sets.

Good design also includes the future workflows: a system that copies a bad paper process onto a screen keeps the problems of the paper.

What are the go-live strategies?

  • Big bang: everything, everywhere, at once. The shortest transition and no period of running two systems, but the highest risk: a problem hits the whole organisation.
  • Phased: by module (first registration, then orders) or by site, one step after another. Lower risk per step, a longer project, and temporary interfaces between old and new parts.
  • Pilot: the complete system at one site or unit first, evaluated for a period, then rolled out to the rest with what was learnt. It tests the whole system in real use with limited exposure.
  • Parallel: old and new systems run together for a period, and results are compared. The safest for data, but the most work: in clinical areas, double entry is a burden and a risk in itself, so it is used more for back-office systems such as finance.

How do waterfall and agile differ?

In waterfall, each phase is finished before the next begins; it suits work with stable, well-known requirements and strict documentation. In agile, the work is done in short cycles (sprints) that each deliver a working part, with users giving feedback all along; it suits work where needs become clear only by using the system. Many health IT projects use a mix: a planned overall life cycle, with agile build cycles inside it.

What do candidates get wrong?

  • Choosing a vendor before the requirements are written. Analysis comes before selection; an RFP without requirements compares sales pitches.
  • Leaving users out of analysis. Requirements missed now are the costliest to fix later.
  • Swapping pilot and phased. A pilot puts the complete system at one site first; phased switches on parts or sites one after another.
  • Swapping compatibility and interoperability. Compatibility: runs alongside. Interoperability: exchanges and uses data.
  • Counting only the purchase price. The total cost of ownership covers the whole life of the system.
  • Stopping at go-live. Evaluation checks whether the promised benefits came, and support continues for years.
  • Adding security at the end. It belongs in every phase.

Summary for revision

  • Order: planning, analysis, design, build or selection, testing, implementation, support, evaluation; then retirement.
  • Money: cost-benefit, TCO over the whole life, payback period (when the money comes back), ROI, NPV.
  • Requirements: functional (what) and non-functional (how well), traced to tests.
  • Go-live: big bang (all at once), phased (parts in turn), pilot (whole system, one site first), parallel (old and new together).
  • Design: compatibility (runs alongside) is not interoperability (exchanges and uses data).

Sources

  • NIST Special Publication 800-37 Revision 2, Risk Management Framework for Information Systems and Organizations: security tied to each phase of the system life cycle.
  • Project Management Institute, A Guide to the Project Management Body of Knowledge (PMBOK Guide): business case, charter, requirements.

Related free practice questions

  • The value of cost-benefit analysis: when is the investment recovered?
  • Compatibility and interoperability: the two design aspects
  • The pilot strategy

The site files this concept under the domain Healthcare Information and Systems Management.

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 exam

Questions 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 · 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 · Build vs buy · 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.

CPHIMS guide Compare certifications Free practice questions Concepts explained About us Terms of Use Privacy Policy Refund Policy Contact us

© 2026 HealthITPrep. This site is not affiliated with or endorsed by HIMSS. CPHIMS is a registered trademark of HIMSS.