Study guide

18.2 Educational Strategies and Maintaining IT Competencies

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.2 Educational Strategies and Maintaining IT Competencies

Key Takeaways Explain This Topic AI

Task A.15 is develop educational strategies for the information and management systems function—who must learn, what they must be able to do, how learning happens, and how transfer is proven.

A class calendar, vendor bootcamp, or unpaid superuser roster is not an educational strategy.

Task A.16 is maintain organizational competencies on current IT technologies and trends; individual certificates do not maintain the organization.

Measure learning transfer with observed performance, not attendance or satisfaction scores.

CPHIMS recertification CE is personal credential maintenance. It is not evidence that the IMS function has an A.15 strategy or an A.16 system.

Last updated: August 2026

18.2 Educational Strategies and Maintaining IT Competencies

Quick Answer: Task A.15 is develop educational strategies for the information and management systems function. Task A.16 is maintain organizational competencies on current IT technologies and trends. A class calendar is not a strategy. Individual certificates do not maintain the organization.

Section 18.1 told you who cannot yet do the job. A.15 is how the IMS function plans learning so those gaps close and the next portfolio wave does not land on unprepared people. A.16 is how the organization —not one heroic analyst—stays competent as technologies and policy move. Chapter 13 already covered end-user training at implementation. This section is leadership of learning as an operating system.

Management and Leadership remains 25% . Education items are not “soft HR.” They are capacity: if the only person who understands identity is at a conference, you do not have an organizational competency. Practice application stems at CPHIMS practice . Quality-improvement education methods overlap CPHQ ; record and coding competency sits deeper on RHIA .

Educational strategy is not a catalog of classes

An educational strategy answers four questions:

Who must learn (HIT staff by function, clinical informatics partners, operational leaders, superusers, and—when IMS owns it—end users)?

What must they be able to do after learning (the A.22 skill standard)?

How will learning happen in the real workflow (modality, time, preceptors)?

How will you know transfer occurred (observed performance, not attendance)?

A.15 is for the information and management systems function . That includes developing HIT people and designing how IMS teaches the rest of the enterprise about systems. It is not a mandate to turn every analyst into a classroom trainer, and it is not the same as a vendor’s implementation curriculum.

Build the strategy from:

  • Competency gaps (A.22)
  • The IT strategic plan and departmental objectives (A.4)
  • The coming portfolio (A.23)—what skills next year’s programs require
  • Risk concentrations (A.17)—single points of knowledge
  • Regulatory and safety duties (privacy, downtime, information blocking)

Then choose modalities that match the skill:

Need Better modality Weak substitute Transfer evidence

New-hire orientation to identity, downtime, minimum-necessary Precepted shifts plus a drill 90-minute video Completes a downtime packet without the EHR

Order-set or CDS build Sandbox with clinical co-review Vendor slide deck Independent build passes peer review

After-hours escalation On-call buddy period Email distribution list Correct severity and owner on two night events

Leader literacy on a trend (ambient documentation, cloud shared responsibility) Short scenario briefing with a residual-risk memo Keynote recording Leader can state what they will not approve

Superuser coaching At-the-elbow with a script and time on the clock “Be a champion” email Superuser time is scheduled; units stop calling the CIO

Adult learning in healthcare fails when it is abstracted from the unit . Analysts learn by building and being reviewed. Leaders learn by deciding a case. Superusers learn by coaching a real note with protected time. Slide completion is activity.

Fund education as capacity , the same way you fund interfaces. “Training if there is leftover budget” is how A.16 later fails. Superuser programs are an educational strategy only when time, competency, and refresh are written. Unpaid champion labor is a staffing cut dressed as engagement.

Measuring A.15: transfer, not hours

Success measures that survive exam stems:

Can the person perform the skill to the A.22 standard without a preceptor?

Did reopen rates, failed changes, or downtime errors fall after the intervention—not just during class week?

Are there at least two people who can perform each critical skill (no single-throat knowledge)?

Did leaders stop approving tools they cannot explain?

