Editorial Policy

Why this policy exists

This page explains how content in this resource is researched, drafted, reviewed, corrected, disclosed, and kept current, so you can judge for yourself how far to trust any page here. A policy that promises reviews that did not happen is worse than no policy, so the aim is simple: every commitment below is meant to be true in operation before it appears on a published page.

You do not need any background to read this. It is written for the same people the rest of the resource is written for — beginners, career changers, certification candidates, students in a formal program, and returning or working learners — plus the educators and reviewers who want to know how the material is made.

What this resource is for, and what it is not

This is independent educational material about medical billing and coding. It is built to help you learn concepts and reading skills. It is not advice for a specific situation, it is not a substitute for a licensed reference or official guidance, and it does not train or authorize you to code, bill, submit claims, access patient records, or interpret law or compliance for an employer. Where a real decision is involved, the controlling authority is always the applicable employer policy, official guidance, the current licensed reference, or a qualified professional — never a page here.

Editorial independence

Decisions about what to cover, how to describe it, and what to recommend are made on educational grounds. No credentialing organization, coding-system publisher, government agency, testing vendor, training provider, employer, or advertiser directs the content. Organizations are named only so you can identify and verify things, never because they sponsor or endorse the material.

If this project ever accepts sponsorship, an affiliate arrangement, free materials, a partnership with a training provider, or support from a credentialing organization, that relationship will be disclosed on the pages it affects and in this policy, and it will not quietly shape an educational recommendation. See conflicts of interest and disclosures below.

How sources are chosen and verified

Facts here are meant to come from the source that actually controls them, in this order of authority:

1. The primary, controlling source. The issuing organization for a credential's own rules; the government agency for a program it administers; the official publisher for a code set; a payer for its own policy; an employer for its own workflow.
2. Official professional organizations, then public academic and institutional sources, and public labor data, each with a full citation.
3. Separately verified secondary educational material, only after the sources above.

Commercial exam-preparation products, forums, social media, and the output of AI tools are never treated as sources for a fact. A higher-authority source wins over a lower one. When two sources genuinely conflict, a page states the ambiguity rather than resolving it by opinion.

A source found is not a claim verified. Locating a document that seems to support a statement is not the same as confirming the statement is currently true. Every change-sensitive claim — a fee, a count, a limit, a score, an eligibility rule, a renewal or continuing-education value, a policy or effective date, a payer rule, a statistic, an organization's current list, a URL — is checked against its controlling source immediately before that page is published, and it carries the date it was last verified and the source version it was checked against. Stable subject matter (how a concept works, what a term means) is confirmed once against a standard reference and taught plainly.

Content states, and what "last reviewed" means

Every piece of content is in exactly one recorded state, and it moves through them in order:

Planning → Draft → Source Review → Technical Review → Compliance Review → Accessibility Review → Approved → Published → Needs Update → Retired

Three plain rules govern those states:

• Generated is not verified. A finished draft — including one an AI tool helped write — is unchecked until a person verifies it.
• Verified is not approved. Confirming the facts is one step; a page still has to pass technical, compliance, and accessibility review.
• Approved is not published. Approval is recorded before a page goes live, and only a published page is presented to you as reviewed.

A page in Planning or Draft is never shown as if it were reviewed. Needs Update is entered when something changes or a reader reports a problem; the affected claims are re-checked before the page is trusted again. Retired content is taken out of navigation and search with a note saying why it was retired and what replaced it.

"Last reviewed" is the date a person last verified that page's change-sensitive claims against their controlling sources. It is not the date the page was written or last edited, and it is not a promise that nothing has changed since. A page that has not finished review shows a pending-review note instead of a date. When you see a real date, treat it as: someone last checked the change-sensitive facts on this day; verify anything you are about to act on against the official source yourself.

Who reviews what

Reviews are done by people in defined roles, and a name and date are recorded when each review is signed off. One person may hold more than one role, but no one signs off a review they did not perform, and the writer never performs the technical review of their own draft.

• Writer — drafts the page from its plan and records the claims and the sources behind them.
• Source verifier — checks each change-sensitive claim against its controlling source and keeps the verification log.
• Technical reviewer — a person with documented professional experience or a current, relevant credential in the page's area (coding, billing, compliance, or hiring and careers), who confirms the content is accurate and correctly limited by setting, payer, code year, and credential.
• Compliance and intellectual-property reviewer — confirms there is no proprietary content, no patient information, no framing that could enable fraud, no guarantees, no continuing-education claims, and correct non-affiliation wording, and records the trademark review.
• Accessibility reviewer — checks the page against the accessibility baseline.
• Learner-perspective reviewer — records how the page reads for a beginner, an adult learner, and a student using it.
• Editor — confirms the quality checklist and the state changes, and owns corrections.

A failed review sends the page back to Draft. If a legal or compliance question comes up, the page is held in Draft, a qualified legal or compliance reviewer resolves it, and the resolution is recorded before the page moves forward.

How the resource is kept current

