Study guide

13.1 Solution Selection Activities

Certified Professional in Healthcare Information and Management Systems CPHIMS

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current Exam Facts 1.2 Eligibility Pathways and Qualifying Experience 1.3 Scoring, Retakes, and Recertification 1.4 Domain-Weighted Study Strategy

2 Healthcare Organizations and Relationships

2.1 Hospitals, Clinics, Ambulatory, and Community Organizations 2.2 Payers, Regulators, Research, and Academic Organizations 2.3 Interrelationships, HIE, and Continuity of Care 2.4 HIT Professional Roles and Organizational Structures

3 Policy, Accreditation, and Care Trends

3.1 Privacy and Security Law: HIPAA and HITECH 3.2 Interoperability Policy and Information Blocking 3.3 Accreditation, Patient Rights, and Environments of Care 3.4 Telehealth, Portals, Wearables, and Population Health

4 Healthcare Applications

4.1 Clinical Applications 4.2 Administrative and Financial Applications 4.3 Consumer-Facing Applications 4.4 Business Intelligence Applications

5 Technology Infrastructure

5.1 Networks and Communications 5.2 Data Integration Architectures 5.3 Infrastructure Privacy and Security 5.4 Cloud, Devices, and Identity Infrastructure

6 Clinical Language, Terminologies, and Metrics

6.1 Clinical Vocabulary 6.2 Healthcare IT Vocabulary 6.3 Clinical Terminologies: SNOMED CT, LOINC, RxNorm, and ICD 6.4 Clinical Metrics and Operational Measures

7 Clinical Effectiveness and Workflows

7.1 System Functionality for Clinical Effectiveness 7.2 Workflows, Order Sets, and Pathways 7.3 Safety, Quality, and Clinical Informatics Design

8 Informatics Analytics

8.1 Analytics Tools, Reports, Tables, and Graphs 8.2 Interpreting Clinical and Operational Outcomes 8.3 Predictive Models in Care and Operations

9 Clinical Content and Decision Support

9.1 Clinical Content Lifecycle 9.2 Clinical Decision Support Types and Design 9.3 CDS Governance, Alert Management, and Knowledge Maintenance

10 Analysis, SDLC, and Improvement Methods

10.1 Systems Development Life Cycle 10.2 Project Management: Needs, Gap, and Requirements 10.3 Process Improvement: DMAIC and PDCA 10.4 Process Maps, Flow Diagrams, and Gap Analysis

11 Analysis: Solutions and the Business Case

11.1 Disparate Data Sets and Alternate Solutions 11.2 Strategic Alignment and Cost-Benefit Analysis 11.3 Proposals, RFPs, RFIs, SLAs, SOWs, and NDAs

12 Systems Design

12.1 Interoperability of Software, Hardware, Networks, and Devices 12.2 Design Compliance and Incorporating Industry Trends 12.3 Business Continuity and Disaster Recovery Design 12.4 Emerging Technologies and Data Governance

13 Selection, Implementation, Support, and Maintenance

13.1 Solution Selection Activities 13.2 Technical Change Management, Training, and Support 13.3 Implementation: Scope, Schedule, Budget, and Quality 13.4 Maintenance, Operations, and Problem-Trend Analysis

14 Testing, Evaluation, Privacy, and Security

14.1 Testing Methodology and Internal Controls 14.2 Validation and Benefits Realization 14.3 Privacy and Security Policies, Access, and Safeguards 14.4 Vulnerabilities, Roles, Data Controls, and Ongoing Validation

15 Strategy and IT Planning

15.1 Contributing to Organizational Strategic Planning 15.2 Assessing the Organizational Environment 15.3 Forecasting Technical and Information Needs 15.4 IT Strategic Plans and Departmental Objectives

16 Performance, Policy, Ethics, and Analytics

16.1 Evaluating Performance Against SLAs and Indicators 16.2 User Satisfaction and Service Effectiveness 16.3 Policies, Legal Compliance, and Ethical Principles 16.4 Comparative Analytics and Presenting Recommendations

17 Communication, Stakeholders, and Change

17.1 Promoting Stakeholder Understanding of IT Opportunities and Constraints 17.2 Business Communications and Consultative Technology Services 17.3 Facilitating Groups, Consensus, and Conflict Resolution 17.4 Organizational Change Management and Stakeholder Relationships

18 People, Projects, Vendors, and Finance

18.1 HIT Roles, Job Descriptions, and Staff Competency 18.2 Educational Strategies and Maintaining IT Competencies 18.3 Managing Projects and Portfolios 18.4 Vendor Contracts, Budgets, and Risk Management

