RF1 segment
This segment represents information that may be useful when sending referrals from the referring provider to the referred-to provider.
The shape of one line
required optional
RF1-2 and its value arrives as RF1-1, so the receiver stores Referral Priority as Referral Status.This page carries the RF1 field table as published and nothing beyond it. The field notes, vendor behaviour, FHIR mapping and parsing guidance that thePID page has are still to be written for RF1.
Every field
| SEQ | LEN | DT | OPT | RP/# | TBL# | ITEM# | Element name | Cardinality |
|---|---|---|---|---|---|---|---|---|
| 250 | CE | O | 0283 | 01137 | Referral Status | 0..1 | ||
| ||||||||
| 250 | CE | O | 0280 | 01138 | Referral Priority | 0..1 | ||
| ||||||||
| 250 | CE | O | 0281 | 01139 | Referral Type | 0..1 | ||
| ||||||||
| 250 | CE | O | Y | 0282 | 01140 | Referral Disposition | 0..* | |
| ||||||||
| 250 | CE | O | 0284 | 01141 | Referral Category | 0..1 | ||
| ||||||||
| 30 | EI | R | 01142 | Originating Referral Identifier | 1..1 | |||
| ||||||||
| 26 | TS | O | 01143 | Effective Date | 0..1 | |||
| ||||||||
| 26 | TS | O | 01144 | Expiration Date | 0..1 | |||
| ||||||||
| 26 | TS | O | 01145 | Process Date | 0..1 | |||
| ||||||||
| 250 | CE | O | Y | 0336 | 01228 | Referral Reason | 0..* | |
| ||||||||
| 30 | EI | O | Y | 01300 | External Referral Identifier | 0..* | ||
| ||||||||
Related
Message types carrying RF1
RF1 appears in 4 message structures, belonging to 4 message types.