17.2 Business Communications and Consultative Technology Services
Key Takeaways
- Domain 4 task A.12 is prepare and deliver business communications—presentations, reports, and project plans—matched to audience and decision type.
- A presentation has an ask, evidence, and residual. A report has grain, method, and honesty about unmatched data. A project plan has scope, schedule, budget, quality, and owners—not a decorative Gantt.
- Task A.14 is provide consultative services on IT: diagnose before prescribing, prefer process improvement when the workflow is the defect, and treat emerging technology as a scan input.
- Consultative service is not order-taking and not vendor theater. The deliverable is advice the organization can accept, sequence, or refuse.
- HIMSS does not publish a CPHIMS-official slide template or consulting methodology. Use the organization’s templates; the exam scores audience fit and diagnosis-before-product.
17.2 Business Communications and Consultative Technology Services
Quick Answer: Task A.12 is prepare and deliver business communications—presentations, reports, and project plans—matched to the audience and the decision. Task A.14 is provide consultative services on IT: change implications, process improvement, and emerging technology. Diagnose before you prescribe. A forty-slide vendor deck is not a board communication.
Section 17.1 taught you to make opportunities and constraints understandable. This section is the artifact and the stance. A.12 is what you put in front of people. A.14 is how you behave when they ask you to “just make it work.” Together they occupy the same exam neighborhood: the CPHIMS professional is not a ticket clerk and not a vendor’s on-site presenter.
A.12: three artifacts, three jobs
The handbook’s examples are not interchangeable.
| Artifact | Job | Must contain | Failure mode |
|---|---|---|---|
| Presentation | Move a specific audience to a decision or a shared understanding | Audience, decision type, ask, evidence, residual, timebox | Forty vendor slides with no ask |
| Report | Leave a durable evidence trail | Question, method, grain, source systems, residual unmatched, recommendation | A dashboard screenshot with no method |
| Project plan | Bind work to owners and constraints | Scope, schedule, budget, quality, risks, owners, displaced work | A Gantt with no acceptance criteria |
Presentations start with who is in the room. Trustees need aim, fully loaded cost, residual risk, and the decision you want this hour. Medical staff need workflow, time, safety, and what happens to the inbox. Nursing needs skill mix, dual-documentation days, and night-shift reality. Finance needs one-time versus run-rate and what a yes displaces. The same content dumped on every audience is not A.12.
Label the decision type on the first slide: inform, consult, or decide. A room that thinks it is deciding when you only came to inform will punish you later. A room that thinks it is being informed when you need a capital decision will leave without a vote.
Reports inherit Chapter 15’s honesty rules. Quote the question. Name source systems. Publish match rate and unmatched residual. Do not let a joined “green” rate travel without the 28% of attributed members who have no encounter. Separate enabling metrics (uptime, tickets, logins) from the outcome the plan asked you to measure. Date the window. A go-live weekend is not a benefits report.
Project plans are communications, not wallpaper. Scope is in and out. Schedule names freeze windows and hypercare, not only a go-live Friday. Budget is fully loaded. Quality names the clinical or operational test that means “done,” not “the vendor said complete.” Owners are operational as well as IT. If the plan cannot name who stops the old paper form, it is not ready to present.
HIMSS does not publish a CPHIMS-official slide master, report outline, or work-breakdown template. Use whatever the organization already governs. The exam scores whether the artifact fits the audience and whether it can support a decision.
Audience translation is the skill
A single technical truth needs different sentences:
- Board / trustees. Mission, fiduciary duty, enterprise risk, multi-year cash. Do not ask them to approve an EHR version number.
- Medical staff. Time, autonomy, evidence, inbox. A workflow change is a clinical decision that happens to use software.
- Nursing and allied health. Skill mix, documentation minutes, glove-and-scanner reality. Superuser time is a staffing request.
- Operations / administration. Throughput, labor, access slots, survey calendar.
- Finance. Contribution margin, covenants, one-time versus run-rate, exit cost.
- Quality / compliance. Measure specs, surveyor language, privacy.
- Vendor (when they are in the room). Scope and acceptance only. They do not present your board packet.
If the CMO asked for a ten-minute decision and you arrive with an architecture deep-dive, you failed A.12 even if every box on the diagram is correct. If HIM leadership asked how the legal record will look after cutover and you bring only a training calendar, you failed A.12.
A.14: consultative service is diagnosis before product
Consultative technology services means you are hired—internally—for judgment, not for order-taking. The handbook’s examples are the three consults you will see on stems: change implications, process improvement, and emerging technologies.
- Diagnose the request. “We need a new inbox product” may be a routing, coverage, or compensation problem. Watch a clinic. Count clicks. Read the last three months of denial or harm data. Chapter 10’s current-state map is a consulting tool.
- Offer more than one path. Status quo, process-only, configure what you already own, interface, buy, or build—the same alternate-solution set as Chapter 11. A consultant who arrives with one SKU is a salesperson.
- Prefer process improvement when the workflow is the defect. DMAIC or PDCA can retire a shadow spreadsheet without a capital request. If you skip that step, A.14 has already failed.
- Treat emerging technology as a scan input. Ambient documentation, generative summarization, ambient listening, computer vision, and new device classes belong in the environmental scan (Chapter 15) and in a time-boxed pilot with a written aim, a BAA, and a stop rule. They do not belong as an unsolicited purchase in next week’s CAB.
- Name change implications early. Who must work differently, what old path must die, what training and reinforcement A.20 will need, and what Chapter 13 RFC the technical cutover will require. Mixing those two “change” words on a stem is a common miss—this section advises; section 17.4 runs organizational change; Chapter 13 runs the RFC.
- Leave advice the organization can refuse. A consult that can only end in “do what I already wanted” is not consultative.
In-house consulting is still consulting. You still disclose conflicts (you own the platform you are recommending). You still write a short findings note. You still separate the diagnostic visit from the sales visit when a vendor tags along.
What consultative service is not
- Taking a departmental order and opening a project because the requester is loud.
- Handing the board a vendor’s ROI slide and calling it your report.
- Using “innovation” to skip intake, a BAA, or a freeze calendar.
- Writing the requirements you will later implement without operations in the room.
- Confusing a lunch-and-learn with a decision presentation.
A.12 and A.14 fail together when the artifact is beautiful and the diagnosis never happened. They also fail when the diagnosis is excellent and the only document is a hallway conversation.
Scenarios and exam traps
Scenario. A vendor offers to “present to the board.” The CIO forwards the forty-slide product deck. A.12 requires you to rewrite: numbered aims, fully loaded cost, residual identity risk, and a single ask. The vendor may answer a scoped technical question in an appendix. They do not own the board narrative.
Scenario. A clinic manager demands a new inbox product because messages are drowning the panel. You watch a morning and find uncovered buckets, no coverage standard, and a routing rule no one maintains. A.14 starts with process improvement and a coverage compact. A product may come later. Ordering the module first is order-taking.
Scenario. Innovation wants a generative-summary pilot in the ED next Monday. There is no written aim, no BAA, and no stop rule. Consultative service is a time-boxed scan: aim, PHI path, evaluation grain, and a date the pilot dies if it does not move the aim. “Innovation” is not an exemption from A.12 documentation.
Scenario. A project plan presented to operations is a Gantt through go-live Friday. No hypercare staffing, no owner for retiring the paper downtime form, no quality test. That is not a plan. Add acceptance, owners, and the freeze window, or do not present it as A.12 complete.
Watch these traps:
- Using the vendor’s deck as your communication.
- Writing a report that hides unmatched residuals.
- Calling a Gantt a project plan.
- Prescribing a product before a current-state diagnosis.
- Treating emerging technology as a purchase rather than a scan-plus-pilot.
- Mixing consultative advice with Chapter 13 authorization to change production.
A vendor offers a forty-slide product deck for next week’s board meeting. What is the A.12-correct communication?
A clinic manager demands a new inbox product because messages are drowning the panel. Observation shows uncovered buckets and an unmaintained routing rule. What is the A.14-correct first service?
Operations is shown a Gantt that ends on go-live Friday. There is no hypercare staffing, no owner for retiring the paper downtime form, and no quality acceptance test. What is missing for A.12?