References to other Chapters

Finance

• 6.
  • 6.1 PURPOSE
  • 6.2 PATIENT ACCOUNTING MESSAGE SET
  • 6.3 TRIGGER EVENTS AND MESSAGE DEFINITIONS
    • 6.3.1 BAR/ACK - add patient account (event P01)
    • 6.3.2 BAR/ACK - purge patient accounts (event P02)
    • 6.3.3 DFT/ACK - post detail financial transactions (event P03)
    • 6.3.4 QRY/DSP - generate bills and accounts receivable statements (event P04)
    • 6.3.5 BAR/ACK - update account (event P05)
    • 6.3.6 BAR/ACK - end account (event P06)
  • 6.4 MESSAGE SEGMENTS
    • 6.4.1 FT1 - financial transaction segment
      • 6.4.1.1 Set ID - FT1 (SI) 00355
      • 6.4.1.2 Transaction ID (ST) 00356
      • 6.4.1.3 Transaction batch ID (ST) 00357
      • 6.4.1.4 Transaction date (TS) 00358
      • 6.4.1.5 Transaction posting date (TS) 00359
      • 6.4.1.6 Transaction type (IS) 00360
      • 6.4.1.7 Transaction code (CE) 00361
      • 6.4.1.8 Transaction description (ST) 00362
      • 6.4.1.9 Transaction description - alt (ST) 00363
      • 6.4.1.10 Transaction quantity (NM) 00364
      • 6.4.1.11 Transaction amount - extended (CP) 00365
      • 6.4.1.12 Transaction amount - unit (CP) 00366
      • 6.4.1.13 Department code (CE) 00367
      • 6.4.1.14 Insurance plan ID (CE) 00368
      • 6.4.1.15 Insurance amount (CP) 00369
      • 6.4.1.16 Assigned patient location (PL) 00133
      • 6.4.1.17 Fee schedule (IS) 00370
      • 6.4.1.18 Patient type (IS) 00148
      • 6.4.1.19 Diagnosis code (CE) 00371
      • 6.4.1.20 Performed by code (XCN) 00372
      • 6.4.1.21 Ordered by code (XCN) 00373
      • 6.4.1.22 Unit cost (CP) 00374
      • 6.4.1.23 Filler order number (EI) 00217
      • 6.4.1.24 Entered by code (XCN) 00765
      • 6.4.1.25 Procedure code (CE) 00393
    • 6.4.2 DG1 - diagnosis segment
      • 6.4.2.1 Set ID - DG1 (SI) 00375
      • 6.4.2.2 Diagnosis coding method (ID) 00376
      • 6.4.2.3 Diagnosis code (CE) 00377
      • 6.4.2.4 Diagnosis description (ST) 00378
      • 6.4.2.5 Diagnosis date/time (TS) 00379
      • 6.4.2.6 Diagnosis type (IS) 00380
      • 6.4.2.7 Major diagnostic category (CE) 00381
      • 6.4.2.8 Diagnostic related group (CE) 00382
      • 6.4.2.9 DRG approval indicator (ID) 00383
      • 6.4.2.10 DRG grouper review code (IS) 00384
      • 6.4.2.11 Outlier type (CE) 00385
      • 6.4.2.12 Outlier days (NM) 00386
      • 6.4.2.13 Outlier cost (CP) 00387
      • 6.4.2.14 Grouper version and type (ST) 00388
      • 6.4.2.15 Diagnosis priority (NM) 00389
      • 6.4.2.16 Diagnosing clinician (XCN) 00390
      • 6.4.2.17 Diagnosis classification (IS) 00766
      • 6.4.2.18 Confidential indicator (ID) 00767
      • 6.4.2.19 Attestation date/time (TS) 00768
    • 6.4.3 DRG - diagnosis related group segment
      • 6.4.3.1 Diagnostic related group (CE) 00382
      • 6.4.3.2 DRG assign date/time (TS) 00769
      • 6.4.3.3 DRG approval indicator (ID) 00383
      • 6.4.3.4 DRG grouper review code (IS) 00384
      • 6.4.3.5 Outlier type (CE) 00385
      • 6.4.3.6 Outlier days (NM) 00386
      • 6.4.3.7 Outlier cost (CP) 00387
      • 6.4.3.8 DRG payor (IS) 00770
      • 6.4.3.9 Outlier reimbursement (CP) 00771
      • 6.4.3.10 Confidential indicator (ID) 00767
    • 6.4.4 PR1 - procedures segment
      • 6.4.4.1 Set ID - PR1 (SI) 00391
      • 6.4.4.2 Procedure coding method (IS) 00392
      • 6.4.4.3 Procedure code (CE) 00393
      • 6.4.4.4 Procedure description (ST) 00394
      • 6.4.4.5 Procedure date/time (TS) 00395
      • 6.4.4.6 Procedure functional type (IS) 00396
      • 6.4.4.7 Procedure minutes (NM) 00397
      • 6.4.4.8 Anesthesiologist (XCN) 00398
      • 6.4.4.9 Anesthesia code (IS) 00399
      • 6.4.4.10 Anesthesia minutes (NM) 00400
      • 6.4.4.11 Surgeon (XCN) 00401
      • 6.4.4.12 Procedure practitioner (XCN) 00402
      • 6.4.4.13 Consent code (CE) 00403
      • 6.4.4.14 Procedure priority (NM) 00404
      • 6.4.4.15 Associated diagnosis code (CE) 00772
    • 6.4.5 GT1 - guarantor segment
      • 6.4.5.1 Set ID - GT1 (SI) 00405
      • 6.4.5.2 Guarantor number (CX) 00406
      • 6.4.5.3 Guarantor name (XPN) 00407
      • 6.4.5.4 Guarantor spouse name (XPN) 00408
      • 6.4.5.5 Guarantor address (XAD) 00409
      • 6.4.5.6 Guarantor ph num - home (XTN) 00410 C
      • 6.4.5.7 Guarantor ph num - business (XTN) 00411
      • 6.4.5.8 Guarantor date and time of birth (TS) 00412
      • 6.4.5.9 Guarantor sex (IS) 00413
      • 6.4.5.10 Guarantor type (IS) 00414
      • 6.4.5.11 Guarantor relationship (IS) 00415
      • 6.4.5.12 Guarantor SSN (ST) 00416
      • 6.4.5.13 Guarantor date - begin (DT) 00417
      • 6.4.5.14 Guarantor date - end (DT) 00418
      • 6.4.5.15 Guarantor priority (NM) 00419
      • 6.4.5.16 Guarantor employer name (XPN) 00420
      • 6.4.5.17 Guarantor employer address (XAD) 00421
      • 6.4.5.18 Guarantor employer phone number (XTN) 00422
      • 6.4.5.19 Guarantor employee ID number (CX) 00423
      • 6.4.5.20 Guarantor employment status (IS) 00424
      • 6.4.5.21 Guarantor organization name (XON) 00425
      • 6.4.5.22 Guarantor billing hold flag (ID) 00773
      • 6.4.5.23 Guarantor credit rating code (CE) 00774
      • 6.4.5.24 Guarantor death date and time (TS) 00775
      • 6.4.5.25 Guarantor death flag (ID) 00776
      • 6.4.5.26 Guarantor charge adjustment code (CE) 00777
      • 6.4.5.27 Guarantor household annual income (CP) 00778
      • 6.4.5.28 Guarantor household size (NM) 00779
      • 6.4.5.29 Guarantor employer identification number (CX) 00780
      • 6.4.5.30 Guarantor marital status code (IS) 00781
      • 6.4.5.31 Guarantor hire effective date (DT) 00782
      • 6.4.5.32 Guarantor employment stop date (DT) 00783
      • 6.4.5.33 Living dependency (IS) 00755
      • 6.4.5.34 Ambulatory status code (IS) 00145
      • 6.4.5.35 Citizenship (IS) 00129
      • 6.4.5.36 Primary language (CE) 00118
      • 6.4.5.37 Living arrangement (IS) 00742
      • 6.4.5.38 Publicity indicator (CE) 00743
      • 6.4.5.39 Protection indicator (ID) 00744
      • 6.4.5.40 Student indicator (IS) 00745
      • 6.4.5.41 Religion (IS) 00120
      • 6.4.5.42 Mother's maiden name (XPN) 00746
      • 6.4.5.43 Nationality (CE) 00739
      • 6.4.5.44 Ethnic group (IS) 00125
      • 6.4.5.45 Contact person's name (XPN) 00748
      • 6.4.5.46 Contact person phone number (XTN) 00749
      • 6.4.5.47 Contact reason (CE) 00747
      • 6.4.5.48 Contact relationship code (IS) 00784
      • 6.4.5.49 Job title (ST) 00785
      • 6.4.5.50 Job code/class (JCC) 00786
      • 6.4.5.51 Guarantor employer's organization (XON) 01299
      • 6.4.5.52 Handicap (IS) 00753
      • 6.4.5.53 Job status (IS) 00752
      • 6.4.5.54 Guarantor financial class (FC) 01231
      • 6.4.5.55 Guarantor race (IS) 01291
    • 6.4.6 IN1 - insurance segment
      • 6.4.6.1 Set ID - IN1 (SI) 00426
      • 6.4.6.2 Insurance plan ID (CE) 00427
      • 6.4.6.3 Insurance company ID (CX) 00428
      • 6.4.6.4 Insurance company name (XON) 00429
      • 6.4.6.5 Insurance company address (XAD) 00430
      • 6.4.6.6 Insurance co contact person (XPN) 00431
      • 6.4.6.7 Insurance co phone number (XTN) 00432
      • 6.4.6.8 Group number (ST) 00433
      • 6.4.6.9 Group name (XON) 00434
      • 6.4.6.10 Insured's group emp. ID (CX) 00435
      • 6.4.6.11 Insured's group emp name (XON) 00436
      • 6.4.6.12 Plan effective date (DT) 00437
      • 6.4.6.13 Plan expiration date (DT) 00438
      • 6.4.6.14 Authorization information (CM) 00439
      • 6.4.6.15 Plan type (IS) 00440
      • 6.4.6.16 Name of insured (XPN) 00441
      • 6.4.6.17 Insured's relationship to patient (IS) 00442
      • 6.4.6.18 Insured's date of birth (TS) 00443
      • 6.4.6.19 Insured's address (XAD) 00444
      • 6.4.6.20 Assignment of benefits (IS) 00445
      • 6.4.6.21 Coordination of benefits (IS) 00446
      • 6.4.6.22 Coord of ben priority (ST) 00447
      • 6.4.6.23 Notice of admission flag (ID) 00448
      • 6.4.6.24 Notice of admission date (DT) 00449
      • 6.4.6.25 Report of eligibility flag (ID) 00450
      • 6.4.6.26 Report of eligibility date (DT) 00451
      • 6.4.6.27 Release information code (IS) 00452
      • 6.4.6.28 Pre-admit cert. (PAC) (ST) 00453
      • 6.4.6.29 Verification date/time (TS) 00454
      • 6.4.6.30 Verification by (XCN) 00455
      • 6.4.6.31 Type of agreement code (IS) 00456
      • 6.4.6.32 Billing status (IS) 00457
      • 6.4.6.33 Lifetime reserve days (NM) 00458
      • 6.4.6.34 Delay before L.R. day (NM) 00459
      • 6.4.6.35 Company plan code (IS) 00460
      • 6.4.6.36 Policy number (ST) 00461
      • 6.4.6.37 Policy deductible (CP) 00462
      • 6.4.6.38 Policy limit - amount (CP) 00463
      • 6.4.6.39 Policy limit - days (NM) 00464
      • 6.4.6.40 Room rate - semi-private (CP) 00465
      • 6.4.6.41 Room rate - private (CP) 00466
      • 6.4.6.42 Insured's employment status (CE) 00467
      • 6.4.6.43 Insured's sex (IS) 00468
      • 6.4.6.44 Insured's employer's address (XAD) 00469
      • 6.4.6.45 Verification status (ST) 00470
      • 6.4.6.46 Prior insurance plan ID (IS) 00471
      • 6.4.6.47 Coverage type (IS) 01227
      • 6.4.6.48 Handicap code (IS) 00753
      • 6.4.6.49 Insured's ID number (CX) 01230
    • 6.4.7 IN2 - insurance additional information segment
      • 6.4.7.1 Insured's employee ID (CX) 00472
      • 6.4.7.2 Insured's social security number (ST) 00473
      • 6.4.7.3 Insured's employer name (XCN) 00474
      • 6.4.7.4 Employer information data (IS) 00475
      • 6.4.7.5 Mail claim party (IS) 00476
      • 6.4.7.6 Medicare health ins card number (ST) 00477
      • 6.4.7.7 Medicaid case name (XPN) 00478
      • 6.4.7.8 Medicaid case number (ST) 00479
      • 6.4.7.9 Champus sponsor name (XPN) 00480
      • 6.4.7.10 Champus ID number (ST) 00481
      • 6.4.7.11 Dependent of champus recipient (CE) 00482
      • 6.4.7.12 Champus organization (ST) 00483
      • 6.4.7.13 Champus station (ST) 00484
      • 6.4.7.14 Champus service (IS) 00485
      • 6.4.7.15 Champus rank/grade (IS) 00486
      • 6.4.7.16 Champus status (IS) 00487
      • 6.4.7.17 Champus retire date (DT) 00488
      • 6.4.7.18 Champus non-avail cert on file (ID) 00489
      • 6.4.7.19 Baby coverage (ID) 00490
      • 6.4.7.20 Combine baby bill (ID) 00491
      • 6.4.7.21 Blood deductible (ST) 00492
      • 6.4.7.22 Special coverage approval name (XPN) 00493
      • 6.4.7.23 Special coverage approval title (ST) 00494
      • 6.4.7.24 Non-covered insurance code (IS) 00495
      • 6.4.7.25 Payor ID (CX) 00496
      • 6.4.7.26 Payor subscriber ID (CX) 00497
      • 6.4.7.27 Eligibility source (IS) 00498
      • 6.4.7.28 Room coverage type/amount (CM) 00499
      • 6.4.7.29 Policy type/amount (CM) 00500
      • 6.4.7.30 Daily deductible (CM) 00501
      • 6.4.7.31 Living dependency (IS) 00755
      • 6.4.7.32 Ambulatory status (IS) 00145
      • 6.4.7.33 Citizenship (IS) 00129
      • 6.4.7.34 Primary language (CE) 00118
      • 6.4.7.35 Living arrangement (IS) 00742
      • 6.4.7.36 Publicity indicator (CE) 00743
      • 6.4.7.37 Protection indicator (ID) 00744
      • 6.4.7.38 Student indicator (IS) 00745
      • 6.4.7.39 Religion (IS) 00120
      • 6.4.7.40 Mother's maiden name (XPN) 00746
      • 6.4.7.41 Nationality (CE) 00739
      • 6.4.7.42 Ethnic group (IS) 00125
      • 6.4.7.43 Marital status (IS) 00119
      • 6.4.7.44 Insured's employment start date (DT) 00787
      • 6.4.7.45 Insured's employment stop date (DT) 00783
      • 6.4.7.46 Job title (ST) 00785
      • 6.4.7.47 Job code/class (JCC) 00786
      • 6.4.7.48 Job status (IS) 00752
      • 6.4.7.49 Employer contact person name (XPN) 00789
      • 6.4.7.50 Employer contact person telephone number (XTN) 00790
      • 6.4.7.51 Employer contact reason code (IS) 00791
      • 6.4.7.52 Insured's contact person name (XPN) 00792
      • 6.4.7.53 Insured's contact person telephone number (XTN) 00793
      • 6.4.7.54 Insured's contact reason code (IS) 00794
      • 6.4.7.55 Relationship to the patient start date (DT) 00795
      • 6.4.7.56 Relationship to the patient stop date (DT) 00796
      • 6.4.7.57 Insurance company contact reason (IS) 00797
      • 6.4.7.58 Insurance company contact phone number (XTN) 00798
      • 6.4.7.59 Policy scope (IS) 00799
      • 6.4.7.60 Policy source (IS) 00800
      • 6.4.7.61 Patient member number (CX) 00801
      • 6.4.7.62 Guarantor's relationship to insured (ID) 00802
      • 6.4.7.63 Insured's telephone number - home (XTN) 00803
      • 6.4.7.64 Insured's employer telephone number (XTN) 00804
      • 6.4.7.65 Military handicapped program code (CE) 00805
      • 6.4.7.66 Suspend flag (ID) 00806
      • 6.4.7.67 Co-pay limit flag (ID) 00807
      • 6.4.7.68 Stoploss limit flag (ID) 00808
      • 6.4.7.69 Insured organization name and ID (XON) 00809
      • 6.4.7.70 Insured employer organization name and ID (XON) 00810
      • 6.4.7.71 Race (IS) 00113
      • 6.4.7.72 HCFA Patient relationship to insured (CE) 00811
    • 6.4.8 IN3 - insurance additional information, certification segment
      • 6.4.8.1 Set ID - IN3 (SI) 00502
      • 6.4.8.2 Certification number (CX) 00503
      • 6.4.8.3 Certified by (XCN) 00504
      • 6.4.8.4 Certification required (ID) 00505
      • 6.4.8.5 Penalty (CM) 00506
      • 6.4.8.6 Certification date/time (TS) 00507
      • 6.4.8.7 Certification modify date/time (TS) 00508
      • 6.4.8.8 Operator (XCN) 00509
      • 6.4.8.9 Certification begin date (DT) 00510
      • 6.4.8.10 Certification end date (DT) 00511
      • 6.4.8.11 Days (CM) 00512
      • 6.4.8.12 Non-concur code/description (CE) 00513
      • 6.4.8.13 Non-concur effective date/time (TS) 00514
      • 6.4.8.14 Physician reviewer (XCN) 00515
      • 6.4.8.15 Certification contact (ST) 00516
      • 6.4.8.16 Certification contact phone number (XTN) 00517
      • 6.4.8.17 Appeal reason (CE) 00518
      • 6.4.8.18 Certification agency (CE) 00519
      • 6.4.8.19 Certification agency phone number (XTN) 00520
      • 6.4.8.20 Pre-certification req/window (CM) 00521
      • 6.4.8.21 Case manager (ST) 00522
      • 6.4.8.22 Second opinion date (DT) 00523
      • 6.4.8.23 Second opinion status (IS) 00524
      • 6.4.8.24 Second opinion documentation received (IS) 00525
      • 6.4.8.25 Second opinion practitioner (XCN) 00526
    • 6.4.9 ACC - accident segment
      • 6.4.9.1 Accident date/time (TS) 00527
      • 6.4.9.2 Accident code (CE) 00528
      • 6.4.9.3 Accident location (ST) 00529
      • 6.4.9.4 Auto accident state (CE) 00812
      • 6.4.9.5 Accident job related indicator (ID) 00813
      • 6.4.9.6 Accident death indicator (ID) 00814
    • 6.4.10 UB1 - UB82 data segment
      • 6.4.10.1 Set ID - UB1 (SI) 00530
      • 6.4.10.2 Blood deductible (NM) 00531
      • 6.4.10.3 Blood furnished-pints of (40) (NM) 00532
      • 6.4.10.4 Blood replaced-pints (41) (NM) 00533
      • 6.4.10.5 Blood not replaced- pints (42) (NM) 00534
      • 6.4.10.6 Co-insurance days (25) (NM) 00535
      • 6.4.10.7 Condition code (IS) 00536
      • 6.4.10.8 Covered days - (23) (NM) 00537
      • 6.4.10.9 Non-covered days - (24) (NM) 00538
      • 6.4.10.10 Value amount and code (CM) 00539
      • 6.4.10.11 Number of grace days (90) (NM) 00540
      • 6.4.10.12 Spec program indicator (44) (CE) 00541
      • 6.4.10.13 PSRO/UR approval indicator (87) (CE) 00542
      • 6.4.10.14 PSRO/UR approved stay-fm (88) (DT) 00543
      • 6.4.10.15 PSRO/UR approved stay-to (89) (DT) 00544
      • 6.4.10.16 Occurrence (28-32) (CM) 00545
      • 6.4.10.17 Occurrence span (33) (CE) 00546
      • 6.4.10.18 Occur span start date (33) (DT) 00547
      • 6.4.10.19 Occur. span end date (33) (DT) 00548
      • 6.4.10.20 UB-82 locator 2 (ST) 00549
      • 6.4.10.21 UB-82 locator 9 (ST) 00550
      • 6.4.10.22 UB-82 locator 27 (ST) 00551
      • 6.4.10.23 UB-82 locator 45 (ST) 00552
    • 6.4.11 UB2 - UB92 data segment
      • 6.4.11.1 Set ID - UB2 (SI) 00553
      • 6.4.11.2 Co-insurance days (ST) 00554
      • 6.4.11.3 Condition code (IS) 00555
      • 6.4.11.4 Covered days (ST) 00556
      • 6.4.11.5 Non-covered days (ST) 00557
      • 6.4.11.6 Value amount and code (CM) 00558
      • 6.4.11.7 Occurrence code & date (CM) 00559
      • 6.4.11.8 Occurrence span code and dates (CM) 00560
      • 6.4.11.9 UB92 field 2, designated for state use (ST) 00561
      • 6.4.11.10 UB92 field 11, designated for state use (ST) 00562
      • 6.4.11.11 UB92 field 31, designated for national use (ST) 00563
      • 6.4.11.12 Document control number (ST) 00564
      • 6.4.11.13 UB92 field 49, designated for national use (ST) 00565
      • 6.4.11.14 UB92 field 56, designated for state use (ST) 00566
      • 6.4.11.15 UB92 field 57, designated for national use (ST) 00567
      • 6.4.11.16 UB92 field 78, designated for state use (ST) 00568
      • 6.4.11.17 Special visit count (NM) 00815
  • 6.5 EXAMPLE TRANSACTIONS
    • 6.5.1 Create a patient billing/accounts receivable record
    • 6.5.2 Post a charge to a patient's account
    • 6.5.3 Update patient accounts - update UB82 information
    • 6.5.4 Update patient accounts - update diagnosis and DRG information
  • 6.6 IMPLEMENTATION CONSIDERATIONS
  • 6.7 OUTSTANDING ISSUES

