Systems Analysis in Health IT
What this domain tests
Systems analysis is about turning a clinical or operational need into a defined, testable requirement set before anything is built. Candidates should be fluent in the requirements lifecycle: elicitation (interviews, observation, workflow shadowing), analysis, documentation, validation, and traceability. Know the difference between functional requirements (what the system does: "the system shall flag duplicate orders") and non-functional requirements (performance, availability, security, usability). Know use cases and user stories, and why a current-state vs. future-state workflow map matters in clinical settings.
Concepts to name confidently
- Gap analysis: comparing current and desired states to define what must change.
- Traceability matrix: links each requirement to design, build, and test artifacts so nothing is silently dropped.
- Data flow diagrams and process maps: show where information moves and where handoffs create risk.
- Interface/HL7-style messaging concepts: systems exchange data through defined interfaces; interface requirements are requirements too.
- Validation vs. verification: verification asks "did we build it right?"; validation asks "did we build the right thing?"
Traps in questions
Watch for answers that jump to a solution before requirements are gathered. Distractor options often describe a design choice when the question asks about analysis. Another common trap: confusing a functional requirement with a constraint (a regulatory or technical limitation). Also watch for "the user said so" answers-requirements must be validated against actual workflow, not just stated preferences.
Rule of thumb
If a question asks what to do first when a workflow problem surfaces, the answer is almost always to observe and document the current-state workflow and stakeholders before proposing technology. Worked example: a unit complains about slow lab result acknowledgment. The analyst shadows the workflow, maps the current state, identifies a manual handoff, and writes a traceable requirement-rather than immediately requesting a new dashboard.