HL7 CP Composite Price
HL7 datatype components CP components from HL7 v2.5.1 Hide components
These are the generated components for the version selected at the top of the page. The article stays practical, and this panel follows the chosen HL7 version.
Components
| Pos | Component | Name | Type | Table | Description |
|---|---|---|---|---|---|
| 1 | CP.1 | Price | MO | Price; Type MO. | |
| 2 | CP.2 | Price Type | ID | 0205 | Price Type; Type ID; HL7 table 0205. |
| 3 | CP.3 | From Value | NM | From Value; Type NM. | |
| 4 | CP.4 | To Value | NM | To Value; Type NM. | |
| 5 | CP.5 | Range Units | CE | Range Units; Type CE. | |
| 6 | CP.6 | Range Type | ID | 0298 | Range Type; Type ID; HL7 table 0298. |
CP carries a price as money plus optional price-type and range detail. It is not a clinical result value; it belongs in charge, billing, contract, and cost-related fields where the receiver needs to understand the amount and why it applies.
In this guide, CP appears in AUT.7, DG1.13, DRG.7, DRG.9, FT1.11, FT1.12 and related fields. That used-by list is a good reality check: the datatype is only half the story, and the field that uses it tells you the workflow.
The component panel above is expanded by default because most datatype pages are used as quick lookup pages. Start there for the exact HL7 v2.5.1 shape, then use the notes below for the practical gotchas.
CP-1 to CP-6: Component Quick Read
The generated component panel above is the formal quick lookup. The short version is below so you can scan the shape without counting carets by eye.
The table-backed components here are CP-2, CP-6. Keep those values to the table or value set your implementation guide names, especially when the field is crossing organization boundaries.
- CP-1 Price - Price. Type MO.
- CP-2 Price Type - Price Type. Type ID. Table 0205.
- CP-3 From Value - From Value. Type NM.
- CP-4 To Value - To Value. Type NM.
- CP-5 Range Units - Range Units. Type CE.
- CP-6 Range Type - Range Type. Type ID. Table 0298.
Practical Notes
Keep numeric values numeric. Do not mix display formatting, unit text, or currency labels into the number component when the datatype has a separate place for that meaning. A format validator for whole numbers or decimals is a simple way to catch this before the receiving system has to complain.
In HL7 Soup Web, click a field that uses CP and the interpretation view will show which component you are sitting in and where that value lives in the raw message. That is especially handy with compact datatypes because one missing caret can move every value after it.
Official and Reference Notes
For formal reference, compare the generated HL7 v2.5.1 panel above with the HL7 v2.5.1 datatype list and the HL7 Terminology data type code system. Local implementation guides can narrow allowed values, tables, and component usage.