6.

6.

Financial Management

6.1 PURPOSE

The Finance chapter describes patient accounting transactions. Other financial transactions may be added in the future. Financial transactions can be sent between applications either in batches or online. As defined in Chapter 2 on batch segments, multiple transactions may be grouped and sent through all file transfer media or programs when using the HL7 Encoding Rules.
This chapter defines the transactions that take place at the seventh level, that is, the abstract messages. The examples included in this chapter were constructed using the HL7 Encoding Rules.

6.2 PATIENT ACCOUNTING MESSAGE SET

The patient accounting message set provides for the entry and manipulation of information on billing accounts, charges, payments, adjustments, insurance, and other related patient billing and accounts receivable information.
This Standard includes all of the data defined in the National Uniform Billing Field Specifications (as adapted by the National Uniform Billing Commission, May 21, 1982 and revised on November 8, 1984 and 1992). We have excluded state-specific coding and suggest that, where required, it be implemented in site-specific "Z" segments. State-specific fields may be included in the Standard at a later time. In addition, no attempt has been made to define data that have traditionally been required for the proration of charges. The requirement for proration is unique to a billing system and not a part of an interface.
We recognize that a wide variety of billing and accounts receivable systems exist today. Therefore, in an effort to accommodate the needs of the most comprehensive systems, we have defined an extensive set of transaction segments.

