I85PREP
⌘ K
CAHIMS study materials
CAHIMS study resources

CAHIMS practice questions

One question at a time. Build your CAHIMS understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Systems Analysis

Which document most directly defines what a new clinical system must do from the users' perspective and is typically baselined before design begins?

  1. Project charter
  2. Disaster recovery plan
  3. Service level agreement
  4. Requirements specification Correct answer.

Explanation

A requirements specification captures the functional and nonfunctional needs the system must satisfy and serves as the reference for design, build, and verification. The other documents govern authority, service commitments, or continuity rather than system behavior.

Question 2Systems Analysis

During interviews, a analyst asks clinicians to describe how they currently complete a workflow and then observes them doing it. Which technique pair is being used?

  1. Prototyping and simulation
  2. Interviewing and direct observation Correct answer.
  3. Joint application design and Delphi
  4. Surveys and document review

Explanation

Interviewing elicits stakeholder descriptions, while direct observation verifies what actually happens in practice. Pairing them helps surface gaps between stated and actual workflow.

Question 3Systems Analysis

Which modeling diagram best shows the sequence of messages exchanged between a user, a registration module, and a billing system over time?

  1. Entity relationship diagram
  2. Org chart
  3. Gantt chart
  4. Sequence diagram Correct answer.

Explanation

A sequence diagram is a behavioral UML model that depicts interactions among participants ordered in time. It is suited to showing message flow between system components.

Question 4Systems Analysis

A stakeholder states that the system 'must be easy to use.' What is the best next step for the analyst?

  1. Defer the statement to the testing phase
  2. Replace it with a technical architecture decision
  3. Accept the statement as a complete requirement
  4. Elicit measurable criteria that define ease of use Correct answer.

Explanation

Vague quality statements must be refined into testable criteria, such as task completion time or error rate thresholds. Without measurable criteria the requirement cannot be verified.

Question 5Systems Analysis

Which category of requirement describes a constraint such as response time under peak load?

  1. Use case precondition
  2. Nonfunctional requirement Correct answer.
  3. Functional requirement
  4. Business rule

Explanation

Nonfunctional requirements describe quality attributes and constraints like performance, availability, and security. Functional requirements describe specific behaviors the system performs.

Question 6Systems Analysis

In a use case description, what does the main success scenario represent?

  1. The typical sequence of steps when nothing goes wrong Correct answer.
  2. The system's nonfunctional constraints
  3. All alternate and exception paths combined
  4. The data entities involved in the process

Explanation

The main success scenario, sometimes called the happy path, documents the normal flow that achieves the actor's goal. Alternate and exception flows are documented separately.

Question 7Systems Analysis

Which artifact is the primary output of the design phase that developers use to build the system?

  1. Design specification Correct answer.
  2. Training manual
  3. Feasibility study
  4. Acceptance test plan

Explanation

The design specification translates requirements into architecture, data, interface, and component designs that guide construction. It sits between requirements and implementation.

Question 8Systems Analysis

What is the main purpose of a traceability matrix in systems analysis?

  1. To link requirements to design, build, and test artifacts Correct answer.
  2. To record meeting minutes
  3. To schedule project resources
  4. To estimate server capacity

Explanation

A traceability matrix maps each requirement forward to design and test artifacts and backward to its source, supporting coverage and change impact analysis. It does not schedule work or estimate capacity.

Question 9Systems Analysis

A hospital wants to replace a paper intake form. The analyst maps each field on the form to a data element and its allowed values. Which analysis activity is this?

  1. Risk register development
  2. Cost-benefit analysis
  3. Data modeling Correct answer.
  4. Workflow simulation

Explanation

Mapping form fields to data elements with defined domains is data modeling, which defines structure and constraints for stored information. It precedes database and interface design.

Question 10Systems Analysis

An analyst needs agreement on a complex cross-departmental workflow from many stakeholders in a short time. Which technique is most appropriate?

  1. One-on-one interviews
  2. Document review
  3. Observation of a single user
  4. Joint application design session Correct answer.

Explanation

Joint application design brings stakeholders together in a facilitated workshop to resolve requirements and workflow conflicts quickly. It is efficient when many perspectives must converge.

Question 11Systems Analysis

A requirement states: 'The system shall allow a nurse to document vital signs within 30 seconds of opening the patient record.' Which quality attribute is being specified?

  1. Security
  2. Interoperability
  3. Maintainability
  4. Performance Correct answer.

Explanation

A time-bound criterion for completing an action specifies performance, a measurable nonfunctional attribute. It defines responsiveness rather than protection, exchange, or modifiability.

