The only required component; usually containing a decimal point. Note that each component
of the MO data type (Section 2.A.41, "MO - money") is a subcomponent here. Bevat 2.16.840.1.113883.3.1937.777.10.15.33MO - Money (DYNAMISCH)
(CP_ype)
@Type
0 … 1
F
MO
@LongName
0 … 1
F
Price
hl7v2:CP.2
ID
0 … 1
A coded value, data type ID. Refer to HL7 Table 0205 - Price type for valid values. Bevat 2.16.840.1.113883.3.1937.777.10.15.83ID - Coded value for HL7 defined tables (DYNAMISCH)
(CP_ype)
@Type
0 … 1
F
ID
@Table
0 … 1
F
HL70205
@LongName
0 … 1
F
Price Type
hl7v2:CP.3
NM
0 … 1
Each is a NM data type; together they specify the "range". The range can be defined
as either time or quantity. For example, the range can indicate that the first 10
minutes of the procedure has one price. Another repetition of the data type can use
the range to specify that the following 10 to 60 minutes of the procedure is charged
at another price per; a final repetition can specify that the final 60 to N minutes
of the procedure at a third price.
Note that, if the <price type> component is TP, both <from value> and <to value> may be null.
A coded value, data type CE, defined by the standard table of units for either time
or quantity (see for example, the tables in Section 7.1.4, "Coding schemes"). This
describes the units associated with the range, e.g., seconds, minutes, hours, days,
quantity (i.e., count); it is required if <from value> and <to value> are present.
Refer to HL7 Table 0298 - CP range type for valid values. Bevat 2.16.840.1.113883.3.1937.777.10.15.83ID - Coded value for HL7 defined tables (DYNAMISCH)
Template CP - Composite price
Lab2Lab IN1 segment
The only required component; usually containing a decimal point. Note that each component
of the MO data type (Section 2.A.41, "MO - money") is a subcomponent here.
ype)