6.3 TRIGGER EVENTS AND MESSAGE DEFINITIONS

The triggering events that follow are served by Detail Financial Transaction (DFT), Add/Change Billing Account (BAR), and General Acknowledgment (ACK) messages.
Each trigger event is documented below, along with the applicable form of the message exchange. The notation used to describe the sequence, optionality, and repetition of segments is described in Chapter 2, "Format for Defining Abstract Messages."

6.3.1 BAR/ACK - add patient account (event P01)

Data are sent from some application (usually a Registration or an ADT system) for example, to the patient accounting or financial system to establish an account for a patient's billing/accounts receivable record. Many of the segments associated with this event are optional. This optionality allows those systems needing these fields to set up transactions that fulfill their requirements and yet satisfy the HL7 requirements.
When an account's start and end dates span a period greater than any particular visit, the P01 (add account) event should be used to transmit the opening of an account. The A01 (admit/visit notification) event can notify systems of the creation of an account as well as notify them of a patient's arrival in the healthcare facility. In order to create a new account without notifying systems of a patient's arrival, use the P01 trigger event.
From Standard Version 2.3 onward, the P01 event should only be used to add a new account that did not exist before, not to update an existing account. The new P05 (update account) event should be used to update an existing account. The new P06 (end account) event should be used to close an account. With the P01 event, EVN-2-date/time of event should contain the account start date.
BAR Add Billing Account Chapter
MSH Message Header 2
EVN Event Type 3
PID Patient Identification 3
[PD1] Additional Demographics 3
{
[ PV1 ] Patient Visit 3
[ PV2 ] Patient Visit - Additional Info 3
[{DB1}] Disability Information 3
[{ OBX }] Observation/Result 7
[{ AL1 }] Allergy Information 3
[{ DG1 }] Diagnosis 6
[ DRG ] Diagnosis Related Group 6
[{ PR1 Procedures 6
[{ ROL }] Role 12
}]
[{ GT1 }] Guarantor 6
[{ NK1 }] Next of Kin/Associated Parties 3
[
{
IN1 Insurance 6
[ IN2 ] Insurance - Additional Info. 6
[ IN3 ] Insurance - Add'l Info. - Cert. 6
}
]
[ACC] Accident Information 6
[UB1] Universal Bill Information 6
[UB2] Universal Bill 92 Information 6
}
The set ID field in the insurance, diagnosis, and procedure segments should be set the first time these segments are sent and can be used in subsequent transactions to update them.
ACK General Acknowledgment Chapter
MSH Message Header 2
MSA Message Acknowledgment 2
[ ERR ] Error 2
The error segment will indicate the fields that caused a transaction to be rejected.

6.3.2 BAR/ACK - purge patient accounts (event P02)

Generally, the elimination of all billing/accounts receivable records will be an internal function controlled, for example, by the patient accounting or financial system. However, on occasion, there will be a need to correct an account, or a series of accounts, that may require that a notice of account deletion be sent from another sub-system and processed, for example, by the patient accounting or financial system. Although a series of accounts may be purged within this one event, we recommend that only one PID segment be sent per event.
BAR Purge Billing Account Chapter
MSH Message Header 2
EVN Event Type 3
{
PID Patient Identification 3
[PD1] Additional Demographics 3
[ PV1 ] Patient Visit 3
[{DB1}] Disability Information 3
}
ACK General Acknowledgment Chapter
MSH Message Header 2
MSA Message Acknowledgment 2
[ ERR ] Error 2
The error segment indicates the fields that caused a transaction to be rejected.

6.3.3 DFT/ACK - post detail financial transactions (event P03)

The Detail Financial Transaction (DFT) message is used to describe a financial transaction transmitted between systems, that is, to the billing system for ancillary charges, ADT to billing system for patient deposits, etc.
DFT Detail Financial Transaction Chapter
MSH Message Header 2
EVN Event Type 3
PID Patient Identification 3
[PD1] Additional Demographics 3
[ PV1 ] Patient Visit 3
[ PV2 ] Patient Visit - Additional Info 3
[{DB1}] Disability Information 3
[{OBX}] Observation/Result 7
{FT1 Financial Transaction 6
[{PR1 Procedure 6
[{ROL}] Role 12
}]
}
[{ DG1 }] Diagnosis 6
[ DRG ] Diagnosis Related Group 6
[{GT1}] Guarantor 6
[
{
IN1 Insurance 6
[ IN2 ] Insurance - Additional Info. 6
[ IN3 ] Insurance - Add'l Info. - Cert. 6
}
]
[ACC] Accident Information 6
Special codes in the Event Type record are used for updating.
ACK General Acknowledgment Chapter
MSH Message Header 2
MSA Message Acknowledgment 2
[ ERR ] Error 2
The error segment indicates the fields that caused a transaction to be rejected.

6.3.4 QRY/DSP - generate bills and accounts receivable statements (event P04)

For patient accounting systems that support demand billing, the QRY/DSP transaction, as defined in Chapter 2, will provide the mechanism with which to request a copy of the bill for printing or viewing by the requesting system.

6.3.5 BAR/ACK - update account (event P05)

The P05 event is sent when an existing account is being updated. From Standard Version 2.3 onward, the P01 (add account) event should no longer be used for updating an existing account, but only for creating a new account.
BAR Update Billing Account Chapter
MSH Message Header 2
EVN Event Type 3
PID Patient Identification 3
[PD1] Additional Demographics 3
{
[ PV1 ] Patient Visit 3
[ PV2 ] Patient Visit - Additional Info 3
[{DB1}] Disability Information 3
[{ OBX }] Observation/Result 7
[{ AL1 }] Allergy Information 3
[{ DG1 }] Diagnosis 6
[ DRG ] Diagnosis Related Group 6
[{ PR1 Procedures 6
[{ ROL }] Role 12
}]
[{ GT1 }] Guarantor 6
[{ NK1 }] Next of Kin/Associated Parties 3
[
{
IN1 Insurance 6
[ IN2 ] Insurance - Additional Info. 6
[ IN3 ] Insurance - Add'l Info. - Cert. 6
}
]
[ACC] Accident Information 6
[UB1] Universal Bill Information 6
[UB2] Universal Bill 92 Information 6
}
ACK General Acknowledgment Chapter
MSH Message Header 2
MSA Message Acknowledgment 2
[ ERR ] Error 2
The error segment indicates the fields that caused a transaction to be rejected.

6.3.6 BAR/ACK - end account (event P06)

The P06 event is a notification that the account is no longer open, that is, no new charges can accrue to this account. This notification is not related to whether or not the account is paid in full. EVN-2-date/time of event must contain the account end date.
BAR End Billing Account Chapter
MSH Message Header 2
EVN Event Type 3
{
PID Patient Identification 3
[ PV1 ] Patient Visit 3
}
ACK General Acknowledgment Chapter
MSH Message Header 2
MSA Message Acknowledgment 2
[ ERR ] Error 2
The error segment indicates the fields that caused a transaction to be rejected.

6.4 MESSAGE SEGMENTS

6.4.1 FT1 - financial transaction segment

The FT1 segment contains the detail data necessary to post charges, payments, adjustments, etc. to patient accounting records.

6.4.1.0 FT1 field definitions

6.4.1.1 Set ID - FT1 (SI) 00355

Definition: This field contains the number that identifies this transaction. For the first occurrence of the segment the sequence number shall be 1, for the second occurrence it shall be 2, etc.

6.4.1.2 Transaction ID (ST) 00356

Definition: This field contains a number assigned by the sending system for control purposes. The number can be returned by the receiving system to identify errors.

6.4.1.3 Transaction batch ID (ST) 00357

Definition: This field uniquely identifies the batch in which this transaction belongs.

6.4.1.4 Transaction date (TS) 00358

Definition: This field contains the date of the transaction. For example, this field would be used to identify the date a procedure, item, or test was conducted or used. It may be defaulted to today's date.

6.4.1.5 Transaction posting date (TS) 00359

Definition: This field contains the date of the transaction that was sent to the financial system for posting.

6.4.1.6 Transaction type (IS) 00360

Definition: This field contains the code that identifies the type of transaction. Refer to user-defined table 0017 - Transaction type for suggested values.

6.4.1.7 Transaction code (CE) 00361

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field contains the code assigned by the institution for the purpose of uniquely identifying the transaction. For example, this field would be used to uniquely identify a procedure, supply item, or test for charging purposes. Refer to user-defined table 0132 - Transaction code for suggested values. See Chapter 7 for a discussion of the universal service ID.

6.4.1.8 Transaction description (ST) 00362

Definition: This field has been retained for backward compatibility only. As of Version 2.3, FT1-7-transaction code contains a component for the transaction description. When used for backward compatibility, FT1-8-transaction description contains a description of the transaction associated with the code entered in FT1-7-transaction code

6.4.1.9 Transaction description - alt (ST) 00363

Definition: This field has been retained for backward compatibility only. As of Version 2.3, FT1-7-transaction code contains a component for the alternate transaction description. When used for backward compatibility, FT1-9-transaction description-alt contains an alternate description of the transaction associated with the code entered in FT1-7-transaction code.

