Study guide

15.4 IT Strategic Plans and Departmental Objectives

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

15.4 IT Strategic Plans and Departmental Objectives

Key Takeaways Explain This Topic AI

Task A.4 is develop and implement an IT strategic plan and departmental objectives that align with and support organizational strategies and goals.

The IT plan is a translation layer and cascade—not a substitute for the organizational plan and not a project list with a new cover.

Departmental objectives need owners, measures, and a quoted organizational aim. Uptime-only or “complete the upgrade” objectives fail the cascade.

The portfolio (run / grow / transform; keep, kill, combine) is how the plan is implemented; capacity is a strategic constraint.

An EHR upgrade may sit in the portfolio as a program if it enables a named capability the aim needs. The upgrade is still not the strategy.

Last updated: August 2026

15.4 IT Strategic Plans and Departmental Objectives

Quick Answer: Domain 4 task A.4 is develop and implement an IT strategic plan and departmental objectives that align with and support organizational strategies and goals . The IT plan is a cascade , not a second government. An EHR upgrade may be a portfolio program. It is still not the strategy.

A.1 contributed to the organizational plan. A.2 read the environment. A.3 forecast capacity, skills, and data against business needs. A.4 is where HIT writes its multi-year plan and this year’s departmental objectives so the rest of the organization can see how information and systems will support the aims—and what will not be done.

Chapter 11’s alignment test (A.7) still applies to every portfolio item. Chapter 16 will evaluate performance against SLAs and indicators; do not hide inside operations metrics here. Chapter 18 returns to project-portfolio mechanics and vendor money. This section is the strategy-to-objectives cascade . Domain 4 is 25% of CPHIMS. Drill the cascade at CPHIMS practice . Quality-aim ownership goes deeper on CPHQ ; you still must write HIT objectives that serve those aims rather than replace them.

Cascade, do not compete

The IT strategic plan is a translation layer :

Organizational aim → IT strategic theme that quotes the aim → departmental objective with owner and measure → portfolio item → benefit residual

If you cannot walk that chain backward from a project to a numbered organizational goal, the item does not belong in the plan as “strategic.” It may still belong as run-the-business (keep the lights on, replace end-of-life, meet a binding regulation). Honesty about run versus grow versus transform is part of A.4, not a branding exercise.

IT-plan element What “good” looks like What fails A.4

Principles Single enterprise identity; EHR as system of record unless a governed exception; cloud and security patterns already decided A new principle invented to justify last week’s purchase

Current state versus aims Gaps against organizational aims and the A.3 forecast Gaps against a vendor roadmap or a conference demo

Multi-year themes “Instrument and improve board access KPI” quoting aim 2.3 “Digital transformation” with no aim ID

Departmental objectives Owner, date window, measure, quoted aim “Complete the EHR upgrade”; “achieve 99.9% uptime” as the only objective

Portfolio Run / grow / transform; keep, kill, combine; capacity envelope A project list in priority-number cosplay

Implementation cadence Quarterly cascade review with operations owners A slide filed after the retreat

The organizational plan remains the parent. If operations amends an aim, the IT plan amends. If HIT wants work that is absent from the parent, that is an A.1 governance request—not a stealth line in the IT appendix.

Departmental objectives are not slogans

A.4 names departmental objectives for a reason. Themes without yearly, owned objectives are posters.

Good (access aim 2.3): “By Q3, ambulatory operations owns a weekly new-patient-wait measure from scheduling plus EHR, with a published match rule and residual, and HIT will deliver the feed and the dual-search registration change the A.3 forecast named.”

Good (harm aim 1.1): “By Q4, close the scan-compliance gap on two high-risk units to the rate quality already specified, with nursing as owner and HIT supplying device reliability and exception workflow.”

Bad: “Complete the EHR upgrade.” That is a milestone, not an objective that supports an organizational goal.

Bad: “Achieve 99.9% uptime.” Reliability can be a run objective. It cannot be the only departmental expression of a strategy about access, harm, or equity.

