The RXV segment details the pharmacy or treatment application’s encoding of specific infusion order parameters
| Seq# | DataElement | Description | Must Implement | Flags | Cardinality | Length | C.LEN | Vocabulary | DataType |
|---|---|---|---|---|---|---|---|---|---|
RXV
|
|||||||||
1
|
03318 | Set ID - RXV | [0..1] | SI | |||||
|
2
|
03319 | Bolus Type | SHALL | [1..1] | [1..1] | ID | |||
|
3
|
03320 | Bolus Dose Amount | [0..1] | NM | |||||
|
4
|
03321 | Bolus Dose Amount Units | [0..1] | CWE | |||||
|
5
|
03322 | Bolus Dose Volume | = | [0..1] | 20 | NM | |||
|
6
|
03323 | Bolus Dose Volume Units | [0..1] | CWE | |||||
|
7
|
03324 | PCA Type | SHALL | [1..1] | [1..2] | ID | |||
|
8
|
03325 | PCA Dose Amount | = | [0..1] | 20 | NM | |||
|
9
|
03326 | PCA Dose Amount Units | [0..1] | CWE | |||||
|
10
|
03327 | PCA Dose Amount Volume | = | [0..1] | 20 | NM | |||
|
11
|
03328 | PCA Dose Amount Volume Units | [0..1] | CWE | |||||
|
12
|
03329 | Max Dose Amount | = | [0..1] | 20 | NM | |||
|
13
|
03330 | Max Dose Amount Units | [0..1] | CWE | |||||
|
14
|
03331 | Max Dose Amount Volume | = | [0..1] | 20 | NM | |||
|
15
|
03332 | Max Dose Amount Volume Units | [0..1] | CWE | |||||
|
16
|
03333 | Max Dose per Time | SHALL | [1..1] | CQ | ||||
|
17
|
03334 | Lockout Interval | [0..1] | CQ | |||||
|
18
|
03339 | Syringe Manufacturer | [0..1] | CWE | |||||
|
19
|
03385 | Syringe Model Number | [0..1] | CWE | |||||
20
|
03386 | Syringe Size |
MAY
True:
False:
|
C= |
[1..1] [0..1] |
20 | NM | ||
|
21
|
03431 | Syringe Size Units |
MAY
True:
False:
|
C |
[1..1] [0..1] |
CWE | |||
|
22
|
00816 | Action Code | [0..1] | [2..2] | ID | ||||
Definition: For the first timing specification transmitted, the sequence number shall be 1; for the second timing specification, it shall be 2; and so on.
Definition: This field identifies the type of bolus being ordered. See HL7 Defined Table 0917 – Bolus Type in Chapter 2C, Code Tables, for example values.
Definition: This field contains the ordered bolus amount. For example, if the ordered bolus is 50 mg, this field contains the value of 50.
Definition: This field indicates the amount units associated with the bolus dose amount. The preferred coding system is MDC; UCUM are also acceptable. Refer to Table 0767 - Bolus Dose Amount Units in Chapter 2C for valid values.
Examples:
263890^MDC_DIM_MILLI_G^MDC
mg^milligram^UCUM
Definition: This field defines the volume measurement for the ordered bolus amount. For example, if the ordered bolus is 5 ml, this field contains the value of 5.
Definition: This field indicates the amount units associated with the bolus dose volume. The preferred coding system is MDC; UCUM are also acceptable. Refer to Table 0768 - Bolus Dose Volume Units in Chapter 2C for valid values.
Examples:
263890^MDC_DIM_MILLI_G^MDC
mg^milligram^UCUM
Definition: This field identifies the type of bolus being ordered. See HL7 Defined Table 0918 – PCA Type in Chapter 2C, Code Tables, for example values.
Definition: This field contains the order’s PCA dose amount. Example: if the ordered bolus is 3 mg, this field contains the value of 3.
Definition: This field indicates the amount units associated with the PCA dose amount. The preferred coding system is MDC; UCUM are also acceptable. Refer to Table 0769 - PCA Dose Amount Units in Chapter 2C for valid values.
Examples:
263890^MDC_DIM_MILLI_G^MDC
mg^milligram^UCUM
Definition: This field defines the volume measurement for the ordered PCA amount volume. For example, if the ordered bolus is 5 ml, this field contains the value of 5.
Definition: This field indicates the amount units associated with the PCA dose volume. The preferred coding system is MDC; UCUM are also acceptable. Refer to Table 0770 - PCA Dose Amount Volume Units in Chapter 2C for valid values.
Examples:
263890^MDC_DIM_MILLI_G^MDC
mg^milligram^UCUM
Definition: This field contains the order’s maximum dose amount. For example, if the ordered bolus is 50 mg, this field contains the value of 50.
Definition: This field indicates the amount units associated with the maximum dose volume. The preferred coding system is MDC; UCUM are also acceptable. Refer to Table 0772 - Max Dose Amount Units in Chapter 2C for valid values.
Examples:
263890^MDC_DIM_MILLI_G^MDC
mg^milligram^UCUM
Definition: This field defines the volume measurement for the ordered max dose amount. For example, if the ordered bolus is 5 ml, this field contains the value of 5.
Definition: This field indicates the amount units associated with the maximum dose volume. The preferred coding system is MDC; UCUM are also acceptable. Refer to Table 0773 - Max Dose Amount Volume Units in Chapter 2C for valid values.
Examples:
263890^MDC_DIM_MILLI_G^MDC
mg^milligram^UCUM
Definition: This field contains the time unit expression of the lock out parameter. For example, if the ordered max dose per time is 4 hours, this field format is "4^h&hours&UCUM".
Definition: This field contains the length of time that must expire between deliveries of PCA doses. For example, if the ordered max dose per time is 10 minutes, this field format is "10^min&minute&UCUM".
Definition: This field contains the manufacturer of the syringe containing the ordered medication.
Definition: This field contains the model number of the syringe containing the ordered medication.
Definition: This field contains the syringe’s numeric total volume size.
Definition: This field indicates the amount units associated with the syringe size. The preferred coding system is MDC; UCUM are also acceptable.
Examples:
263890^MDC_DIM_MILLI_G^MDC
mg^milligram^UCUM
(Definition from OH1.2 in Ch. 3)
Definition: This field contains a code defining the action to be taken for this segment. It allows this segment to be sent to delete or update, for example, previously sent information. Refer to HL7 Table 0206 – Segment Action Code in Chapter 2C, Code Tables, for valid values.
(Definition from OH2.2 in Ch. 3)
Definition: This field contains a code defining the action to be taken for this segment. It allows this segment to be sent to delete or update, for example, previously sent information. Refer to HL7 Table 0206 – Segment Action Code in Chapter 2C, Code Tables, for valid values.
(Definition from OH3.2 in Ch. 3)
Definition: This field contains a code defining the action to be taken for this segment. It allows this segment to be sent to delete or update, for example, previously sent information. Refer to HL7 Table 0206 – Segment Action Code in Chapter 2C, Code Tables, for valid values.
(Definition from OH4.2 in Ch. 3)
Definition: This field contains a code defining the action to be taken for this segment. It allows this segment to be sent to delete or update, for example, previously sent information. Refer to HL7 Table 0206 – Segment Action Code in Chapter 2C, Code Tables, for valid values.
(Definition from ORC.35 in Ch. 4)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when either ORC-2 and/or ORC 3 is valued with a unique identifier in accordance with Chapter 2, Section 2.10.4.2.
(Definition from OBR.55 in Ch. 4)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when either an OBR-2 and/or OBR-3 is valued with unique identifier in accordance with Chapter 2, Section 2.10.4.2.
(Definition from IPC.10 in Ch. 4)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when the combination of IPC-1, IPC-2, IPC-3, and IPC-4 represents a unique identifier according to Chapter 2, Section 2.10.4.2.
(Definition from BPX.22 in Ch. 4)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when an BPX is uniquely identified sufficiently within the specific implementation using BPX-17 or BPX-6 as agreed to by the trading partners and in accordance with Chapter 2, Section 2.10.4.2.
(Definition from BTX.21 in Ch. 4)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when an BTX is uniquely identified sufficiently within the specific implementation using BTX-20 or BTX-3 as agreed to by the trading partners in accordance with Chapter 2, Section 2.10.4.2.
(Definition from DON.34 in Ch. 4)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when an DON is uniquely identified sufficiently within the specific implementation using DON-1 in accordance with Chapter 2, Section 2.10.4.2.
(Definition from BUI.13 in Ch. 4)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when an BUI is uniquely identified sufficiently within the specific implementation using BUI-2 in accordance with Chapter 2, Section 2.10.4.2
(Definition from RXV.22 in Ch. 4A)
Definition: The intended handling by the receiver of the infusion order is represented by this segment. Refer to HL7 Table 0206 – Segment Action Code in Chapter 2C, Code Tables, for valid values.
(Definition from CDO.2 in Ch. 4A)
Definition: The Action Code indicates whether the cumulative dosage segment is intended to be added, deleted, updated, or did not change. If the field is not valued in any CDO segments for the order, the segments are considered to have been sent in snapshot mode. If some but not all CDO segments for the order do not have the action code valued, the default value is Add. Refer to HL7 Table 0206 - Segment Action Code in Chapter 2C, Code Tables, for valid values.
(Definition from OBR.55 in Ch. 7)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when an either OBR-2 and/or OBR-3 is valued with unique identifier in accordance with Chapter 2, Section 2.10.4.2.
(Definition from OBX.31 in Ch. 7)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when an OBX-21 is valued in accordance with guidance in Chapter 2, Section 2.10.4.2.
(Definition from SPM.35 in Ch. 7)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when an SPM-2 or SPM-31 is valued in accordance with the guidance in Chapter 2, Section 2.10.4.2.
(Definition from PRT.2 in Ch. 7)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0287 – Problem/goal action code for valid values.
(Definition from CSR.17 in Ch. 7)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when CSR-1 and CSR-4, or CSR-2 and CSR-5 are valued as agreed to by the trading partners in accordance with the guidance in Chapter 2, Section 2.10.4.2.
(Definition from CTI.4 in Ch. 7)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when CTI-1 is valued in accordance with the guidance in Chapter 2, Section 2.10.4.2.
(Definition from SHP.12 in Ch. 7)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when SHP-1 is valued in accordance with the guidance in Chapter 2, Section 2.10.4.2.
(Definition from PAC.9 in Ch. 7)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when PAC-2 is valued in accordance with the guidance in Chapter 2, Section 2.10.4.2.
(Definition from GOL.1 in Ch. 12)
Definition: The action code field gives the intent of the problem or goal. Refer to HL7 Table 0287 – Problem/Goal Action Code in Chapter 2C, Code Tables, for valid values.
(Definition from PRB.1 in Ch. 12)
Definition: This field contains the intent of the message. Refer to HL7 Table 0287 – Problem/Goal Action Code in Chapter 2C, Code Tables, for valid values.
(Definition from PTH.1 in Ch. 12)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0287 – Problem/Goal Action Code in Chapter 2C, Code Tables, for valid values.
(Definition from DEV.1 in Ch. 17)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0287 – Problem/goal action code for valid values.
®© HL7.org 2019+. HL7 v2+ generated on December 11, 2020
Links:
Version History
|
Propose a change
|
License
The Demo site for our new HL7 Version 2+ (plus) Standard