6.4.1.10 Transaction quantity (NM) 00364

Definition: This field contains the quantity of items associated with this transaction.

6.4.1.11 Transaction amount - extended (CP) 00365

Components: <price (MO)> ^ <price type (ID)> ^ <from value (NM)> ^ <to value (NM)> ^ <range units (CE)> ^ <range type (ID)>
Subcomponents of price: <quantity (NM)> & <denomination (ID)>
Subcomponents of range units: <identifier (ST)> & <text (ST)> & <name of coding system (ST)> & <alternate identifier (ID)> & <alternate text (ST)> & <name of alternate coding system (ST)>
Definition: This field contains the amount of a transaction. It may be left blank if the transaction is automatically priced. Total price for multiple items.

6.4.1.12 Transaction amount - unit (CP) 00366

Components: <price (MO)> ^ <price type (ID)> ^ <from value (NM)> ^ <to value (NM)> ^ <range units (CE)> ^ <range type (ID)>
Subcomponents of price: <quantity (NM)> & <denomination (ID)>
Subcomponents of range units: <identifier (ST)> & <text (ST)> & <name of coding system (ST)> & <alternate identifier (ID)> & <alternate text (ST)> & <name of alternate coding system (ST)>
Definition: This field contains the unit price of a transaction. Price of a single item.

6.4.1.13 Department code (CE) 00367

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field contains the department code that controls the transaction code described above. Refer to user-defined table 0049 - Department code for suggested values.

6.4.1.14 Insurance plan ID (CE) 00368

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field contains the identifier of the primary insurance plan with which this transaction should be associated. Refer to user-defined table 0072 - Insurance plan ID for suggested values.

6.4.1.15 Insurance amount (CP) 00369

Components: <price (MO)> ^ <price type (ID)> ^ <from value (NM)> ^ <to value (NM)> ^ <range units (CE)> ^ <range type (ID)>
Subcomponents of price: <quantity (NM)> & <denomination (ID)>
Subcomponents of range units: <identifier (ST)> & <text (ST)> & <name of coding system (ST)> & <alternate identifier (ID)> & <alternate text (ST)> & <name of alternate coding system (ST)>
Definition: This field contains the amount to be posted to the insurance plan referenced above.

6.4.1.16 Assigned patient location (PL) 00133

Components: <point of care (IS)> ^ <room (IS)> ^ <bed (IS)> ^ <facility (HD)> ^ <location status (IS)> ^ <person location type (IS)> ^ <building (IS)> ^ <floor (IS)> ^ <location description (ST)>
Subcomponents of facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>
Definition: This field contains the current patient location. This can be the location of the patient when the charge item was ordered or when the charged service was rendered. For the current assigned patient location, use PV1-3-assigned patient location.

6.4.1.17 Fee schedule (IS) 00370

Definition: This field contains the code used to select the appropriate fee schedule to be used for this transaction posting. Refer to user-defined table 0024 - Fee schedule for suggested values.

6.4.1.18 Patient type (IS) 00148

Definition: This field contains the type code assigned to the patient for this episode of care (visit or stay). Refer to user-defined table 0018 - Patient type for suggested values. This is for use when the patient type for billing purposes is different than the visit patient type in PV1-18-patient type.

6.4.1.19 Diagnosis code (CE) 00371

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field contains the primary diagnosis code for billing purposes. ICD9-CM is assumed for all diagnosis codes. This is the most current diagnosis code that has been assigned to the patient. ICD10 can also be used. Refer to user-defined table 0051 - Diagnosis code for suggested values.

6.4.1.20 Performed by code (XCN) 00372

Components: <ID number (ST)> ^ <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <source table (IS)> ^ <assigning authority (HD)> ^ <name type code(ID)> ^ <identifier check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <identifier type code (IS)> ^ <assigning facility (HD)>
Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Definition: This field contains the composite number/name of the person/group that performed the test/procedure/transaction, etc. This is the service provider. Refer to user-defined table 0084 - Performed by for suggested values. Multiple names and identifiers for the same practitioner may be sent in this field, not multiple practitioners. The legal name is assumed to be in the first repetition. When the legal name is not sent, a repeat delimiter must be sent first for the first repetition. The components of this field are described in Chapter 2.

6.4.1.21 Ordered by code (XCN) 00373

Components: <ID number (ST)> ^ <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <source table (IS)> ^ <assigning authority (HD)> ^ <name type code(ID)> ^ <identifier check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <identifier type code (IS)> ^ <assigning facility (HD)>
Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Definition: This field contains the composite number/name of the person/group that ordered the test/ procedure/transaction, etc. Multiple names and identifiers for the same practitioner may be sent in this field, not multiple practitioners. The legal name is assumed to be in the first repetition. When the legal name is not sent, a repeat delimiter must be sent first for the first repetition. The components for this field are described in Chapter 2.

6.4.1.22 Unit cost (CP) 00374

Components: <price (MO)> ^ <price type (ID)> ^ <from value (NM)> ^ <to value (NM)> ^ <range units (CE)> ^ <range type (ID)>
Subcomponents of price: <quantity (NM)> & <denomination (ID)>
Subcomponents of range units: <identifier (ST)> & <text (ST)> & <name of coding system (ST)> & <alternate identifier (ID)> & <alternate text (ST)> & <name of alternate coding system (ST)>
Definition: This field contains the unit cost of transaction. The cost of a single item.

6.4.1.23 Filler order number (EI) 00217

Components: <entity identifier (ST)> ^ <namespace ID (IS)> ^ <universal ID (ST)> ^ <universal ID type (ID)>
Definition: This field is used when the billing system is requesting observational reporting justification for a charge. This is the number used by a filler to uniquely identify a result. See Chapter 4 for a complete description.

6.4.1.24 Entered by code (XCN) 00765

Components: <ID number (ST)> ^ <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <source table (IS)> ^ <assigning authority (HD)> ^ <name type code(ID)> ^ <identifier check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <identifier type code (IS)> ^ <assigning facility (HD)>
Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Definition: This field identifies the composite number/name of the person who entered the insurance information.

6.4.1.25 Procedure code (CE) 00393

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field contains a unique identifier assigned to the procedure, if any, associated with the charge. Refer to user-defined table 0088 - Procedure code for suggested values. This field is a CE data type for compatibility with clinical and ancillary systems.

6.4.2 DG1 - diagnosis segment

The DG1 segment contains patient diagnosis information of various types, for example, admitting, primary, etc. The DG1 segment is used to send multiple diagnoses (for example, for medical records encoding). It is also used when the FT1-19-diagnosis does not provide sufficient information for a billing system. This diagnosis coding should be distinguished from the clinical problem segment used by caregivers to manage the patient (see Chapter 12, Patient Care). Coding methodologies are also defined.

6.4.2.0 DG1 field definitions

6.4.2.1 Set ID - DG1 (SI) 00375

Definition: This field contains the number that identifies this transaction. For the first occurrence of the segment the sequence number shall be 1, for the second occurrence it shall be 2, etc.

6.4.2.2 Diagnosis coding method (ID) 00376

Definition: This field has been retained for backward compatibility only. Use the components of DG1-3-diagnosis code instead of this field. When used for backward compatibility, ICD9 is the recommended coding methodology. Refer to HL7 table 0053 - Diagnosis coding method for valid values.

6.4.2.3 Diagnosis code (CE) 00377

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: Use this field instead of DG1-2-coding method and DG1-4-diagnosis description. (Those two fields have been retained for backward compatibility only.) DG1-3-diagnosis code contains the diagnosis code assigned to this diagnosis. Refer to user-defined table 0051- Diagnosis code for suggested values. This field is a CE data type for compatibility with clinical and ancillary systems.
See Chapter 7 for suggested diagnosis codes. For the name of the coding system, refer to Chapter 7, Section 7.14, "Coding schemes," Figure 7-2-Diagnostic Coding Schemes.

6.4.2.4 Diagnosis description (ST) 00378

Definition: This field has been retained for backward compatibility only. Use the components of DG1-3-diagnosis code field instead of this field. When used for backward compatibility, DG1-4-diagnosis description contains a description that best describes the diagnosis.

6.4.2.5 Diagnosis date/time (TS) 00379

Definition: This field contains the date/time that the diagnosis was determined.

6.4.2.6 Diagnosis type (IS) 00380

Definition: This field contains a code that identifies the type of diagnosis being sent. Refer to user-defined table 0052 - Diagnosis type. This field should no longer be used to indicate "DRGÓ because the DRG fields have moved to the new DRG segment.

6.4.2.7 Major diagnostic category (CE) 00381

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field has been retained for backward compatibility only. This field should only be used in a master file transaction. Refer to user-defined table 0118 - Major diagnostic category for suggested values.

6.4.2.8 Diagnostic related group (CE) 00382

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field has been retained for backward compatibility only. This field has moved to the new DRG segment. It contains the DRG for the transaction. Interim DRG's could be determined for an encounter. Refer to user-defined table 0055 - DRG code for suggested values.

6.4.2.9 DRG approval indicator (ID) 00383

Definition: This field has been retained for backward compatibility only. This field has moved to the new DRG segment. This field indicates if the DRG has been approved by a reviewing entity. Refer to HL7 table 0136 - Yes/no indicator for valid values.

6.4.2.10 DRG grouper review code (IS) 00384

Definition: This field has been retained for backward compatibility only. This field has moved to the new DRG segment. Refer to user-defined table 0056 - DRG grouper review code for suggested values. This code indicates that the grouper results have been reviewed and approved.

6.4.2.11 Outlier type (CE) 00385

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field has been retained for backward compatibility only. This field has moved to the new DRG segment. When used for backward compatibility, this field contains the type of outlier that has been paid. Refer to user-defined table 0083 - Outlier type for suggested values.

6.4.2.12 Outlier days (NM) 00386

Definition: This field has been retained for backward compatibility only. This field has moved to the new DRG segment. When used for backward compatibility, this field contains the number of days that have been approved for an outlier payment.

6.4.2.13 Outlier cost (CP) 00387

Components: <price (MO)> ^ <price type (ID)> ^ <from value (NM)> ^ <to value (NM)> ^ <range units (CE)> ^ <range type (ID)>
Subcomponents of price: <quantity (NM)> & <denomination (ID)>
Subcomponents of range units: <identifier (ST)> & <text (ST)> & <name of coding system (ST)> & <alternate identifier (ID)> & <alternate text (ST)> & <name of alternate coding system (ST)>
Definition: This field has been retained for backward compatibility only. This field has moved to the new DRG segment. When used for backward compatibility, this field contains the amount of money that has been approved for an outlier payment.

6.4.2.14 Grouper version and type (ST) 00388

Definition: This field has been retained for backward compatibility only. This field has moved to the new DRG segment. When used for backward compatibility, this field contains the grouper version and type.

6.4.2.15 Diagnosis priority (NM) 00389