13.1 Solution Selection Activities

Key Takeaways Explain This Topic AI

Domain 3 task C.1 is a controlled selection process: name stakeholders, freeze must-haves, then run scripted demonstrations, site visits, and reference checks against a scorecard published before the first vendor enters the room.

Stakeholders include the people who will live with, pay for, integrate, regulate, or be harmed by the product—not only IT and a vendor-friendly medical director.

A demonstration you do not script is demo theater. Score exception paths, dirty data, identity, interfaces, and downtime, not only seeded happy-path screens.

Site visits and reference checks need a peer match and a script. A vendor lighthouse tour and a single CIO quote are marketing, not evidence.

Score independently, then reconcile safety and integration outliers. Averaging a pharmacy “unsafe” with a marketing “beautiful” is not a decision.

Last updated: August 2026

13.1 Solution Selection Activities

Quick Answer: Task C.1 is how you choose after analysis and design have named the problem. Identify stakeholders , then run scripted demonstrations , site visits , and reference checks against a weighted scorecard . A vendor-run walk-through of happy-path screens is demo theater , not selection.

Domain 3, Information and Systems Management, is 30% of CPHIMS. Chapters 10–12 covered SDLC, the business case, RFPs, and design. Task C.1 starts when more than one path is still viable and someone must pick. The exam is not scoring who liked the booth. It is scoring whether the right people saw the right work, whether the scorecard existed before the first demo, and whether you caught the exception path the vendor did not show.

Use free CPHIMS practice questions after this chapter for “who scores the demo” and “what did the site visit miss” stems. CPHQ cares about the quality outcome the system must support. RHIA cares about the legal record the selected product will create. CPHIMS wants the selection process .

Why selection is a controlled activity

A healthcare purchase binds capital, interfaces, identity, medication safety, revenue, and years of operations. Selecting on one champion’s conference impression, or on a sole-source letter that never met stakeholders, is how you inherit a product that cannot file a CCD, cannot support two-identifier transfusion, or cannot survive a surveyor’s downtime question.

CPHIMS stems hide a broken selection inside a political sentence: “the CMO loved the demo,” “we already paid the deposit,” “the vendor’s reference site is just like us.” Name the missing activity. Then name the artifact that would have caught it.

Identify stakeholders before anyone books a demo

A stakeholder is anyone who must live with, pay for, integrate, regulate, or be harmed by the choice. A team that is only IT plus a vendor-friendly medical director fails C.1 even if the RFP was beautiful.

Role Why they sit What they score Classic miss if absent

Clinical operations (nursing, physicians, pharmacy, lab, imaging, HIM) Work-as-done and safety Workflow fit, exception paths, documentation Happy-path only; night shift invisible

Informatics / application owners Build, CDS, content Configurability, catalogs, upgrade burden A product no one can locally govern

Architecture, security, identity, interface Technical feasibility Integration, MPI, BAA, environments, audit A pretty UI with no identity or log

Revenue cycle / finance Cash and TCO License plus implementation, interfaces, staffing Cheap license; expensive remainder

Compliance, privacy, quality, risk Law and survey HIPAA, ONC criteria, Joint Commission, 508 Breaks patient access or accessibility

Biomed / clinical engineering Devices on the network Pump, monitor, modality pairing Guest-SSID “interoperability”

Shift-level end users Daily clicks and harm Time, cognitive load, glove-and-scanner reality Superusers never saw the real build

Executive sponsor Authority and money Alignment to strategy (Chapter 11) Orphaned project when the champion leaves

Write the list before invitations. Weight the scorecard so clinical safety and integration cannot be outvoted by a slick UI. Patients and families are stakeholders for consumer-facing tools (portals, RPM); they rarely sit in the RFP room, but accessibility and identity still get a criterion.

The C.1 activity set

Treat selection as a sequence, not a lunch-and-learn.

Freeze requirements and must-haves from the business case and design (Chapters 11–12). Must-haves are pass/fail, not 1–5 polish scores.

Name stakeholders and the scoring method —who votes, how weights work, what a dissent looks like.

Script demonstrations from your use cases, not the vendor’s slide order.

Run site visits at organizations that actually resemble yours (size, mix, EHR adjacency, medical-staff culture), not only the vendor showcase.

Execute reference checks with a structured script. Talk to operations and the help desk, not only the CIO who signed.

Score independently, then reconcile. Average last. Discuss first when scores diverge on a safety item.

Document residual risk for the winner. Selection is a decision with known gaps, not a claim of perfection.

RFP and RFI language lived in Chapter 11. C.1 is the evaluation theater you refuse to let the vendor direct .

Demonstrations that are not theater

