Study guide
1.2 Eligibility Pathways and Qualifying Experience
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
1.2 Eligibility Pathways and Qualifying Experience
Key Takeaways Explain This Topic AI
Meet one of three pathways: bachelor’s + 5 years information and management systems experience including 3 in healthcare; graduate degree or higher + 3 years including 2 in healthcare; or 10 years including 8 in healthcare.
Qualifying experience includes systems analysis; design; selection, implementation, support, and maintenance; testing and evaluation; privacy and security; information systems; clinical informatics; and management engineering.
A healthcare setting includes hospitals, consulting firms, vendors, government, academic institutions, payers, and public health — not only bedside provider employers.
Documentation of eligibility is not submitted with the application unless HIMSS selects the file for audit.
After approval, the Authorization to Test window is 90 days; a one-time paid extension can add another 90 days within one year of the initial application.
Last updated: August 2026
Quick Answer: Qualify by one pathway: bachelor’s + 5 years information and management systems experience ( 3 in healthcare ); graduate degree or higher + 3 years ( 2 in healthcare ); or 10 years ( 8 in healthcare ). HIMSS does not collect proof unless it audits you. After approval you have 90 days to test.
Eligibility is the gate that sits in front of every CPHIMS fee. HIMSS designed CPHIMS as a mid-career professional exam. The three pathways exist so a master’s-prepared informaticist, a bachelor’s-prepared EHR implementation lead, and a long-tenured operator without a degree can all reach the same blueprint — but only if the years , the duty types , and the healthcare-setting subset line up. Applying on hope, or on a job title that sounds clinical, is how people pay $559 / $609 / $729 and then fail an audit.
Why the pathway math is a CPHIMS skill, not paperwork trivia
Domain IV will later ask you to define HIT roles and evaluate staff competency. Domain III will ask you to staff selection, testing, and support work. The eligibility rules preview that same professional judgment: what counts as information and management systems work , and what counts as a healthcare setting . If you cannot classify your own résumé the way the handbook classifies experience, you will mis-classify project teams later.
CPHIMS is independent of CAHIMS and CPDHTS. Holding CAHIMS does not automatically make you CPHIMS-eligible, and a digital-transformation job title does not move you onto the CPDHTS outline. Adjacent credentials such as CPHQ or RHIA may sit on the same leadership team; they do not replace the CPHIMS year-and-setting test.
The three pathways (meet one, not a blend)
You must fulfill one of the following. You do not average them, and you do not combine a partial degree path with a partial experience-only path.
Pathway 1 — Bachelor’s degree
Hold a baccalaureate degree from an accredited college or university plus five (5) years of information and management systems hands-on work experience, including at least three (3) years in a healthcare setting .
Pathway 2 — Graduate degree or higher
Hold a graduate degree or higher from an accredited college or university plus three (3) years of information and management systems experience, including at least two (2) years in a healthcare setting .
Pathway 3 — Experience only
Hold ten (10) years of information and management systems experience, including at least eight (8) years in a healthcare setting . No degree is required on this path, but the healthcare-setting bar is the highest of the three.
- Pathway Education Total IMS years Healthcare-setting years
- Bachelor’s Accredited bachelor’s 5 3
- Graduate or higher Accredited master’s, doctorate, or equivalent graduate degree 3 2
- Experience only None required 10 8
- IMS here means information and management systems , not “any job in a hospital” and not “any IT job anywhere.”
- What duties count as information and management systems experience
The handbook repeats the same duty list on every pathway. Count work in:
- Systems analysis
- Design
- Selection, implementation, support, and maintenance
- Testing and evaluation
- Privacy and security
- Information systems
- Clinical informatics
- Management engineering
That list is broader than “EHR analyst” and narrower than “works in healthcare.” A nurse manager who never touched systems selection, design, testing, privacy, or informatics does not accumulate IMS years just because the unit used an EHR. A management engineer who redesigned clinic throughput with information systems does accumulate IMS years even if the badge says “process improvement” rather than “IT.”
Hands-on matters on the bachelor’s pathway language. Supervising a help desk from a spreadsheet of tickets can count if you were accountable for support and maintenance. Forwarding tickets you never triaged usually does not. When in doubt, map each role to a named duty on the list and keep a work sample you could produce in an audit: a go-live plan you authored, a security control you implemented, a test script you executed, a selection scorecard you ran.
What counts as a healthcare setting
A healthcare setting is not limited to a hospital payroll. The handbook defines it as experience with a provider of health services or products to a healthcare facility , and it gives examples:
- Hospitals and other care-delivery organizations
- Healthcare consulting firms
- Vendors
- Federal, state, or local government offices
- Academic institutions
- Payers
- Public health
This is the most missed eligibility fact among vendor and payer candidates. Three years implementing a certified EHR for a health-IT vendor can satisfy the healthcare-setting subset on the bachelor’s path. Two years as a clinical-informatics analyst at a Medicaid plan can satisfy the graduate path. Eight years in a public-health surveillance shop can satisfy the experience-only path. Conversely, five years of retail-bank core-systems work is IMS experience but not healthcare-setting experience. Mixes are allowed: a bachelor’s candidate might have two years of generic systems analysis plus three years of hospital implementation.
Do not invent extra shortcuts. Dual degrees do not cut the healthcare-setting years. Part-time work is not automatically prorated in the handbook; if your hours were not professional-level IMS work, do not count the calendar span as if it were full-time leadership. Internships and coursework are education, not IMS years, unless you were employed in a qualifying duty.
Application, attestation, and audit
Apply on the HIMSS website using the first and last name on your government-issued ID . Pay the current first-time fee with the application. Documentation of eligibility does not need to be submitted with the application. HIMSS reserves the right to verify what you attested. If you are selected for an audit , you will be asked for proof — typically degree documentation and evidence of the years and settings you claimed.
That “attest now, prove later” model is a gift and a trap. The gift is speed: complete applications can be approved and an ATT emailed in about 3–5 business days . The trap is overclaiming. If an audit finds that your “three healthcare years” were actually one hospital year plus two years of unrelated retail IT, HIMSS can hold or deny eligibility. Keep a private packet: diploma or transcript, dated job descriptions, and a supervisor who can confirm duty mix.
Special testing accommodations are a separate packet. Declare the request on the application, then send the handbook’s Request for Special Examination Accommodations form and licensed-professional documentation to certification@himss.org . Approved accommodations appear on the ATT and are provided at no extra exam fee.
The 90-day ATT clock
Once HIMSS confirms eligibility, you must schedule and sit within ninety (90) days . The ATT email is what unlocks Pearson VUE scheduling; you cannot book before it arrives. Most centers run six days a week, but popular urban slots disappear, so book early even if you plan to sit in week ten.
If you do not schedule, or you cancel and do not reschedule inside the 90 days, you may buy a one-time extension that adds another 90 days, provided you pay the extension fee within one year of the initial application . The current HIMSS page lists the extension at $149 ; the May 2024 handbook still lists $129 . After one year, you submit a new complete application and the full first-time fee . Extensions do not reset eligibility rules; they only extend an already-approved window.
Use the 90 days. A common failure mode is waiting for a “perfect” study month, missing the window, and paying an extension — or worse, a full re-application — before a single scored item.
Loading diagram... Which CPHIMS eligibility pathway applies
Scenarios and traps
Scenario: the vendor implementer. Maya has a bachelor’s degree, four years implementing an inpatient EHR for a vendor, and one year of prior retail-POS systems analysis. She meets the 5 / 3 bachelor’s test: five IMS years, four of them already in a healthcare setting (vendor work counts). She does not need ten years.
Scenario: the graduate informaticist. Omar has an MS in biomedical informatics and 2.5 years as a clinical-informatics analyst at a payer. He is short. The graduate path needs three IMS years including two healthcare years. His healthcare-setting years are fine; he still needs additional IMS time.
Scenario: the ten-year operator. Priya has no degree, nine years as a hospital clinical-systems analyst, and two earlier years in telecom network operations. She has 11 IMS years and nine healthcare-setting years, which clears the ten / eight experience-only bar. She is eligible on pathway 3. If those hospital years had been only seven, she would not be.
Trap: counting bedside years as IMS years. Twelve years as an ICU nurse with no systems-analysis, design, selection, implementation, testing, privacy, informatics, or management-engineering accountability does not create a CPHIMS pathway. Super-user time can count when it is structured implementation or support work; informal “I help my friends with the EHR” does not.
Trap: assuming vendors and payers do not count. The handbook lists them. Exclude only work that is not IMS or not a healthcare setting.
Trap: mailing a binder with the application. Do not delay applying to assemble transcripts unless you were already selected for audit. Apply, then keep the binder ready.
Trap: missing the 90-day ATT. Approval is not an open-ended ticket. Book Pearson as soon as the ATT arrives, then study toward a date. If the date slips, follow the handbook-plus-current-Pearson reschedule rules from section 1.1 before the window dies.
When you are eligible, use free CPHIMS practice questions to test whether your on-the-job years actually map to the four domains — eligibility gets you in the room; the outline still has to be studied.