Definition: This field has been retained for backward compatibility only. This field should no longer be used for DRG priority, because the DRG fields have moved to the new DRG segment.
When used for backward compatibility, DG1-15-diagnosis priority contains the number that identifies the significance or priority of the diagnosis or DRG code. The numbers have the following meanings:
0 the admitting diagnosis
1 the primary diagnosis
2 and higher for ranked secondary diagnoses

6.4.2.16 Diagnosing clinician (XCN) 00390

Components: <ID number (ST)> ^ <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <source table (IS)> ^ <assigning authority (HD)> ^ <name type code(ID)> ^ <identifier check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <identifier type code (IS)> ^ <assigning facility (HD)>
Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Definition: This field contains the individual responsible for generating the diagnosis information. Multiple names and identifiers for the same person may be sent in this field, not multiple diagnosing clinicians. The legal name is assumed to be in the first repetition. When the legal name is not sent, a repeat delimiter must be sent first for the first repetition. The components for this field are described in Chapter 2.

6.4.2.17 Diagnosis classification (IS) 00766

Definition: This field indicates if the patient information is for a diagnosis or a non-diagnosis code. Refer to user-defined table 0228 - Diagnosis classification for suggested values.

6.4.2.18 Confidential indicator (ID) 00767

Definition: This field indicates whether the diagnosis is confidential. Refer to HL7 table 0136 - Yes/no indicator for valid values.
Y the diagnosis is a confidential diagnosis
N the diagnosis does not contain a confidential diagnosis

6.4.2.19 Attestation date/time (TS) 00768

Definition: This field contains the time stamp that indicates the date and time that the attestation was signed.

6.4.3 DRG - diagnosis related group segment

The DRG segment contains diagnoses-related grouping information of various types. The DRG segment is used to send the DRG information, for example, for billing and medical records encoding.

6.4.3.0 DRG field definitions

6.4.3.1 Diagnostic related group (CE) 00382

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field contains the DRG for the transaction. Interim DRG's could be determined for an encounter. For the identifier component, refer to user-defined table 0055-DRG code for suggested values. For the name of coding system component, send the grouper version and type.

6.4.3.2 DRG assign date/time (TS) 00769

Definition: This field contains the time stamp to indicate the date and time that the DRG was assigned.

6.4.3.3 DRG approval indicator (ID) 00383

Definition: This field indicates if the DRG has been approved by a reviewing entity. Refer to HL7 table 0136 - Yes/no indicator for valid values.

6.4.3.4 DRG grouper review code (IS) 00384

Definition: Refer to user-defined table 0056 - DRG grouper review code for suggested values. This code indicates that the grouper results have been reviewed and approved.

6.4.3.5 Outlier type (CE) 00385

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: Refer to user-defined table 0083 - Outlier type for suggested values. Refers to the type of outlier that has been paid.

6.4.3.6 Outlier days (NM) 00386

Definition: This field contains the number of days that have been approved as an outlier payment.

6.4.3.7 Outlier cost (CP) 00387

Components: <price (MO)> ^ <price type (ID)> ^ <from value (NM)> ^ <to value (NM)> ^ <range units (CE)> ^ <range type (ID)>
Subcomponents of price: <quantity (NM)> & <denomination (ID)>
Subcomponents of range units: <identifier (ST)> & <text (ST)> & <name of coding system (ST)> & <alternate identifier (ID)> & <alternate text (ST)> & <name of alternate coding system (ST)>
Definition: This field contains the amount of money that has been approved for an outlier payment.

6.4.3.8 DRG payor (IS) 00770

Definition: This field indicates the associated DRG Payor. Refer to user-defined table 0229 - DRG payor for suggested values.

6.4.3.9 Outlier reimbursement (CP) 00771

Components: <price (MO)> ^ <price type (ID)> ^ <from value (NM)> ^ <to value (NM)> ^ <range units (CE)> ^ <range type (ID)>
Subcomponents of price: <quantity (NM)> & <denomination (ID)>
Subcomponents of range units: <identifier (ST)> & <text (ST)> & <name of coding system (ST)> & <alternate identifier (ID)> & <alternate text (ST)> & <name of alternate coding system (ST)>
Definition: Where applicable, the outlier reimbursement amount indicates the part of the total reimbursement designated for reimbursement of outlier conditions (day or cost).

6.4.3.10 Confidential indicator (ID) 00767

Definition: This field indicates if the DRG contains a confidential diagnosis. Refer to HL7 table 0136 - Yes/no indicator for valid values.
Y the DRG contains a confidential diagnosis
N the DRG does not contain a confidential diagnosis

6.4.4 PR1 - procedures segment

The PR1 segment contains information relative to various types of procedures that can be performed on a patient. The PR1 segment can be used to send procedure information, for example: Surgical, Nuclear Medicine, X-ray with contrast, etc. The PR1 segment is used to send multiple procedures, for example, for medical records encoding or for billing systems.

6.4.4.0 PR1 field definitions

6.4.4.1 Set ID - PR1 (SI) 00391

Definition: This field contains the number that identifies this transaction. For the first occurrence of the segment the sequence number shall be 1, for the second occurrence it shall be 2, etc.

6.4.4.2 Procedure coding method (IS) 00392

Definition: This field has been retained for backward compatibility only. Use the components of PR1-3-procedure code instead of this field.
When used for backward compatibility, PR1-2-procedure coding method contains the methodology used to assign a code to the procedure (CPT4, for example). If more than one coding method is needed for a single procedure, this field and the associated values in PR1-3-procedure code and PR1-4-procedure description may repeat. In this instance, the three fields (PR1-2 through 4) are directly associated with one another. Refer to user-defined table 0089 - Procedure coding method for suggested values.

6.4.4.3 Procedure code (CE) 00393

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: Use this field instead of PR1-2-procedure coding method and PR1-4-procedure description. Those two fields have been retained for backward compatibility only. This field contains a unique identifier assigned to the procedure. Refer to user-defined table 0088 - Procedure code for suggested values. This field is a CE data type for compatibility with clinical and ancillary systems.

6.4.4.4 Procedure description (ST) 00394

Definition: This field has been retained for backward compatibility only. Use the components of PR1-3-procedure code instead of this field. The field contains a text description that describes the procedure.

6.4.4.5 Procedure date/time (TS) 00395

Definition: This field contains the date/time that the procedure was performed.

6.4.4.6 Procedure functional type (IS) 00396

Definition: This field contains the optional code that further defines the type of procedure. Refer to user-defined table 0230 - Procedure functional type for suggested values.

6.4.4.7 Procedure minutes (NM) 00397

Definition: This field indicates the length of time in whole minutes that the procedure took to complete.

6.4.4.8 Anesthesiologist (XCN) 00398

Components: <ID number (ST)> ^ <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <source table (IS)> ^ <assigning authority (HD)> ^ <name type code(ID)> ^ <identifier check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <identifier type code (IS)> ^ <assigning facility (HD)>
Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Definition: HL7 has introduced the ROL segment to report a wide range of practitioner roles related to a single procedure. This segment is described in Chapter 12. When using trigger events introduced in HL7 Version 2.3, it is recommended that the ROL segment be used to report all practitioner roles related to the procedure.
However, in order to maintain backward compatibility, the practitioner roles existing in HL7 Version 2.2 (PR1-8-anesthesiologist, PR1-11-surgeon, and PR1-12-procedure practitioner) should also be populated in the PR1 segment as per the HL7 2.2 specifications. You may additionally report the practitioner information in the ROL segment (See Chapter 12, Section 12.3.3, "ROL - role segment").
When this field is used for backward compatibility, the XCN data type applies. It contains the anesthesiologist who administered the anesthesia. Use values in user-defined table 0010 - Physician ID for first component. Multiple names and identifiers for the same person should be sent in this field, not multiple anesthesiologists. The legal name is assumed to be in the first repetition. When the legal name is not sent, a repeat delimiter must be sent first for the first repetition. The components for this data type are described in Chapter 2.

6.4.4.9 Anesthesia code (IS) 00399

Definition: This field contains a unique identifier of the anesthesia used during the procedure. Refer to user-defined table 0019 - Anesthesia code for suggested values.

6.4.4.10 Anesthesia minutes (NM) 00400

Definition: This field contains the length of time in minutes that the anesthesia was administered.

6.4.4.11 Surgeon (XCN) 00401

Components: <ID number (ST)> ^ <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <source table (IS)> ^ <assigning authority (HD)> ^ <name type code(ID)> ^ <identifier check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <identifier type code (IS)> ^ <assigning facility (HD)>
Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Definition: HL7 has introduced the ROL segment to report a wide range of practitioner roles related to a single procedure. This segment is described in Chapter 12. When using trigger events introduced in HL7 Version 2.3, it is recommended that the ROL segment be used to report all practitioner roles related to the procedure.
However, in order to maintain backward compatibility, the practitioner roles existing in HL7 Version 2.2 (PR1-8-anesthesiologist, PR1-11-surgeon, and PR1-12-procedure practitioner) should also be populated in the PR1 segment as per the HL7 2.2 specifications. You may additionally report the practitioner information in the ROL segment (See Chapter 12, Section 12.3.3, "ROL - role segment").
When this field is being used for backward compatibility, the XCN data type applies. It contains the surgeon who performed the procedure. Use the values in user-defined table 0010 - Physician ID for the first component. Multiple names and identifiers for the same person should be sent in this field, not multiple surgeons. The legal name is assumed to be in the first repetition. When the legal name is not sent, a repeat delimiter must be sent first for the first repetition. The components for this data type are described in Chapter 2.

6.4.4.12 Procedure practitioner (XCN) 00402

Components: <ID number (ST)> ^ <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <source table (IS)> ^ <assigning authority (HD)> ^ <name type code(ID)> ^ <identifier check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <identifier type code (IS)> ^ <assigning facility (HD)>
Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Definition: HL7 has introduced the ROL segment to report a wide range of practitioner roles related to a single procedure. This segment is described in Chapter 12. When using trigger events introduced in HL7 Version 2.3, it is recommended that the ROL segment be used to report all practitioner roles related to the procedure.
However, in order to maintain backward compatibility, the practitioner roles existing in HL7 Version 2.2 (PR1-8-anesthesiologist, PR1-11-surgeon, and PR1-12-procedure practitioner) should also be populated in the PR1 segment as per the HL7 2.2 specifications. You may additionally report the practitioner information in the ROL segment (See Chapter 12, Section 12.3.3, "ROL - role segment").
This field contains the different types of practitioners associated with this procedure. The ID and name components follow the standard rules defined for a composite name (XCN) field. The last component, identifier type code, indicates which type of procedure practitioner is shown. When the identifier type component is unvalued, it is assumed that the practitioner identified is a resident. Use values in user-defined table 0010 - Physician ID for the first component. Refer to user-defined table 0133 - Procedure practitioner identifier code type for suggested values for the identifier type code component. The components of this data type are described in Chapter 2.

6.4.4.13 Consent code (CE) 00403

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field contains the type of consent that was obtained for permission to treat the patient. Refer to user-defined table 0059 - Consent code for suggested values.