Demo theater is a vendor-controlled walk-through of seeded data, day-shift attending physicians, and the three screens that always look good. CPHIMS wants you to break that script.

You bring the script . Use cases come from current-state maps (Chapter 10): admission med rec at 02:00, a look-alike drug, a duplicate MRN, a downtime restart, a discharge CCD, a denied claim, a pump rate that does not match the eMAR.

Use your catalogs, or at least dirty, realistic data. Seeded “Test, Patient” with one allergy is not a test.

Score exception paths as heavily as happy paths. If the product cannot show the exception, it failed the must-have, not the polish criterion.

Timebox. A four-hour demo that never reaches interfaces or identity is incomplete.

Separate sales engineers from implementation references . The person who will actually build your instance should answer technical questions.

Record scores during the demo on the published rubric. Memory after a dinner is not a scorecard.

Site visits and reference checks

A site visit is structured observation of work-as-done at a peer, not a campus tour. Match on relevant constraints: critical-access versus academic, employed versus independent medical staff, same core EHR or a true rip-and-replace, union staffing, state privacy extras. Watch a unit that is not the vendor’s favorite floor. Ask to see night shift, the ED at boarding, or the Friday discharge crush. Ask what they would not buy again, and what the help desk’s top ten tickets were at day 90. Bring the same scorecard . A virtual visit can cover screens; it rarely replaces walking the med-room or watching BCMA in gloves. A vendor-selected “lighthouse” that went live last month with unlimited consultant hours is a marketing asset—one data point, not the decision.

Reference checks are interviews you control. Use a script: go-live harm events, interface count versus promised count, realized versus promised staffing, upgrade pain, contract surprises, downtime, and whether the executive sponsor is still there. Talk to roles that match yours : CMIO, nursing informatics, pharmacy, revenue cycle, interface lead, service-desk manager. Ask for a site that struggled , not only the three names on the slide. Document date, role, and what was claimed versus what you can verify.

Scoring without theater

Publish the weighted scorecard before the first vendor enters the room.

Criterion class Typical weight band (illustrative) Pass/fail?

  • Fit to must-have clinical and safety requirements High Yes—fail a must-have and they are out
  • Integration, identity, interoperability (Chapter 12) High Often pass/fail on MPI, audit, certified API

Total cost of ownership (license, implementation, interfaces, staffing, upgrades) Medium-high No, but disclose assumptions

  • Usability and workflow for the actual roles Medium-high No
  • Vendor viability, support model, upgrade cadence Medium No
  • Strategic alignment and extensibility Medium No
  • Demo polish and “wow” Low or zero Never a must-have

Independent scoring first. A facilitator who averages everyone into 3.7 hides a pharmacy “unsafe” next to a marketing “beautiful.” Reconcile outliers on safety and integration in the room. Do not let a late lunch convert a fail into a 4.

Sole-source is still a selection. You still run a scripted demo against must-haves, still check references, still write residual risk. “We already use their EHR” is a constraint, not a waiver of C.1.

Loading diagram... Selection fails at the first skipped C.1 activity

Scenarios and exam traps

Scenario. A CMO returns from a conference and wants to sole-source a new ED tracker because “the demo was incredible.” Informatics has no stakeholder list and no scorecard. C.1 starts by naming who must live with boarding, lab turnaround, and identity—not by booking the sales engineer. A conference booth is a scan input (Chapter 12), not a selection.

Scenario. Three vendors demo. Two follow your night-shift med-rec script. One refuses and shows a seeded discharge of a healthy adult. Marketing scores that vendor a 5 for “executive presence.” Pharmacy scores a fail on allergy interrupt. The facilitator publishes a 3.9 average. Reopen the fail. A must-have is not a dimension you average away.

Scenario. The only site visit is the vendor’s showcase academic center, live for six weeks, with a 40-person optimization army. Your organization is a community hospital with two interface analysts. That visit does not match. Find a peer, or treat the lighthouse as color commentary.

Scenario. Reference calls go only to the three CIOs on the slide, all of whom signed last year. No one asks the help desk or night-shift nursing. Add those roles to the script or admit you have advertising, not references.

Watch these traps:

Letting the vendor run the demo agenda.

Scoring polish and skipping identity, interfaces, and exception paths.

Averaging a safety fail into a passing mean.

Visiting only the showcase or calling a virtual screen-share a site visit.

Treating a single executive quote as a reference check.

Calling sole-source a reason to skip C.1.

Task C.1 is scored when you can name the missing stakeholder, the missing script, or the missing scorecard. Section 13.2 then asks how you change the technical environment and train the people who will click the winner.