There is no single review calendar. Each page carries the specific triggers that should bring it back for re-checking — for example, a credential-policy change, a code-year or guideline release, a new edition of a reference, a change in government policy, a labor-data release, a broken or changed link, or a reported correction. When a trigger fires, the affected pages move to Needs Update, the affected claims are re-verified, and the review dates and change notes are updated. Links are checked before a page is published and again whenever a trigger fires. Certification pages are additionally re-checked whenever the issuing organization announces a change to eligibility, designations, delivery, fees, renewal, or continuing-education requirements.

How corrections work, and how to report an error

Corrections are never made silently. When something is wrong, it is fixed in the open and the change is recorded. The process is:

issue reported → claim reviewed → primary source checked → correction approved → content updated → metadata updated → material change documented

Anyone can start it — a reader, a reviewer, or a contributor. The editor logs the report, the claim is reviewed against the source that controls it, and the correction is approved by the editor, with technical review when the change is substantive. The content is updated, the "Last reviewed" date and version are updated, and any material change is noted visibly on the page so you can see what changed. A pattern of readers being confused, even without a factual error, is also treated as a defect and sent back to revise the page's plan.

To report a possible error: send the page title or address, the exact wording you are questioning, and — if you have it — the official source you believe is correct, to the resource's published contact channel. (This Draft does not yet display that contact address; the published policy will name the specific way to reach the editor. Until then, this section defines the process the global disclaimer's "report a possible error" line points to.)

How AI tools are used in drafting, and their limits

AI tools may help draft structure, wording, and summaries. They are held to firm limits, and their use is disclosed here in plain terms:

• Text an AI tool helped write is not verified, not approved, and not publishable until it passes the full workflow above. Generated is not verified; verified is not approved; approved is not published.
• Every factual claim in AI-assisted text is checked by a person against the controlling source. Any citation an AI tool suggests is opened and checked as if it were an anonymous forum post; if it cannot be verified, it is removed rather than softened.
• AI tools are never used to reconstruct proprietary content, such as code descriptors, exam questions, or commercial study materials.
• No patient information and no employer-confidential information is ever entered into an AI tool.
• An AI tool is never allowed to invent coding, billing, or compliance guidance. Certification details are always checked directly against the issuing organization.
• Practice questions drafted with AI assistance are rewritten by a person and must pass originality review.

Conflicts of interest and disclosures

Anyone who works on a page discloses any financial or professional relationship with an organization named in that content — a credentialing organization, a publisher, a training provider, an employer, or a vendor. A person with such a relationship does not perform the technical or compliance review of that content. Any sponsorship, affiliate link, free material, partnership, or organizational support is disclosed on the pages it affects and in this policy. Resource listings disclose their cost model and any relationship. If paid placement ever exists, it is labeled as such and is never presented as an editorial recommendation.

Non-affiliation

This resource is independent. It is not affiliated with, endorsed by, sponsored by, or approved by any credentialing organization, coding-system publisher, government agency, testing vendor, or training provider. Names are used for identification only. Verify every credential requirement with the issuing organization before acting.

How sources are cited

Published pages cite the organization and the document behind each verified claim, with the official link and the date it was verified. Statistics carry full data-citation details. Secondary sources are never cited for a rule. Citations are not padded, and a source that was not actually consulted is not cited. While a page is still in draft, a change-sensitive value may appear only inside the marker, which the pre-publication check replaces with a last-verified date and version — so a published page never carries that marker.

Practice content is original

Every practice question here is original educational material, written from documented learning objectives, with per-item documentation, an originality review, and its own retirement triggers. No recalled, leaked, copied, or closely paraphrased exam or commercial content is ever used. Practice is labeled as original educational content, not official exam content, and completing it is not evidence of exam or job readiness.

Accessibility commitment

Every page is meant to meet an accessibility baseline: a clear heading structure, short sections, descriptive links, alternative text for anything visual, no meaning carried by color alone, expanded acronyms, tables that read line by line, and plain-language support that does not strip out the correct terminology. Accessibility review is a required state a page must pass, not an optional courtesy.

Privacy commitment

No content contains patient information or real-looking identifiers; all examples are fictional (for instance, Patient A, Clinic X, Health Plan Y). If this resource ever adds an interactive feature, that feature will follow privacy-conscious defaults and will publish its own privacy disclosure before it launches.

When content is retired

A page is retired when its subject is no longer accurate and cannot be reasonably updated, when the source that controlled it is withdrawn, when a newer page replaces it, or when review finds it unsafe to keep. A retired page leaves a short note with the reason and the replacement, and internal links are updated to point to what replaced it. Practice questions are retired one at a time under the same idea.

What this policy does not claim

To be clear about the boundaries of this page: it does not claim that any specific page here has already been reviewed, it does not claim accreditation, it does not claim continuing-education or continuing-education-unit credit, and it does not claim affiliation with or endorsement by any organization. It describes the standard every page is held to. This policy page is itself a Draft and has not completed that standard yet.