6.4.4.14 Procedure priority (NM) 00404

Definition: This field contains a number that identifies the significance or priority of the procedure code.
0 the admitting procedure
1 the primary procedure
2 and higher for ranked secondary procedures

6.4.4.15 Associated diagnosis code (CE) 00772

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field contains the diagnosis which is the primary reason this procedure was performed, e.g., Medicare wants to know for which diagnosis this procedure is submitted for inclusion on HCFA 1500 form.

6.4.5 GT1 - guarantor segment

The GT1 segment contains guarantor (e.g., the person or the organization with financial responsibility for payment of a patient account) data for patient and insurance billing applications.

6.4.5.0 GT1 field definitions

6.4.5.1 Set ID - GT1 (SI) 00405

Definition: Set ID-GT1 contains a number that identifies this transaction. For the first occurrence of the segment the sequence shall be 1, for the second occurrence it shall be 2, etc.

6.4.5.2 Guarantor number (CX) 00406

Components: <ID (ST)> ^ <check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <assigning authority (HD)> ^ <identifier type code (IS)> ^ <assigning facility (HD)
Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Definition: This field contains the primary identifier, or other identifiers, assigned to the guarantor.

6.4.5.3 Guarantor name (XPN) 00407

Components: <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <name type code (ID) >
Definition: This field contains the name of the guarantor. Multiple names for the same guarantor may be sent in this field. The legal name is assumed to be in the first repetition. When the legal name is not sent, a repeat delimiter must be sent first for the first repetition. The components for this data type are described in Chapter 2.

Beginning with Version 2.3, if the guarantor is an organization, send a null value (" ") in GT1-3-guarantor person name and put the organization name in GT1-21-guarantor organization name. Either guarantor person name or guarantor organization name is required.

6.4.5.4 Guarantor spouse name (XPN) 00408

Components: <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <name type code (ID) >
Definition: This field contains the name of the guarantor's spouse. Multiple names for the same guarantor spouse may be sent in this field. The legal name is assumed to be in the first repetition. When the legal name is not sent, a repeat delimiter must be sent first for the first repetition. The components for this data type are described in Chapter 2.

6.4.5.5 Guarantor address (XAD) 00409

Components: <street address (ST)> ^ <other designation (ST)> ^ <city (ST)> ^ <state or province (ST)> ^ <zip or postal code(ST)> ^ <country (ID)> ^ < address type (ID)> ^ <other geographic designation (ST)> ^ <county/parish code (IS)> ^ <census tract (IS)>
Definition: This field contains the guarantor's address. Multiple addresses for the same person may be sent in this field. The mailing address is assumed to be in the first repetition. When the mailing address is not sent, a repeat delimiter must be sent first for the first repetition.

6.4.5.6 Guarantor ph num - home (XTN) 00410 C

components: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] ^ <telecommunication use code (ID)> ^ <telecommunication equipment type (ID)> ^ <email address (ST)> ^ <country code (NM)> ^ <area/city code (NM)> ^ <phone number (NM)> ^ <extension (NM)> ^ <any text (ST)>
Definition: This field contains the guarantor's home phone number. All personal phone numbers for the guarantor may be sent in this field. The primary telephone number is assumed to be in the first repetition. When the primary telephone number is not sent, a repeat delimiter must be sent first for the first repetition. The components for this data type are described in Chapter 2.

6.4.5.7 Guarantor ph num - business (XTN) 00411

Components: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] ^ <telecommunication use code (ID)> ^ <telecommunication equipment type (ID)> ^ <email address (ST)> ^ <country code (NM)> ^ <area/city code (NM)> ^ <phone number (NM)> ^ <extension (NM)> ^ <any text (ST)>
Definition: This field contains the guarantor's business phone number. All business phone numbers for the guarantor may be sent in this field. The primary telephone number is assumed to be in the first repetition. When the primary telephone number is not sent, a repeat delimiter must be sent first for the first repetition. The components for this data type are described in Chapter 2.

6.4.5.8 Guarantor date and time of birth (TS) 00412

Definition: This field contains the guarantor's date of birth.

6.4.5.9 Guarantor sex (IS) 00413

Definition: This field contains the guarantor's gender. Refer to user-defined table 0001 - Sex for valid values.

6.4.5.10 Guarantor type (IS) 00414

Definition: This field indicates the type of guarantor, e.g., individual, institution, etc. Refer to user-defined table 0068 - Guarantor type for suggested values.

6.4.5.11 Guarantor relationship (IS) 00415

Definition: This field indicates the relationship of the guarantor with the patient, e.g., parent, child, etc. Refer to user-defined table 0063 - Relationship for suggested values.

6.4.5.12 Guarantor SSN (ST) 00416

Definition: This field contains the guarantor's social security number.

6.4.5.13 Guarantor date - begin (DT) 00417

Definition: This field contains the date that the guarantor becomes responsible for the patient's account.

6.4.5.14 Guarantor date - end (DT) 00418

Definition: This field contains the date that the guarantor stops being responsible for the patient's account.

6.4.5.15 Guarantor priority (NM) 00419

Definition: This field is used to determine the order in which the guarantors are responsible for the patient's account. "1Ó = primary guarantor, "2Ó = secondary guarantor, etc.

6.4.5.16 Guarantor employer name (XPN) 00420

Components: <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <name type code (ID) >
Definition: This field contains the name of the guarantor's employer, if the employer is a person. When the guarantor's employer is an organization, use GT1-51-guarantor employer's organization name Multiple names for the same person may be sent in this field, not multiple employers. The legal name must be sent first in the repetition. When the legal name is not sent, a repeat delimiter must be sent first for the first repetition. The components for this data type are described in Chapter 2.

6.4.5.17 Guarantor employer address (XAD) 00421

Components: <street address (ST)> ^ <other designation (ST)> ^ <city (ST)> ^ <state or province (ST)> ^ <zip or postal code(ST)> ^ <country (ID)> ^ < address type (ID)> ^ <other geographic designation (ST)> ^ <county/parish code (IS)> ^ <census tract (IS)>
Definition: This field contains the guarantor's employer's address. Multiple addresses for the same employer may be sent in this field. The mailing address must be sent first in the repetition. When the mailing address is not sent, a repeat delimiter must be sent first for the first repetition.

6.4.5.18 Guarantor employer phone number (XTN) 00422

Components: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] ^ <telecommunication use code (ID)> ^ <telecommunication equipment type (ID)> ^ <email address (ST)> ^ <country code (NM)> ^ <area/city code (NM)> ^ <phone number (NM)> ^ <extension (NM)> ^ <any text (ST)>
Definition: This field contains the guarantor's employer's phone number. Multiple phone numbers for the same employer. The primary telephone number must be sent first in the sequence. When the primary telephone number is not sent, a repeat delimiter must be sent first for the first repetition. The components for this data type are described in Chapter 2.

6.4.5.19 Guarantor employee ID number (CX) 00423

Components: <ID (ST)> ^ <check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <assigning authority (HD)> ^ <identifier type code (IS)> ^ <assigning facility (HD)
Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Definition: This field contains the guarantor's employee number.

6.4.5.20 Guarantor employment status (IS) 00424

Definition: This field contains the code that indicates the guarantor's employment status, e.g., full time, part time, self-employed, etc. Refer to user-defined table 0066 - Employment status for suggested values.

6.4.5.21 Guarantor organization name (XON) 00425

Components: <organization name (ST)> ^ <organization name type code (ID)> ^ <ID number (ID)> ^ <check digit (NM)> ^ < check digit scheme (ID)> ^ <assigning authority (HD)> ^ <identifier type code (ID)> ^ <assigning facility ID (HD)>
Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Definition: This field contains the name of the guarantor when the guarantor is an organization. Multiple names for the same guarantor may be sent in this field, not multiple guarantors. The legal name is assumed to be in the first repetition. When the legal name is not sent, a repeat delimiter must be sent first for the first repetition. The components for this data type are described in Chapter 2.
Beginning with Version 2.3, if the guarantor is a person, send a null value ("") in GT1-21-guarantor organization name and put the person name in GT1-3-guarantor person name. Either guarantor person name or guarantor organization name is required.

6.4.5.22 Guarantor billing hold flag (ID) 00773

Definition: Refer to HL7 table 0136 - Yes/no indicator for valid values. This field indicates whether or not a system should suppress printing of the guarantor's bills.
Y a system should suppress printing of guarantor's bills
N a system should not suppress printing of guarantor's bills

6.4.5.23 Guarantor credit rating code (CE) 00774

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field contains the guarantor's credit rating.

6.4.5.24 Guarantor death date and time (TS) 00775

Definition: This field is used to indicate the date and time at which the guarantor's death occurred.

6.4.5.25 Guarantor death flag (ID) 00776

Definition: This field indicates whether or not the guarantor is deceased. Refer to HL7 table 0136 - Yes/no indicator for valid values.
Y the guarantor is deceased
N the guarantor is living

6.4.5.26 Guarantor charge adjustment code (CE) 00777

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field contains user-defined codes that indicate which adjustments should be made to this guarantor's charges. For example, when the hospital agrees to adjust this guarantor's charges to a sliding scale. Refer to user-defined table 0218 - Charge adjustment for suggested values.
Example: This field would contain the value used for sliding-fee scale processing.

6.4.5.27 Guarantor household annual income (CP) 00778

Components: <price (MO)> ^ <price type (ID)> ^ <from value (NM)> ^ <to value (NM)> ^ <range units (CE)> ^ <range type (ID)>
Subcomponents of price: <quantity (NM)> & <denomination (ID)>
Subcomponents of range units: <identifier (ST)> & <text (ST)> & <name of coding system (ST)> & <alternate identifier (ID)> & <alternate text (ST)> & <name of alternate coding system (ST)>
Definition: This field contains the combined annual income of all members of the guarantor's household.

6.4.5.28 Guarantor household size (NM) 00779

Definition: This field specifies the number of people living at the guarantor's primary residence.

6.4.5.29 Guarantor employer identification number (CX) 00780

Components: <ID (ST)> ^ <check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <assigning authority (HD)> ^ <identifier type code (IS)> ^ <assigning facility (HD)
Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Definition: This is a code that uniquely identifies the guarantor's employer when the employer is a person. It may be a user-defined code or a code defined by a government agency (Federal Tax ID#).
When further breakdowns of employer information are needed, such as a division or plant, it is recommended that the coding scheme incorporate the relationships (e.g., define separate codes for each division).

6.4.5.30 Guarantor marital status code (IS) 00781

Definition: This field contains the marital status of the guarantor. Refer to user-defined table 0002 - Marital status for suggested values.

6.4.5.31 Guarantor hire effective date (DT) 00782

Definition: This field contains the date that the guarantor's employment began.

6.4.5.32 Guarantor employment stop date (DT) 00783

Definition: This field indicates the date on which the guarantor's employment with a particular employer ended.

6.4.5.33 Living dependency (IS) 00755

