Study guide
18.3 Managing Projects and Portfolios
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
18.3 Managing Projects and Portfolios
Key Takeaways Explain This Topic AI
Task A.23 is manage projects and portfolios of projects. A project is a temporary unique deliverable; a program coordinates related projects for a shared benefit; a portfolio is the selected mix under capacity.
Demand management classifies incoming work and publishes what a new yes displaces. Forty “P1” projects means demand was not managed.
Operations and “small interfaces” consume the same scarce people as chartered projects. Classification is part of management.
A PMO supports governance. It does not own clinical outcomes or replace the portfolio owner who can kill work.
An EHR upgrade may be a program in the portfolio. It is still not an organizational strategy.
Last updated: August 2026
18.3 Managing Projects and Portfolios
Quick Answer: Task A.23 is manage projects and portfolios of projects . A project is a temporary unique deliverable. A program coordinates related projects for a shared benefit. A portfolio is the governed set of work selected under capacity. Demand management decides what a new yes displaces.
Chapter 15.4 put the IT plan and a keep/kill/combine portfolio on the page. Chapter 13 taught scope, schedule, budget, and quality inside an implementation. A.23 is the leadership skill that sits between them: classify the work, manage demand, and run the stack so strategy does not drown in “small requests.”
An EHR upgrade may be a program in the portfolio. It is still not a strategy (15.1). Use free CPHIMS practice questions for classification and intake stems. Benefits measurement after go-live returns in chapter 14; do not confuse a green Gantt with a realized harm or access aim.
Project, program, portfolio, operations
HIMSS does not publish a CPHIMS-official intake score or mandate a PMI template. The distinctions still decide stems.
Level Definition Timebox Success Manager question
Operations / run Recurring work that keeps today’s services alive Ongoing Reliability, SLA, problem trend Is this a ticket, a standard change, or disguised project work?
Project Temporary endeavor with a start, an end, and a unique result Weeks to months (sometimes longer) Agreed scope delivered and handed to operations What unique result, and who accepts it?
Program Related projects managed together because the benefit appears only if they stay coordinated Multi-project, often multi-year Benefits across components What shared outcome requires these projects to move as one?
Portfolio The selected mix of programs, projects, and sometimes major operational investments Continuous, refreshed with the plan Strategic contribution under capacity What does the organization not do if we say yes?
Examples that survive stems:
Project: Turn on electronic prescribing of controlled substances in twelve clinics with a named acceptance test.
Program: Closed-loop medication safety—dispensing interoperability, barcode administration, pharmacy verification redesign, downtime med-pass, and benefits measurement. Managing those as unrelated projects will “finish” devices and still miss the harm aim.
Portfolio: The fiscal-year mix of run (identity modernization), grow (ambulatory access tools), and transform (hospital-at-home) that the A.3 forecast said the staff can absorb.
A PMO is a support and governance function. It does not own clinical outcomes. A project manager runs a project. A program manager integrates dependent projects. A portfolio owner (often the CIO with an integrated operations–finance–quality–HIT committee) selects and stops work. Do not staff a PMO and call the org chart “portfolio management.”
Demand management
Demand management is the process that turns incoming wants into classified work and an honest capacity conversation. Without it, you get forty “priority-one” projects, shadow work funded by a department, and an official portfolio that is only a slide.
Typical flow:
Intake with a written organizational or departmental objective (A.1/A.4), not a vendor demo.
Classify: operations, project, or component of an existing program. “Just a small interface” is usually a project or a program increment.
Estimate capacity in the scarce unit—often skilled people from 18.1, not dollars alone.
Compare to the portfolio. What in-flight work uses the same identity, interface, informatics, or testing pool?
Decide: accept, defer, combine, or refuse. Publish what the new yes displaces .
Charter only after the decision. A charter is not an intake form.
Shadow projects are demand that skipped the gate. They consume the same competent people, create unowned interfaces, and later appear as “urgent” production risk. Treat them as unauthorized portfolio entries, not as entrepreneurial spirit. The operational and contract treatment of shadow IT is section 18.4; A.23’s job is to stop pretending the official list is the real list.
Managing the work once selected
For projects , A.23 expects the usual controls in a healthcare key: scope that names clinical acceptance, a schedule that respects safety freezes, a budget that includes internal labor, testing (chapter 14), and a named operational owner for the day after go-live. Green bars with no benefits owner are theater.
For programs , add integration: shared risk register, shared identity and environment plan, sequenced go-lives, and a benefits measure that no single project can claim alone. Killing a component because it is late may be correct project control and still be wrong program control if the remaining pieces cannot produce the benefit.
For portfolios , add cadence: quarterly keep/kill/combine against the written aims and the actual remaining capacity . Adding a new transform program without stopping something is not management. Resource leveling is people math. If the same three interface analysts appear on every charter, you do not have a portfolio. You have a queue with extra logos.
Stage gates (intake → charter → design → build → test → train → go-live → benefits) are tools. They are not a HIMSS-required waterfall. Iterative delivery still needs portfolio intake and an operational home. “We are agile” is not permission to skip classification or demand management.
People from 18.1 and education from 18.2 are the binding constraint more often than capital. A portfolio that assumes contractors will appear with production competency is not managed; it is hoped.
Distinctions the exam will punish
Project versus program versus portfolio versus operations .
Demand management versus project scheduling . Scheduling assumes the work was already selected.
PMO versus portfolio owner who can kill .
On time / on budget versus benefits the program exists to create .
Strategic program versus strategy . The upgrade is still not the organizational aim.
Loading diagram... Demand management: classify, compare capacity, then keep kill or combine
Study heuristic: A.23 failures that fill a slide and empty the staff (relative emphasis, not official weights)
Scenarios and exam traps
Scenario. Closed-loop medications is split into five unrelated projects with five sponsors. Reassemble as a program. The benefit is safer administration, not five green charters.
Scenario. The portfolio list shows 40 priority-one items. That is a demand-management failure. Force ranking against capacity and aims; publish the deferred list. A new yes without a named displacement is not A.23.
Scenario. Cardiology funds a “quick” imaging viewer because official intake is slow. The same identity and interface pool will still do the work. Pull it into demand management. Do not bless it after go-live because it is already loved.
Scenario. Leadership calls the EHR upgrade “the portfolio.” It is one program at most. The portfolio is everything else you will stop or starve if the upgrade consumes the year.
Watch these traps:
Calling every request a project—or calling a program a single project so dependencies disappear.
Treating the PMO as the strategy or outcome owner.
Forty P1s and no displacement list.
Ignoring operations work that consumes the same scarce people.
Allowing departmental shadow projects to skip intake.
Declaring portfolio success when only Gantt bars are green.
If you can classify the work, name the capacity unit, and say what a new yes stops, you are doing A.23 at professional level. Drill those stems at /practice/cphims .