Question 12Systems Analysis

Which approach best manages scope creep during a clinical system implementation?

  1. Approving changes informally to keep stakeholders happy
  2. Establishing a formal change control process with impact assessment Correct answer.
  3. Freezing all requirements permanently at kickoff
  4. Rejecting all change requests without review

Explanation

A formal change control process evaluates each proposed change for cost, schedule, and risk before approval, keeping scope deliberate. Informal approval or blanket rejection undermines stakeholder trust and project control.

Question 13Systems Analysis

In an entity relationship model, a patient can have many encounters but each encounter belongs to exactly one patient. What is this relationship called?

  1. Many-to-many
  2. Zero-to-zero
  3. One-to-many Correct answer.
  4. One-to-one

Explanation

A one-to-many relationship exists when one instance of an entity relates to multiple instances of another while each of those relates back to only one. Here one patient maps to many encounters.

Question 14Systems Analysis

What is the primary benefit of building a prototype during analysis?

  1. It validates understanding and surfaces unmet needs early Correct answer.
  2. It finalizes the production architecture
  3. It replaces the need for written requirements
  4. It guarantees the project will be on schedule

Explanation

Prototypes give stakeholders something concrete to react to, exposing misunderstandings and missing requirements before costly build. They supplement rather than replace documented requirements.

Question 15Systems Analysis

An analyst is comparing two vendor systems and needs to rank them against weighted criteria. Which tool fits best?

  1. Decision matrix Correct answer.
  2. Control chart
  3. Pareto chart
  4. Affinity diagram

Explanation

A decision matrix scores alternatives against weighted criteria to produce a transparent comparison. It is well suited to structured vendor selection.

Question 16Systems Analysis

Which model describes the states a laboratory order passes through and the events that trigger transitions?

  1. Class diagram
  2. Context diagram
  3. State transition diagram Correct answer.
  4. Data flow diagram

Explanation

A state transition diagram models the permitted states of an object and the events that cause movement between them, ideal for order lifecycle tracking. It focuses on behavior over time rather than data flow or structure.

Question 17Systems Analysis

During validation of requirements, a stakeholder asks whether the requirement set is complete. Which check is being performed?

  1. Testing that code meets the requirement
  2. Confirmation that every need has a corresponding requirement Correct answer.
  3. Estimating the cost of each requirement
  4. Verification that requirements are internally consistent

Explanation

Completeness validation confirms that all identified stakeholder needs are represented in the requirement set. Consistency, code testing, and cost estimation address different concerns.

Question 18Systems Analysis

A new order-entry module must exchange HL7 messages with an existing pharmacy system. Which requirement category does this primarily belong to?

  1. Recoverability
  2. Interoperability Correct answer.
  3. Usability
  4. Portability

Explanation

Interoperability requirements define the system's ability to exchange and use information with other systems, such as via HL7 messaging. Usability, portability, and recoverability address different quality attributes.

Question 19Systems Analysis

A project team notices that a single requirement appears in the traceability matrix without any linked test case. What does this most likely indicate?

  1. The design is finalized
  2. The test plan is complete
  3. The requirement may be unverified Correct answer.
  4. The requirement is overestimated

Explanation

A requirement without a linked test case indicates a coverage gap, meaning the requirement may go unverified. Traceability supports identifying such gaps before release.

Question 20Systems Analysis

Which technique is most useful for prioritizing a large set of candidate requirements with limited stakeholder time?

  1. Fishbone diagram
  2. MoSCoW categorization Correct answer.
  3. Run chart
  4. Force field analysis

Explanation

MoSCoW categorizes requirements as must, should, could, and won't have, producing a clear priority ordering. It is designed for rapid prioritization with stakeholders.

Question 21Systems Analysis

An analyst discovers that two requirements conflict: one mandates audit logging of every view, another mandates sub-second screen loads under peak load. What is the best first step?

  1. Document the conflict and negotiate a resolution with stakeholders Correct answer.
  2. Drop the performance requirement
  3. Drop the audit requirement
  4. Implement both and let testing reveal the issue

Explanation

Conflicting requirements should be documented and resolved through stakeholder negotiation, possibly by refining thresholds or scoping. Silently dropping either requirement or deferring to testing risks rework and unmet needs.

Question 22Systems Analysis

A legacy system's undocumented business rules must be captured before replacement. Which combination of techniques is most effective?

  1. Benchmarking and cost analysis
  2. Code review and interviews with long-tenured staff Correct answer.
  3. Surveys and focus groups
  4. Prototyping and usability testing

Explanation

