Maintaining the Structure and Accuracy of Charge Data
A patient can receive a correctly documented service, have the right procedure code assigned, and still end up with an inaccurate charge. Sometimes the problem isn't in the clinical record or the claim itself. It is in the configuration connecting the two.
The Charge Description Master (CDM), often called the chargemaster, is one of those connections. It helps translate an organization’s billable services, items, and supplies into structured charge information. A seemingly small change to a CDM record can influence thousands of subsequent transactions if that item is used frequently.
The CDM connects operational charge selection with billing fields, prices, revenue codes, and other configuration. A discrepancy on the finished claim may be the first visible sign that a master record or its maintenance controls need review.
The CDM as a Billing Control
A CDM is an organization-maintained catalog of chargeable services, procedures, supplies, and other items. In a hospital setting, it commonly contains internal item identifiers, descriptions, departments, prices, and coding or billing attributes used by connected systems. The precise fields depend on the institution, its services, and how the CDM interfaces with charge capture and patient accounting.
The CDM is sometimes called a price list, but that description is incomplete. A record may do more than state a dollar amount. It can identify the charge to use for a specific item, connect that item to a revenue code or applicable HCPCS code, define the charge unit, and control when the item is available. HFMA’s revenue-cycle education illustrates the CDM as a combination of charge, coding, department, and volume information.[1]
| Concept | Meaning in practice | What it does not mean |
|---|---|---|
| Internal CDM item | A hospital-specific record that represents a service or item for charging. | Not a universal industry code shared by every hospital. |
| Gross charge | The organization’s established charge for the item or service. | Not necessarily the contracted allowed amount or the amount collected. |
| HCPCS/CPT relationship | A billing code associated with an item when applicable. | Not proof that a service is documented, covered, or separately payable. |
| Revenue code | An institutional claim code indicating a category of service or cost center. | Not a replacement for a required procedure code or an internal department ID. |
| CDM maintenance | Controlled review of charge-related record attributes and effective dates. | Not unrestricted authority for any staff member to change prices or coding. |
CDM, coding, charge capture, and claims are different layers
Charge capture identifies what was actually provided. The CDM helps turn supported activity into charge records. Coding validates the applicable classification of services and diagnoses. Billing assembles the information into a claim, where payer and claim-level edits may still apply. These processes can overlap within one system, but they don't become interchangeable simply because they share data.
Where the CDM Fits in the Revenue Cycle
CDM decisions can affect a service well before a bill is produced. Department managers, clinical operations, purchasing, pharmacy, laboratory, radiology, coding, finance, information technology, patient accounting, and revenue integrity may all contribute information used to establish or maintain charge records. The exact ownership model varies by organization.
From performed service to billed charge
- A department documents or otherwise records the service, procedure, medication, or supply that was actually provided.
- The relevant department or clinical system identifies the billable item and may send an item identifier, quantity, date, and encounter details.
- A charge engine or patient accounting system uses configured mapping to identify a CDM record and its charge attributes.
- Validation processes can hold, reject, or route records when identifiers, units, required coding data, or account information do not agree.
- Supported charge lines proceed to claim preparation; coding and billing perform additional checks appropriate to the setting and payer.
- The payer processes the submitted claim using applicable coverage, payment, and contract rules.
A missing charge may originate in documentation, a department feed, charge mapping, a held transaction, or the CDM itself. Finding the missing line in a billing report is the beginning of the investigation, not a diagnosis of its cause.
Who owns the decision?
| Role or team | Typical contribution | Review boundary |
|---|---|---|
| Service department | Confirms the item or service, intended unit, and operational use. | Should not independently decide billing codes outside assigned authority. |
| Coding / HIM | Assesses coding rules and documentation implications. | May not own charge pricing or system deployment. |
| Revenue integrity / CDM team | Coordinates item requests, field validation, maintenance controls, and reviews. | Changes may still require financial, coding, or operational approvals. |
| Finance / contracting | Reviews pricing policy and financial effects; contracting validates payer terms as needed. | Gross charges are not the same as contracted reimbursement. |
| IT / interfaces / patient accounting | Builds, tests, and deploys approved configurations and mappings. | Technical ability to change a field does not itself authorize a policy decision. |
| Compliance / audit | Evaluates relevant regulatory, documentation, and control risks. | Does not replace designated clinical or coding judgment. |
What Information Is Stored in a CDM?
There is no universal CDM column layout. Even the same health system may use different linked applications for departmental items, medication records, and billing charge records. The following fields illustrate what a reviewer might encounter.
| CDM field | What to examine | Example review question |
|---|---|---|
| Internal item / charge ID | Unique item identifier and whether it is active. | Does the department feed reference this exact ID? |
| Description | Service name and clarity for the intended users. | Could two similarly named entries be selected incorrectly? |
| Department / cost center | Operational ownership and routing. | Is the charge coming from the correct department? |
| Revenue code | Institutional service category assigned when applicable. | Does the designated coding team approve this relationship? |
| CPT / HCPCS and modifier | Applicable code association, if required or maintained. | Is the code current and supported for this service? |
| Charge amount | Gross charge per defined CDM unit. | Was the new price properly approved and loaded? |
| Unit of charge | Whether one unit means one item, dose, quantity, time increment, or another defined measure. | Does quantity 2 represent two billable units? |
| Effective / end date | Period when the record or attribute is valid. | Will transactions for an earlier date select the intended version? |
| Status / flags | Active, inactive, chargeable, review, or other local designations. | Is the entry blocked or available only for specific settings? |
| Interface / source mapping | Crosswalk to a departmental catalog or automated feed. | Does the source code point to the right CDM item? |
Understanding units is especially important
A CDM amount only becomes meaningful when its unit is understood. If a department reports one administration containing two units of a supply, the billing quantity should reflect the relevant charge-unit definition and reporting rules. The clinical quantity, CDM charge quantity, and claim units may not always be numerically identical.
Building or Updating a CDM Record
A dependable change process begins with a business reason and ends with evidence that the change reached the expected accounts correctly. Individual hospitals use different request forms and approval chains, but a controlled workflow often contains the following activities.
Step 1: Identify the requested change
A new procedure, discontinued supply, department relocation, updated code, price review, changed charging unit, or repeated interface error may trigger a request. The request should identify the exact item, proposed change, requested effective date, and supporting records. A vague instruction such as “fix the lab charge” is not enough to protect other transactions using similar descriptions.
Step 2: Validate service and coding details
Confirm the clinical or operational description with the owning department. Route HCPCS/CPT, revenue-code, modifier, or related coding questions to qualified reviewers. A CDM field cannot make unsupported reporting appropriate merely because the system permits a value.
Step 3: Review pricing and financial implications
Where pricing changes are proposed, determine the governing pricing policy and approval authority. Examine volumes, related or duplicate charge items, and expected downstream impacts. A hospital charge amount may differ from allowed reimbursement, and not every reimbursement methodology changes when the gross charge changes.
Step 4: Approve and control the effective date
Record the requested value, approved value, approver, reason, and effective date. Depending on system functionality, retain a version history or other audit trail. Pay special attention to date-of-service logic: a newly deployed record shouldn't silently rewrite historical transactions unless a defined correction process requires it.
Step 5: Test before and after deployment
Use a non-production environment when available, or another approved test process. Verify item lookup, mapping, quantity behavior, charges, code fields, claim output, and exception handling. Where multiple systems are involved, testing only the CDM maintenance screen is insufficient.
Step 6: Communicate, reconcile, and monitor
Tell affected departments what changed and when. Review sample post-change transactions and compare expected results with actual charges. Document unexpected issues, assign ownership, and resolve or escalate them before treating the change as complete.
| Change-control evidence | Purpose |
|---|---|
| Request / ticket ID | Connects the change to its approved business reason. |
| Old and new values | Makes the precise modification reviewable. |
| Approvals | Shows decisions were made by authorized owners. |
| Effective date and deployment time | Distinguishes intended dates from actual implementation. |
| Test cases and results | Demonstrates the mapping, quantity, coding, and charge outcomes. |
| Post-deployment validation | Shows that live transactions behaved as intended. |
| Exception log / rollback plan | Supports controlled response if the change creates errors. |
Worked Example: A CDM Mapping Change
The following fictional case demonstrates the mechanics of a controlled update. The codes and amounts are illustrative rather than coding advice for any particular service.
| Record / observation | What the reviewer sees | Interpretation |
|---|---|---|
| Department completion log | 12 RAD-220 exams documented. | Source activity appears to exist. |
| Charge transaction queue | 9 mapped to a valid CDM item; 3 rejected for unmapped source ID. | Some transactions reached billing, but three require investigation. |
| Approved charge definition | $420 per supported exam. | Expected gross charges for 12 exams: 12 × $420 = $5,040. |
| Accepted charges | 9 × $420 = $3,780. | Accepted charge amount is $1,260 below the expected total. |
| Pending exceptions | 3 × $420 = $1,260 if all three services and quantities are confirmed. | The arithmetic identifies potential impact; it does not by itself authorize billing. |
How the discrepancy is resolved
- Match the three rejected transmissions to source completion records and their patient encounters.
- Confirm that RAD-220 is the intended item, that the CDM record and source mapping were approved, and that the rejection was not followed by a later successful transmission.
- Have the designated configuration owner correct the mapping through the approved change process, preserving effective-date and audit requirements.
- Reprocess or enter the three supported charges according to the organization’s policy, checking for duplicates first.
- Verify all 12 source services have appropriate charge records and that the actual item, unit, and charge fields are correct.
- Document the defect, affected dates, total supported corrections, testing, and follow-up monitoring.
The expected $1,260 difference helps prioritize investigation. The proper financial result depends on verified services, billing requirements, and any claim corrections that may already be needed. It should not be labeled a confirmed cash loss or reimbursement recovery.
Reconciliation: Totals Can Match While Transactions Are Wrong
CDM oversight isn't only a matter of whether the department’s activity report and charge totals agree. Aggregate numbers can conceal offsetting errors. Matching transactions at the appropriate item, encounter, service date, and unit level is often more revealing.
| Item | Documented units | Posted units | Difference | Gross charge implication |
|---|---|---|---|---|
| A ($200/unit) | 3 | 2 | 1 missing | Potential $200 omitted charge |
| B ($150/unit) | 2 | 4 | 2 excess | Potential $300 excess charge |
| Total | 5 | 6 | Not comparable as one item | Net $100 overstatement; two distinct errors |
To reconcile correctly, determine whether the apparent duplicates represent separate documented services, whether the unit definitions match, and whether the transmission or mapping was applied to the right source events. Netting discrepancies together can conceal inaccurate claim detail.
What reports are useful?
- Department activity and completion records, including unique event or transaction IDs.
- CDM item master and effective-date history.
- Charge transaction, exception, and correction logs.
- Interface acceptance and rejection reports.
- Patient accounting or billing charge line details.
- Claim edit or rejected-claim workqueues, where relevant.
Common CDM Errors and How to Investigate Them
The most useful troubleshooting question is not simply whether a CDM value looks wrong, but which source, transformation, or approval step produced the unexpected outcome. Different errors can create similar symptoms.
| Observed issue | First checks | Appropriate next action |
|---|---|---|
| Charge missing after a completed service | Documentation, source event ID, queue status, mapping and effective date. | Confirm the service and locate the failed step before authorized reprocessing. |
| Incorrect or obsolete code association | Effective code-set date, applicable setting, approved coding guidance. | Refer the code relationship for coding validation; update through change control. |
| Unexpected number of units | Source quantity, package or dose conversion, CDM charge unit, claim unit. | Correct the root mapping or documented quantity as authorized; validate affected transactions. |
| Wrong department or revenue category | Item owner, department mapping, claim field output. | Coordinate with appropriate operations, coding, and system teams. |
| Duplicate or near-identical CDM items | Item IDs, descriptions, status, transaction usage. | Determine whether items are legitimately distinct before retiring or redirecting one. |
| Price differs from approved schedule | Item version, gross-charge record, effective date, interface or account overrides. | Escalate to pricing/CDM owner and validate affected service dates. |
| Historical claim changes after update | Version history, date-selection logic, reprocessing activity. | Protect audit history and review whether correction or rollback is required. |
| Repeated rejected lines across encounters | Common source IDs, release dates, interface logs and error patterns. | Document a sample, assign a technical owner, and monitor post-fix rates. |
A correction is not complete until the result is verified
A ticket marked “resolved” is evidence that someone finished a task, not proof that the charging pathway is correct. Confirm sample source events and their posted lines, check the relevant dates, and assess whether the same error continues. When claims have already been submitted, correction may require a separate billing review rather than only a CDM change.
CDM Accuracy, Reimbursement, and Compliance
A charge amount isn't a promise of payment. Under a payer contract, reimbursement may depend on fee schedules, case rates, APCs, DRGs, percentages of charges, packaged services, or other defined methodologies. Some arrangements may make charge data particularly important, but it is still necessary to validate the actual contract and payer processing before calling a charge discrepancy an underpayment.
For certain Medicare outpatient claims, CMS’s Integrated Outpatient Code Editor performs claim-level checks and supports APC and payment-status assignments. The CDM helps supply charge data, but the downstream editor evaluates the claim under its own rules.[2] CMS also describes NCCI edits intended to address improper code combinations and units, which is another reason an internally accepted charge should not be assumed to be billable without review.[3]
Price transparency is related, but not the same as the CDM
CMS hospital price-transparency rules require applicable hospitals to publish specified standard-charge information, including gross charges, discounted cash prices, payer-specific negotiated charges, and other required amounts, using prescribed disclosure formats. That public machine-readable file is not simply an internal chargemaster exported unchanged. It has additional data elements, format requirements, and regulatory definitions.[4]
For 2026, CMS finalized updates to machine-readable-file reporting, including specified allowed-amount data elements where negotiated charges use percentages or algorithms. These requirements need to be checked against the current CMS template and implementation guidance rather than presumed to be fields in every internal CDM.[5][6]
Recognizing larger control failures
A single inaccurate item may call for an ordinary correction. Multiple related items with the same mapping problem, a sudden spike in zero-charge transactions, or errors beginning after a software release may justify a broader investigation. Staff can identify a pattern using authorized reports and escalate it. Determining financial exposure, changing enterprise interfaces, and approving recovery activity require the appropriate owners and evidence.
Detailed contract variance investigations, sustained leakage analysis, and corrective-control design belong in the Revenue Integrity & Contract Management guides. The foundational skill here is recognizing the difference between a charge-record error and a proven reimbursement problem.
Practical CDM Review Checklist
Use this as an educational reference for reviewing a charge item or a proposed change. Local workflows and approval requirements still control the actual actions.
- ☐Confirm the item’s unique ID, description, owning department, and intended service or supply.
- ☐Identify the authoritative source record showing the service or item was provided.
- ☐Check whether the record is active for the relevant date of service.
- ☐Review the applicable coding, revenue-code, and modifier attributes with qualified owners.
- ☐Verify charge units and any source-to-charge unit conversion.
- ☐Compare gross charge and requested changes to the approved schedule.
- ☐Confirm the source-system mapping and exception-handling behavior.
- ☐Find and document approvals, old/new values, and effective dates.
- ☐Test representative scenarios, including invalid, duplicate, or historical transactions.
- ☐Reconcile a post-change sample at the item and encounter level, not only by net dollars.
- ☐Determine whether already billed accounts require a separate authorized correction.
- ☐Document unresolved exceptions, ownership, and evidence that the issue stopped recurring.
Connecting CDM Knowledge to Other Revenue Cycle Work
The CDM lives at an intersection. Charge-entry teams may identify missing or mismapped items; coding reviews decide whether reporting attributes are appropriate; claims teams encounter downstream edits; revenue integrity monitors exception patterns; contract analysts determine how submitted charges interact with reimbursement agreements.
Our earlier Charge Entry & Charge Reconciliation guide teaches source-to-charge matching. CPT, HCPCS & ICD-10-CM Fundamentals and Modifiers & Coding Guidelines provide deeper classification context. The next Coding Edits & Documentation Requirements guide will examine additional validation before a claim proceeds. All are related, but none replaces controlled CDM maintenance.
A dependable chargemaster isn't defined by whether every item has a price populated. It is defined by whether the right supported activity reliably produces the right charge information through a traceable and appropriately controlled process.
References and Further Learning
The resources below support the technical and regulatory discussion in this guide. Requirements are specific to their stated scope and may change; confirm applicability and current versions before using them operationally.
References
| Source | What It Supports |
|---|---|
| 1. HFMA, Revenue Cycle Management and Revenue Calculations | CDM purpose, example fields, and organizational maintenance responsibilities. |
| 2. CMS, Integrated Outpatient Code Editor | Outpatient institutional claim editing, APC assignment, and claim-level validation. |
| 3. CMS, National Correct Coding Initiative | PTP edits and medically unlikely edits; why units and code relationships warrant validation. |
| 4. CMS, Hospital Price Transparency: Hospitals | Scope of the hospital standard-charge disclosure requirement and the types of standard charges reported. |
| 5. CMS, CY 2026 OPPS/ASC Final Rule: Hospital Price Transparency | 2026 machine-readable-file updates; distinguish public disclosure from the internal CDM. |
| 6. CMS, Hospital Price Transparency Templates and Data Dictionary | Technical formats and field definitions for hospital machine-readable price-transparency files. |
Additional Learning
| Resource | What You’ll Learn |
|---|---|
| CMS, Hospital Price Transparency Resources | Implementation guidance, FAQs, and training for hospitals. |
| CMS, Outpatient Code Editor | Understand how claim edits and APC-related outputs are evaluated. |
| HFMA, Revenue Cycle Management and Revenue Calculations | Explore the relationship between revenue integrity, CDM, and operational reporting. |
Educational Disclaimer
Revenue Cycle Uncovered is an independent educational resource. Content is provided for general informational purposes and does not represent the policies, practices, or positions of any employer or organization. Workflows, payer requirements, regulations, and operational practices may vary. Information should be independently verified when applied to specific situations.