Attendance, satisfaction scores, and “we offered the class” do not prove strategy. CPHIMS recertification (45 CE hours in three years, including two ethics hours) is personal credential maintenance . It is not evidence that the IMS function has an educational strategy, and it is not an A.16 program.

  • Maintaining organizational competency on technologies and trends (A.16)
  • A.16 is organizational and current . It is not “our staff once took a cloud class.”

Organizational competency means the enterprise can recognize, evaluate, and operate a technology or trend at the level its role requires:

  • Executives: what to fund, what to refuse, what residual risk they are accepting
  • IMS: how to implement, secure, integrate, and support
  • Clinicians and HIM: how documentation, identity, and the legal record change
  • Frontline support: how to recognize a new failure mode

Current IT technologies and trends in a CPHIMS frame are the ones that change operations or risk—not every vendor announcement. Typical 2026 cluster: ambient documentation, generative tools on PHI, cloud shared responsibility, identity-centric security, information-blocking and network-based exchange, virtual nursing, medical-device integration, and cybersecurity as an operations problem. HIMSS does not publish a CPHIMS-required trend list. Use the organization’s environmental scan (A.2) and forecast (A.3).

A maintenance system that works:

Horizon owner. Someone (often enterprise architecture or the CMIO/CIO pair) is accountable for scanning—not a volunteer chat channel.

Triage. Park, brief, or operationalize. Most trends are parked with a reason.

Role-graded briefings. A board memo, an IMS lab, and a HIM huddle are different products.

Hands-on residue. If you will operate it, competency moves from briefing to A.22 evaluation.

Sunset. Last year’s trend literacy (a retired portal widget, an old interface engine) should not crowd this year’s identity work.

Vendor education is a source , not a strategy. Treat it as marketing until a vendor-neutral owner restates what the organization must be able to do. Sending the entire department to the same conference is not A.16; it is a calendar and a concentration risk (nobody is home).

Shadow IT is often an A.16 failure mode. When official education is slow or refusal is unexplained, departments buy consumer AI, scheduling widgets, or “free” analytics. The educational response is not only a scolding policy. It is a fast, honest briefing: here is the approved path, here is the risk, here is how to request a governed exception. Risk treatment itself belongs with A.17 in section 18.4; A.16’s job is to keep the organization competent enough not to be surprised.

Distinctions the exam will punish

Educational strategy versus training schedule versus implementation curriculum (chapter 13).

Organizational competency versus individual certification .

Trend awareness versus authorization to implement .

Vendor enablement versus vendor-neutral literacy .

Personal CE for CPHIMS versus A.16 maintenance .

Loading diagram... A.15 strategy and A.16 maintenance: from competency gaps to organizational literacy

Study heuristic: A.15/A.16 mistakes that leave the organization unprepared (relative emphasis, not official weights)

Scenarios and exam traps

Scenario. After every EHR upgrade, all analysts sit through 40 hours of vendor lecture. Ticket quality does not change. Rebuild A.15 around the A.22 gaps: sandbox builds, precepted changes, and a sample of independent work. Keep vendor hours for what is actually new.

Scenario. The CIO says the organization is current because three directors hold CPHIMS. Certificates are individual. Ask who can brief residual risk on ambient documentation and who can operate identity if the cloud broker fails. That is A.16.

Scenario. A service line wants generative inbox-drafting next month. No organizational briefing exists. Deliver a short, role-graded competency package first (privacy, legal record, hallucination, BAA). Then portfolio and contract. Do not skip to a pilot because the demo was fluent.

Scenario. Superusers trained two years ago are still listed as the education strategy. Refresh or retire the roster. Stale champions are a false competency.

Watch these traps:

Equating a class catalog with A.15.

Counting CPHIMS or CE hours as organizational maintenance.

Letting vendor roadshows be the only trend education.

Measuring attendance instead of transfer.

Leaving critical skills in one person’s head and calling that “expertise.”

Using unpaid superusers as the entire strategy.

If you can name who must learn, prove transfer, and show how the organization stays current without depending on one certificate, you are doing A.15 and A.16 at professional level. Keep drilling at /practice/cphims .