HL7 CDM Charge Description Master
HL7 field reference CDM fields from HL7 v2.5.1 Show fields
These are the generated fields for the version selected at the top of the page. The document stays the same, but the reference panel follows that version.
Fields
| Field | Name | Required | Repeatable | Type | Table |
|---|---|---|---|---|---|
| CDM.1 | Primary Key Value - CDM | Yes | No | CE | 0132 |
| CDM.2 | Charge Code Alias | No | Yes | CE | 9999 |
| CDM.3 | Charge Description Short | Yes | No | ST | |
| CDM.4 | Charge Description Long | No | No | ST | |
| CDM.5 | Description Override Indicator | No | No | IS | 0268 |
| CDM.6 | Exploding Charges | No | Yes | CE | 9999 |
| CDM.7 | Procedure Code | No | Yes | CE | 0088 |
| CDM.8 | Active/Inactive Flag | No | No | ID | 0183 |
| CDM.9 | Inventory Number | No | Yes | CE | 0463 |
| CDM.10 | Resource Load | No | No | NM | |
| CDM.11 | Contract Number | No | Yes | CX | |
| CDM.12 | Contract Organization | No | Yes | XON | |
| CDM.13 | Room Fee Indicator | No | No | ID | 0136 |
CDM is a charge-description master row, used to distribute charge codes, prices, descriptions, and effective dates.
Billing segments are where clinical activity starts turning into charge, reimbursement, and account data. They can look administrative, but a bad code or account reference can cause real downstream cleanup.
Treat charge codes, revenue codes, grouping values, effective dates, and account identifiers as controlled data. Free-text labels are useful for humans, but receivers usually post, price, or group from the coded values.
The v2.5.1 structures show CDM in MFN_M04 - Master files charge description and MFR_M04 - Master files charge description. That tells you where it can appear, but the implementation guide still decides which optional fields are meaningful.
For practical interface work, read the generated field panel for datatype, required, repeatable, and table details, then use the notes below to decide what the field should mean in the receiving workflow.
CDM-1 carries a measured, counted, priced, or dosed value. A number without the expected unit, currency, or companion qualifier is much easier to misread than an empty field.
The generated panel links this to HL7 table 0132; many real interfaces narrow that list further, so follow the receiver's implementation guide.
CDM-2 carries a measured, counted, priced, or dosed value. A number without the expected unit, currency, or companion qualifier is much easier to misread than an empty field.
The generated panel links this to HL7 table 9999; many real interfaces narrow that list further, so follow the receiver's implementation guide.
CDM-3 is human-readable context. Keep it useful for display and troubleshooting, but do not hide required workflow logic here unless the implementation guide explicitly says the receiver parses it.
CDM-4 is human-readable context. Keep it useful for display and troubleshooting, but do not hide required workflow logic here unless the implementation guide explicitly says the receiver parses it.
CDM-5 is human-readable context. Keep it useful for display and troubleshooting, but do not hide required workflow logic here unless the implementation guide explicitly says the receiver parses it.
The generated panel links this to HL7 table 0268; many real interfaces narrow that list further, so follow the receiver's implementation guide.
CDM-6 carries a measured, counted, priced, or dosed value. A number without the expected unit, currency, or companion qualifier is much easier to misread than an empty field.
The generated panel links this to HL7 table 9999; many real interfaces narrow that list further, so follow the receiver's implementation guide.
CDM-7 identifies the Procedure Code for this billing workflow. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
If there are several identifiers, use repetitions deliberately and make each repeat self-explanatory rather than relying on position alone.
CDM-8 carries Active/Inactive Flag for this billing workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
The generated panel links this to HL7 table 0183; many real interfaces narrow that list further, so follow the receiver's implementation guide.
CDM-9 identifies the Inventory Number for this billing workflow. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
If there are several identifiers, use repetitions deliberately and make each repeat self-explanatory rather than relying on position alone.
CDM-10 carries Resource Load for this billing workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
CDM-11 identifies the Contract Number for this billing workflow. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
If there are several identifiers, use repetitions deliberately and make each repeat self-explanatory rather than relying on position alone.
CDM-12 identifies an organization, clinic, facility, department, or company involved in this billing workflow. Keep the organization identifier and display name separate when the datatype supports it.
Repeats should represent genuinely separate organizations or aliases, not several fragments of the same name.
CDM-13 tells the receiver the state of this billing workflow. Status fields often drive workflow branches, so use the agreed code and do not infer a status just because another field looks complete.
The coded value should follow HL7 table 0136 or the narrower table in the local profile.
Related links
- FT1 - Financial Transaction
- DG1 - Diagnosis
- DRG - Diagnosis Related Group
- PR1 - Procedures
- PV1 - Patient Visit
- IN1 - Insurance
- IN2 - Insurance Additional Information
- IN3 - Insurance Additional Information, Certification
- MFN_M04 - Master files charge description
- MFR_M04 - Master files charge description