Undocumented rules often reside in legacy code and in the knowledge of experienced staff, so reviewing code alongside interviews surfaces implicit logic. Surveys and benchmarking do not reliably recover embedded rules.

Question 23Systems Analysis

An analyst models a process where a prior authorization request may be approved, denied, or pended for more information, with pended requests returning to review. Which modeling element is essential to represent the pended loop?

  1. A nonfunctional performance constraint
  2. An alternate or exception flow returning to a prior step Correct answer.
  3. A data entity relationship
  4. A single linear main success scenario

Explanation

Loops and re-entry points are captured as alternate or exception flows that branch from and return to the main path. A purely linear scenario cannot represent the pended return.

Question 24Systems Analysis

A stakeholder insists on a requirement that the analyst believes is technically infeasible. What is the most appropriate professional response?

  1. Accept it and plan to fail during testing
  2. Document the concern and facilitate discussion of alternatives and trade-offs Correct answer.
  3. Quietly omit the requirement from the specification
  4. Escalate immediately to cancel the project

Explanation

Professional practice is to document the feasibility concern transparently and work with stakeholders to explore alternatives and trade-offs. Omitting, escalating to cancellation, or planning failure are not constructive.

Question 25Systems Analysis

A team is choosing between a waterfall and an iterative approach for a project with rapidly evolving clinical requirements. Which consideration most favors an iterative approach?

  1. Regulatory documentation must be produced once at the end
  2. The project has no access to end users
  3. Frequent feedback and incremental delivery reduce risk of building the wrong solution Correct answer.
  4. Requirements are stable and fully known

Explanation

Iterative approaches deliver increments and gather feedback frequently, reducing the risk of building to misunderstood or changing requirements. Stable requirements and one-time documentation favor sequential approaches.

Question 26Systems Analysis

Which document primarily defines what the system must do from the user's perspective and serves as the basis for a contract between the customer and the development team?

  1. Software requirements specification Correct answer.
  2. Network topology diagram
  3. Project charter
  4. Database schema

Explanation

A software requirements specification captures functional and nonfunctional requirements and is the shared reference for stakeholders and builders. The other artifacts serve governance, infrastructure, or data-design purposes rather than defining required behavior.

Question 27Systems Analysis

A requirement states that the pharmacy label printer must produce a label within two seconds of a verified dispense event. Which characteristic of a good requirement does this statement best demonstrate?

  1. Verifiability Correct answer.
  2. Modifiability
  3. Feasibility
  4. Traceability

Explanation

A requirement is verifiable when it is stated so that a test can objectively confirm it, which the measurable two-second threshold allows. Traceability concerns links to other artifacts, modifiability concerns ease of change, and feasibility concerns whether it can be built.

Question 28Systems Analysis

Which elicitation technique is most appropriate when an analyst needs to observe how clinicians actually perform a task in its real setting rather than how they describe it?

  1. Observation Correct answer.
  2. Survey
  3. Document analysis
  4. Brainstorming

Explanation

Observation captures actual work behavior in context and often reveals workarounds that interviews miss. Surveys collect opinions at scale, document analysis relies on existing records, and brainstorming generates ideas rather than revealing current practice.

Question 29Systems Analysis

In a data flow diagram, what does a process symbol represent?

  1. A conduit that moves data between other symbols
  2. An external party that supplies or receives data
  3. A transformation that converts input data flows into output data flows Correct answer.
  4. A repository where data rests between activities

Explanation

Processes in a data flow diagram represent work that transforms inputs into outputs. Data stores hold data at rest, external entities sit outside the system boundary, and data flows are the conduits between them.

Question 30Systems Analysis

What is the primary purpose of a context diagram in systems analysis?

  1. To schedule the development iterations
  2. To list the detailed test cases
  3. To specify the internal database tables
  4. To define the system boundary and its external interfaces Correct answer.

Explanation

A context diagram shows the system as a single process surrounded by external entities, establishing scope and interfaces. It deliberately hides internal detail, so it does not define tables, tests, or schedules.

Question 31Systems Analysis

Which UML diagram is best suited to showing the sequence of messages exchanged between objects over time for a single scenario?

  1. Deployment diagram
  2. Sequence diagram Correct answer.
  3. State machine diagram
  4. Class diagram

Explanation

A sequence diagram orders messages among participants along a time axis for one scenario. Class diagrams show static structure, state machines show object lifecycles, and deployment diagrams show physical node allocation.

Question 32Systems Analysis

What is the main role of a business process model in systems analysis?

  1. To depict how work currently or should flow across roles and systems Correct answer.
  2. To record the physical storage layout of the database
  3. To estimate the cost of hardware procurement
  4. To document the programming language conventions

