Reference·RXR Segment·RXR-1
HL7 v2 Reference

HL7 v2 RXR-1 (Route): Format, Values, and Testing Notes

Jul 28, 2026 · 4 min read
RXR-2 →

RXR-1 is the one field in the segment that almost every system populates, which is exactly why a bad route code is so easy to miss — the field is never blank, it is just sometimes wrong.

Quick answer

RXR-1 is a coded element (CE/CWE) identifying how the substance was administered — for example orally, intramuscularly, intravenously, or topically. It is typically drawn from a locally adopted route table, with each value carrying a code, a display name, and a coding system identifier.

What this field contains

PO^Oral^HL70162
Oral route — used for tablets, liquids, and other substances taken by mouth
IM^Intramuscular^HL70162
Injected route — the most common route for vaccines and many injectable medications
IV^Intravenous^HL70162
Infused route — used for infusions and IV push medications, frequently paired with a pump device in RXR-3

Example

Synthetic example Generated by Synthibase
RXA|0|1|20260726090000||08^Hep B, adult^CVX|0.5|mL^^UCUM|||||||||||CP|A
RXR|IM^Intramuscular^HL70162|LD^Left Deltoid^HL70163|SY^Syringe^HL70164

RXR-1 carries IM^Intramuscular^HL70162 — code, display text, and coding system components for a synthetic intramuscular administration.

Where this trips people up

Test data generators frequently hardcode a single route value, so parsing logic that only ever sees IM never gets exercised against oral, topical, or subcutaneous routes. That gap surfaces when a real feed sends a route the mapping table doesn't recognize, and the record either gets rejected outright or silently defaults to the wrong route in a downstream display — a discrepancy nobody notices until a chart audit flags a dose that says it was swallowed when it was actually injected.

HL7 v2 RXR Segment Guide: Fields, Format, and Testing Gotchas
HL7 ADT Messages: A01 through A08 Explained
How to Write EDI Test Cases
Stop hand-crafting route edge cases
Synthibase generates synthetic RXR segments across the full range of administration routes — oral, injected, infused, and topical — so your mapping logic gets tested against more than the one route someone typed in a fixture file.
Start free trial →
This page is written independently by Synthibase for testing and informational purposes. It is not an official publication of HL7 International or X12/Washington Publishing Company, and is not a substitute for reviewing the official standard or your trading partner's companion guide. See our Terms of Service for full legal terms.