Definition: Identifies the specific living conditions of the guarantor. Refer to user-defined table 0223 - Living dependency for suggested values.

6.4.5.34 Ambulatory status code (IS) 00145

Definition: Identifies the transient state of mobility for the guarantor. Refer to user-defined table 0009 - Ambulatory status for suggested values.

6.4.5.35 Citizenship (IS) 00129

Definition: This field contains the code to identify the guarantor's citizenship. HL7 recommends using ISO table 3166 as the suggested values in user-defined table 0171 - Citizenship.

6.4.5.36 Primary language (CE) 00118

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field identifies the guarantor's primary speaking language. HL7 recommends using ISO table 639 as the suggested values in user-defined table 0296 - Language.

6.4.5.37 Living arrangement (IS) 00742

Definition: This field identifies the situation in which the person lives at his residential address. Refer to the user-defined table 0220- Living arrangement for suggested values.

6.4.5.38 Publicity indicator (CE) 00743

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field contains a user-defined code indicating what level of publicity is allowed (e.g., No Publicity, Family Only) for a guarantor. Refer to user-defined table 0215 - Publicity indicator for suggested values.

6.4.5.39 Protection indicator (ID) 00744

Definition: This field identifies the guarantor's protection, which determines whether or not access to information about this enrollee should be restricted from users who do not have adequate authority. Refer to HL7 table 0136 - Yes/no indicator for valid values.
Y restrict access
N do not restrict access

6.4.5.40 Student indicator (IS) 00745

Definition: This field indicates whether the guarantor is currently a student, and whether the patient is a full-time or part-time student. This field does not indicate the degree level (high school, college) of the student, or his/her field of study (accounting, engineering, etc.). Refer to user-defined table 0231- Student status for suggested values.

6.4.5.41 Religion (IS) 00120

Definition: This field indicates the type of religion practiced by the guarantor. Refer to user-defined table 0006 - Religion for suggested values.

6.4.5.42 Mother's maiden name (XPN) 00746

Components: <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <name type code (ID) >
Definition: This field indicates the guarantor's mother's maiden name.

6.4.5.43 Nationality (CE) 00739

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field contains a code that identifies the nation or national grouping to which the person belongs. This may be different from a person's citizenship in countries in which multiple nationalities are recognized (for example, Spain: Basque, Catalan, etc.). HL7 recommends using ISO table 3166 as suggested values in user-defined table 0212 - Nationality.

6.4.5.44 Ethnic group (IS) 00125

Definition: This field contains the guarantor's ethnic or race group. ERISA has a published list of ethnic classifications that may be used by local agreement at a site. Refer to user-defined table 0189 - Ethnic group for suggested values.

6.4.5.45 Contact person's name (XPN) 00748

Components: <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <name type code (ID) >
Definition: This field contains the name of the person who should be contacted regarding the guarantor bills, etc. This may be someone other than the guarantor. (Contact guarantor's wife regarding all bills - guarantor lives out of country). The components for this data type are described in Chapter 2.
This is a repeating field that allows for multiple names for the same person. The legal name is assumed to be in the first repetition. When the legal name is not sent, a repeat delimiter must be sent first for the first repetition.

6.4.5.46 Contact person phone number (XTN) 00749

Components: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] ^ <telecommunication use code (ID)> ^ <telecommunication equipment type (ID)> ^ <email address (ST)> ^ <country code (NM)> ^ <area/city code (NM)> ^ <phone number (NM)> ^ <extension (NM)> ^ <any text (ST)>
Definition: This field contains the telephone number of the guarantor (person) to contact regarding guarantor bills, etc. Multiple phone numbers for that person may be sent in this sequence. The primary telephone number is assumed to be in the first repetition. When the primary telephone number is not sent, a repeat delimiter must be sent first for the first repetition. The components for this data type are described in Chapter 2.

6.4.5.47 Contact reason (CE) 00747

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field contains a user-defined code that identifies the reason for contacting the guarantor, for example, to phone the guarantor if payments are late. Refer to user-defined table 0222 - Contact reason for suggested values.

6.4.5.48 Contact relationship code (IS) 00784

Definition: Identifies the guarantor relationship to the contact person specified above. Some examples of the relationship between the guarantor and the guarantor contact person might include wife, attorney, power of attorney, self, and organization. Refer to user-defined table 0063 - Relationship for suggested values.

6.4.5.49 Job title (ST) 00785

Definition: This field contains a descriptive name of the guarantor's occupation (e.g., Sr. Systems Analyst, Sr. Accountant).

6.4.5.50 Job code/class (JCC) 00786

Components: <job code (IS)> ^ <job class (IS)>
Definition: This field contains the guarantor's job code and employee classification. Refer to user-defined tables 0327 - Job code and 0328 - Job class for suggested values.

6.4.5.51 Guarantor employer's organization name (XON) 01299

Components: <organization name (ST)> ^ <organization name type code (ID)> ^ <ID number (ID)> ^ <check digit (NM)> ^ < check digit scheme (ID)> ^ <assigning authority (HD)> ^ <identifier type code (ID)> ^ <assigning facility ID (HD)>
Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Definition: This field contains the name of the guarantor's employer when the guarantor's employer is an organization. When the guarantor's employer is a person, use GT1-16 guarantor employer name. Multiple names for the same guarantor may be sent in this field. The legal name is assumed to be in the first repetition. When the legal name is not sent, a repeat delimiter must be sent first for the first repetition. The components of this data type are described in Chapter 2.

6.4.5.52 Handicap (IS) 00753

Definition: This field contains a code to describe the guarantor's disability. Refer to user-defined table 0310 - Handicap for suggested values.

6.4.5.53 Job status (IS) 00752

Definition: This field contains a code that identifies the guarantor's current job status, for example, part- time/workers comp, full-time/leave of absence, full-time/suspended. Refer to user-defined table 0311 - Job status for suggested values.

6.4.5.54 Guarantor financial class (FC) 01231

Components: <financial class (IS)> ^ <effective date (TS)>
Definition: This field contains the financial class (FC) assigned to the guarantor for the purpose of identifying sources of reimbursement. It can be different than that of the patient. When the FC of the guarantor is different than the FC of the patient, and the guarantor's coverage for that patient has been exhausted, the source of reimbursement falls back onto the FC of the patient. Refer to user-defined table 0064 - Financial class for suggested values.

6.4.5.55 Guarantor race (IS) 01291

Definition: This field refers to the guarantor's race. Refer to user-defined table 0005 - Race for suggested values.

6.4.6 IN1 - insurance segment

The IN1 segment contains insurance policy coverage information necessary to produce properly pro-rated and patient and insurance bills.

6.4.6.0 IN1 field definitions

6.4.6.1 Set ID - IN1 (SI) 00426

Definition: IN1-1-set ID contains the number that identifies this transaction. For the first occurrence the sequence number shall be 1, for the second occurrence it shall be 2, etc.

6.4.6.2 Insurance plan ID (CE) 00427

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field contains a unique identifier for the insurance plan. Refer to user-defined table 0072 - Insurance plan ID. To eliminate a plan, the plan could be sent with null values in each subsequent element. If the respective systems can support it, a null value can be sent in the plan field.

6.4.6.3 Insurance company ID (CX) 00428

Components: <ID (ST)> ^ <check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <assigning authority (HD)> ^ <identifier type code (IS)> ^ <assigning facility (HD)>
Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Definition: This field contains a unique identifier the insurance company.

6.4.6.4 Insurance company name (XON) 00429

Components: <organization name (ST)> ^ <organization name type code (ID)> ^ <ID number (ID)> ^ <check digit (NM)> ^ < check digit scheme (ID)> ^ <assigning authority (HD)> ^ <identifier type code (ID)> ^ <assigning facility ID (HD)>
Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Definition: This field contains the name of the insurance company. Multiple names for the same insurance company may be sent in this field. The legal name is assumed to be in the first repetition. When the legal name is not sent, a repeat delimiter must be sent first for the first repetition. The components of this data type are described in Chapter 2.

6.4.6.5 Insurance company address (XAD) 00430

Components: <street address (ST)> ^ <other designation (ST)> ^ <city (ST)> ^ <state or province (ST)> ^ <zip or postal code(ST)> ^ <country (ID)> ^ < address type (ID)> ^ <other geographic designation (ST)>^ <county/parish code (IS)> ^ <census tract (IS)>
Definition: This field contains the address of the insurance company. Multiple addresses for the same insurance company may be sent in this field. The mailing address is assumed to be in the first repetition. When the mailing address is not sent, a repeat delimiter must be sent first for the first repetition.

6.4.6.6 Insurance co contact person (XPN) 00431

Components: <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <name type code (ID) >
Definition: This field contains the name of the person who should be contacted at the insurance company. Multiple names for the same contact person may be sent in this field. The legal name is assumed to be in the first repetition. When the legal name is not sent, a repeat delimiter must be sent first for the first repetition. The components of this data type are described in Chapter 2.

6.4.6.7 Insurance co phone number (XTN) 00432

Components: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] ^ <telecommunication use code (ID)> ^ <telecommunication equipment type (ID)> ^ <email address (ST)> ^ <country code (NM)> ^ <area/city code (NM)> ^ <phone number (NM)> ^ <extension (NM)> ^ <any text (ST)>
Definition: This field contains the phone number of the insurance company. Multiple phone numbers for the same insurance company may be sent in this field. The primary phone number is assumed to be in the first repetition. When the primary phone number is not sent, a repeat delimiter must be sent first for the first repetition. The components of this data type are described in Chapter 2.

6.4.6.8 Group number (ST) 00433

Definition: This field contains the group number of the insured's insurance.

6.4.6.9 Group name (XON) 00434

Components: <organization name (ST)> ^ <organization name type code (ID)> ^ <ID number (ID)> ^ <check digit (NM)> ^ < check digit scheme (ID)> ^ <assigning authority (HD)> ^ <identifier type code (ID)> ^ <assigning facility ID (HD)>
Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Definition: This field contains the group name of the insured's insurance. The components of this data type are described in Chapter 2.

6.4.6.10 Insured's group emp. ID (CX) 00435

Components: <ID (ST)> ^ <check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <assigning authority (HD)> ^ <identifier type code (IS)> ^ <assigning facility (HD)
Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Definition: This field holds the group employer ID for the insured's insurance.

6.4.6.11 Insured's group emp name (XON) 00436

Components: <organization name (ST)> ^ <organization name type code (ID)> ^ <ID number (ID)> ^ <check digit (NM)> ^ < check digit scheme (ID)> ^ <assigning authority (HD)> ^ <identifier type code (ID)> ^ <assigning facility ID (HD)>
Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Definition: This field contains the name of the employer that provides the employee's insurance. Multiple names for the same employer may be sent in this sequence. The legal name must be sent first. When the legal name is not sent, a repeat delimiter must be sent first for the first repetition. The components of this data type are described in Chapter 2.

6.4.6.12 Plan effective date (DT) 00437