Explanation

Business process models describe activities, decisions, and handoffs across roles, giving analysts a shared view of current or future operations. They do not address storage layout, coding conventions, or hardware costs.

Question 33Systems Analysis

An analyst must confirm that a requirements specification uses terms consistently and contains no contradictory statements. Which review activity is being performed?

  1. Cost-benefit analysis
  2. Feasibility study
  3. Risk register update
  4. Requirements inspection Correct answer.

Explanation

Inspection is a structured review of the requirements text for defects such as inconsistency, ambiguity, and contradiction. Feasibility and cost-benefit analyses judge viability, and a risk register tracks risks rather than text quality.

Question 34Systems Analysis

A hospital's patient registration system must integrate with a regional health information exchange. The analyst writes a requirement stating the exact message format, trigger events, and acknowledgment behavior. Which requirement type does this best exemplify?

  1. Performance requirement
  2. Usability requirement
  3. Interface requirement Correct answer.
  4. Security requirement

Explanation

Interface requirements specify how the system exchanges data with external systems, including formats, triggers, and acknowledgments. Performance, security, and usability requirements address speed, protection, and ease of use respectively.

Question 35Systems Analysis

An analyst is decomposing a large clinical documentation system into modules. Which principle suggests grouping functions that change together and separating those that change for different reasons?

  1. High cohesion Correct answer.
  2. Vertical scaling
  3. Defensive design
  4. Loose coupling

Explanation

High cohesion means related responsibilities are grouped within a module, so changes to one concern stay localized. Loose coupling reduces dependencies between modules, defensive design handles errors, and vertical scaling adds resources to a server.

Question 36Systems Analysis

During analysis, a team creates a working screen mock-up that users can click through without any backend logic. Which type of prototype is this?

  1. Pilot system
  2. Production release
  3. High-fidelity evolutionary prototype
  4. Low-fidelity throwaway prototype Correct answer.

Explanation

A clickable mock-up without backend logic is a low-fidelity throwaway prototype used to validate understanding and then discarded. Evolutionary prototypes are built to become the product, and pilots and releases are deployed systems.

Question 37Systems Analysis

An analyst needs to understand why emergency department staff bypass a triage step in the electronic record. Which approach is most likely to reveal the underlying cause?

  1. Reviewing the vendor's marketing materials
  2. Counting the number of licenses purchased
  3. Reading the project charter
  4. Interviewing staff in their work area while reviewing the screens they use Correct answer.

Explanation

Contextual interviewing at the point of work lets the analyst see the screens and constraints that drive the workaround. Marketing materials, charters, and license counts say nothing about actual task behavior.

Question 38Systems Analysis

A requirements model shows that a medication order must be verified by a pharmacist before it can be dispensed. Which model element captures this restriction?

  1. A glossary term
  2. A use case actor
  3. A data dictionary entry
  4. A constraint on the ordering of events Correct answer.

Explanation

Ordering restrictions between events are constraints, often expressed in process or state models. A data dictionary defines data elements, actors are roles interacting with use cases, and glossary terms define vocabulary.

Question 39Systems Analysis

An analyst must show how a patient's demographic data element is defined, including its type, allowed values, and source. Which artifact should be used?

  1. Use case diagram
  2. Data dictionary Correct answer.
  3. Swimlane process diagram
  4. Gantt chart

Explanation

A data dictionary records definition, type, format, allowed values, and origin for each data element. Use case diagrams show actors and goals, Gantt charts schedule work, and swimlane diagrams show process flow.

Question 40Systems Analysis

A team models a clinical workflow as a series of activities with decision points, parallel branches, and role assignments. Which notation is designed specifically for this purpose?

  1. UML class diagram
  2. ERD
  3. Decision table
  4. BPMN Correct answer.

Explanation

BPMN is a standard notation for business processes with activities, gateways, parallel paths, and pools or lanes for roles. ERDs model data relationships, class diagrams model static structure, and decision tables tabulate rule combinations.

Question 41Systems Analysis

An analyst finds that a single requirement is linked to three design elements but no test case. What is the most appropriate corrective action?

  1. Delete the requirement from the specification
  2. Remove the linked design elements
  3. Create a test case that verifies the requirement and link it Correct answer.
  4. Close the requirement as out of scope

Explanation

A requirement without verification coverage is a gap that should be closed by adding a linked test case. Deleting the requirement, removing design elements, or closing it as out of scope would discard needed functionality rather than ensure verification.

Question 42Systems Analysis

