Overview
The Medical Record Number (MRN) occupies Field 3b on the UB-04 claim form, positioned directly below the patient's control number. This field serves as a unique identifier assigned by the provider to track a patient's clinical history across multiple encounters. While the NUBC UB-04 Manual defines this space for the MRN, it is technically classified as an optional field for both inpatient and outpatient claims. According to CMS Pub. 100-04 Chapter 25, the MRN is not required for claim processing and will not be reflected on the Explanation of Benefits (EOB) or the Electronic Remittance Advice (ERA). Despite its optional status, many facilities utilize this field to facilitate internal reconciliation between their Electronic Health Record (EHR) and their billing software, ensuring that payments are posted to the correct clinical file.
When to Use This Field
Use Field 3b when your internal facility workflow requires a secondary link between the financial record and the clinical chart. For example, a Critical Access Hospital (CAH) may populate this field to assist their internal audit team when pulling charts for a Recovery Audit Contractor (RAC) request. Since the Patient Control Number in Field 3a often changes per encounter, the MRN provides a static reference point. Another scenario involves Long-Term Care Hospitals (LTCH) where patients have extended stays; the MRN helps the billing department verify that the diagnostic codes on the claim match the physician's notes in the permanent medical file. Even though Noridian Healthcare Solutions confirms this field is not a requirement for Medicare adjudication, private payers may occasionally request it to streamline their own internal patient indexing, though they cannot legally deny a claim solely for its absence.
Step-by-Step Claim Example
Consider a scenario at an Ambulatory Surgical Center (ASC) where a patient undergoes a laparoscopic cholecystectomy. The billing specialist enters the unique encounter ID 'ASC-99887' into Field 3a (Patient Control Number). To ensure the clinical team can easily find the operative report later, the specialist enters the permanent patient ID 'MRN-12345' into Field 3b. When the claim is transmitted via the 837I electronic format, this data maps to Loop 2300, REF02 (Reference Identification) with a 'EA' qualifier. The payer receives the claim, ignores Field 3b during the adjudication process, and issues a payment based on the DRG or APC assignment. When the remittance advice arrives, the MRN is absent, but the billing team uses the Patient Control Number from Field 3a to post the payment. This workflow demonstrates that Field 3b is a 'convenience field' rather than a 'compliance field' under CMS guidelines.
Common Mistakes & Audit Red Flags
The most frequent error regarding Field 3b is confusing it with the Patient Control Number (Field 3a). If a biller places the MRN in Field 3a, the facility will struggle to reconcile the payment because the MRN is not unique to the specific visit. Another audit red flag occurs when facilities include sensitive data, such as a Social Security Number, in Field 3b; this violates HIPAA Privacy Rules and can lead to significant fines. Furthermore, some billers mistakenly believe that populating Field 3b will help resolve Duplicate Claim denials. In reality, payers like Palmetto GBA ignore this field entirely during their duplicate logic checks. If your clearinghouse is stripping data from Field 3b, do not attempt to force it into other required fields, as this will trigger a 'Front-End' rejection for invalid data formats.
Related Codes & Fields
Because Field 3b is a free-text alphanumeric field used for internal tracking, it does not have enumerated child codes or sub-identifiers. However, it is closely related to other header fields on the UB-04. You should review the requirements for Field 3a (Patient Control Number) to understand how it differs from the MRN. Additionally, ensure that the patient's identity in Field 3b aligns with the demographic data in Field 8 (Patient Name) and the insurance identifiers in Field 60 (Insured's Unique ID). While Field 3b is optional, these surrounding fields are mandatory for successful claim adjudication under NUBC standards.
References
Need to extract UB04 data?
Upload your UB04 PDFs and get structured data in seconds.
Start ExtractingFormJuicer Data Insights
This guide was developed by the FormJuicer Billing Research Team using official CMS and NUBC guidelines, combined with patterns observed from processing thousands of real UB-04 documents through our system.
Last Updated: 2026-04-12
Sources: CMS Pub. 100-04 Chapter 25, NUBC Official UB-04 Manual, Medicare Contractor Bulletins (Noridian, Palmetto, CGS)