18.4.149 RDS - Pharmacy/Treatment Dispense Message (Event O13) (4A.3.8)

The RDS message may be created by the pharmacy/treatment application for each instance of dispensing a drug or treatment to fill an existing order or orders. In the most common case, the RDS messages would be routed to a Nursing application or to some clinical application, which needs the data about drugs dispensed or treatments given. As a site-specific variant, the original order segments (RXO, RXE and their associated RXR/RXCs) may be sent optionally (for comparison).

The ORC must have the filler order number and the order control code RE. The RXE and associated RXCs may be present if the receiving application needs any of their data. The RXD carries the dispense data for a given issuance of medication: thus it may describe a single dose, a half-day dose, a daily dose, a refill of a prescription, etc. The RXD is not a complete record of an order. Use the RXO and RXE segments if a complete order is needed. It is a record from the pharmacy or treatment supplier to the Nursing application (or other) with drug/treatment dispense and administration instructions.

The FT1 segment is optional and repeating in order to accommodate multiple charge, benefit and pricing situations. Example use cases demonstrating zero, one and two FT1 segments follow:

In the case where the RDS message represents a dispense event that is in process (i.e., has not been received by the patient), the financial transactions associated with the dispense do not yet exist. Until the financial transactions associated with the dispense event have been completed, no FT1 segment may exist in the message.

In the case where the RDS message represents a dispense event that has been received by the patient, and thus all financial transactions have been completed, the RDS message may contain one or more FT1 segments. Examples of single and multiple FT1 segments follow.

Payment for the dispense event completed by a single payor:

MSH|^&~\|Pharm|GenHosp|CIS|GenHosp|2006082911150700||RDS^O13^RDS_O13|...

PID|...

ORC|RE|...

RXD|1|00310-0131-10^LISINOPRIL 10MG TABLET^NDC|200607150830|100|TAB|...

FT1|1|||200607151035||PY|00310-0131-10^LISINOPRIL 10MG TABLET^NDC|||100|125.43&USD|...

Payment for the dispense event involves multiple payment sources:

MSH|^&~\|Pharm|GenHosp|CIS|GenHosp|2006082213000700||RDS^O13^RDS_O13|...

PID|...

ORC|RE|...

RXD|1|00340-0241-10^VERAPAMIL 120MG TABLET^NDC|200607200940|100|TAB|...

FT1|1|||200607211055||CD|00340024110^VERAPAMIL 120MG TABLET ^NDC|||100|55.43&USD|... (amount paid by insurance)

FT1|2|||200607211055||CP|00340024110^VERAPAMIL 120MG TABLET ^NDC|||100|5.00&USD|... (copay paid by patient)

Note: The use of RDS with the trigger of O01 and RRD with the trigger O02 is maintained for backward compatibility as of v 2.4 and is withdrawn as of v 2.7.

• Message
• ACK Choreography
• FHIR Structure Definition
• v2.xml XSD
• ER7 Example
• XML Example

Segment	Cardinality	Implement	Status
RDS^O13^RDS_O13
MSH Message Header	[1..1]	SHALL
ARV Access Restriction
SFT Software Segment
UAC User Authentication Credential Segment	[0..1]
NTE Notes and Comments
PATIENT	[0..1]
PID Patient Identification	[1..1]	SHALL
PD1 Patient Additional Demographic	[1..1]	SHALL
PRT Participation Information
ARV Access Restriction			B
NTE Notes and Comments
AL1 Patient Allergy Information
PATIENT_VISIT	[0..1]
PV1 Patient Visit	[1..1]	SHALL
PV2 Patient Visit - Additional Information	[0..1]
PRT Participation Information
ARV Access Restriction			B
ORDER	[1..*]	SHALL
ORC Common Order	[1..1]	SHALL
PRT Participation Information
TIMING
TQ1 Timing/Quantity	[1..1]	SHALL
TQ2 Timing/Quantity Relationship
ORDER_DETAIL	[0..1]
RXO Pharmacy/Treatment Order	[1..1]	SHALL
PRT Participation Information
ORDER_DETAIL_SUPPLEMENT	[0..1]
NTE Notes and Comments	[1..*]	SHALL
RXR Pharmacy/Treatment Route	[1..*]	SHALL
COMPONENT
RXC Pharmacy/Treatment Component Order	[1..1]	SHALL
NTE Notes and Comments
ENCODING	[0..1]
RXE Pharmacy/Treatment Encoded Order	[1..1]	SHALL
PRT Participation Information
NTE Notes and Comments
TIMING_ENCODED	[1..*]	SHALL
TQ1 Timing/Quantity	[1..1]	SHALL
TQ2 Timing/Quantity Relationship
RXR Pharmacy/Treatment Route	[1..*]	SHALL
RXC Pharmacy/Treatment Component Order
RXD Pharmacy/Treatment Dispense	[1..1]	SHALL
PRT Participation Information
NTE Notes and Comments
RXR Pharmacy/Treatment Route	[1..*]	SHALL
RXC Pharmacy/Treatment Component Order
CDO Cumulative Dosage
OBSERVATION
OBX Observation/Result	[1..1]	SHALL
PRT Participation Information
NTE Notes and Comments
FT1 Financial Transaction

 

RDS_O13

MSH-15	MSH-16	Immediate ACK	Application Ack
Blank	Blank	-	RRD^O14^RRD_O14
NE	NE	-	-
NE	AL, SU, ER	-	RRD^O14^RRD_O14
AL, SU, ER	AL, SU, ER	ACK^O13^ACK	RRD^O14^RRD_O14

We need some ER7 examples...

We need some XML examples...