Definition: This field contains the date that the insurance goes into effect.

6.4.6.13 Plan expiration date (DT) 00438

Definition: This field indicates the last date of service that the insurance will cover or be responsible for.

6.4.6.14 Authorization information (CM) 00439

Components: <authorization number (ST)> ^ <date (DT)> ^ <source (ST)>
Definition: Based on the type of insurance, some coverage plans require that an authorization number or code be obtained prior to all non-emergency admissions, and within 48 hours of an emergency admission. Insurance billing would not be permitted without this number. The date and source of authorization are the components of this field.

6.4.6.15 Plan type (IS) 00440

Definition: This field contains the coding structure that identifies the various plan types, for example, Medicare, Medicaid, Blue Cross, HMO, etc. Refer to user-defined table 0086 - Plan ID for suggested values.

6.4.6.16 Name of insured (XPN) 00441

Components: <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <name type code (ID) >
Definition: This field contains the name of the insured person. The insured is the person who has an agreement with the insurance company to provide healthcare services to persons covered by the insurance policy. Multiple names for the same insured person may be sent in this field. The legal name is assumed to be in the first repetition. When the legal name is not sent, a repeat delimiter must be sent first for the first repetition. The components of this data type are described in Chapter 2.

6.4.6.17 Insured's relationship to patient (IS) 00442

Definition: This field indicates the insured's relationship to the patient. Refer to user-defined table 0063 - Relationship for suggested values.

6.4.6.18 Insured's date of birth (TS) 00443

Definition: This field contains the date of birth of the insured.

6.4.6.19 Insured's address (XAD) 00444

Components: <street address (ST)> ^ <other designation (ST)> ^ <city (ST)> ^ <state or province (ST)> ^ <zip or postal code(ST)> ^ <country (ID)> ^ < address type (ID)> ^ <other geographic designation (ST)> ^ <county/parish code (IS)> ^ <census tract (IS)>
Definition: This field contains the address of the insured person. The insured is the person who has an agreement with the insurance company to provide healthcare services to persons covered by an insurance policy. Multiple addresses for the same insured person may be in this field. The mailing address must be sent in the first repetition. When the legal name is not sent, a repeat delimiter must be sent first for the first repetition.

6.4.6.20 Assignment of benefits (IS) 00445

Definition: This field indicates whether the insured agreed to assign the insurance benefits to the healthcare provider. If so, the insurance will pay the provider directly. Refer to user-defined table 0135 - Assignment of benefits for suggested values.

6.4.6.21 Coordination of benefits (IS) 00446

Definition: This field indicates whether this insurance works in conjunction with other insurance plans, or if it provides independent coverage and payment of benefits regardless of other insurance that might be available to the patient. Refer to user-defined table 0173 - Coordination of benefits for suggested values.

6.4.6.22 Coord of ben priority (ST) 00447

Definition: If the insurance works in conjunction with other insurance plans, this field contains priority sequence. Values are: 1, 2, 3, etc.

6.4.6.23 Notice of admission flag (ID) 00448

Definition: This field indicates whether the insurance company requires a written notice of admission from the healthcare provider. Refer to HL7 table 0136 - Yes/no indicator for valid values.

6.4.6.24 Notice of admission date (DT) 00449

Definition: If a notice is required, this field indicates the date that it was sent.

6.4.6.25 Report of eligibility flag (ID) 00450

Definition: This field indicates whether this insurance carrier sends a report that indicates that the patient is eligible for benefits and whether it identifies those benefits. Refer to HL7 table 0136 - Yes/no indicator for valid values.

6.4.6.26 Report of eligibility date (DT) 00451

Definition: This field indicates whether a report of eligibility (ROE) was received, and also indicates the date that it was received.

6.4.6.27 Release information code (IS) 00452

Definition: This field indicates whether the healthcare provider can release information about the patient, and what information can be released. Refer to user-defined table 0093 - Release information code for suggested values.

6.4.6.28 Pre-admit cert. (PAC) (ST) 00453

Definition: This field contains the pre-admission certification code. If the admission must be certified before the admission, this is the code associated with the admission.

6.4.6.29 Verification date/time (TS) 00454

Definition: This field contains the date/time that the healthcare provider verified that the patient has the indicated benefits.

6.4.6.30 Verification by (XCN) 00455

Components: <ID number (ST)> ^ <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <source table (IS)> ^ <assigning authority (HD)> ^ <name type code(ID)> ^ <identifier check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <identifier type code (IS)> ^ <assigning facility (HD)>
Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Definition: Refers to the person who verified the benefits. Multiple names for the same insured person may be sent in this field. The legal name is assumed to be in the first repetition. When the legal name is not sent, a repeat delimiter must be sent first for the first repetition. The components of this data type are described in Chapter 2.

6.4.6.31 Type of agreement code (IS) 00456

Definition: This field is used to further identify an insurance plan. Refer to user-defined table 0098 - Type of agreement for suggested values. Refer to user-defined table 0098 - Type of agreement for suggested values.

6.4.6.32 Billing status (IS) 00457

Definition: This field indicates whether the particular insurance has been billed and, if so, the type of bill. Refer to user-defined table 0022 - Billing status for suggested values.

6.4.6.33 Lifetime reserve days (NM) 00458

Definition: This field contains the number of days left for a certain service to be provided or covered under an insurance policy.

6.4.6.34 Delay before L.R. day (NM) 00459

Definition: This field indicates the delay before lifetime reserve days.

6.4.6.35 Company plan code (IS) 00460

Definition: This field contains optional information to further define the data in IN1-3-insurance company ID. Refer to user-defined table 0042 - Company plan code. This table contains codes used to identify an insurance plan uniquely.

6.4.6.36 Policy number (ST) 00461

Definition: This field contains the individual policy number of the insured to uniquely identify this patient's plan. For special types of insurance numbers, there are also special fields in the IN2 segment for Medicaid, Medicare, Champus (i.e., IN2-8-Medicaid case number, IN2-6-Medicare health ins card number, IN2-10-Champus ID number). But we recommend that this field (IN1-36-policy number) be filled even when the patient's insurance number is also passed in one of these other fields.

6.4.6.37 Policy deductible (CP) 00462

Components: <price (MO)> ^ <price type (ID)> ^ <from value (NM)> ^ <to value (NM)> ^ <range units (CE)> ^ <range type (ID)>
Subcomponents of price: <quantity (NM)> & <denomination (ID)>
Subcomponents of range units: <identifier (ST)> & <text (ST)> & <name of coding system (ST)> & <alternate identifier (ID)> & <alternate text (ST)> & <name of alternate coding system (ST)>
Definition: This field contains the amount specified by the insurance plan that is the responsibility of the guarantor.

6.4.6.38 Policy limit - amount (CP) 00463

Components: <price (MO)> ^ <price type (ID)> ^ <from value (NM)> ^ <to value (NM)> ^ <range units (CE)> ^ <range type (ID)>
Subcomponents of price: <quantity (NM)> & <denomination (ID)>
Subcomponents of range units: <identifier (ST)> & <text (ST)> & <name of coding system (ST)> & <alternate identifier (ID)> & <alternate text (ST)> & <name of alternate coding system (ST)>
Definition: This field has been retained for backward compatibility only. Use IN2-policy type/amount instead of this field. This field contains the maximum amount that the insurance policy will pay. In some cases, the limit may be for a single encounter.

6.4.6.39 Policy limit - days (NM) 00464

Definition: This field contains the maximum number of days that the insurance policy will cover.

6.4.6.40 Room rate - semi-private (CP) 00465

Components: <price (MO)> ^ <price type (ID)> ^ <from value (NM)> ^ <to value (NM)> ^ <range units (CE)> ^ <range type (ID)>
Subcomponents of price: <quantity (NM)> & <denomination (ID)>
Subcomponents of range units: <identifier (ST)> & <text (ST)> & <name of coding system (ST)> & <alternate identifier (ID)> & <alternate text (ST)> & <name of alternate coding system (ST)>
Definition: This field has been retained for backward compatibility only. Use IN2-28-room coverage type/amount instead of this field. When used for backward compatibility, IN2-40-room rate-semi-primate contains the average room rate that the policy covers.

6.4.6.41 Room rate - private (CP) 00466

Components: <price (MO)> ^ <price type (ID)> ^ <from value (NM)> ^ <to value (NM)> ^ <range units (CE)> ^ <range type (ID)>
Subcomponents of price: <quantity (NM)> & <denomination (ID)>
Subcomponents of range units: <identifier (ST)> & <text (ST)> & <name of coding system (ST)> & <alternate identifier (ID)> & <alternate text (ST)> & <name of alternate coding system (ST)>
Definition: This field has been retained for backward compatibility only. Use IN2-28-room coverage type/amount instead of this field. When used for backward compatibility IN2-29-room rate-private contains the maximum private room rate that the policy covers.

6.4.6.42 Insured's employment status (CE) 00467

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: Refer to user-defined table 0066 - Employment status for suggested values.

6.4.6.43 Insured's sex (IS) 00468

Definition: This field contains the gender of the insured. Refer to user-defined table 0001 - Sex for valid values.

6.4.6.44 Insured's employer's address (XAD) 00469

Components: <street address (ST)> ^ <other designation (ST)> ^ <city (ST)> ^ <state or province (ST)> ^ <zip or postal code(ST)> ^ <country (ID)> ^ < address type (ID)> ^ <other geographic designation (ST)> ^ <county/parish code (IS)> ^ <census tract (IS)>
Definition: This field contains the address of the insured employee's employer. Multiple addresses for the same employer may be sent in this field. The mailing address must be sent first. When the mailing address is not sent, a repeat delimiter must be sent first for the first repetition.

6.4.6.45 Verification status (ST) 00470

Definition: This field contains the status of this patient's relationship with this insurance carrier.

6.4.6.46 Prior insurance plan ID (IS) 00471

Definition: This field uniquely identifies the prior insurance plan when the plan ID changes. Refer to user-defined table 0072 - Insurance plan ID for suggested values.

6.4.6.47 Coverage type (IS) 01227

Definition: This field contains the coding structure that identifies the type of insurance coverage, or what type of services are covered for the purposes of a billing system. For example, a physician billing system will only want to receive insurance information for plans which cover physician/professional charges. Refer to user-defined table 0309 - Coverage type for suggested values.

6.4.6.48 Handicap code (IS) 00753

Definition: This field contains a code to describe the insured's disability. Refer to user-defined table 0310 - Handicap for suggested values.

6.4.6.49 Insured's ID number (CX) 01230

Components: <ID (ST)> ^ <check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <assigning authority (HD)> ^ <identifier type code (IS)> ^ <assigning facility (HD)
Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Definition: This data element contains a healthcare institution's identifiers for the insured.

6.4.7 IN2 - insurance additional information segment

The IN2 segment contains additional insurance policy coverage and benefit information necessary for proper billing and reimbursement. Fields used by this segment are defined by HCFA or other regulatory agencies.