An analyst must document a complex rule where reimbursement depends on combinations of coverage type, procedure code, and authorization status. Which technique most clearly presents all combinations?

  1. Use case diagram
  2. Decision table Correct answer.
  3. Context diagram
  4. Sequence diagram

Explanation

A decision table enumerates condition combinations against actions, making complex rule logic explicit and checkable. Use case, sequence, and context diagrams show interactions or scope, not combinatorial rules.

Question 43Systems Analysis

A project has a fixed regulatory deadline and stable, well-understood requirements. Which development approach is most consistent with these conditions?

  1. Exploratory iterative approach
  2. Plan-driven sequential approach Correct answer.
  3. Continuous deployment with no requirements baseline
  4. Ad hoc development with no documentation

Explanation

When requirements are stable and a fixed deadline or regulatory baseline exists, a plan-driven sequential approach supports predictability and documentation. Exploratory iteration suits changing requirements, and the other options abandon controls needed for compliance.

Question 44Systems Analysis

An analyst is preparing a requirements package for a clinical system. Which pairing correctly matches an artifact with its primary purpose?

  1. ERD to list nonfunctional performance targets
  2. Context diagram to define database indexes
  3. Use case specification to describe actor-system interactions for a goal Correct answer.
  4. Data dictionary to schedule project milestones

Explanation

A use case specification details the interactions between actors and the system to achieve a goal. Data dictionaries define data elements, ERDs model data relationships, and context diagrams show system boundaries.

Question 45Systems Analysis

A clinical stakeholder requests a feature that duplicates an existing system capability. Before adding it to the requirements baseline, what should the analyst do first?

  1. Escalate directly to the vendor without analysis
  2. Reject the request without discussion
  3. Assess the gap between the request and existing capability and document the rationale Correct answer.
  4. Immediately add the feature to the baseline

Explanation

The analyst should analyze whether the request is truly new, how it differs from existing capability, and record the rationale before changing the baseline. Adding it immediately, escalating without analysis, or rejecting outright all skip the needed assessment.

Question 46Systems Analysis

Two departments describe the same intake process differently, and each insists its version is correct. Which analysis technique best resolves the discrepancy?

  1. Facilitated joint session to build a shared process model Correct answer.
  2. Separate interviews with each department only
  3. Review of the vendor contract
  4. Reading the organizational chart

Explanation

A facilitated joint session lets both groups surface differences and agree on a single model, resolving conflicts through negotiation. Separate interviews preserve the divergence, while contracts and org charts do not describe the process.

Question 47Systems Analysis

An analyst is deciding whether to model a system's behavior with a state machine or a sequence diagram. Which consideration most strongly favors a state machine?

  1. The need to show the physical deployment of servers
  2. The need to show static class relationships
  3. The need to show how one entity's status changes in response to events over its lifetime Correct answer.
  4. The need to show message order among several collaborating objects for one scenario

Explanation

State machines model the lifecycle of a single entity, capturing states and event-driven transitions. Sequence diagrams focus on inter-object message order for one scenario, class diagrams show static structure, and deployment diagrams show physical nodes.

Question 48Systems Analysis

A requirements set is judged against the question: can each requirement be traced back to a stakeholder need or source? Which quality check is being applied?

  1. Completeness
  2. Testability
  3. Necessity and traceability to source Correct answer.
  4. Consistency

Explanation

Tracing each requirement to an originating need confirms it is necessary and justified. Consistency checks for conflicts, completeness checks for missing requirements, and testability checks whether requirements can be verified.

Question 49Systems Analysis

A hospital wants to modernize a legacy scheduling system. The analyst must decide which legacy business rules to preserve and which to retire. Which approach is most defensible?

  1. Rely solely on the vendor's default configuration
  2. Preserve all rules found in the code without review
  3. Extract rules from code, interviews, and policy documents, then validate each with business owners Correct answer.
  4. Retire all rules and design new ones from scratch

Explanation

Rules should be gathered from multiple sources and validated with owners so that obsolete rules can be retired deliberately. Preserving all code rules, discarding everything, or defaulting to vendor configuration all skip validation against current business need.

Question 50Systems Analysis

An analyst identifies a requirement that is technically risky and depends on an unproven interface. Which action best supports informed decision-making before committing to the baseline?

  1. Document the risk and propose a feasibility spike or proof of concept Correct answer.
  2. Remove the requirement to avoid conflict
  3. Approve the requirement and defer all analysis
  4. Ignore the risk until development begins

Explanation

Documenting the risk and validating feasibility with a spike or proof of concept produces evidence before commitment. Ignoring the risk, removing the requirement, or deferring analysis leaves the project exposed to avoidable failure.