13.1 Solution Selection Activities

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.

CPHIMS practice questionsPractice questions with detailed explanations

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.

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.

1. Freeze requirements and must-haves from the business case and design (Chapters 11–12). Must-haves are pass/fail, not 1–5 polish scores.
2. Name stakeholders and the scoring method—who votes, how weights work, what a dissent looks like.
3. Script demonstrations from your use cases, not the vendor’s slide order.
4. Run site visits at organizations that actually resemble yours (size, mix, EHR adjacency, medical-staff culture), not only the vendor showcase.
5. Execute reference checks with a structured script. Talk to operations and the help desk, not only the CIO who signed.
6. Score independently, then reconcile. Average last. Discuss first when scores diverge on a safety item.
7. 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.

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.

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:

1. Letting the vendor run the demo agenda.
2. Scoring polish and skipping identity, interfaces, and exception paths.
3. Averaging a safety fail into a passing mean.
4. Visiting only the showcase or calling a virtual screen-share a site visit.
5. Treating a single executive quote as a reference check.
6. 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.