CMRS (ACAC) key terms

A structured examination of patient documentation to confirm that care was documented, supported, coded, and billed correctly. Reviewers compare the record against standards, policies, and payer rules and record findings for follow-up.

The original record entry that supports a reported fact, such as a progress note, operative report, or lab result. Reviewers rely on source documents rather than summaries or secondary reports when validating codes and charges.

The chronological record of who accessed, created, or changed documentation and when. It lets reviewers reconstruct events, detect late entries or alterations, and demonstrate that findings are traceable to evidence.

Documentation added after the fact to record care already delivered. Valid late entries are dated and timed when written, labeled as additions, and signed; unlabeled or backdated entries raise authenticity concerns during review.

The accuracy, completeness, and consistency of documentation and data across systems. Reviewers test integrity by comparing records, claims, and reports for mismatches, gaps, or unexplained changes.

An organizational or accreditor requirement describing what must be documented, by whom, and within what timeframe. Standards cover authentication, timeliness, amendments, and required elements for specific record types.

The process of verifying that a record entry was made or approved by the responsible author, typically through signature or a secure electronic credential. Missing or invalid authentication undermines the reliability of the documented information.

An evaluation of whether diagnosis and procedure codes, modifiers, and charges align with documented services and payer payment rules. The review tests accuracy, completeness, and support for each claim line.

The process of translating documented diagnoses and procedures into standardized codes. Correct assignment requires that the record contain the specificity the code set demands, such as laterality, severity, or approach.

A code element that clarifies or adjusts how a service or procedure is reported, such as indicating a distinct service or a professional versus technical component. Unsupported modifiers can cause overpayment or denials.

Reporting components of a service separately when a single comprehensive code should have been used, often to increase payment. Reviewers look for this pattern by comparing billed combinations against code-edit rules.

A payer or system rule that flags combinations of codes as inappropriate to bill together, or that requires a modifier to explain why both apply. Edits help reviewers identify potentially incorrect claim lines.

An automated pre-submission check that compares claims against edits, coverage rules, and data requirements. Scrubbing reduces avoidable denials but does not replace human review of documentation support.

A program that improves the precision, clarity, and completeness of provider documentation so that coded data and quality measures reflect the patient's true clinical picture without altering the record's meaning.

A compliant written or verbal request asking a provider to clarify or add documentation, such as linking a diagnosis to a condition. Queries must be non-leading, cite the evidence, and avoid suggesting a specific answer.

A clarification request that suggests or steers the provider toward a particular response, undermining record integrity. Compliant queries present the clinical facts neutrally and let the provider determine the answer.

The determination that a service is reasonable and needed for the patient's condition, consistent with accepted standards and payer coverage rules. Documentation must show the clinical rationale, not just the service performed.

The condition established after study to be chiefly responsible for the encounter. Correct selection drives payment, risk adjustment, and quality reporting, so reviewers test whether the record clearly supports it.

A legal or payer-imposed obligation governing billing, privacy, documentation, or program participation. Examples include conditions of participation, coverage policies, and anti-fraud statutes that reviews are designed to test.

A payer decision about whether a service is covered and payable for a given patient and circumstance. Reviewers compare documentation against published coverage criteria to judge whether billed services met those criteria.

An organization's structured set of policies, training, monitoring, and reporting channels designed to prevent and detect violations of law and payer rules. Effective programs include a code of conduct and a non-retaliation policy.

The defined boundaries of a review, including the period, populations, claim types, and objectives covered. A clear scope keeps sampling and conclusions defensible and prevents findings from being overgeneralized.

The complete set of records, claims, or providers from which a review population is drawn. Defining it accurately is essential because the universe determines what conclusions the sample can support.

Selecting a subset of records to represent a larger population when reviewing everything is impractical. Method choice affects whether results can be projected and how much confidence findings carry.

A selection method in which every item in the population has a known chance of being chosen. Random selection supports statistical projection of error rates to the full population.

Applying error rates found in a valid sample to the full population to estimate total overpayment or compliance risk. Extrapolation is defensible only when the sampling method supports it and is documented.

The proportion of reviewed items containing a compliance or coding error. It is calculated from the sample, reported with its basis, and used to prioritize corrective action and measure improvement over time.

Three related categories of improper conduct: intentional deception for gain, misuse of resources, and practices that cause unnecessary cost or poor quality. Distinguishing intent matters because consequences and remedies differ.

A request for payment that the submitter knows or should know is false or unsupported by the record. Liability can arise under false claims statutes even without proof of specific intent to defraud.

Any payment exceeding what is due for services actually rendered and documented. Identified overpayments generally must be reported and returned within defined timeframes once identified.

Legal safeguards that prohibit retaliation against individuals who report suspected fraud or compliance violations in good faith. These protections encourage internal reporting and are a core element of an effective compliance program.

A documented conclusion that a reviewed item did or did not meet a stated standard, supported by evidence and criteria. Findings should state the condition, the requirement, the effect, and the recommended action.

The written communication of scope, methodology, findings, and recommendations from a review. A strong report is objective, evidence-based, and clear enough for both operational and executive readers to act on.

A documented set of steps, owners, and deadlines to fix the root cause of a finding and prevent recurrence. Effective plans include measurable milestones and a follow-up method to verify the fix worked.

A structured method for identifying the underlying process failure that produced an error rather than only describing the symptom. Its output shapes corrective actions that prevent repeat findings.

The duty to protect patient and organizational information from unauthorized access or disclosure. Reviewers access only what the assignment requires and follow minimum-necessary and secure-handling practices.

The principle that access to and disclosure of protected information should be limited to what is needed for the specific purpose. Reviewers apply it by requesting only relevant records and redacting unrelated content.

Individually identifiable health information held or transmitted by a covered entity or business associate. Its use and disclosure are governed by privacy and security rules that reviewers must follow during audits.

The requirement that reviewers reach conclusions free from influence by the people or functions being reviewed. Independence protects objectivity and is supported by reporting lines and separation of audit from operational duties.

An impartial mindset in which conclusions rest on evidence and criteria rather than personal preference or pressure. Objectivity requires honesty about limitations and willingness to report unfavorable results.

A situation in which a reviewer's personal, financial, or professional interest could bias judgment. Reviewers disclose such situations and recuse themselves from assignments where impartiality could be questioned.