EHR System Implementation & Management 2 — Questions and Answers
Question 1: Which implementation strategy involves running the old and new EHR systems simultaneously for a period to compare outputs and ensure accuracy?
- Big bang cutover
- Phased rollout
- Parallel conversion (Correct answer)
- Pilot implementation
Correct answer: Parallel conversion
Parallel conversion runs both systems simultaneously so staff can compare results and catch discrepancies before fully retiring the legacy system.
Question 2: During EHR go-live, 'super users' are primarily responsible for:
- Configuring the system database
- Providing peer-to-peer support on the floor (Correct answer)
- Approving vendor change orders
- Managing downtime procedures
Correct answer: Providing peer-to-peer support on the floor
Super users are trained power users embedded in clinical units to provide immediate peer support and answer questions during and after go-live.
Question 3: An EHR governance committee is BEST described as:
- A group that writes the technical code for EHR updates
- A cross-functional body that prioritizes system changes and sets policy (Correct answer)
- A vendor team that manages software releases
- A compliance team focused solely on HIPAA audits
Correct answer: A cross-functional body that prioritizes system changes and sets policy
Governance committees bring together clinical, administrative, and technical stakeholders to make decisions about system priorities, policies, and change management.
Question 4: What is the purpose of a 'system stress test' before EHR go-live?
- To train end users on all system modules
- To evaluate vendor contract terms
- To simulate peak load conditions and identify performance bottlenecks (Correct answer)
- To review billing codes for compliance
Correct answer: To simulate peak load conditions and identify performance bottlenecks
Stress testing simulates high concurrent user loads to ensure the system can handle peak usage without degraded performance.
Question 5: Which of the following BEST defines 'scope creep' in an EHR implementation project?
- A security breach that expands the attack surface
- Uncontrolled expansion of project requirements beyond the original plan (Correct answer)
- Data migration errors that increase data volume
- Additional vendor modules added through formal change orders
Correct answer: Uncontrolled expansion of project requirements beyond the original plan
Scope creep refers to unplanned, unapproved additions to project scope that can delay timelines and increase costs.
Question 6: When converting historical patient data to a new EHR, which process ensures that the data retains its original meaning and structure?
- Data normalization
- Data mapping (Correct answer)
- Data warehousing
- Data deduplication
Correct answer: Data mapping
Data mapping defines how fields and values from the source system correspond to fields in the target EHR, preserving meaning during migration.
Question 7: A hospital's EHR implementation team discovers that physician workflow requires a custom order set not available in the standard build. The BEST next step is to:
- Go live without the order set and add it later
- Submit a formal change request to evaluate feasibility and impact (Correct answer)
- Ask the vendor to immediately override the build
- Cancel the go-live until the vendor adds the feature
Correct answer: Submit a formal change request to evaluate feasibility and impact
A formal change request process ensures that customizations are evaluated for scope, cost, and timeline impact before being approved.
EHR System Implementation & Management 2
Which implementation strategy involves running the old and new EHR systems simultaneously for a period to compare outputs and ensure accuracy?