Which is NOT a reason why the SDLC is important for EHR systems?

• A. Because poorly designed software has not yet been linked to security risks.
• B. Need for user satisfaction and high quality
• C. In-house development or integration of an EHR
• D. Because failure to plan adequately for software integration can limit efficiency and be costly in project over-runs and lost productivity.

Answer: (A)

Focusing on how the SDLC supports EHR success means recognizing how it keeps systems secure, usable, and well integrated, while also guiding project planning to avoid overruns. An SDLC approach ensures security risks are considered early, design and testing emphasize quality and usability, and there is a clear path for either building in-house or integrating with existing health IT components. It also helps plan for how the new EHR will mesh with other systems and workflows, so the project stays on schedule and within budget.

The statement about poorly designed software not being linked to security risks is not accurate. In reality, weak design often creates security vulnerabilities, which the SDLC aims to prevent through secure design practices, risk assessment, and testing. That makes the other reasons true benefits of applying the SDLC to EHR projects, while the stated option does not reflect a valid justification.