18.2 Educational Strategies and Maintaining IT Competencies

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.

CPHIMS practicePractice questions with detailed explanations

Educational strategy is not a catalog of classes

An educational strategy answers four questions:

1. Who must learn (HIT staff by function, clinical informatics partners, operational leaders, superusers, and—when IMS owns it—end users)?
2. What must they be able to do after learning (the A.22 skill standard)?
3. How will learning happen in the real workflow (modality, time, preceptors)?
4. 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:

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:

1. Horizon owner. Someone (often enterprise architecture or the CMIO/CIO pair) is accountable for scanning—not a volunteer chat channel.
2. Triage. Park, brief, or operationalize. Most trends are parked with a reason.
3. Role-graded briefings. A board memo, an IMS lab, and a HIM huddle are different products.
4. Hands-on residue. If you will operate it, competency moves from briefing to A.22 evaluation.
5. 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.

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:

1. Equating a class catalog with A.15.
2. Counting CPHIMS or CE hours as organizational maintenance.
3. Letting vendor roadshows be the only trend education.
4. Measuring attendance instead of transfer.
5. Leaving critical skills in one person’s head and calling that “expertise.”
6. Using unpaid superusers as the entire strategy.

/practice/cphimsPractice questions with detailed explanations