15.1 Contributing to Organizational Strategic Planning
Key Takeaways
- Domain 4 task A.1 is contribute to organizational strategic planning, for example by measuring performance against organizational goals.
- HIT is an input to the organization’s plan—capacity, constraint, information, and enabling options—not a sidecar digital strategy that asks the board for a blessing.
- An EHR upgrade, cloud migration, or “AI strategy” is a project or program. It is not an organizational strategy until it serves a written aim.
- Quote the numbered goal, use organizational grain, name an operational owner, and keep enabling metrics (uptime, tickets, logins) from substituting for outcomes.
- HIMSS does not publish a CPHIMS-official scorecard or planning framework. Use the organization’s governed plan and measures.
15.1 Contributing to Organizational Strategic Planning
Quick Answer: Domain 4 task A.1 is contribute to organizational strategic planning—for example by measuring performance against organizational goals. HIT brings information, capacity, and constraint into the organization’s plan. It is not a sidecar. An EHR upgrade is a project. It is not a strategy.
Management and Leadership is 25% of CPHIMS—about one scored item in four on the 100-scored-item, two-hour form. This chapter opens that domain. Chapter 11 already taught you to fail a cash-rich project that is missing from the written plan (task A.7). Task A.1 is earlier in the cycle: how the healthcare information and management systems professional helps form and steer the organizational plan, and how the organization knows whether last year’s aims actually moved.
Why contribution is not ownership of the plan
The organization—not the IT department—owns strategy. Boards approve mission, vision, values, multi-year aims, and the capital envelope. Service-line and operating leaders own volume, quality, access, equity, research, teaching, and margin. The CPHIMS professional contributes:
- Evidence of what current systems can and cannot support
- Performance information that shows whether written aims moved
- Capacity and constraint (people, interfaces, identity, security, capital, vendor and legal load)
- Options that enable a written aim (virtual access, closed-loop medications, revenue integrity, neighborhood clinics)
Contribution is not “present the IT roadmap and ask the board to bless it.” That reverses the cascade. Task A.4 (section 15.4) is where IT writes its own plan after organizational aims exist.
If you are invited only to price systems after the retreat, you are late. Ask for the aim list first. Then bring measures, residual data problems, and a capacity envelope—not a product demo. A sidecar digital deck that never enters the integrated planning committee is theater, even if the typography is excellent.
What counts as strategy
Strategy answers where the organization will create value and which tradeoffs it will accept. Typical healthcare planning stack:
| Element | Job | HIT contribution |
|---|---|---|
| Mission, vision, values | Why we exist; how we behave | Test whether a proposed digital initiative honors stated values (equity, stewardship, safety) |
| Environmental scan | Market, regulation, competitors, community need | Bring technology and information-policy facts (information blocking, telehealth payment, cyber risk) as inputs, not as the destination |
| Multi-year aims | Three-to-five outcomes the board will hold leadership to | Name which data and systems can measure those aims honestly |
| Annual operational goals | This year’s KPIs and owners | Instrument the KPI; refuse vanity IT metrics as substitutes |
| Initiatives and capital | Finite set of bets | Translate aims into enabling work; say what a new yes displaces |
| Performance system | How the board knows | Scorecards at organizational grain, with residual honesty |
An EHR upgrade is not a strategy. It can be a program that enables a strategy—safer medication use, ambulatory growth, a required certification, or interoperability the plan already named. If the only sentence on the slide is “we will upgrade the EHR,” you have a project charter. Same costume, other fabrics: cloud migration, “AI strategy,” “become a digital health system,” “stand up a command center.” None of those is an organizational aim until they attach to access, quality, equity, workforce, teaching, research, or financial sustainability the board actually wrote.
SWOT, PESTLE, and competitor maps are inputs to planning. They are not the plan. A wall of strengths and threats with no chosen aims and no measures is environmental scanning (section 15.2), not a finished A.1 contribution.
HIMSS does not publish a CPHIMS-official Balanced Scorecard, Hoshin matrix, or OKR template. Use the framework the organization already governs. What the exam tests is whether you measure organizational goals and treat IT as input, not as a parallel government.
Measure performance against organizational goals
The handbook’s example for A.1 is the contribution most candidates under-weight: measure performance against organizational goals.
Rules that survive exam stems:
- Quote the goal. “Reduce median new-patient wait from 38 days to 21” is a goal. “Improve access” is a slogan.
- Use the organization’s grain. Attributed panel, completed episode, discharge, member-month—not portal logins unless the plan defined logins as the access metric.
- Name the operational owner. A strategy without an owner becomes an IT dashboard nobody uses.
- Separate enabling metrics from outcome metrics. EHR uptime can enable access. It does not measure access. Ticket volume does not measure documentation-burden reduction.
- Publish residual honesty. If 28% of attributed members have no in-system encounter, do not report “the” diabetes control rate as if the aim is on track.
- Time the window. Go-live is a milestone. Goal performance is a trend after the process changed.
A practical A.1 package for a strategy retreat:
- Last year’s numbered aims, baseline, current value, and known data residuals
- Which aims have no reliable measure today (that is a planning finding, not a reason to skip the aim)
- What the current portfolio can absorb this year if something new is added
- Two or three enabling options per strained aim—not a single favorite platform
That package is how HIT contributes. It is also how you later evaluate alignment (chapter 11) without theater.
In a health system, contribution often means one enterprise scorecard with local drill-down, not a hospital-by-hospital “IT success” report. In an FQHC or critical-access hospital, contribution often means being honest that workforce, broadband, and identity—not another module—are the binding constraints on the access aim. In an academic center, research and GME aims are organizational aims; they are not optional IT hobbies.
Where HIT sits in the planning cycle
Typical multi-year / annual loop:
- Scan the market, regulation, community need, and technology as an input, not as the destination.
- Confirm or revise aims with the board.
- Cascade aims to service lines and support departments.
- Build the initiative portfolio and capital plan.
- Instrument the measures.
- Review quarterly: keep, kill, or reshape.
- Refresh the plan.
The HIT professional belongs in steps 1, 3, 4, 5, and 6 as a planner who carries information, not as a vendor of projects. Governance that makes contribution real includes an integrated planning or strategy committee (operations, finance, quality, medical staff, HIT), written intake that starts with the organizational objective identifier, and a portfolio view that shows what a new yes displaces.
Distinctions the exam will punish
- Organizational strategic plan versus IT strategic plan. A.1 is the first. A.4 is the second. Do not swap the labels.
- Contribute versus approve. You do not need board authority to contribute. You do need facts and the discipline to measure.
- Strategy versus execution verb. Upgrade, migrate, implement, and “stand up” are tactics until they serve a written aim.
- Performance versus activity. Training hours and help-desk tickets are activity. Harm, wait time, and panel access are performance—if they are the written goals.
Scenarios and exam traps
Scenario. The CIO is asked to “bring the digital strategy” to the board retreat. The organizational plan’s numbered aims are ambulatory access, harm reduction, and a new neighborhood clinic. Arrive with last year’s wait-time and harm trends, the identity residual on the diabetes registry, and capacity to absorb one major program—not a vendor roadmap titled Digital.
Scenario. A steering committee wants the year’s strategy to be “complete the EHR upgrade.” Ask which written aim the upgrade unlocks (closed-loop meds, ambulatory growth, a required certification). If no one can quote the aim, the upgrade is a project requesting a strategy costume. Park it until operations names the outcome and owner.
Scenario. The IT scorecard is all green: 99.9% EHR uptime, ticket backlog down, training hours up. New-patient wait is still 38 days and the access aim is red. Celebrate operations reliability if you must; do not tell the board the strategy is on track. Uptime enabled nothing that the plan asked you to measure.
Scenario. Quality wants a single diabetes-control rate for the equity aim. Claims, EHR, and device files disagree, and 28% of attributed members have no encounter. Publish the residual. A joined “green” rate is not A.1 measurement; it is a decorated meeting.
Watch these traps:
- Treating an EHR upgrade, cloud move, or AI program as the organizational strategy.
- Writing a sidecar IT plan and calling the blessing “contribution.”
- Substituting enabling metrics (uptime, tickets, logins, training hours) for organizational outcomes.
- Measuring activity after go-live and calling it benefits realization.
- Arriving at planning only to price systems after aims were chosen without information.
- Inventing a HIMSS-official CPHIMS scorecard formula.
A CIO is invited to the board retreat to “present the digital strategy.” The written organizational aims are ambulatory access, harm reduction, and a neighborhood clinic. What is the best A.1 contribution?
A steering committee declares that this year’s organizational strategy is “complete the EHR upgrade.” How should the CPHIMS professional treat that statement?
IT reports 99.9% EHR uptime and a falling ticket backlog while median new-patient wait remains 38 days against a written goal of 21. What does measuring performance against organizational goals require?