Study guide

5.2 Requirements Gathering, Systems Analysis & Workflow Mapping

HIMSS CAHIMS Certified Associate in Healthcare Information and Management Systems Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction & Exam Overview

1.1 About the CAHIMS Exam & Eligibility 1.2 Exam Format, Blueprints & Scoring

2 Chapter 2: Healthcare Organizations & Delivery Settings

2.1 Healthcare Organization Types & Care Delivery Settings 2.2 Organizational Structure, Governance & Clinical Roles 2.3 Healthcare Financial Operations, Billing & Reimbursement Models

3 Chapter 3: Healthcare IT Infrastructure & Hardware

3.1 Healthcare Hardware, End-User Devices & Infrastructure 3.2 Network Architecture, Connectivity & Cloud Infrastructure 3.3 Database Systems, Storage Solutions & Data Architecture

4 Chapter 4: Clinical Informatics & EHR Systems

4.1 Electronic Health Records (EHR) & Clinical Documentation 4.2 Clinical Decision Support (CDS) & Computerized Provider Order Entry (CPOE) 4.3 Health Information Exchange (HIE) & Interoperability 4.4 Healthcare Data Standards, Terminologies & Code Sets 4.5 Clinical Metrics & Informatics Performance Indicators 4.6 Data Visualization Techniques for Healthcare Analytics

5 Chapter 5: Systems Development Life Cycle & Systems Analysis

5.1 Systems Development Life Cycle (SDLC) & Project Initiation 5.2 Requirements Gathering, Systems Analysis & Workflow Mapping 5.3 Vendor Selection, RFP Process & System Evaluation

6 Chapter 6: Systems Implementation, Testing & Maintenance

6.1 System Implementation, Data Migration & Cutover Strategies 6.2 System Testing, User Acceptance Testing (UAT) & Quality Assurance 6.3 System Maintenance, Technical Support & Helpdesk Operations

7 Chapter 7: Privacy, Security & Regulatory Compliance

7.1 HIPAA Privacy Rule & Protected Health Information (PHI) 7.2 HIPAA Security Rule, Safeguards & Risk Analysis 7.3 HITECH Act, Breach Notification & Enforcement 7.4 Healthcare Cybersecurity, Threat Vectors & Risk Management

8 Chapter 8: IT Strategic Planning & Governance

8.1 Healthcare IT Strategic Planning & IT Governance 8.2 Performance Metrics, Analytics & Quality Improvement

9 Chapter 9: Leadership, Project & Change Management

9.1 Project Management Fundamentals in Health IT 9.2 Change Management, Organizational Readiness & End-User Training 9.3 Professional Ethics, Conduct & Business Communication

5.2 Requirements Gathering, Systems Analysis & Workflow Mapping

Key Takeaways Explain This Topic AI

Requirements elicitation combines multiple qualitative and quantitative techniques, including interviews, focus groups, surveys, Joint Application Development (JAD) workshops, and clinical shadowing.

Healthcare IT requirements are divided into functional (system actions), non-functional (performance, security, availability), clinical (patient safety, decision support), and regulatory categories.

Workflow analysis uses standard flowcharting and Business Process Model and Notation (BPMN) swimlane diagrams to visually map As-Is clinical operations and design To-Be future states.

Gap analysis compares current operational capabilities against future-state objectives to identify specific missing technology, interfaces, staff skills, and process controls.