Bad: “Become a digital workplace.” No owner, no measure, no aim.

Write objectives that operations can recognize as their aim with HIT as the enabling department. If the only audience who understands the objective is the technical steering group, you have not cascaded—you have translated the strategy into jargon and called it alignment.

Objectives should absorb the A.3 forecast: the skills you will hire or contract, the identity work, the site network, the BAA load. An objective that assumes infinite analyst capacity is a wish list with a date.

Portfolio is how you implement the plan

“Develop and implement ” is official language. Implementation of an IT strategic plan is not a go-live. It is running a portfolio against the cascade:

Intake starts with the organizational objective identifier and the A.2 environment note (who will veto, which driver is live).

Prioritize against written aims and against capacity. A yes is a no to something else; show the displacement.

Classify run (keep current services safe and supported), grow (scale a current aim), transform (new capability the plan named).

Review quarterly: keep, kill, combine, or send back to strategy governance.

Name benefit owners in operations. HIT can own a feed; it cannot own wait time.

An EHR upgrade belongs here as a program when the plan can name the capability the aim needs—new ambulatory site support the current version cannot carry, a safety requirement, a certification date, a security debt that blocks the risk appetite the board already set. The upgrade still does not become the strategy, the theme, or the only departmental objective. If the upgrade exists only to “stay current,” it is run-the-business capital, and it must compete honestly with other run items.

Cloud migrations, data platforms, and “AI” follow the same rule. They enter the portfolio when A.3 linked them to a business need and A.1 still has a parent aim. Otherwise they are sidecar government.

Implement means refresh, not laminate

A plan that cannot change is decoration. Implementation includes:

  • An annual refresh after the organizational plan moves
  • Quarterly portfolio reviews with finance, quality, and clinical operations—not only HIT
  • A public list of what was killed and why (capacity, environment, or lost parent aim)
  • Departmental huddles that track objectives , not only tickets

Architecture and security as constraints that protect the plan , not as a veto theater that never appears until design

HIMSS does not publish a required CPHIMS IT-plan template, theme count, or scoring sheet. Use the organization’s governance. The exam tests whether the plan supports organizational strategies and goals , whether objectives are real, and whether you can tell a project from a strategy.

Loading diagram... A.4 cascade: organizational aims to themes, objectives, and a portfolio that can hold an upgrade without becoming one

Study heuristic: A.4 failures that produce a project list with a strategy cover (relative emphasis, not official weights)

Scenarios and exam traps

Scenario. The CIO publishes a three-year “digital strategic plan” that never cites the board’s access, harm, or clinic aims. Send it back to A.1. A.4 cannot start from a blank parent. Themes must quote organizational strategies and goals.

Scenario. Departmental objectives are “complete the EHR upgrade” and “99.9% uptime.” Rewrite. If the upgrade enables closed-loop meds on the harm aim, say that, with nursing as owner and a scan-compliance measure. Keep uptime as a run objective, not as the strategy costume.

Scenario. The portfolio has 40 “P1” projects. That is not implementation. Force keep/kill/combine against the capacity the A.3 forecast already said was binding. Show what a new yes displaces.

Scenario. After the retreat, the IT plan is laminated and filed. Nine months later a merger environment (A.2) changes the access aim. Implementation means a refresh and a kill list—not loyalty to last year’s slide.

Watch these traps:

Writing an IT plan that competes with, rather than supports, the organizational plan.

Treating an EHR upgrade as the strategy, the theme, or the only objective.

Objectives with no owner, no measure, and no quoted aim.

A numbered project list offered as a portfolio.

Filing the plan and skipping quarterly keep/kill/combine.

Inventing a HIMSS-required CPHIMS plan template or score.

If you can cascade aim → theme → owned objective → portfolio item, and you can keep an upgrade in its place as a program, you are doing A.4 at professional level. Mix those items at /practice/cphims .