Most CHDA eligibility confusion comes from candidates assuming they need both a health information credential and a bachelor's degree, or assuming the "3 years of experience" language is a hard requirement. Neither is accurate. This guide breaks down the actual eligibility pathways, the real domain weighting straight from AHIMA's exam content outline, and the format details that most secondary prep sites either get wrong or leave out entirely.
What the CHDA Certifies
The Certified Health Data Analyst (CHDA) is AHIMA's credential for professionals who acquire, manage, analyze, interpret, and report on healthcare data at an advanced level. Unlike entry-level HIM credentials, CHDA assumes you're already working with data pipelines, governance policies, and stakeholder reporting — it validates the ability to turn raw healthcare data into decisions, not just organize records.
Eligibility: Two Pathways, Not One
AHIMA's CHDA eligibility requirement is a fork, not a checklist — you need to qualify through exactly one of these two routes:
- Pathway 1 — Credential Route: Hold a current RHIT® (Registered Health Information Technician) or RHIA® (Registered Health Information Administrator) credential. No specific years of experience are mandated on top of this.
- Pathway 2 — Degree Route: Hold a bachelor's degree or higher from a college or university accredited by a recognized accrediting body, in any field.
- Recommended, not required: Three years of experience working with healthcare data (analytics, reporting, acquisition, management, interpretation, or governance) is recommended by AHIMA as adequate preparation, but it is not a formal, verified eligibility gate the way the credential or degree requirement is.
The practical takeaway: an RHIT with zero years of formal "data analyst" job experience and a bachelor's degree holder from an unrelated field are both technically eligible to register. Whether either is prepared to pass at a 300 scaled-score threshold against 121 scored items is the real question — and that's a function of study, not paperwork.
Exam Format, Fees & Difficulty
| Detail | Specification |
|---|---|
| Total Questions | 142 (121 scored + 21 unscored pretest) |
| Time Limit | 3.5 hours (210 minutes) |
| Passing Score | 300 (scaled score) |
| Exam Fee (AHIMA Member) | $259 |
| Exam Fee (Non-Member) | $329 |
| Retake Fee | Same as initial exam fee |
| Certification Period | 2 years, with continuing education (CE) requirements for renewal |
The 21 pretest items are seeded randomly throughout the exam and are unscored — used only for AHIMA's own item-bank validation. You cannot identify which questions are pretest versus scored during the exam, so every item has to be treated as if it counts.
The 5-Domain Breakdown
| Domain | Weight |
|---|---|
| Data Acquisition and Management | 21-25% |
| Data Interpretation and Reporting | 20-24% |
| Business Needs Assessment | 19-23% |
| Data Analysis | 19-23% |
| Data Governance | 11-15% |
Data Acquisition and Management is the single heaviest domain, but the practical reading of this table is different from what most candidates expect walking in: four of the five domains cluster tightly between 19% and 25%, meaning there's no single domain you can skip or under-study without real risk. Data Governance is the outlier at 11-15% — smaller, but far from trivial, since it's also the domain candidates with a pure analytics background (rather than HIM background) tend to underestimate.
🎯 Want the Free CHDA Study Guide?
Get real-format practice questions with full rationale, delivered instantly by email. Get the Free CHDA Exam Prep Guide
The Gap Most CHDA Prep Content Skips
Generic CHDA study guides tend to treat the exam as a straight knowledge test — memorize definitions, know the formulas, move on. What AHIMA's own content outline and CHDA-specific prep sources actually emphasize is applied reasoning across a full data workflow, not isolated fact recall. Three areas candidates consistently underestimate:
- Data lineage and audit-trail reasoning. Questions frequently ask you to trace how data moves from source system to report, and to identify where a data quality issue could have originated — not just define what data lineage means.
- Stakeholder communication scenarios. A meaningful share of Data Interpretation and Reporting items are scenario-based: given a dataset and a non-technical audience, what's the appropriate way to present the finding? This is a skill, not a fact, and it's hard to cram for in the final week.
- Data governance beyond policy definitions. Governance questions go past "what is a data steward" into applied compliance situations — HIPAA-adjacent data-sharing scenarios, retention policy conflicts, and de-identification standards applied to real cases.
Timed practice that forces you to reason through scenarios — not just flashcard-style recall — is the single biggest lever for closing this gap before exam day.
Domain-Weighted Study Plan
- Data Acquisition and Management (21-25%). The top-weighted domain. Covers data sources, extraction methods, data quality validation, and the technical mechanics of getting healthcare data into an analyzable state. Prioritize this first.
- Data Interpretation and Reporting (20-24%). Statistical interpretation, benchmarking, visualization choices, and translating findings for clinical and executive audiences. Practice scenario-based questions here specifically, not just definitions.
- Business Needs Assessment (19-23%). Understanding what a stakeholder is actually asking for, scoping an analytics request correctly, and identifying the right data sources and metrics before analysis begins.
- Data Analysis (19-23%). Core statistical and analytical methods — rates, ratios, risk adjustment, basic regression concepts — applied to healthcare-specific datasets.
- Data Governance (11-15%). Smallest domain by weight but not by risk. Data stewardship, compliance frameworks, retention and de-identification policy, and data security principles as they apply to healthcare data specifically.
Sample CHDA Exam Questions
Question 1 (Domain: Data Acquisition and Management)
A hospital's readmission report shows inconsistent patient counts compared to the source EHR system. What is the FIRST step an analyst should take to resolve this discrepancy?
- A. Immediately correct the report to match the EHR system's numbers
- B. Trace the data lineage from the EHR source through each transformation step to the report
- C. Assume the EHR system contains the error and ignore the report
- D. Rebuild the report from scratch without investigating the cause
Correct Answer: B. Before correcting any numbers, the analyst must trace data lineage — following the data from its source through every extraction, transformation, and load step — to identify exactly where the discrepancy was introduced. Jumping to a fix (A) or rebuilding blind (D) risks repeating the same error, and assuming either system is automatically correct (C) skips the actual diagnostic work the domain tests.
Question 2 (Domain: Data Interpretation and Reporting)
An analyst needs to present a statistically significant but clinically modest improvement in infection rates to a hospital board with no statistics background. What is the MOST appropriate approach?
- A. Present the raw p-value and confidence interval without further explanation
- B. Translate the finding into plain-language context, such as real-world impact and trend direction, alongside a simple visual
- C. Omit the finding since it is not highly significant
- D. Use only technical statistical terminology to maintain accuracy
Correct Answer: B. Effective healthcare data reporting for a non-technical audience means translating statistical findings into plain-language, decision-relevant context — what changed, why it matters, and what it means going forward — typically paired with a clear visual. Raw statistical output (A, D) fails the audience, and omitting a real finding (C) is not a valid response regardless of effect size.
Question 3 (Domain: Data Governance)
A data analyst receives a request to share a de-identified patient dataset with an external research partner. Which action is required BEFORE the data can be shared?
- A. Verify the de-identification method meets HIPAA Safe Harbor or Expert Determination standards
- B. Share the dataset immediately since it is already de-identified
- C. Add the research partner's name to the hospital's general data access list
- D. Convert the dataset to a PDF format before sharing
Correct Answer: A. Before sharing any dataset described as "de-identified," a data governance-conscious analyst must verify it actually meets a recognized standard — HIPAA's Safe Harbor method or Expert Determination — rather than assuming the label is accurate. File format (D) and general access-list changes (C) do not address the compliance requirement, and skipping verification (B) is the exact governance failure this domain tests for.
Final Verdict
The CHDA rewards candidates who can reason through a full data workflow — acquisition, analysis, interpretation, and governance — rather than those who've simply memorized definitions. With four of five domains clustered between 19% and 25%, there's no shortcut domain to skip, and the applied-reasoning format means timed, scenario-based practice matters more than flashcards in the final weeks. On eligibility: check which of the two pathways — the RHIT/RHIA credential or the bachelor's degree — actually applies to you, and don't let the "3 years recommended" language make you think you need to wait to register if you're otherwise ready.
📚 Recommended Study Resources & Video Tutorials
Access verified study guides and tutorial walkthroughs matching this certification:
- CHDA Exam Prep: Free real-format practice questions with full rationale for the AHIMA CHDA exam.