Requirements prioritization frameworks like MoSCoW (Must, Should, Could, Won't) prevent project scope creep and align system builds with core patient care priorities.

Last updated: July 2026

  • 5.2 Requirements Gathering, Systems Analysis & Workflow Mapping
  • The Critical Role of Systems Analysis

Systems analysis acts as the vital translation bridge between clinical practice and technical architecture. In health IT, technical systems rarely fail due to bad code; they fail because the system was built without a deep understanding of actual clinical workflows. When software forces clinicians into cumbersome data entry patterns, clinicians create unsafe workarounds, experience cognitive burnout, and suffer reduced productivity.

The primary objective of systems analysis is to elicit, analyze, document, and validate what a new system must accomplish to support clinical care, administrative operations, and regulatory mandates.

Requirements Elicitation Techniques

Gathering requirements from diverse healthcare stakeholders—physicians, staff nurses, pharmacists, revenue cycle managers, and compliance officers—requires a combination of elicitation methods:

1. One-on-One Interviews

Structured or semi-structured interviews with domain experts provide in-depth qualitative insights into specific departmental challenges. While time-intensive, interviews build trust and uncover detailed nuances that broad surveys miss.

2. Focus Groups and Joint Application Development (JAD) Workshops

JAD sessions bring cross-functional stakeholders into facilitated, highly structured workshops. Bringing nurses, physicians, pharmacists, and IT analysts together into a single room accelerates consensus building and resolves conflicting departmental priorities (such as medication order formatting between pharmacy and nursing).

3. Direct Clinical Observation (Shadowing)

Analysts directly shadow clinicians during active shifts to observe real-world workflows in emergency departments, intensive care units, or outpatient clinics. Shadowing reveals hidden workarounds, paper shadow records, and informal communication channels that users forget to mention during verbal interviews.

4. Surveys and Questionnaires

Distributing standardized questionnaires allows analysts to gather quantitative data across large, geographically dispersed user populations. Surveys are efficient for capturing high-level satisfaction metrics and feature preference ratings.

5. Document and Artifact Analysis

Reviewing legacy policy manuals, paper charts, order sets, audit logs, and existing incident reports provides empirical background data regarding baseline operational volume and error rates.

Healthcare Requirement Types

Requirements must be precisely categorized to guide system architects, procurement officers, and testing teams.

Functional Requirements

Functional requirements specify what the system must do —the operational actions, inputs, outputs, and automated behaviors.

Example: "The system must automatically calculate patient body surface area (BSA) upon entry of height and weight."

  • Example: "The system must generate an electronic prescription and transmit it via Surescripts network."
  • Non-Functional Requirements

Non-Functional requirements specify how well the system must perform —quality attributes, technical performance, and system constraints.

  • Performance: "Medication interaction alerts must display within 1.0 second of order entry."
  • Availability: "The system must maintain 99.99% operational uptime 24/7/365."
  • Security: "Data at rest must be encrypted using FIPS 140-2 validated AES-256 standards."
  • Clinical Requirements

Clinical requirements focus on patient safety, decision support, and clinical quality metrics .

Example: "The system must display hard-stop clinical decision support alerts when ordering duplicate anticoagulant therapy."

Regulatory Requirements

Regulatory requirements mandate compliance with legal, accreditation, and government standards .

Example: "The system must maintain immutable audit logs recording every access to protected health information (PHI) as required by HIPAA Security Rule 45 CFR § 164.312."

  • Example: "The system must conform to ONC Health IT 2015 Edition Cures Update certification criteria."
  • Requirement Types Comparison Matrix

Requirement Category Core Focus Primary Question Answered Representative Health IT Example Primary Verification Method

Functional System Features & Actions What does the system do? Transmit CPOE orders to pharmacy module System Integration Testing

Non-Functional Performance & Quality How well does it perform? Process query results in under 1.5 seconds Performance & Load Testing

Clinical Care Quality & Patient Safety Does it support safe care? Alert on severe drug-drug interactions Clinical Scenario Validation

Regulatory Law & Accreditation Is the system legally compliant? Enforce AES-256 encryption on mobile devices Security Audit & Certification

Clinical Workflow Analysis & Swimlane Mapping

Workflow analysis evaluates how clinical tasks, information, and patients move through healthcare delivery pathways. The process follows two main stages:

Current State ("As-Is") Mapping: Visualizing the existing operational process, including bottlenecks, manual handoffs, and workarounds.

Future State ("To-Be") Mapping: Designing the optimized workflow after technological integration, eliminating redundant steps.

Business Process Model and Notation (BPMN) & Swimlanes

Complex clinical processes involve multiple roles. Swimlane diagrams organize process steps into parallel lanes representing specific departments or job roles (e.g., Patient, Nurse, Physician, Pharmacist, EHR System). +-----------------------------------------------------------------------------------+

  • | PATIENT : [ Arrives at Clinic ] ---> [ Provides ID & Insurance ] |
  • +-----------------------------------------------------------------------------------+
  • | TRIAGE NURSE: [ Captures Vital Signs ] ---> [ Enters Chief Complaint in EHR ] |
  • +-----------------------------------------------------------------------------------+
  • | PHYSICIAN : [ Reviews Chart ] ---> [ Conducts Exam ] ---> [ Orders CPOE Med ] |
  • +-----------------------------------------------------------------------------------+
  • | PHARMACIST : [ Receives Electronic Order ] ---> [ Verifies Dose ] ---> [ Dispenses]|
  • +-----------------------------------------------------------------------------------+
  • Standard Flowchart Mapping Symbols

Oval (Terminator): Represents start and end points of a clinical workflow.

Rectangle (Process): Represents a discrete operational step or action (e.g., "Administer IV push").

Diamond (Decision): Represents a branching point with conditional logic (e.g., "Is Patient Allergic to Penicillin? Yes/No").

Document Symbol: Indicates physical paper forms, printouts, or generated report outputs.

Flow Arrow: Indicates the direction of process execution and information transfer.

Gap Analysis Methodology

A Gap Analysis compares the current operational state ("where we are") against the desired future state ("where we need to be"). It explicitly identifies the missing elements—software features, network infrastructure, staff skills, or policy revisions—required to achieve organizational objectives.

4-Step Gap Analysis Process

Define Target Future State: Document specific performance benchmarks, clinical capabilities, or regulatory targets.

Analyze Current State: Measure baseline metrics, current system features, and existing workflow limitations.

Identify Gaps: Highlight missing capabilities (e.g., current EHR lacks barcoded medication administration support).

Formulate Action Plan: Develop prioritized initiatives, technology acquisitions, and training programs to close identified gaps.

Gap Analysis Matrix Example

Operational Area Current State (As-Is) Future State (To-Be) Identified Gap Action Plan

Medication Admin Nurse manually checks paper MAR against IV bag Barcode Scanner verifies patient wristband & MAR Lack of wireless handheld scanners & BCMA module Procure 150 wireless scanners; license BCMA module

Sepsis Alerting Physician manually reviews lab blood counts EHR automatically calculates SIRS criteria & fires alert EHR lacks automated clinical algorithm triggers Configure real-time CDS sepsis alerting rule

Patient Access Patients request records via paper mail Patients download CCDA records via online portal Legacy portal lacks API FHIR connectivity Deploy ONC-compliant FHIR patient portal

Requirements Prioritization (MoSCoW Method)

Not all user requests are equally critical. Project teams employ the MoSCoW framework to prioritize requirements and defend against scope creep:

M - Must Have: Non-negotiable requirements essential for go-live (e.g., e-prescribing compliance, basic billing generation).

S - Should Have: Important features that add significant value but can be temporarily delayed with manual workarounds.

C - Could Have: Desirable "nice-to-have" features implemented only if time and budget permit.

W - Won't Have (This Time): Stakeholder requests explicitly out of scope for the current release but saved for future phases.