837 Transaction Set Listing
008020X324 Health Care Claim: Institutional- Loop 1000A - SUBMITTER NAMERequired1
- Loop 1000B - RECEIVER NAMERequired1
- Loop 2000A - BILLING PROVIDER LEVELRequired>1
- Loop 2010AA - BILLING PROVIDER NAMERequired1
- Loop 2010AB - PAY-TO ADDRESSSituational1
- Loop 2010AC - PAY-TO PLAN NAMESituational1
- Loop 2010AD - PAY-TO FACTORING AGENT NAMESituational1
- Loop 2000B - SUBSCRIBER LEVELRequired>1
- Loop 2010BA - SUBSCRIBER NAMERequired1
- Loop 2010BB - PAYER NAMERequired1
- Loop 2000C - PATIENT LEVELSituational>1
- Loop 2010CA - PATIENT NAMERequired1
- Loop 2300 - CLAIM INFORMATIONRequired100
- Loop 2310A - ATTENDING PROVIDER NAMESituational1
- Loop 2310B - OPERATING PHYSICIAN NAMESituational1
- Loop 2310C - OTHER OPERATING PHYSICIAN NAMESituational1
- Loop 2310D - RENDERING PROVIDER NAMESituational1
- Loop 2310E - SERVICE LOCATION NAMESituational1
- Loop 2310F - REFERRING PROVIDER NAMESituational1
- Loop 2320 - OTHER SUBSCRIBER INFORMATIONSituational10
- Loop 2330A - OTHER SUBSCRIBER NAMERequired1
- Loop 2330B - OTHER PAYER NAMERequired1
- Loop 2330C - OTHER PAYER ATTENDING PROVIDERSituational1
- Loop 2330D - OTHER PAYER OPERATING PHYSICIANSituational1
- Loop 2330E - OTHER PAYER OTHER OPERATING PHYSICIANSituational1
- Loop 2330F - OTHER PAYER SERVICE LOCATIONSituational1
- Loop 2330G - OTHER PAYER RENDERING PROVIDERSituational1
- Loop 2330H - OTHER PAYER REFERRING PROVIDERSituational1
- Loop 2330I - OTHER PAYER BILLING PROVIDERSituational1
- Loop 2400 - SERVICE LINE NUMBERRequired999
- Loop 2410 - DRUG/SUPPLY IDENTIFICATIONSituational1
- Loop 2420A - OPERATING PHYSICIAN NAMESituational1
- Loop 2420B - OTHER OPERATING PHYSICIAN NAMESituational1
- Loop 2420C - RENDERING PROVIDER NAMESituational1
- Loop 2420D - REFERRING PROVIDER NAMESituational1
- Loop 2430 - LINE ADJUDICATION INFORMATIONSituational25
ISA - INTERCHANGE CONTROL HEADER
- For compliant implementations under this implementation guide, ISA13, the interchange Control Number, must be a positive unsigned number. Therefore, the ISA segment can be considered a fixed record length segment.
- The first element separator defines the element separator to be used through the entire interchange.
- Spaces in the example interchanges are represented by "." for clarity.
- The ISA segment terminator defines the segment terminator used throughout the entire interchange.
- All positions within each of the data elements must be filled.
- The Interchange Control Number, ISA13, must be identical to the associated Interchange Trailer IEA02.
- Must be a positive unsigned number and must be identical to the value in IEA02.
GS*HC - FUNCTIONAL GROUP HEADER
ST*837 - TRANSACTION SET HEADER
- This element must be populated with the guide identifier named in Section 1.2.
- This field contains the same value as GS08. Some translator products strip off the ISA and GS segments prior to application (ST-SE) processing. Providing the information from the GS08 at this level will ensure that the appropriate application mapping is used at translation time.
BHT*0019 - BEGINNING OF HIERARCHICAL TRANSACTION
- BHT✱0019✱00✱0123✱20220618✱0932✱CH~
- BHT✱0019✱00✱44445✱20220213✱0345✱RP~
- The inventory file number of the transmission assigned by the submitter's system. This number operates as a batch control number.
- Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
NOTE: At the time of this writing, Subrogation Demand is not a HIPAA mandated use of the 837 transaction.
NM1*41 - SUBMITTER NAME
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
PER*IC - SUBMITTER EDI CONTACT INFORMATION
- P0304
If either PER03 or PER04 is present, then the other is required. - P0506
If either PER05 or PER06 is present, then the other is required. - P0708
If either PER07 or PER08 is present, then the other is required.
- When the communication number represents a telephone number in the United States and other countries using the North American Dialing Plan (for voice, data, fax, etc.), the communication number must always include the area code and phone number using the format AAABBBCCCC where AAA is the area code, BBB is the telephone number prefix, and CCCC is the telephone number. Therefore, the following telephone number (555) 555-1234 would be represented as 5555551234. Do not submit long distance access numbers, such as 1, in the telephone number. Telephone extensions, when applicable, must be submitted in the next element immediately following the telephone number. When submitting telephone extensions, only submit the numeric extension, do not include data that indicates an extension, such as "ext" or "x-".
- The contact information in this segment identifies the person in the submitter organization who deals with data transmission issues. If data transmission problems arise, this is the person to contact in the submitter organization.
- There are 2 repetitions of the PER segment to allow for six possible communication numbers including extensions.
NM1*40 - RECEIVER NAME
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
HL - BILLING PROVIDER LEVEL
- The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.
- The HL segment defines a top-down/left-right ordered structure.
PRV*BI - BILLING PROVIDER SPECIALTY INFORMATION
If either PRV02 or PRV03 is present, then the other is required.
CUR*85 - FOREIGN CURRENCY INFORMATION
- C0807
If CUR08 is present, then CUR07 is required. - C0907
If CUR09 is present, then CUR07 is required. - L101112
If CUR10 is present, then at least one of CUR11 or CUR12 are required. - C1110
If CUR11 is present, then CUR10 is required. - C1210
If CUR12 is present, then CUR10 is required. - L131415
If CUR13 is present, then at least one of CUR14 or CUR15 are required. - C1413
If CUR14 is present, then CUR13 is required. - C1513
If CUR15 is present, then CUR13 is required. - L161718
If CUR16 is present, then at least one of CUR17 or CUR18 are required. - C1716
If CUR17 is present, then CUR16 is required. - C1816
If CUR18 is present, then CUR16 is required. - L192021
If CUR19 is present, then at least one of CUR20 or CUR21 are required. - C2019
If CUR20 is present, then CUR19 is required. - C2119
If CUR21 is present, then CUR19 is required.
NM1*85 - BILLING PROVIDER NAME
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
- When the entity is not a Health Care provider (for example, personal care services, carpenters, etc.), the Billing Provider should be the legal entity. However, willing trading partners may agree upon varying definitions. Proprietary identifiers necessary for the receiver to identify the entity are to be reported in the Loop ID-2010BB REF, Billing Provider Secondary Identification segment.
- When the Billing Provider is an organization health care provider, the organization health care provider's NPI or its subpart's NPI is reported in NM109. When a health care provider organization has determined that it needs to enumerate its subparts, it will report the NPI of a subpart as the Billing Provider. The subpart reported as the Billing Provider MUST always represent the most detailed level of enumeration as determined by the organization health care provider and MUST be the same identifier sent to any trading partner. For additional explanation, see section 1.10.3 Organization Health Care Provider Subpart Presentation.
N3 - BILLING PROVIDER ADDRESS
- Post Office Box or Lock Box addresses are to be sent in the Pay-To Address Loop (Loop ID-2010AB), if necessary.
- The Billing Provider Address must be a street address. If billing provider location is in an area where there are no street addresses, enter a description of the location (for example, "crossroad of State Road 34 and 45" or "Exit near Mile marker 265 on Interstate 80").
N4 - BILLING PROVIDER CITY, STATE, ZIP CODE
- E0207
Only one of N402 or N407 may be present. - E0308
Only one of N403 or N408 may be present. - C0605
If N406 is present, then N405 is required. - C0704
If N407 is present, then N404 is required.
- CODE SOURCE 51: ZIP Code
- CODE SOURCE 932: Universal Postal Codes
REF*EI - BILLING PROVIDER TAX IDENTIFICATION
At least one of REF02 or REF03 is required.
The Employer's Identification Number must be a string of exactly nine numbers with no separators.
For example, "001122333" would be valid, while sending "001-12-2333" or "00-1122333" would be invalid.
PER*IC - BILLING PROVIDER CONTACT INFORMATION
- P0304
If either PER03 or PER04 is present, then the other is required. - P0506
If either PER05 or PER06 is present, then the other is required. - P0708
If either PER07 or PER08 is present, then the other is required.
AND
Loop ID-2010AC (Pay-to Plan) or Loop ID-2010AD (Pay-to Factoring Agent) is present. If not required by implementation guide, do not send.
- When the communication number represents a telephone number in the United States and other countries using the North American Dialing Plan (for voice, data, fax, etc.), the communication number must always include the area code and phone number using the format AAABBBCCCC where AAA is the area code, BBB is the telephone number prefix, and CCCC is the telephone number. Therefore, the following telephone number (555) 555-1234 would be represented as 5555551234. Do not submit long distance access numbers, such as 1, in the telephone number. Telephone extensions, when applicable, must be submitted in the next element immediately following the telephone number. When submitting telephone extensions, only submit the numeric extension, do not include data that indicates an extension, such as "ext" or "x-".
- There are 2 repetitions of the PER segment to allow for six possible communication numbers including extensions.
NM1*87 - PAY-TO ADDRESS
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
N3 - PAY-TO ADDRESS - ADDRESS
- N3✱1234 MAIN STREET✱FLOOR 5~
- N3✱PO BOX 123~
N4 - PAY-TO ADDRESS CITY, STATE, ZIP CODE
- E0207
Only one of N402 or N407 may be present. - E0308
Only one of N403 or N408 may be present. - C0605
If N406 is present, then N405 is required. - C0704
If N407 is present, then N404 is required.
- CODE SOURCE 51: ZIP Code
- CODE SOURCE 932: Universal Postal Codes
NM1*PTP - PAY-TO PLAN NAME
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
N3 - PAY-TO PLAN ADDRESS
N4 - PAY-TO PLAN CITY, STATE, ZIP CODE
- E0207
Only one of N402 or N407 may be present. - E0308
Only one of N403 or N408 may be present. - C0605
If N406 is present, then N405 is required. - C0704
If N407 is present, then N404 is required.
- CODE SOURCE 51: ZIP Code
- CODE SOURCE 932: Universal Postal Codes
REF*2U - PAY-TO PLAN SECONDARY IDENTIFICATION
At least one of REF02 or REF03 is required.
OR
Required when an additional identification number to that provided in the NM109 of this loop is necessary to identify the entity.
If not required by this implementation guide, do not send.
REF*EI - PAY-TO PLAN TAX IDENTIFICATION NUMBER
At least one of REF02 or REF03 is required.
The Employer's Identification Number must be a string of exactly nine numbers with no separators.
For example, "001122333" would be valid, while sending "001-12-2333" or "00-1122333" would be invalid.
NM1*O4 - PAY-TO FACTORING AGENT NAME
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
- This segment is not a HIPAA requirement as of this writing.
- This loop must not be used if the 2010AC Pay-to Plan loop is used.
N3 - PAY-TO FACTORING AGENT ADDRESS
N4 - PAY-TO FACTORING AGENT CITY, STATE, ZIP CODE
- E0207
Only one of N402 or N407 may be present. - E0308
Only one of N403 or N408 may be present. - C0605
If N406 is present, then N405 is required. - C0704
If N407 is present, then N404 is required.
- CODE SOURCE 51: ZIP Code
- CODE SOURCE 932: Universal Postal Codes
REF*2U - PAY-TO FACTORING AGENT SECONDARY IDENTIFICATION
At least one of REF02 or REF03 is required.
OR
Required when an additional identification number to that provided in the NM109 of this loop is necessary to identify the entity.
If not required by this implementation guide, do not send.
REF - PAY-TO FACTORING AGENT TAX IDENTIFICATION NUMBER
At least one of REF02 or REF03 is required.
The Employer's Identification Number must be a string of exactly nine numbers with no separators.
For example, "001122333" would be valid, while sending "001-12-2333" or "00-1122333" would be invalid.
The Social Security Number must be a string of exactly nine numbers with no separators.
For example, sending "111002222" would be valid, while sending "111-00-2222" would be invalid.
PER*IC - PAY-TO FACTORING AGENT CONTACT INFORMATION
- P0304
If either PER03 or PER04 is present, then the other is required. - P0506
If either PER05 or PER06 is present, then the other is required. - P0708
If either PER07 or PER08 is present, then the other is required.
- When the communication number represents a telephone number in the United States and other countries using the North American Dialing Plan (for voice, data, fax, etc.), the communication number must always include the area code and phone number using the format AAABBBCCCC where AAA is the area code, BBB is the telephone number prefix, and CCCC is the telephone number. Therefore, the following telephone number (555) 555-1234 would be represented as 5555551234. Do not submit long distance access numbers, such as 1, in the telephone number. Telephone extensions, when applicable, must be submitted in the next element immediately following the telephone number. When submitting telephone extensions, only submit the numeric extension, do not include data that indicates an extension, such as "ext" or "x-".
- There are 2 repetitions of the PER segment to allow for six possible communication numbers including extensions.
HL - SUBSCRIBER LEVEL
- The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.
- The HL segment defines a top-down/left-right ordered structure.
- If a patient can be uniquely identified to the destination payer in Loop ID-2010BB by a unique Member Identification Number, then the patient is reported in the subscriber loop, and the patient HL in Loop ID-2000C is not used.
- If the patient is not the subscriber and cannot be identified to the destination payer by a unique Member Identification Number or it is not known to the sender if the Member Identification number is unique, both this HL and the patient HL in Loop ID-2000C are required.
SBR - SUBSCRIBER INFORMATION
- Within a given claim, the various values for the Payer Responsibility Sequence Number Code (other than value "U") may occur no more than once.
- This code value identifies, in the opinion of the submitter, the relative adjudication order of the destination payer among all of the payers identified in this claim.
OR
Use when the original claim did not provide the responsibility sequence for this payer.
- This is not the number uniquely identifying the subscriber. The unique subscriber number is submitted in Loop ID-2010BA-NM109.
- Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
NM1*IL - SUBSCRIBER NAME
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
This data element is used only to indicate generation or patronymic.
N3 - SUBSCRIBER ADDRESS
OR
Required when the Claim Filing Indicator Code in Loop ID-2000B SBR09 = WC (Workers' Compensation). If not required by this implementation guide, do not send.
N4 - SUBSCRIBER CITY, STATE, ZIP CODE
- E0207
Only one of N402 or N407 may be present. - E0308
Only one of N403 or N408 may be present. - C0605
If N406 is present, then N405 is required. - C0704
If N407 is present, then N404 is required.
OR
Required when the Claim Filing Indicator Code in Loop ID-2000B SBR09 = WC (Workers' Compensation). If not required by this implementation guide, do not send.
- CODE SOURCE 51: ZIP Code
- CODE SOURCE 932: Universal Postal Codes
DMG*D8 - SUBSCRIBER DEMOGRAPHIC INFORMATION
- P0102
If either DMG01 or DMG02 is present, then the other is required. - P1011
If either DMG10 or DMG11 is present, then the other is required. - C1105
If DMG11 is present, then DMG05 is required.
REF*SY - SUBSCRIBER SOCIAL SECURITY NUMBER
At least one of REF02 or REF03 is required.
The Social Security Number must be a string of exactly nine numbers with no separators.
For example, sending "111002222" would be valid, while sending "111-00-2222" would be invalid.
REF*Y4 - PROPERTY & CASUALTY CLAIM NUMBER
At least one of REF02 or REF03 is required.
OR
Required when the services included in this claim are considered Workers' Compensation and the claim number has been established by the payer at the time of service. If not required by this implementation guide, do not send.
- This is a Property & Casualty payer-assigned claim number. Providers receive this number from the Property & Casualty payer during eligibility determinations or some other communication with that payer. See Section 1.4.3, Property & Casualty, for additional information about Property & Casualty claims.
- This segment is not a HIPAA requirement as of this writing.
- In the case where the patient is the same person as the subscriber, the Property & Casualty Claim Number is sent in Loop ID-2010BA. In the case where the patient is a different person than the subscriber, this number is sent in Loop ID-2010CA. If Loop ID-2010CA is sent, then the Property & Casualty Claim Number must not be sent in Loop ID-2010BA.
PER*IC - PROPERTY & CASUALTY SUBSCRIBER CONTACT INFORMATION
- P0304
If either PER03 or PER04 is present, then the other is required. - P0506
If either PER05 or PER06 is present, then the other is required. - P0708
If either PER07 or PER08 is present, then the other is required.
- When the communication number represents a telephone number in the United States and other countries using the North American Dialing Plan (for voice, data, fax, etc.), the communication number must always include the area code and phone number using the format AAABBBCCCC where AAA is the area code, BBB is the telephone number prefix, and CCCC is the telephone number. Therefore, the following telephone number (555) 555-1234 would be represented as 5555551234. Do not submit long distance access numbers, such as 1, in the telephone number. Telephone extensions, when applicable, must be submitted in the next element immediately following the telephone number. When submitting telephone extensions, only submit the numeric extension, do not include data that indicates an extension, such as "ext" or "x-".
- For Property & Casualty, the Property & Casualty Subscriber Contact may be used to report the name and telephone number of the policyholder. The policyholder for automobile accident claims is typically the individual or company listed on the proof of insurance card. The policyholder for workers' compensation claims is typically the patient's employer. When the policyholder or "subscriber" is a non-person entity, it is recommended that the health care provider use the name of a responsible individual within that organization.
NM1*PR - PAYER NAME
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
- This is the destination payer.
- For the purposes of this implementation the term payer is synonymous with several other terms, such as, repricer and third party administrator.
N3 - PAYER ADDRESS
N4 - PAYER CITY, STATE, ZIP CODE
- E0207
Only one of N402 or N407 may be present. - E0308
Only one of N403 or N408 may be present. - C0605
If N406 is present, then N405 is required. - C0704
If N407 is present, then N404 is required.
- CODE SOURCE 51: ZIP Code
- CODE SOURCE 932: Universal Postal Codes
REF*2U - PAYER SECONDARY IDENTIFICATION
At least one of REF02 or REF03 is required.
OR
Required when an additional identification number to that provided in the NM109 of this loop is necessary to identify the entity.
If not required by this implementation guide, do not send.
REF - BILLING PROVIDER SECONDARY IDENTIFICATION
At least one of REF02 or REF03 is required.
HL - PATIENT LEVEL
- The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.
- The HL segment defines a top-down/left-right ordered structure.
PAT - PATIENT INFORMATION
- P0506
If either PAT05 or PAT06 is present, then the other is required. - P0708
If either PAT07 or PAT08 is present, then the other is required.
NM1*QC - PATIENT NAME
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
N3 - PATIENT ADDRESS
N4 - PATIENT CITY, STATE, ZIP CODE
- E0207
Only one of N402 or N407 may be present. - E0308
Only one of N403 or N408 may be present. - C0605
If N406 is present, then N405 is required. - C0704
If N407 is present, then N404 is required.
- CODE SOURCE 51: ZIP Code
- CODE SOURCE 932: Universal Postal Codes
DMG*D8 - PATIENT DEMOGRAPHIC INFORMATION
- P0102
If either DMG01 or DMG02 is present, then the other is required. - P1011
If either DMG10 or DMG11 is present, then the other is required. - C1105
If DMG11 is present, then DMG05 is required.
REF*Y4 - PROPERTY & CASUALTY CLAIM NUMBER
At least one of REF02 or REF03 is required.
OR
Required when the services included in this claim are considered Workers' Compensation and the claim number has been established by the payer at the time of service. If not required by this implementation guide, do not send.
- This is a Property & Casualty payer-assigned claim number. Providers receive this number from the Property & Casualty payer during eligibility determinations or some other communication with that payer. See Section 1.4.3, Property & Casualty, for additional information about Property & Casualty claims.
- This segment is not a HIPAA requirement as of this writing.
REF - PROPERTY & CASUALTY PATIENT IDENTIFIER
At least one of REF02 or REF03 is required.
The Social Security Number must be a string of exactly nine numbers with no separators.
For example, sending "111002222" would be valid, while sending "111-00-2222" would be invalid.
PER*IC - PROPERTY & CASUALTY PATIENT CONTACT INFORMATION
- P0304
If either PER03 or PER04 is present, then the other is required. - P0506
If either PER05 or PER06 is present, then the other is required. - P0708
If either PER07 or PER08 is present, then the other is required.
CLM - CLAIM INFORMATION
- The developers of this implementation guide recommend that trading partners limit the size of the transaction (ST-SE envelope) to a maximum of 5000 CLM segments. There is no recommended limit to the number of ST-SE transactions within a GS-GE or ISA-IEA. Willing trading partners can agree to set limits higher.
- For purposes of this documentation, the claim detail information is presented only in the patient level. Specific claim detail information can be given in either the subscriber or the patient hierarchical level. Because of this, the claim information is said to "float". Claim information is positioned in the same hierarchical level that describes its owner-participant, either the subscriber or the patient. In other words, the claim information, Loop ID-2300, is placed following Loop ID-2010BB in the Subscriber Hierarchical Level (HL) when patient information is sent in Loop ID-2010BA of the Subscriber HL. Claim information is placed in the Patient HL when the patient information is sent in Loop ID-2010CA of the Patient HL. When the patient is the subscriber or is considered to be the subscriber, Loop ID-2000C and Loop ID-2010CA are not sent. See Subscriber/Patient HL Segment explanation in section 1.4.4.2.2.2 for details.
- The maximum number of characters to be supported for this field is '35'. Characters beyond the maximum are not required to be stored nor returned by any 837-receiving system.
- When Loop ID-2010AC is not present, this identifier is generated by the provider for the purpose of reassociation to their claim accounts receivable, and must not be modified. This identifier, as submitted in the 837, is returned in the 835 and/or other transactions. This identifier is not to be validated beyond standard TR3 syntax and semantic rules.
- When Loop ID-2010AC is present, CLM01 represents the Pay-To Plan's claim number (ICN/DCN) assigned during their processing of the claim. See Section 1.4.2.4 Coordination of Benefits - Subrogation for information on subrogation claim reporting.
- The developers of this implementation guide strongly recommend that submitters use unique identifiers for this data element for each individual claim.
- The Total Claim Charge Amount must be greater than or equal to zero.
- The total claim charge amount must balance to the sum of all service line charge amounts reported in the Institutional Service Line (SV2) segments for this claim.
- Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
- C023-01 does not contain the last position of the Uniform Bill Type Code (the Claim Frequency Code).
- C023-02 qualifies C023-01.
- This element is NOT for reporting whether the patient has or has not assigned benefits to the provider. The benefit assignment indicator is in CLM08.
- This element indicates the provider's assignment with the Medicare Fee For Service (FFS) program and by extension the Medicare Advantage Plan (Medicare Part C).
- The value in this element does not supersede an agreement between the provider and payer regarding assignment or participation status unless that agreement allows claim by claim exceptions.
- On COB claims where Medicare is not the destination payer, assignment or participation designation with Medicare is not reported in this CLM07 element; rather, it is reported in the Loop 2320 Other Insurance Coverage Information (OI Segment) corresponding to Medicare as the other payer.
OR
Use when the provider does not have a participation agreement with Medicare but has elected to accept assignment for this claim.
OR
Use when state or federal laws require a signature be collected.
DTP*523 - ORIGINAL CLAIM CREATION DATE
DTP*096 - DISCHARGE TIME
AND
The patient was discharged from the facility
AND
The discharge time is known
AND
Loop ID-2300 CLM19 (Predetermination of Benefits Code) is not used.
If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
DTP*434 - STATEMENT DATES
DTP*435 - ADMISSION DATE/HOUR OR START OF CARE DATE
- Predetermination requests are indicated in CLM19.
- It is acceptable for the Admission Date to differ from the Statement From Date reported in Loop 2300 DTP Statement Dates.
- For inpatient services, this is the date of admission. For other services, such as home health and hospice, it is the date the episode of care began.
DTP*050 - REPRICER RECEIVED DATE
CL1 - INSTITUTIONAL CLAIM CODE
PWK - CLAIM SUPPLEMENTAL INFORMATION
- P0506
If either PWK05 or PWK06 is present, then the other is required. - P1011
If either PWK10 or PWK11 is present, then the other is required.
- PWK06 is a unique identifier assigned by the provider to be used to identify the supplemental documentation for this claim. When using the X12N 275 - Additional Information to Support a Health Care Claim or Encounter, the number in PWK06 is carried in the TRN Segment.
- For the purpose of this implementation, the maximum field length is 50.
REF*G3 - PREDETERMINATION IDENTIFICATION
At least one of REF02 or REF03 is required.
REF*EW - MAMMOGRAPHY CERTIFICATION NUMBER
At least one of REF02 or REF03 is required.
REF*9F - REFERRAL NUMBER
At least one of REF02 or REF03 is required.
REF*G1 - PRIOR AUTHORIZATION
At least one of REF02 or REF03 is required.
- This segment must not be used to report the Predetermination of Benefits Identification Number.
- Generally, prior authorization numbers are assigned by the payer or UMO to authorize a service prior to it being performed. The UMO (Utilization Management Organization) is generally the entity empowered to make a decision regarding the outcome of a health services review or is the owner of information. The prior authorization number carried in this REF is specific to the destination payer reported in the Loop ID-2010BB. If other payers have similar numbers for this claim, report that information in the Loop ID-2330B REF which holds that payer's information.
REF*F8 - PAYER CLAIM CONTROL NUMBER
At least one of REF02 or REF03 is required.
REF*9A - REPRICED CLAIM NUMBER
At least one of REF02 or REF03 is required.
- This information is specific to the destination payer reported in Loop ID-2010BB.
- This segment is not completed by providers. The information is completed by repricers only.
REF*9C - ADJUSTED REPRICED CLAIM NUMBER
At least one of REF02 or REF03 is required.
- This information is specific to the destination payer reported in Loop ID-2010BB.
- This segment is not completed by providers. The information is completed by repricers only.
REF*D9 - CLAIM IDENTIFIER FOR TRANSMISSION INTERMEDIARIES
At least one of REF02 or REF03 is required.
REF*EA - MEDICAL RECORD NUMBER
At least one of REF02 or REF03 is required.
REF*P4 - DEMONSTRATION PROJECT IDENTIFIER
At least one of REF02 or REF03 is required.
REF*G4 - PEER REVIEW ORGANIZATION (PRO) APPROVAL NUMBER
At least one of REF02 or REF03 is required.
REF*SOJ - PROPERTY & CASUALTY STATE OF CLAIM JURISDICTION
At least one of REF02 or REF03 is required.
- This segment is not a HIPAA requirement as of this writing.
- This is not the state of jurisdiction for determination of benefits but is the state whose rules under which the electronic claim has been submitted.
K3 - FILE INFORMATION
- The K3 segment is used only when necessary to meet the unexpected data requirement of a regulatory/legislative authority. Before this segment can be used:
- X12N must conclude there is no other available option in the implementation guide to meet the emergency regulatory/legislative requirement.
- The requester must submit a change request accompanied by the relevant business documentation and receive approval for the request.
Upon review of the request, X12N will issue an approval or denial decision to the requesting entity. Approved usage(s) of the K3 Segment will be reviewed by the applicable X12N work group to develop a permanent change to include the business case in future transaction implementations. - Only when all of the requirements above have been met, may the regulatory agency require the temporary use of the K3 segment.
NTE - CLAIM NOTE
OR
Required when in the judgment of the provider, narrative information from the forms "Home Health Certification and Plan of Treatment" or "Medical Update and Patient Information" is needed to substantiate home health services.
If not required by this implementation guide, do not send.
NTE*ADD - BILLING NOTE
If not required by this implementation guide, do not send.
CR8*Z - HIGH RISK IMPLANTED OR EXPLANTED DEVICE
AND
The provider and payer have mutually agreed or are mandated by state or federal laws/regulations to exchange only the Device Identifier of the Unique Device Identifier.
OR
Required when known that a high risk implantable device has been explanted due to safety concerns about premature failure
AND
The provider and payer have mutually agreed or are mandated by state or federal laws/regulations to exchange only the Device Identifier of the Unique Device Identifier.
If not required by this implementation guide, do not send.
http://accessgudid.nlm.nih.gov/
Available from:
National Library of Medicine
8600 Rockville Pike
Bethesda, MD 20894
CRC*EP - EPSDT SCREENING SERVICE AND REFERRAL INFORMATION
OR
Use when a patient is scheduled for another appointment with screening provider for diagnostic or corrective treatment for at least one health problem identified during an initial or periodic screening service (not including dental referrals).
OR
Use when a patient is scheduled for another appointment with screening provider for diagnostic or corrective treatment for at least one health problem identified during an initial or periodic screening service (not including dental referrals).
OR
Use when a patient is scheduled for another appointment with screening provider for diagnostic or corrective treatment for at least one health problem identified during an initial or periodic screening service (not including dental referrals).
HI - PRINCIPAL DIAGNOSIS
- HI✱ABK:H25032~
- HI✱ABK:H25032:::::::Y~
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
HI - ADMITTING DIAGNOSIS
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
HI - PATIENT'S REASON FOR VISIT
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
HI - EXTERNAL CAUSE OF INJURY
- HI✱ABN:Y773✱ABN:Y92230~
- HI✱ABN:Y773:::::::N✱ABN:Y92230:::::::N~
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
HI - DIAGNOSIS RELATED GROUP (DRG) INFORMATION
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
HI - OTHER DIAGNOSIS INFORMATION
- HI✱ABF:I10:::::::Y✱ABF:R9431:::::::N✱ABF:H59312:::::::N~
- HI✱ABF:I10✱ABF:R9431✱ABF:H59312~
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
HI - PRINCIPAL PROCEDURE INFORMATION
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
HI - OTHER PROCEDURE INFORMATION
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
HI - OCCURRENCE SPAN INFORMATION
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
HI - OCCURRENCE INFORMATION
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
HI - VALUE INFORMATION
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
- If HI01-05 is populated, then HI01-10 must not be used.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- If HI02-05 is populated, then HI02-10 must not be used.
- Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- If HI03-05 is populated, then HI03-10 must not be used.
- Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- If HI04-05 is populated, then HI04-10 must not be used.
- Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- If HI05-05 is populated, then HI05-10 must not be used.
- Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- If HI06-05 is populated, then HI06-10 must not be used.
- Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- If HI07-05 is populated, then HI07-10 must not be used.
- Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- If HI08-05 is populated, then HI08-10 must not be used.
- Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- If HI09-05 is populated, then HI09-10 must not be used.
- Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- If HI10-05 is populated, then HI10-10 must not be used.
- Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- If HI11-05 is populated, then HI11-10 must not be used.
- Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- If HI12-05 is populated, then HI12-10 must not be used.
- Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
HI - CONDITION INFORMATION
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
HCP - CLAIM PRICING/REPRICING INFORMATION
- R0113
At least one of HCP01 or HCP13 is required. - P0910
If either HCP09 or HCP10 is present, then the other is required. - P1112
If either HCP11 or HCP12 is present, then the other is required.
- This information is specific to the destination payer reported in Loop ID-2010BB.
- This segment is not completed by providers. The information is completed by repricers only.
NM1*71 - ATTENDING PROVIDER NAME
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
PRV*AT - ATTENDING PROVIDER SPECIALTY INFORMATION
If either PRV02 or PRV03 is present, then the other is required.
REF - ATTENDING PROVIDER SECONDARY IDENTIFICATION
At least one of REF02 or REF03 is required.
NM1*72 - OPERATING PHYSICIAN NAME
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
- See National Uniform Billing Committee (NUBC) Official UB Data Specifications Manual for definition of institutional providers.
- Information in this Loop ID-2310 applies to the entire claim unless overridden on a service line by the presence of Loop ID-2420 with the same value in NM101.
REF - OPERATING PHYSICIAN SECONDARY IDENTIFICATION
At least one of REF02 or REF03 is required.
NM1*OOP - OTHER OPERATING PHYSICIAN NAME
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
- See National Uniform Billing Committee (NUBC) Official UB Data Specifications Manual for definition of institutional providers.
- Information in this Loop ID-2310 applies to the entire claim unless overridden on a service line by the presence of Loop ID-2420 with the same value in NM101.
- This Other Operating Physician segment can only be used when Operating Physician information (Loop ID-2310B) is also sent on this claim.
REF - OTHER OPERATING PHYSICIAN SECONDARY IDENTIFICATION
At least one of REF02 or REF03 is required.
NM1*82 - RENDERING PROVIDER NAME
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
OR
Required when the Rendering Provider is different than the Attending Provider reported in Loop ID-2310A of this claim AND the claim includes only a professional component.
If not required by this implementation guide, do not send.
- See National Uniform Billing Committee (NUBC) Official UB Data Specifications Manual for definition of institutional providers.
- Information in Loop ID-2310 applies to all professional services in the claim unless overridden on a service line by the presence of Loop ID-2420 with the same value in NM101.
REF - RENDERING PROVIDER SECONDARY IDENTIFICATION
At least one of REF02 or REF03 is required.
NM1*77 - SERVICE LOCATION NAME
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
AND
the Service Location is not a subpart of the Billing Provider with its own NPI that is different than the NPI reported in Loop ID-2010AA NM109. If not required by this implementation guide, do not send.
N3 - SERVICE LOCATION ADDRESS
N4 - SERVICE LOCATION CITY, STATE, ZIP CODE
- E0207
Only one of N402 or N407 may be present. - E0308
Only one of N403 or N408 may be present. - C0605
If N406 is present, then N405 is required. - C0704
If N407 is present, then N404 is required.
- CODE SOURCE 51: ZIP Code
- CODE SOURCE 932: Universal Postal Codes
REF - SERVICE LOCATION SECONDARY IDENTIFICATION
At least one of REF02 or REF03 is required.
AND
the Billing Provider Loop ID-2010AA NM109 is not used,
AND
an identifier is necessary for the receiver to identify the provider.
If not required by this implementation guide, do not send.
NM1*DN - REFERRING PROVIDER NAME
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
- See National Uniform Billing Committee (NUBC) Official UB Data Specifications Manual for definition of institutional providers.
- Information in this Loop ID-2310 applies to the entire claim unless overridden on a service line by the presence of Loop ID-2420 with the same value in NM101.
REF*A6 - REFERRING PROVIDER SECONDARY IDENTIFICATION
At least one of REF02 or REF03 is required.
SBR - OTHER SUBSCRIBER INFORMATION
- All information contained in Loop ID-2320 applies only to the payer identified in Loop ID-2330B of this iteration of Loop ID-2320. If information for an additional payer is necessary, repeat Loop ID-2320 with its respective 2330 Loops.
- See Section 1.4.2 for more information on Coordination of Benefits.
- Within a given claim, the various values for the Payer Responsibility Sequence Number Code (other than value "U") may occur no more than once.
- When sending Line Adjudication Information for this payer, the identifier sent in SVD01 (Other Payer Responsibility Sequence Code) of Loop ID-2430 (Line Adjudication Information) must match this value when used.
- This code value identifies, in the opinion of the submitter, the relative adjudication order of the non-destination payer in this iteration of Loop ID-2320 among all of the payers identified in this claim.
OR
Use when the original claim did not provide the responsibility sequence for this payer.
- This is not the number uniquely identifying the subscriber. The unique subscriber number is submitted in Loop 2330A-NM109 for this iteration of Loop ID-2320.
- Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
RAS - CLAIM ADJUSTMENT INFORMATION
- This monetary amount is the adjustment amount. A negative amount increases the payment, and a positive amount decreases the payment. This amount must not be zero (0).
- Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
- P0203
If either C05802 or C05803 is present, then the other is required. - C0403
If C05804 is present, then C05803 is required. - C0504
If C05805 is present, then C05804 is required. - C0605
If C05806 is present, then C05805 is required. - C0706
If C05807 is present, then C05806 is required.
- More than one iteration of this composite may only be provided when the entire claim submitted charge is being adjusted by this RAS segment and there are multiple adjustment reasons that are each applicable for the adjustment of that full amount in RAS01.
- This composite identifies the reason for the adjustment of the dollar amount identified in RAS01.
AMT*D - COORDINATION OF BENEFITS (COB) PAYER PAID AMOUNT
OR
Required when Loop ID-2010AC is present.
If not required by this implementation guide, do not send.
- It is acceptable to show "0" as the amount paid.
- Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
AMT*B6 - CLAIM ALLOWED AMOUNT
OR
Required when submitting a Coordination of Benefits (COB) claim, and the Other Payer identified in Loop ID-2330B of this iteration of Loop ID- 2320 has adjudicated this claim and the payer issued a paper, virtual, or other alternate format of remittance advice with the allowed amount reported and the submitter does not have the ability to report line item information.
OR
Required when submitting a Coordination of Benefits (COB) claim, and the Other Payer identified in Loop ID-2330B of this iteration of Loop ID- 2320 is the same as the submitter reported in Loop ID-1000A. If not required by this implementation guide, do not send.
- This is Loop ID-2100 Claim Allowed Amount (AMT02) when reported on an 835.
- This is the total claim allowed amount when remittance information is reported using other formats.
- In situations other than payer to payer COB, this amount is not sent if it is not explicitly available on an 835 or other remittance. If the allowed amount is not available, do not calculate the amount.
- When the Claim Allowed Amount is zero dollars, report zero (0).
AMT*EAF - REMAINING PATIENT LIABILITY AMOUNT
AND
In the provider's opinion, the amount billable to the patient, is different than the sum of the amounts (RAS01) associated with Patient Responsibility (PR) Claim Adjustment Group Code (RAS02) in this 2320 loop. If not required by this implementation guide, may be provided at the sender's discretion, but cannot be required by the receiver.
- In the judgment of the provider, this is the remaining amount to be paid after adjudication by the Other Payer identified in Loop ID-2330B of this iteration of Loop ID-2320. The amount reported here may, or may not, equal the sum of the amounts reported as Patient Responsibility (PR) in the RAS segments.
- This segment is not used in Payer-to-Payer Coordination of Benefits (COB).
- This segment is not used if the line level (Loop ID-2430) Remaining Patient Liability AMT segment is used for this Other Payer.
AMT*A8 - COORDINATION OF BENEFITS (COB) TOTAL NON-COVERED AMOUNT
OI - OTHER INSURANCE COVERAGE INFORMATION
MIA - INPATIENT ADJUDICATION INFORMATION
MOA - OUTPATIENT ADJUDICATION INFORMATION
LQ - HEALTH CARE REMARK CODES
If LQ01 is present, then LQ02 is required.
NM1*IL - OTHER SUBSCRIBER NAME
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
- If a patient can be uniquely identified by the Other Payer reported in Loop ID-2330B by a unique Member Identification Number, then the patient is reported in the subscriber loop.
- See Section 1.4.2 for more information on Coordination of Benefits.
N3 - OTHER SUBSCRIBER ADDRESS
N4 - OTHER SUBSCRIBER CITY, STATE, ZIP CODE
- E0207
Only one of N402 or N407 may be present. - E0308
Only one of N403 or N408 may be present. - C0605
If N406 is present, then N405 is required. - C0704
If N407 is present, then N404 is required.
- CODE SOURCE 51: ZIP Code
- CODE SOURCE 932: Universal Postal Codes
REF*SY - OTHER SUBSCRIBER SOCIAL SECURITY NUMBER
At least one of REF02 or REF03 is required.
The Social Security Number must be a string of exactly nine numbers with no separators.
For example, sending "111002222" would be valid, while sending "111-00-2222" would be invalid.
NM1*PR - OTHER PAYER NAME
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
N3 - OTHER PAYER ADDRESS
N4 - OTHER PAYER CITY, STATE, ZIP CODE
- E0207
Only one of N402 or N407 may be present. - E0308
Only one of N403 or N408 may be present. - C0605
If N406 is present, then N405 is required. - C0704
If N407 is present, then N404 is required.
- CODE SOURCE 51: ZIP Code
- CODE SOURCE 932: Universal Postal Codes
DTP*573 - PAYMENT EFFECTIVE DATE
REF*2U - OTHER PAYER SECONDARY IDENTIFIER
At least one of REF02 or REF03 is required.
OR
Required when an additional identification number to that provided in the NM109 of this loop is necessary to identify the entity.
If not required by this implementation guide, do not send.
REF*G1 - OTHER PAYER PRIOR AUTHORIZATION NUMBER
At least one of REF02 or REF03 is required.
- This segment must not be used to report the Predetermination of Benefits Identification Number.
- When prior authorization is submitted at this level (Loop ID-2330B) it applies to all the service lines that do not have an overriding REF - Prior Authorization (Loop ID-2400).
REF*9F - OTHER PAYER REFERRAL NUMBER
At least one of REF02 or REF03 is required.
If not required by this implementation guide, do not send.
REF*G3 - OTHER PAYER PREDETERMINATION IDENTIFICATION
At least one of REF02 or REF03 is required.
If not required by this implementation guide, do not send.
REF*F8 - OTHER PAYER CLAIM CONTROL NUMBER
At least one of REF02 or REF03 is required.
OR
Required when the Other Payer's Claim Control Number is available. If not required by this implementation guide, do not send.
REF*1K - OTHER PAYER PREVIOUS CLAIM CONTROL NUMBER
At least one of REF02 or REF03 is required.
AND
Loop ID-2330 REF F8 is used.
If not required by this implementation guide, do not send.
NM1*71 - OTHER PAYER ATTENDING PROVIDER
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
REF - OTHER PAYER ATTENDING PROVIDER SECONDARY IDENTIFICATION
At least one of REF02 or REF03 is required.
NM1*72 - OTHER PAYER OPERATING PHYSICIAN
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
REF - OTHER PAYER OPERATING PHYSICIAN SECONDARY IDENTIFICATION
At least one of REF02 or REF03 is required.
NM1*OOP - OTHER PAYER OTHER OPERATING PHYSICIAN
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
REF - OTHER PAYER OTHER OPERATING PHYSICIAN SECONDARY IDENTIFICATION
At least one of REF02 or REF03 is required.
NM1*77 - OTHER PAYER SERVICE LOCATION
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
REF - OTHER PAYER SERVICE LOCATION SECONDARY IDENTIFICATION
At least one of REF02 or REF03 is required.
NM1*82 - OTHER PAYER RENDERING PROVIDER
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
REF - OTHER PAYER RENDERING PROVIDER SECONDARY IDENTIFICATION
At least one of REF02 or REF03 is required.
NM1*DN - OTHER PAYER REFERRING PROVIDER
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
REF*A6 - OTHER PAYER REFERRING PROVIDER SECONDARY IDENTIFICATION
At least one of REF02 or REF03 is required.
NM1*85 - OTHER PAYER BILLING PROVIDER
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
REF - OTHER PAYER BILLING PROVIDER SECONDARY IDENTIFICATION
At least one of REF02 or REF03 is required.
LX - SERVICE LINE NUMBER
- The LX functions as a line counter.
- The Service Line LX segment must begin with one and is incremented by one for each additional service line of a claim.
- LX01 is used to indicate bundling in SVD06 in the Line Item Adjudication loop. See Section 1.4.2.3 for more information on bundling and unbundling.
SV2 - INSTITUTIONAL SERVICE LINE
- R0102
At least one of SV201 or SV202 is required. - P0405
If either SV204 or SV205 is present, then the other is required.
- C003-01 qualifies C003-02 and C003-08.
- If C003-08 is used, then C003-02 represents the beginning value in the range in which the code occurs.
- C003-03 modifies the value in C003-02 and C003-08.
- C003-04 modifies the value in C003-02 and C003-08.
- C003-05 modifies the value in C003-02 and C003-08.
- C003-06 modifies the value in C003-02 and C003-08.
- C003-07 is the description of the procedure identified in C003-02.
- C003-08 represents the ending value in the range in which the code occurs.
- C003-09 modifies the value in C003-02 and C003-08.
- C003-10 modifies the value in C003-02 and C003-08.
- C003-11 modifies the value in C003-02 and C003-08.
- C003-12 modifies the value in C003-02 and C003-08.
Some procedures (such as anesthesia and laboratory) have code descriptors that include "Not Otherwise Specified"; however, these are not considered "non-specific" procedure codes.
- This is the total charge amount for this service line. The amount is inclusive of the provider's base charge and any applicable tax amounts reported within this line's AMT segments.
- Zero "0" is an acceptable value for this element.
- Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
PWK - LINE SUPPLEMENTAL INFORMATION
- P0506
If either PWK05 or PWK06 is present, then the other is required. - P1011
If either PWK10 or PWK11 is present, then the other is required.
- PWK06 is a unique identifier assigned by the provider to be used to identify the supplemental documentation for this claim. When using the X12N 275 - Additional Information to Support a Health Care Claim or Encounter, the number in PWK06 is carried in the TRN Segment.
- For the purpose of this implementation, the maximum field length is 50.
DTP - SERVICE/ASSESSMENT DATE
OR
Required when a drug is being submitted and the payer's adjudication or predetermination is known to be impacted by the drug duration or the date the prescription was written.
If not required by this implementation guide, do not send.
- In cases where a drug is being submitted on a service line, a date range may be used to indicate drug duration for which the drug supply will be used by the patient. The difference in dates, including both the beginning and end dates, are the days supply of the drug.
Example: 20110101 - 20110107 (1/1/2011 to 1/7/2011) is used for a 7 day supply where the first day of the drug used by the patient is 1/1/2011. In the event a drug is administered on less than a daily basis (for example, every other day) the date range would include the entire period during which the drug is supplied, including the last day of use.
Example: 20110101 - 20110108 (1/1/2011 to 1/8/2011) is used for an 8 day supply where the prescription is written for Q48 (every 48 hours), four doses of the drug are dispensed and the first dose is used on 1/1/2011. - Predetermination requests are indicated in CLM19.
REF*G3 - SERVICE PREDETERMINATION IDENTIFICATION
At least one of REF02 or REF03 is required.
- P0304
If either C04003 or C04004 is present, then the other is required. - P0506
If either C04005 or C04006 is present, then the other is required.
- The value reported in this field must match the corresponding Other Payer Responsibility Sequence Code reported in Loop ID-2320 SBR01.
- Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
REF*6R - LINE ITEM CONTROL NUMBER
At least one of REF02 or REF03 is required.
- If the provider does not use a unique line item control number or the originating claim did not have a line item control number (i.e., Payer to Payer COB, paper to electronic), then use the LX01 value.
- Submitters are STRONGLY encouraged to routinely send a unique line item control number on all service lines, particularly if the submitter automatically posts their remittance advice. Submitting a unique line item control number allows the capability to automatically post by service line.
- The line item control number needs to be unique within a Provider's Assigned Claim Identifier (CLM01). Payers are required to return this number in the remittance advice transaction (835) if the provider sends it to them in the 837 and adjudication is based upon line item detail regardless of whether bundling or unbundling has occurred.
- The maximum number of characters to be supported for this field is 30. A submitter may submit fewer characters depending upon their needs. Characters beyond 30 are not required to be stored nor returned by any 837-receiving system.
- Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
REF*EW - MAMMOGRAPHY CERTIFICATION NUMBER
At least one of REF02 or REF03 is required.
REF*9B - REPRICED LINE ITEM REFERENCE NUMBER
At least one of REF02 or REF03 is required.
REF*9D - ADJUSTED REPRICED LINE ITEM REFERENCE NUMBER
At least one of REF02 or REF03 is required.
REF*LX - INVESTIGATIONAL DEVICE EXEMPTION NUMBER
At least one of REF02 or REF03 is required.
AMT*GT - SERVICE TAX AMOUNT
AMT*N8 - FACILITY TAX AMOUNT
AMT*SCT - STATE CARE TAX
- Sales Tax is not reported in this Segment.
- The State Care Tax Amount must be included in the Line Item Charge Amount (SV203) of the related Service Line.
NTE*TPO - THIRD PARTY ORGANIZATION NOTES
HCP - LINE PRICING/REPRICING INFORMATION
- R0113
At least one of HCP01 or HCP13 is required. - P0910
If either HCP09 or HCP10 is present, then the other is required. - P1112
If either HCP11 or HCP12 is present, then the other is required.
- This information is specific to the destination payer reported in Loop ID-2010BB.
- This segment is not completed by providers. The information is completed by repricers only.
- This information is specific to the APG.
- Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
- This information is specific to the APG.
- Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
LIN - DRUG/SUPPLY IDENTIFICATION
- P0405
If either LIN04 or LIN05 is present, then the other is required. - P0607
If either LIN06 or LIN07 is present, then the other is required. - P0809
If either LIN08 or LIN09 is present, then the other is required. - P1011
If either LIN10 or LIN11 is present, then the other is required. - P1213
If either LIN12 or LIN13 is present, then the other is required. - P1415
If either LIN14 or LIN15 is present, then the other is required. - P1617
If either LIN16 or LIN17 is present, then the other is required. - P1819
If either LIN18 or LIN19 is present, then the other is required. - P2021
If either LIN20 or LIN21 is present, then the other is required. - P2223
If either LIN22 or LIN23 is present, then the other is required. - P2425
If either LIN24 or LIN25 is present, then the other is required. - P2627
If either LIN26 or LIN27 is present, then the other is required. - P2829
If either LIN28 or LIN29 is present, then the other is required. - P3031
If either LIN30 or LIN31 is present, then the other is required.
OR
Required when the provider or submitter chooses to report NDC numbers or the Device Identifier of the Unique Device Identifier to enhance the claim reporting or adjudication processes.
If not required by this implementation guide, do not send.
Legacy Identification Numbers Assigned to Devices (National Drug Code (NDC) and National Health-Related Item Code Numbers (NHRIC)) have been discontinued and replaced by Device Identifier of the Unique Device Identifier (see section 1.5 Terminology for definition of device).
See section 21 CFR Parts 16, 801, 803, et al. Unique Device Identification System; Final Rule section 801.57.
Prior to the mandated implementation date for the Unique Device Identifier, willing trading partners may agree to follow an early implementation approach.
Code Source: FDA Global Unique Device Identifier Database (GUDID) http://accessgudid.nlm.nih.gov/
Available from:
National Library of Medicine
8600 Rockville Pike
Bethesda, MD 20894
CTP - QUANTITY
- E0312
Only one of CTP03 or CTP12 may be present. - P0405
If either CTP04 or CTP05 is present, then the other is required. - C0607
If CTP06 is present, then CTP07 is required. - C0902
If CTP09 is present, then CTP02 is required. - C1002
If CTP10 is present, then CTP02 is required. - C1103
If CTP11 is present, then CTP03 is required. - C1202
If CTP12 is present, then CTP02 is required.
(See Figures Appendix for examples of use)
- If C001-02 is not used, its value is to be interpreted as 1.
- If C001-03 is not used, its value is to be interpreted as 1.
- If C001-05 is not used, its value is to be interpreted as 1.
- If C001-06 is not used, its value is to be interpreted as 1.
- If C001-08 is not used, its value is to be interpreted as 1.
- If C001-09 is not used, its value is to be interpreted as 1.
- If C001-11 is not used, its value is to be interpreted as 1.
- If C001-12 is not used, its value is to be interpreted as 1.
- If C001-14 is not used, its value is to be interpreted as 1.
- If C001-15 is not used, its value is to be interpreted as 1.
REF - PRESCRIPTION OR COMPOUND DRUG ASSOCIATION NUMBER
At least one of REF02 or REF03 is required.
OR
Required when the provided medication involves the compounding of two or more drugs being reported and there is no prescription number.
If not required by this implementation guide, do not send.
- In cases where a compound drug is being billed, the components of the compound will all have the same prescription number. Payers receiving the claim can relate all the components by matching the prescription number.
- For cases where the drug is provided without a prescription (for example, from a physician's office), the value provided in this segment is a "link sequence number". The link sequence number is a provider assigned number that is unique to this claim. Its purpose is to enable the receiver to piece together the components of the compound.
NM1*72 - OPERATING PHYSICIAN NAME
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
AND
The Operating Physician for this line is different than the Operating Physician reported in Loop ID-2310B (claim level).
If not required by this implementation guide, do not send.
REF - OPERATING PHYSICIAN SECONDARY IDENTIFICATION
At least one of REF02 or REF03 is required.
If REF04 is used, REF02 is a proprietary provider number assigned by the non-destination payer identified in the Other Payer Name loop, Loop ID-2330B, associated with this claim.
OR
Use when reporting a proprietary provider number assigned by the non-destination payer identified in REF04-02 of this segment. This is true regardless of whether that payer is a government, private, commercial or any other payer.
- P0304
If either C04003 or C04004 is present, then the other is required. - P0506
If either C04005 or C04006 is present, then the other is required.
- The value reported in this field must match the corresponding Other Payer Responsibility Sequence Code reported in Loop ID-2320 SBR01.
- Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
NM1*OOP - OTHER OPERATING PHYSICIAN NAME
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
AND
The Other Operating Physician for this line is different than the Other Operating Physician reported in Loop ID-2310C (claim level).
If not required by this implementation guide, do not send.
REF - OTHER OPERATING PHYSICIAN SECONDARY IDENTIFICATION
At least one of REF02 or REF03 is required.
If REF04 is used, REF02 is a proprietary provider number assigned by the non-destination payer identified in the Other Payer Name loop, Loop ID-2330B, associated with this claim.
OR
Use when reporting a proprietary provider number assigned by the non-destination payer identified in REF04-02 of this segment. This is true regardless of whether that payer is a government, private, commercial or any other payer.
- P0304
If either C04003 or C04004 is present, then the other is required. - P0506
If either C04005 or C04006 is present, then the other is required.
- The value reported in this field must match the corresponding Other Payer Responsibility Sequence Code reported in Loop ID-2320 SBR01.
- Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
NM1*82 - RENDERING PROVIDER NAME
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
AND
State or federal regulatory requirements call for a "combined claim", that is, a claim that includes both facility and professional components (for example, a Medicaid clinic bill or Critical Access Hospital Claim).
AND
The Rendering Provider for this line is different than the Rendering Provider reported in Loop ID 2310D (claim level).
If not required by this implementation guide, do not send.
REF - RENDERING PROVIDER SECONDARY IDENTIFICATION
At least one of REF02 or REF03 is required.
If REF04 is used, REF02 is a proprietary provider number assigned by the non-destination payer identified in the Other Payer Name loop, Loop ID-2330B, associated with this claim.
OR
Use when reporting a proprietary provider number assigned by the non-destination payer identified in REF04-02 of this segment. This is true regardless of whether that payer is a government, private, commercial or any other payer.
- P0304
If either C04003 or C04004 is present, then the other is required. - P0506
If either C04005 or C04006 is present, then the other is required.
- The value reported in this field must match the corresponding Other Payer Responsibility Sequence Code reported in Loop ID-2320 SBR01.
- Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
NM1*DN - REFERRING PROVIDER NAME
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
AND
The Referring Provider for this line is different than the Referring Provider reported in Loop ID 2310F (claim level). If not required by this implementation guide, do not send.
REF*A6 - REFERRING PROVIDER SECONDARY IDENTIFICATION
At least one of REF02 or REF03 is required.
If REF04 is used, REF02 is a proprietary provider number assigned by the non-destination payer identified in the Other Payer Name loop, Loop ID-2330B, associated with this claim.
OR
Use when reporting a proprietary provider number assigned by the non-destination payer identified in REF04-02 of this segment. This is true regardless of whether that payer is a government, private, commercial or any other payer.
- P0304
If either C04003 or C04004 is present, then the other is required. - P0506
If either C04005 or C04006 is present, then the other is required.
- The value reported in this field must match the corresponding Other Payer Responsibility Sequence Code reported in Loop ID-2320 SBR01.
- Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
SVD - LINE ADJUDICATION INFORMATION
- Zero "0" is an acceptable value for this element.
- Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
- C003-01 qualifies C003-02 and C003-08.
- If C003-08 is used, then C003-02 represents the beginning value in the range in which the code occurs.
- C003-03 modifies the value in C003-02 and C003-08.
- C003-04 modifies the value in C003-02 and C003-08.
- C003-05 modifies the value in C003-02 and C003-08.
- C003-06 modifies the value in C003-02 and C003-08.
- C003-07 is the description of the procedure identified in C003-02.
- C003-08 represents the ending value in the range in which the code occurs.
- C003-09 modifies the value in C003-02 and C003-08.
- C003-10 modifies the value in C003-02 and C003-08.
- C003-11 modifies the value in C003-02 and C003-08.
- C003-12 modifies the value in C003-02 and C003-08.
- This is the number of paid units from the remittance advice. When paid units are not present on the paper remittance advice or known by the provider, the value must be one.
- The maximum length for this field is 8 digits excluding the decimal. When a decimal is used, the maximum number of digits allowed to the right of the decimal is three. A negative value is not allowed.
RAS - SERVICE ADJUSTMENT INFORMATION
- This monetary amount is the adjustment amount. A negative amount increases the payment, and a positive amount decreases the payment. This amount must not be zero (0).
- Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
- P0203
If either C05802 or C05803 is present, then the other is required. - C0403
If C05804 is present, then C05803 is required. - C0504
If C05805 is present, then C05804 is required. - C0605
If C05806 is present, then C05805 is required. - C0706
If C05807 is present, then C05806 is required.
- This composite identifies the reason for the adjustment of the dollar amount identified in RAS01.
- More than one iteration of this composite may only be provided when the entire service submitted charge is being adjusted by this RAS segment and there are multiple adjustment reasons that are each applicable for the adjustment of that full amount in RAS01.
DTP*573 - PAYMENT EFFECTIVE DATE
AMT*B6 - SERVICE ALLOWED AMOUNT
The Other Payer referenced in SVD01 (of this iteration of Loop ID-2430) has adjudicated this claim and provided the 835 with line level allowed amount information to the submitter.
OR
The Other Payer identified in SVD01 (of this iteration of Loop ID-2430) has adjudicated this claim and the submitter received a paper, virtual, or other alternate format of remittance advice with the allowed amount reported.
OR
The Other Payer referenced in SVD01 (of this iteration of Loop ID-2430) is the same as the submitter reported in Loop ID-1000A.
If not required by this implementation guide, do not send.
- This is the 835 Loop ID-2110 Claim Allowed Amount (AMT02) when the remittance information is reported on an 835.
- This is the service line allowed amount when remittance information is reported using other formats.
- This amount is not sent if it is not explicitly available on an 835 or other remittance. If the allowed amount is not available, do not calculate the amount.
- When the service line allowed amount is zero dollars, report zero (0).
AMT*EAF - REMAINING PATIENT LIABILITY AMOUNT
AND
The claim level (Loop ID-2320) Remaining Patient Liability AMT segment for this other payer is not used,
AND
The provider has the ability to report line item information,
AND
In the provider's opinion, the amount billable to the patient, is different than the sum of the amounts (RAS01) associated with Patient Responsibility (PR) Claim Adjustment Group Code (RAS02) in this 2430 loop. If not required by this implementation guide, may be provided at the sender's discretion, but cannot be required by the receiver.
- This segment is not used in Payer-to-Payer Coordination of Benefits (COB).
- In the judgment of the provider, this is the remaining amount to be paid after adjudication by the Other Payer referenced in SVD01 of this iteration of Loop ID-2430.
- This segment is not used if the claim level (Loop ID-2320) Remaining Patient Liability AMT segment is used for this Other Payer.
LQ - HEALTH CARE REMARK CODES
If LQ01 is present, then LQ02 is required.
SE - TRANSACTION SET TRAILER
GE - FUNCTIONAL GROUP TRAILER
IEA - INTERCHANGE CONTROL TRAILER
| | 837 Health Care Claim: Institutional (008020X324)SEPTEMBER 2021 Copyright © 2008-21, X12 Incorporated, Format © 2008-21 Washington Publishing Company. Exclusively published by the Washington Publishing Company. No part of this publication may be distributed, posted, reproduced, stored in a retrieval system, or transmitted in any form or by any means without the prior written permission of the copyright owner. All rights reserved. Abstract The Health Care Claim: Institutional Implementation Guide describes the use of the X12 Health Care Claim (837) transaction set to submit and transfer institutional claims and encounters to primary, secondary, and subsequent payers.
|
PrefaceX12 standards are developed to identify the broadest data requirements for a transaction set. Type 3 Technical Reports (TR3), also known as implementation guides, define the explicit data requirements for a specific business purpose. Trading partners who implement according to the instructions in this TR3 can exchange data consistently with multiple trading partners. As X12 does not define transport requirements, trading partners define their specific transport requirements separately. |
1.1 Implementation Purpose and ScopeFor the health care industry to achieve the potential administrative cost savings with Electronic Data Interchange (EDI), standards have been developed to facilitate consistent implementation by all organizations. To facilitate a smooth transition into the EDI environment, uniform implementation is critical. This is the technical report document for the X12N 837 Health Care Claims (837) transaction for institutional claims, encounters, and/or requests for predetermination of benefits (estimates). Unless noted otherwise, the term "claim" in this guide applies to all these uses. See X12 Wordbook for definitions. This document provides a definitive statement of what trading partners must be able to support in this version of the 837. |
1.2 Version InformationThis implementation guide is based on the October 2020 X12 standards, referred to as Version 8, Release 2 (008020). The unique Version/Release/Industry Identifier Code for transaction sets that are defined by this implementation guide is 008020X324. The two-character Functional Identifier Code for the transaction set included in this implementation guide:
The Version/Release/Industry Identifier Code and the applicable Functional Identifier Code must be transmitted in the Functional Group Header (GS segment) that begins a functional group of these transaction sets. For more information, see the descriptions of GS01 and GS08 in Appendix C EDI Control Directory. |
1.3.1 Batch and Real-Time UsageThere are multiple methods available for sending and receiving business transactions electronically. Two common modes for EDI transactions are batch and real-time. Batch - In a batch mode the sender does not remain connected while the receiver processes the transactions. Processing is usually completed according to a set schedule. If there is an associated business response transaction (such as a 271 Response to a 270 Request for Eligibility), the receiver creates the response transaction and stores it for future delivery or transmits the response transaction back to the sender of the original transaction. The sender of the original transmission reconnects at a later time and picks up the response transaction. Note: The sender of the original transmission may not always be the entity that picks up the response transaction at a later time (e.g. Provider submitting through a clearinghouse.) Real-Time - In real-time mode the sender remains connected while the receiver processes the transactions and returns a response transaction to the sender. This implementation guide does not set specific response time parameters for implementers. This implementation guide was based on requirements for batch and real-time modes. Willing trading partners may use batch or real-time mode. |
1.3.2 Other Usage LimitationsWhen processing in batch mode, receiving trading partners may have system limitations which control the size of the transmission they can receive. Some submitters may have the capability and the desire to transmit large 837 transactions with thousands of claims contained in them. The developers of this implementation guide recommend that trading partners limit the size of the transaction (ST-SE envelope) to a maximum of 5000 CLM segments. Willing trading partners can agree to higher limits. There is no recommended limit to the number of ST-SE transactions within a GS-GE or ISA-IEA. When a claim is processed in real-time, only one CLM per ISA/IEA is allowed and must be responded to in a single communication session. |
1.4 Business UsageThis transaction set can be used to submit health care claim billing information, encounter information, or requests for predetermination from providers of health care services to payers, either directly or via intermediary billing services and claims clearinghouses. It can also be used to transmit health care claims and billing payment information between payers with different payment responsibilities where coordination of benefits (COB) is required or between payers and regulatory agencies to monitor the rendering, billing, and/or payment of health care services within a specific health care/insurance industry segment. For purposes of this standard, providers of health care products or services may include entities such as physicians, dentists, hospitals, pharmacies, other medical facilities or suppliers, and entities providing medical information to meet regulatory requirements. The payer is a third party entity that pays claims or administers the insurance product or benefit or both. For example, a payer may be an insurance company, health maintenance organization (HMO), preferred provider organization (PPO), government agency (Medicare, Medicaid, TRICARE, etc.) or an entity such as a third party administrator (TPA), repricer, or third party organization (TPO) that may be contracted by one of those groups. A regulatory agency is an entity responsible, by law or rule, for administering and monitoring a statutory benefits program or a specific segment of the health care/insurance industry. The transaction defined by this implementation guide is generally intended to originate with the health care provider or health care provider's designated agent. In some instances, a health care payer may originate an 837 to report a health care encounter to another payer or sponsoring organization. In other cases, where a Factoring Agent is involved, the Factoring Agent, who has acquired the ownership of the receivable, but has not provided the medical service or product related to a claim, may originate an 837 to another payer for reimbursement. The 837 Transaction provides all necessary information to allow the destination payer to at least begin to adjudicate the claim. The 837 coordinates with a variety of other transactions including, but not limited to, the following: Health Care Status Notification (277), Health Care Claim Payment/Advice (835) and the Implementation Acknowledgement (999). See Section 1.6 - Transaction Acknowledgments, and Section 1.7 - Related Transactions, for a summary description of these interactions. NOTE: |
1.4.1 Health Care Transaction FlowEach X12 implementation guide explains how to use X12 transaction sets to meet a single defined business purpose. The diagrams found at https://www.x12.org/flow depict the business functions supported by the X12 health care implementation guides. |
1.4.2 Coordination of Benefits Note: COB functionality supported in this implementation guide minimizes manual intervention and/or the necessity for paper supporting documentation. Electronic COB is predicated upon using two transactions – the 837 and the 835 Health Care Claim Payment/Advice. See Section 1.4.2.1 - Coordination of Benefits Data Models - Detail for information about using these transactions to achieve a totally electronic interchange of COB information. Refer to Chapter 3, for information on examples. Section 1.4.2.2 - Coordination of Benefits Claims from Paper or Proprietary Remittance Advices provides guidance on creating electronic COB claims when the payer's remittance was a paper or proprietary remittance advice. |
1.4.2.1 Coordination of Benefits Data Models - DetailThe 837 Transaction handles two different models of benefit coordination. Both models are discussed in this section. Section 3, Examples, contains detailed examples of the Provider-to-Payer-to-Provider model. Each COB related data element contains notes within this implementation guide specifying when it is used. The HIPAA final rules contain additional information on COB. Since prior implementation guides used the CAS segment for adjustments at both the claim and service levels, there will be a need to convert to the RAS segment when implementing this guide's instructions. The CAS segment supported up to six separate adjustments (amount, CARC and quantity) consistent with a single Claim Adjustment Group Code. The RAS segment supports only one adjustment per segment. As a result, converting from the CAS to the RAS will involve the creation of more RAS segments than the number of CAS segments in prior versions. There is a one to one relationship between a CAS amount, CARC and quantity trio and a single RAS segment. In prior versions that used the CAS segment, Remark Codes that were related to an adjustment were reported in the MIA or MOA segment at the claim level or the LQ segment at the service level. With the RAS segment, the Remark Codes must now be associated directly with the related CARC, when a relationship to a specific CARC exists. This change requires a modification from a business perspective and is not a simple mapping change. This change clarifies the fact that Remark Codes serve multiple functions within the 835 transaction. Sometimes they are related to a CARC and are a critical part of the message of a specific RAS segment/CARC. Other times they have no correlation to the RAS segment and provide additional information that is part of the general claim or service adjudication message. Whenever a Remark Code is associated with a CARC or a CARC requires the presence of a Remark Code, the Remark Code must be reported in the RAS03 composite data structure with the CARC. Remark Codes that are not associated with a specific CARC must still be reported in the LQ segment. Model 1 – Provider-to-Payer-to-Provider Step 1. In model 1, the provider originates the transaction and sends the claim information to Payer A, the primary payer. See Figure 1.1 - Provider-to-Payer-to-Provider COB Model. The Subscriber loop (Loop ID-2000B) contains information about the person who holds the policy with Payer A. Loop ID-2320 contains information about Payer B and the subscriber who holds the policy with Payer B. In this model, the primary payer adjudicates the claim and sends an electronic remittance advice (RA) transaction (835) back to the provider. The 835 contains any claim adjustment reason codes that apply to that specific claim. The claim adjustment reason codes detail what was adjusted and why. Figure 1.1 - Provider-to-Payer-to-Provider COB Model Step 2. Upon receipt of the 835, the provider sends a second health care claim transaction (837) to Payer B, the secondary payer. The Subscriber loop (Loop ID-2000B) now contains information about the subscriber who holds the policy with Payer B. The Other Subscriber Information loop (Loop ID-2320) now contains information about the subscriber for Payer A. Any total amounts paid at the claim level go in the AMT segment with qualifier D (Payer Amount Paid) in Loop ID-2320. All claim level adjustment codes are retrieved from the 835 from Payer A and put in the RAS (Claim Adjustment Information) segment in Loop ID-2320. Claim Level Allowed Amounts reported in the 835 are included in an AMT with qualifier B6 (Allowed - Actual) in Loop ID-2320. Line Level adjustment reason codes are retrieved similarly from the 835 and go in the RAS (Service Adjustment Information) segment in the 2430 loop. Line Level Allowed Amounts reported in the 835 are included in an AMT with qualifier B6 in Loop ID-2430. Payer B adjudicates the claim and sends the provider an electronic remittance advice. Step 3. If there are additional payers (not shown in Figure 1.1 - Provider-to-Payer-to-Provider COB Model), step 2 is repeated with the Subscriber loop (Loop ID-2000B) having information about the subscriber who holds the policy with Payer C, the tertiary payer. COB information specific to Payer A continues to be included as written in step 2 with an occurrence of Loop ID-2320 and specifying the payer as primary. If necessary, Loop ID-2430 is included for any line level adjudications. COB information specific to Payer B is included by repeating the Loop ID-2320 again and specifying the payer as secondary. If necessary, Loop ID-2430 is included for Payer B line level adjudications. Model 2 – Provider-to-Payer-to-Payer Step 1. In model 2, the provider originates the transaction and sends claim information to Payer A, the primary payer. See Figure 1.2 - Provider-to-Payer-to-Payer COB Model. The Subscriber loop (Loop ID-2000B) contains information about the person who holds the policy with Payer A. Subscriber/payer information about secondary coverage is included in Loop ID-2320 or is on file at Payer A as a result of an eligibility file sent by Payer B (as in Medicare crossover arrangements). In this model, the primary payer adjudicates the claim and sends an 835 back to the provider. Figure 1.2 - Provider-to-Payer-to-Payer COB Model Step 2. All COB information from Payer A is placed in the appropriate Loop ID-2320 and/or Loop ID-2430. In reformatting the claim, Payer A takes the information about their subscriber and places it in Loop ID-2320. Payer A also takes the information about Payer B, the secondary payer/subscriber, and places it in the appropriate fields in the Subscriber Loop ID-2000B. Then Payer A sends the claim to Payer B. Step 3. Payer B receives the claim from Payer A and adjudicates the claim. Payer B sends an 835 to the provider. If there is a tertiary payer, Payer B performs step 2 in either Model 1 or Model 2. |
1.4.2.1.1Â Coordination of Benefits - Claim LevelThe destination payer's information is located in Loop ID-2010BB. In addition, any destination payer-specific claim information (for example, referral number) is located in the 2300 loop. All provider identifiers in the 2310 REF Segments are specific to the destination payer. Loop ID-2320 occurs once for each payer responsible for the claim, except for the payer receiving the 837 transaction set (destination payer). Provider identifiers in the 2330 REF Segments are specific to the corresponding non-destination payer. Loop ID-2320 contains the following:
Inside Loop ID-2320, Loop ID-2330 contains the information for the payer and the subscriber. As the claim moves from payer to payer, the destination payer's information in Loop ID-2000B and Loop ID-2010BB must be exchanged with the next payer's information from Loop ID-2320/2330. |
1.4.2.1.2Â Coordination of Benefits - Service Line LevelLoop ID-2430 is a situational loop that can occur up to 15 times for each service line. As each payer adjudicates the service lines, occurrences may be added to this loop to explain how the payer adjudicated the service line. Loop ID-2430 contains the following:
To enable accurate matching of billed service lines with paid service lines, the payer must return the original billed procedure code(s) and/or modifiers in the SVC06 composite data element of the 835 if they are different from those used to pay the line. |
1.4.2.2Â Coordination of Benefits Claims from Paper or Proprietary Remittance AdvicesClaim submitters may at times need or choose to create electronic secondary/tertiary coordination of benefit (COB) claims to subsequent payers due to regulatory or business relationships when the prior payer's remittance was a paper or proprietary remittance advice. This situation may occur when the prior payer(s) is not a regular trading partner of the claim submitter or the prior payer(s) is a HIPAA non-covered entity and produces a proprietary electronic remittance (e.g., Workers' Compensation). Provider information systems that have the functionality to generate electronic claim transactions to payers have the majority of the information necessary to create a COB claim. Ideally, payers have adopted usage of the standard codes sets for paper remittance advices or have provided crosswalks for their paper or nonstandard electronic remittances to accommodate creation of COB claims. However, this will not always occur. When standard codes are not available from a prior payer(s) paper/proprietary remittance advice(s), the COB claim submitter must translate the proprietary adjustment/denial edit messages to standard codes. Generally, a subsequent COB payer(s) determines payment on a combination of "Group Code" and "Claim Adjustment Reason Code" provided in the RAS segment(s) at either the claim or service line. Group Codes are included in an external code list (see Appendix A for code list reference) and include Patient Responsibility, Contractual Obligation, Payer Initiated, and Other Adjustments. The Claim Adjustment Reason Code (CARC) is equally important in subsequent payers' determination of payment responsibility. In most instances, paper or proprietary monetary adjustments may easily be cross-walked to the standard CARCs using the CARC list available at https://x12.org/codes/claim-adjustment-reason-codes. Payment adjustments by the prior payer(s) that are not readily cross-walked to standard CARCs are reported using default CARC 192 (*Nonstandard adjustment code from paper remittance advice). Submitters must not use default code 192 when a more specific code is available. Some CARCs, such as CARC 96 (*Non-covered charges.), require a Remittance Advice Remark Code (RARC) to further explain the reason for the adjustment. It is important to include the most descriptive CARC available, along with appropriate associated RARCs. Note: Some Claim Adjustment Reason Codes require at least one Remittance Advice Remark Code (RARC) to further explain the reason for adjustment. The claim submitter is responsible for determining the most appropriate Remittance Advice Remark Code to use. *NOTE - All code descriptions are as of the publication of this book. Please refer to https://x12.org/codes for the most current description. |
1.4.2.3 Coordination of Benefits - SubrogationAt the time of this publication, subrogation is not a HIPAA mandated business usage of the X12 837 Health Care Claim; however, willing trading partners may use this Implementation Guide for this purpose. This Implementation Guide provides the ability for willing trading partners to allow direct billing by one payer to another payer for the purpose of claim subrogation. These pay-to-plan claims are identified by:
The payer seeking payment is also identified in Loop ID-2330B (Other Payer Name). Loop ID-2320 (Other Subscriber Information) and Loop ID-2430 (Line Adjudication Information) includes all required segments to indicate adjudication results of the original claim that was submitted to that payer by the Billing Provider. For Subrogation claims, the submitting payer's own Payer Claim Control Number is reported in Loop ID-2300 (Claim Information) data element CLM01 (Claim Submitter's Identifier), rather than the Provider's Assigned Claim Identifier. The submitting payer's Payer Claim Control Number is reported here so that the identifier can be carried through for payment re-association purposes. Receiving payers are to direct information requests about subrogation claims to the submitting payer (as identified in Loop ID-2330B (Other Payer Name)) rather than to the original billing provider. |
1.4.2.4 Claim / Service Adjustment Information SegmentThe Claim Adjustment Information and Service Adjustment Information Segments (Loop ID 2320 and 2430 RAS segment, which replaces the CAS segment from previous implementation guides) provide the amounts, reasons, and quantities of any adjustments that the prior payer(s) made to the original submitted charge and to the units related to the claim or service(s). The sum of the adjustments at the claim and service level is the total adjustment for the entire claim. Adjustments reported at the Service level (Loop ID 2430) are not repeated at the claim level (Loop ID 2320) and vice versa. Each RAS segment identifies a single adjustment to the original submitted charge for the claim/service by: Amount – this is the amount of the adjustment. A positive value reduces the payment; a negative value increases the payment. This is required, and must not be zero. Adjustment Group Code – identifies and categorizes the general class of the adjustment and any related responsibility from a set of codes in a standard external code list. This is required. CARC/RARC Composites Remark Codes within a specific iteration of the composite are directly related to the CARC in that iteration of the composite. See the RAS segment detail in the 2320 and 2430 loops for complete structural information. Claim Adjustment Reason Code (CARC) – identifies the reason for the adjustment using a code from a standard external code list. At least one is required. Additional CARCs can be provided for a single amount, when the amount represents a total adjustment explained by more than 1 reason. Multiple CARCs must all relate to the adjustment amount reported in RAS01 and Group Code reported in RAS02. All CARCs related to the adjustment amount reported in RAS01 must be reported in the RAS segment to eliminate the need for repetitive claim submission and adjustment notification. Each unique adjustment amount requires its own RAS segment. If an adjustment amount has only 1 reason, do not combine with any other adjustments in a RAS. For example, patient responsibility amounts for deductible and co-pay would not be combined in one RAS segment, since each has their own individual adjustment amount. Two separate RAS segments are required. Remark Code – identifies additional information related specifically to a CARC that further clarifies the adjustment reason. Up to five Remark Codes can be associated with each CARC. The Remark Codes can only be from one of the standard external code lists listed in the RAS segment detail in the 2320 and 2430 loops, including the Remittance Advice Remark Code (RARC) external code list, the Insurance Industry Specific Remark Code (IISRC) external code list or the standard NCPDP Reject Codes external code list. Remark Codes are situational and are required when they are necessary for the provider to fully understand the adjustment message for the claim adjustment reason. Note – when a CARC description requires the presence of a Remark Code to complete the message, that Remark Code must be provided in the related RAS03 composite directly associated with the CARC. Certain informational Remark Codes can be used without any association to a specific CARC, at either the claim or service level (some of these remark codes begin with the word "ALERT"). Remark codes used without any association to a specific CARC are included in the claim level (2320 loop) or service level (2430 loop) Health Care Remark Codes (LQ) segment. Adjustment Quantity – This is the non-covered days (2320 loop) or non-covered units of service (2430 loop) when the adjustment amount is related to a reduction in the related units. The Adjustment Quantity is situational and is required when the adjustment is related to non-covered days or units of service. At the Service line level (2430 loop) this element represents adjusted service unit count. The Service level (2430 loop) includes a balancing requirement related to the adjusted service unit count – the submitted Service Units Count minus the Adjustment Quantities (2430 RAS04 elements) must equal the Paid Units of Service (SVD05). |
1.4.3 Property & CasualtyProperty & Casualty (P&C) is the broad term given to lines of business including, but not limited to, liability, auto medical payment coverage, auto no-fault, homeowners, workers' compensation, boat, recreational vehicle (RV), and all-terrain vehicle (ATV). Most P&C policies carry a medical expense reimbursement benefit as part of the coverage. For most P&C claim events, member ID's/policy numbers do not necessarily identify the covered persons, since even strangers to the policy (e.g. passengers in the vehicle, customers, and visitors) can receive medical expense reimbursement coverage under a P&C policy. The P&C insurance card identifies the policyholder(s) and the covered vehicle(s)/property. The policy number is rarely used to identify the covered events associated to the submission of a claim (bill). Instead, the P&C claim number is used to tie the bill to a covered event. The claim number is the key to associating the patient to a unique event. It is possible to have more than one patient associated to an event and more than one event per patient, each with unique coverage requirements with its associated limits, as well as any adjudication rules that would apply. P&C bills or predetermination requests must include both the bill information as well as the information related to the event that caused the injury or illness. Information concerning the event is necessary to associate a bill or predetermination request with the P&C claim event. P&C insurance is governed by state insurance regulations, statutes, Departments of Labor, Workers' Compensation Boards, or other jurisdictionally defined entities, which often mandate compliance with Jurisdiction-specific procedures. The date of accident/occurrence/onset of symptoms (Date of Loss) is a critical piece of information and must always be transmitted in the HI Segment (Occurrence Information) within Loop ID-2300 (Claim Loop). The Date of Loss is used to determine the eligibility of coverage for the unique claim event. The unique identification number assigned by the payer for the specific event, referred to in P&C as a claim number, must be provided. The claim number is transmitted in the Property & Casualty Claim Number REF segment of Loop ID-2010BA if the patient is the subscriber or Loop ID-2010CA if the patient is not the subscriber. Failure to submit the required Accident Date and Property & Casualty Claim Number is inconsistent with the TR3 and will result in the claim being rejected or delayed in the adjudication process depending on the business practices of the payer. When sending an appeal or reconsideration Property & Casualty bill, it is important to indicate that the bill is a replacement bill in CLM05-03 with a value of 7, and to include the payer's claim control number of the original bill in the Payer Claim Control Number REF segment in Loop ID-2300. The insured reported in the Subscriber detail segments may be a non-person such as an employer or a business. |
1.4.4 Data OverviewThe data overview introduces the 837 transaction set structure and describes the positioning of business data within the structure. For a review of X12 nomenclature, segments, data elements, hierarchical levels, and looping structure, see Appendix B, X12 Control and Guidance, and Appendix C, EDI Control Directory. |
1.4.4.1 Loop Labeling, Sequence, and UseThe 837 transaction uses two naming conventions for loops. Loops are labeled with a descriptive name as well as with a shorthand label. Loop ID-2000A BILLING PROVIDER contains information about the billing provider, pay-to address and pay-to plan. The descriptive name – BILLING PROVIDER – informs the user of the overall focus of the loop. The Loop ID is a short-hand name, for example 2000A, that gives, at a glance, the position of the loop within the overall transaction. Loop ID-2010AA BILLING PROVIDER NAME, Loop ID-2010AB PAY-TO ADDRESS, and Loop ID-2010AC PAY-TO PLAN NAME are sub loops of Loop ID-2000A. When a loop is used more than once, a letter is appended to its numeric portion to allow the user to distinguish the various iterations of that loop when using the shorthand name of the loop. For example, loop 2000 has three possible iterations: Billing Provider Hierarchical Level (HL), Subscriber HL and Patient HL. These loops are labeled 2000A, 2000B and 2000C respectively. Under this guide, the hierarchical levels must be looked at as nested loops and constructed in that fashion, where 2000A is the highest level loop, 2000B is nested inside of 2000A and 2000C is nested inside of 2000B. The order of multiple subloops that do not involve hierarchical structure and that do have the same numeric position within the transaction is less important. Such subloops do not need to be sent in the same order in which they appear in this implementation guide. For such subloops in this transaction, the numeric portion of the loop ID does not end in 00. For example, Loop ID-2010 has two possibilities within Loop ID-2000B (Loop ID-2010BA Subscriber Name and Loop ID-2010BB Payer Name). Each of these 2010 loops is at the same numeric position in the transaction. Since they do not specify an HL, it is not necessary to use them in any particular order. However, it is not acceptable to send subloop 2330 before loop 2310 because these are not equivalent subloops. In a similar manner, if a single loop has multiple iterations (repetitions) of a particular segment, the sequence of those segments within a transaction is not important and is not required to follow the same order in which they appear in this implementation guide. For example, there are many DTP segments in the 2300 loop. It is not required that Discharge Time be sent before Statement Dates. However, it is required that the DTP segment in the 2300 loop come after the CLM segment because it is carried in a different position within the 2300 loop. |
1.4.4.2 Data Use by Business UseThe 837 is divided into two tables. Table 1 contains transaction control information and is described in Section 1.4.4.2.1 - Table 1 - Transaction Control Information. Table 2 contains the detail information for the transaction's business function and is described in Section 1.4.4.2.2 - Table 2 - Detail Information. |
1.4.4.2.1 Table 1 - Transaction Control InformationTable 1 is named the Header level (see Figure 1.3 - Header Level). Table 1 identifies the start of a transaction, the specific transaction set, the transaction's business purpose, and the submitter/receiver identification numbers. Figure 1.3 - Header Level |
1.4.4.2.1.1 Transaction Set Header (ST) SegmentThe Transaction Set Header (ST) segment identifies the transaction set by using 837 as the data value for the transaction set identifier code data element, ST01. The transaction set originator assigns the unique transaction set control number that is contained in ST02. Because the 837 is multi-functional, it is important for the receiver to know which business purpose is served. ST03 contains a reference to the specific implementation guide used to create this 837 transaction. |
1.4.4.2.1.2 Beginning of Hierarchical Transaction (BHT) SegmentThe BHT segment indicates that the transaction uses a hierarchical data structure. The data elements within the BHT are used in the following way:
|
1.4.4.2.2 Table 2 - Detail InformationTable 2 uses the hierarchical level structure. Each hierarchical level is comprised of a series of loops. Numbers identify the loops. The hierarchical level in Loop ID-2000 identifies the participants and the relationship to other participants. The individual or entity information is contained in Loop ID-2010. |
1.4.4.2.2.1 Hierarchical Level (HL) SegmentsThe following describes the HL structure within the claim transaction. The Billing Provider or Subscriber HLs may contain multiple "child" HLs. A child HL indicates an HL that is nested within (subordinate to) the previous HL. Hierarchical levels may also have a parent HL. A parent HL is the HL that is one level out in the nesting structure. An example follows.
For the Subscriber HL, the Billing Provider HL is the parent. The Patient HL is the child. The Subscriber HL is contained within the Billing Provider HL. The Patient HL is contained within the Subscriber HL. |
1.4.4.2.2.2 Subscriber / Patient Hierarchical Level (HL) SegmentsThe following information illustrates claim submissions when the patient is the subscriber and when the patient is not the subscriber. NOTES Claim submission when the patient is the subscriber or is considered to be the subscriber: Billing provider (HL03=20) Subscriber (HL03=22) Claim level information Line level information, as needed Claim/encounter submission when the patient is not the subscriber: Billing provider (HL03=20) Subscriber (HL03=22) Patient (HL03=23) Claim level information Line level information, as needed |
1.4.4.2.2.3 Hierarchical Level (HL) Structural ExampleIf the billing provider is submitting claims for more than one subscriber, each of whom may or may not have dependents, the HL structure between the transaction set header and trailer (ST-SE) could look like the following: BILLING PROVIDER SUBSCRIBER #1 (Patient #1) Claim level information Line level information, as needed SUBSCRIBER #2 PATIENT #P2.1 (for example, subscriber #2 spouse) Claim level information Line level information, as needed PATIENT #P2.2 (for example, subscriber #2 first child) Claim level information Line level information, as needed PATIENT #P2.3 (for example, subscriber #2 second child) Claim level information Line level information, as needed SUBSCRIBER #3 (Patient #3) Claim level information Line level information, as needed SUBSCRIBER #4 (Patient #4) Claim level information Line level information, as needed SUBSCRIBER #4 (repeated) PATIENT #P4.1 (for example, #4 subscriber's first child) Claim level information Line level information, as needed Based on the previous example, the HL structure will be as follows: HL*1**20*1~ (BILLING PROVIDER) 1Â Â Â = HL sequence number **(blank) Â Â Â Â = there is no parent HL (characteristic of the billing provider HL) 20Â Â = information source 1Â Â Â = there is at least one child HL to this HL HL*2*1*22*0~ (SUBSCRIBER #1) 2Â Â Â = HL sequence number 1Â Â Â = parent HL 22Â Â = subscriber 0Â Â Â = no subordinate HLs to this HL (there is no child HL to this HL - claim level data follows) HL*3*1*22*1~ (SUBSCRIBER #2) 3Â Â Â = HL sequence number 1Â Â Â = parent HL 22Â Â = subscriber 1Â Â Â = there is at least one child HL to this HL HL*4*3*23*0~ (PATIENT #P2.1) 4Â Â Â = HL sequence number 3Â Â Â = parent HL 23Â Â = dependent 0Â Â Â = no subordinate HLs in this HL (there is no child HL to this HL - data follows) HL*5*3*23*0~ (PATIENT #P2.2) 5Â Â Â = HL sequence number 3Â Â Â = parent HL 23Â Â = dependent 0Â Â Â = no subordinate HLs in this HL (there is no child HL to this HL - claim level data follows) HL*6*3*23*0~ (PATIENT #P2.3) 6Â Â Â = HL sequence number 3Â Â Â = parent HL 23Â Â = dependent 0Â Â Â = no subordinate HLs in this HL (there is no child HL to this HL - claim level data follows) HL*7*1*22*0~ (SUBSCRIBER AND PATIENT #3) 7Â Â Â = HL sequence number 1Â Â Â = parent HL 22Â Â = subscriber 0Â Â Â = no subordinate HLs in this HL (there is no child HL to this HL - claim level data follows) HL*8*1*22*0~ (SUBSCRIBER AND PATIENT #4) 8Â Â Â = HL sequence number 1Â Â Â = parent HL 22Â Â = subscriber 0Â Â Â = no subordinate HLs HL*9*1*22*1~ (SUBSCRIBER #4) 9Â Â Â = HL sequence number 1Â Â Â = parent HL 22Â Â = subscriber 1Â Â Â = there is at least one child HL to this HL HL*10*9*23*0~ (PATIENT #P4.1) 10Â Â = HL sequence number 9Â Â Â = parent HL 23Â Â = dependent 0Â Â Â = no subordinate HLs If another billing provider is listed in the same ST-SE functional group, it could be listed as follows: HL*100**20*1~. The HL sequence number of 100 indicates that there are 99 previous HL segments and it is the billing provider level HL (HL03 = 20). |
1.4.4.2.2.4 Hierarchical Level (HL) Structural SummaryThe following information summarizes coding and structure of the HL segment:
|
1.4.4.2.2.5 Claim StructureAfter the HL structure is defined and the Subscriber and/or Patient information is listed, the specific claim information follows:
|
1.4.4.2.2.6 Provider Taxonomy Code ReportingThe Health Care Provider Taxonomy code set describes the provider grouping, classification and area of specialization, and is maintained by the National Uniform Claim Committee (NUCC). For use in an 837 claim, the provider determines the code value from the code set (external Code Source 682) that most accurately describes the discrete specialization under which the provider performed the services reported on the claim. The payer may request providers submit a specialty under which they are credentialed but may not otherwise dictate the code value to be reported. |
1.4.5 BalancingIn order to ensure internal claim integrity, amounts reported in the 837 MUST balance at two different levels – the claim and the service line. |
1.4.5.1 Claim LevelThere are two different ways the claim information must balance. They are as follows. 1) Claim Charge Amounts 2) Claim Payment Amounts Balancing of claim payment information is done payer by payer. For a given payer that has service line adjudication data, the sum of all line level payment amounts (Loop ID-2430 SVD02) less any claim level adjustment amounts (Loop ID-2320 RAS adjustments) must balance to the claim level payment amount (Loop ID-2320 AMT02). When a previous payer's adjudication data is only at the claim level, the claim level Payer Paid Amount (Loop ID-2320 AMT02) must equal the Total Claim Charge Amount (Loop ID-2300 CLM02) less any claim level adjustment amounts for that payer (Loop ID-2320 RAS adjustments). Expressed as a calculation for given payer that has service line adjudication data: {Loop ID-2320 AMT02 payer payment} = {sum of Loop ID-2430 SVD02 payment amounts} minus {sum of Loop ID-2320 RAS adjustment amounts}. Line Level Payment Amounts Adjustment Calculations Claim Level Payment Amount Example: Claim Payment = 80.00 Line 1 Charge = 80.00 Line 2 Charge = 20.00 Claim payment ($80) = Line 1 payment ($70) plus Line 2 payment ($15) minus claim adjustment ($5). |
1.4.5.2 Service LineNote: This section does not apply to predetermination requests. Line Adjudication Information (Loop ID-2430) is reported when the payer identified in Loop ID-2330B has adjudicated the claim and service line payments and/or adjustments have been applied. Service line balancing applies independently for each Payer's Line Adjudication Information loop, Loop ID-2430. In order to balance, the sum of all service line adjustments and the service line payment within a Payer's 2430 Line Adjudication Information loop must balance to the Line Item Charge Amount for that service line. When a single service line has multiple 2430 loops for the same Payer, balancing logic must be modified. In the case of 2430 loops from two benefit plans from the same Payer, each SVD loop must balance independently as described above. Whereas, in the case of a single payer's adjudication unbundling services resulting in multiple 2430 loops, one for each unbundled service, the payments and adjustments for all such loops for that Payer must be summed together to balance to the Line Item Charge. The balancing calculation for each 2430 loop (other than the exceptions listed above) is as follows: {Sum of all Loop-ID 2430 RAS01 Adjustment Amounts}, Example: Line 1 Payment = 70.00 Line 2 Charge = 20.00 Line 1 adjustment ($10) plus Line 1 payment ($70) = Line 1 charge ($80) Line 2 adjustment ($5) plus Line 2 payment ($15) = Line 2 charge ($20) |
1.4.6 Obtaining Approval for use of K3 SegmentThe K3 Segment was added to X12N transactions to support a temporary solution for unexpected data requirements of a regulatory/legislative authority. It cannot be used for any other purpose. |
1.4.6.1 Requester SubmissionBefore a proposal can be considered by X12N, a change request must be submitted with the relevant business documentation to the X12 change request website at https://x12.org/resources/forms/maintenance-requests. |
1.4.6.2 X12N Review/ApprovalX12N will review the request to determine the business need. If X12N determines that there is business need and there is no method to meet the requirement, the requester will receive approval to use the K3 Segment on a temporary basis until a permanent location can be defined within a future transaction implementation. |
1.4.6.3 Formatting of K3 ContentThe format in which the requirements will be met within the K3 Segment itself must be coordinated between the requester and X12N to ensure a consistent implementation of the requirements for all trading partners. X12N will work with the requester to define those format requirements and will post an RFI (Request for Interpretation) to the X12 Interpretation Portal at https://x12.org/resources/forms/request-interpretation on behalf of the requester. |
1.5 Business TerminologyTo ensure consistent use of terms, definitions, and acronyms across X12 products, X12 maintains the Wordbook, a comprehensive corporate glossary. The included terms are either proprietary to X12, cite definitions published by another authority, or represent common terms and definitions that are relevant to X12's work. The terms and definitions defined in the Wordbook are used in X12 work products when applicable, without modification or revision. The Wordbook can be referenced online at wordbook.x12.org. |
1.6 Transaction AcknowledgmentsThe purpose of transaction acknowledgments is to report to the sender whether the transaction being acknowledged was accepted or rejected. The X12 Technical Report Type 2, Acknowledgment Reference Model provides guidance on several control structures and transaction set standards intended to augment EDI auditing and control systems. |
1.7 Related TransactionsThere are one or more transactions related to the transactions described in this implementation guide. |
1.7.1 Health Care Claim Payment/Advice (835)Information in the Health Care Claim Payment/Advice (835) transaction is generated by the payer's adjudication system. However, in a coordination of benefits (COB) situation where the provider is sending an 837 claim to a secondary payer for payment, information from the 835 may be included in the secondary 837. Data from specific segments/elements in the 835 are crosswalked directly into the subsequent 837. The payer's response to a predetermination request (837) will also be returned in a Health Care Claim Payment/Advice (835) transaction when the predetermination request was processed successfully. Refer to the Health Care Claim Payment / Remittance Advice TR3 for information on coding specific to a response to a predetermination request. If the services described in the predetermination request are subsequently rendered and then submitted in an 837 claim for payment, another 835 will be returned to advise of the finalized adjudication results and payment. The 835 response to a real-time claim for payment or a real-time predetermination request may be returned in either batch or real-time mode. |
1.8 Trading Partner AgreementsTrading partner agreements are used to establish and document the relationship between trading partners. A trading partner agreement must not override the specifications in this implementation guide if a transmission is reported in GS08 to be a product of this implementation guide. |
1.9 Transaction ComplianceThere are three types of compliance that may be relevant to a transmitted transaction. Compliance with implementation guide requirements Compliance with state and federal regulation Compliance with trading partner contractual agreements |
1.9.1 Transaction Compliance with Implementation Guide RequirementsA transaction complies with X12 implementation guide requirements if the transaction satisfies all format and content rules and constraints specified in the applicable X12 standards and the implementation guide (also known as a TR3) itself. Should additional clarification of an X12 implementation guide requirement be desired, two options are available.
X12 does not specify the business rules that the receiving entity must use to decide when to accept or reject a transaction. The receiver will handle transactions that are not TR3-compliant based on its own business process. A receiver may specify its business rules in a trading partner agreement or companion document. As stated in §1.8, these documents do not override TR3 requirements, nor change how transaction compliance with this TR3 is determined. |
1.9.2 Transaction Compliance with State and Federal RegulationsThis implementation guide has been developed for use as an insurance industry implementation guide. At the time of publication it has not been adopted as a state or federal standard. Should this implementation guide be adopted as a standard, the adopting authority will establish compliance dates for its use by impacted entities. X12 is not the authority for determining compliance with regulatory requirements that might further constrain implementation guide requirements. Questions of compliance for regulatory requirements should be directed to the governing authority. X12 does not specify the business rules that the receiving entity must use to decide when to accept or reject a transaction. The receiver will handle transactions that do not comply with applicable regulatory requirements as specified by the applicable regulation(s) or governing authority. |
1.9.3 Transaction Compliance with Contractual RequirementsX12 is not the authority for determining compliance with contractual requirements that might further constrain implementation guide requirements. Questions of compliance for contractual requirements should be directed to the contracting entity. X12 does not specify the business rules that the receiving entity must use to decide when to accept or reject a transaction. The receiver will handle transactions that do not comply with contractual requirements as specified by the applicable contract or contracting entity. |
1.10 National Provider Identifier Usage within the HIPAA 837 TransactionImplementation and use of the National Provider Identifier (NPI) has a direct impact on the generation of 837 transaction sets. Previous versions contained placeholder codes and elements in anticipation of the official Rule. With publication of the final rule and industry input on implementation direction, the authors have identified the following areas for clarification and direction for use within the implementation guide.
|
1.10.1 Providers who are Not Eligible for EnumerationAtypical providers are service providers that do not meet the definition of health care provider. Examples include taxi drivers, carpenters, personal care providers, etc. Although they are not eligible to receive an NPI, these providers perform services that are reimbursed by some health plans. This implementation guide accommodates both the NPI (to identify health care providers) and proprietary identifiers (to identify atypical/non-health care providers). |
1.10.2 Organization Health Care Provider Subpart RepresentationHistorically, there has been no standard representation of organization health care providers. How the health care provider entity has been identified has varied by trading partner. The NPI subpart concept provides an organization health care provider the ability to represent itself in a manner consistent to all trading partners. In the health care claim, there are two possible locations for organization health care provider entities to be reported. They are Billing Provider and Service Location. Billing Provider. In many instances the Billing Provider is an organization; therefore, the Billing Provider NPI reported would belong to an organization health care provider. The Billing Provider may be an individual only when the services were performed by, and will be paid to, an independent, non-incorporated individual. When an organization health care provider has determined that it has subparts requiring enumeration, that organization health care provider will report the NPI of the subpart as the Billing Provider. The subpart reported as the Billing Provider MUST always represent the most detailed level of enumeration as determined by the organization health care provider and MUST be the same identifier sent to any trading partner. NOTE Service Location. An organization health care provider's NPI used to identify the Service Location must be external to the entity identified as the Billing Provider (for example; reference lab). It is not permissible to report an organization health care provider's NPI as the Service Location if the Service Location is a subpart of the Billing Provider. |
1.10.3 Subparts and the 2010AA - Billing Provider Name LoopWhen the Billing Provider is an organization health care provider, the NPI of the organization health care provider or its subpart is reported in NM109. When an organization health care provider has determined a need to enumerate subparts, it is required that a subpart's NPI be reported as the Billing Provider. The subpart reported as the Billing Provider MUST always represent the most detailed level of enumeration and MUST be the same identifier sent to any trading partner. For additional explanation, see Section 1.10.2 - Organization Health Care Provider Subpart Representation. The Billing Provider may be an individual only when the health care provider performing services is an independent, unincorporated entity. In these cases, the Billing Provider is the individual whose Tax Identification Number (TIN) is used for IRS Form 1099 purposes. That individual's NPI is reported in NM109, and the individual's TIN must be reported in the REF segment of Loop ID-2010AA. The individual's NPI must be reported when the individual provider is eligible for an NPI. The TIN of the Billing Provider, used for IRS Form 1099 purposes, must be reported in the REF segment of Loop ID-2010AA Billing Provider. When the Billing Provider is an atypical provider, the Billing Provider should be the legal entity. However, willing trading partners may agree upon varying definitions. Proprietary or legacy identifiers necessary for the trading partner to identify the entity are to be reported in the REF segment of Loop ID-2010BB Payer Name. The TIN, used for IRS Form 1099 purposes, must be reported in the REF segment of Loop ID-2010AA Billing Provider. |
1.11 Coding of Drugs in the 837 ClaimThis section provides guidance on the coding of compound drug claims under HIPAA as accomplished in the 2400 and 2410 loops. |
1.11.1 Compound Drug BillingAn 837 for a multiple ingredient compound will have one 2400 loop for each ingredient with the HCPCS code in SV202-02, the provider's charge for that ingredient in SV203, and the associated units in SV205. When required by situational rules, the 2410 loop is sent with the NDC number in LIN03 with the associated quantity in CTP04. Loop ID-2410 REF02 must have the same prescription number, or the same linkage number if provided without a prescription, for each ingredient of the compound to enable the payer to differentiate and link the ingredients to a single compound. |
1.12.1 Individuals with one Legal NameIn those situations where an individual has only one legal name, report that name in the last name data element of the NM1 segment, specifically the NM103. The first and middle name data elements for that NM1 segment are then not used. This guideline is true for all loops containing an NM1 segment that may identify an individual. |
1.12.2 Situational Data specific to Payer's AdjudicationThis implementation guide contains a number of Situational Rules which state the element or segment is required when a payer's adjudication is known to be impacted by that information. These rules must not be construed as allowing the current payer to reject a claim or transaction if the information is submitted but not used by that payer. The condition in these situational rules is based on a known impact to any potential payer's adjudication. The purpose is to enable proper adjudication for any potential downstream payers as well as allow affected providers to collect and report information consistently for all trading partners when desired. As a result, the submitter is not restricted from sending the information to other payers in addition to the specific payer that has a known adjudication impact. In a payer-to-payer COB model, each payer should pass all data received in case it is needed by a subsequent payer. |
1.12.3Â Multiple REF Segments with the same QualifierA repeat of a REF segment within the same loop is not allowed when the qualifier in the REF01 data element is the same. However, there is one important exception to this rule. Within the 837, there are data elements reported in Loop ID-2400 and the various 2420 loops which are payer specific (for example: Referral Number, Prior Authorization Number, Provider Identifiers...). When these pieces of information are reported, the composite data element in REF04 is used to identify the associated payer. In all cases, the reported data belongs to the destination payer when REF04 is not used. When REF04 is used, the value reported in the first component (REF04-01) equals 2U. This qualifier indicates the value reported in the following component (REF04-02) is a payer identifier. This payer identifier "links" to one of the payer identifiers found in Loop ID-2330B NM109. |
1.12.4 Provider Tax IDsFor purposes of this implementation, the Billing Provider is the provider or provider organization to which payment is intended to be made. This payment is included in the provider's 1099 reporting. The Employer Identification Number (EIN) or Social Security Number (SSN) for the billing provider is only reported in the Billing Provider Tax Identification REF segment in Loop ID-2010AA Billing Provider. The EIN and SSN qualifiers are not valid in any provider REF segments other than the 2010AA Billing Provider loop. Other reference qualifiers must be used in the REF segments in those loops to provide identifying information, such as "A6" for Provider's Identifier. |
1.12.5Â Inpatient and Outpatient DesignationThe determination of what constitutes an Inpatient or Outpatient claim is defined in the external code set developed by the National Uniform Billing Committee in its Data Specifications Manual (UB Manual) beginning with UB-04. General guidelines are contained in the Type of Bill section of the UB Manual. Inpatient and Outpatient claims are distinguished by Type of Bill and other factors. Certain bill types are designated for inpatient use while others are designated for outpatient reporting. Exceptions to the general rules are documented with reference to the specific data elements affected. |
1.12.6 Date of Service for Predetermination RequestsSince the date of service associated with a predetermination request is assumed to be the date the transaction is created, validation of all medical code sets (such as procedure codes and diagnosis codes) is based upon the creation date reported in the DTP Segment (Original Claim Creation Date). The determination of reimbursement rates, patient responsibility, or any other situation where the service date would have significance, are to be based upon the date of payer adjudication. |
1.12.7 Unique Device Identifier ReportingThe Unique Device Identifier (UDI) has been established by the Food and Drug Administration (FDA) for the purposes of uniquely identifying all medical devices through their lifecycle from production to use in or with patients. The UDI is composed of two identifiers - Device Identifier (DI) and Product Identifier (PI). The DI portion of the UDI identifies the device labeler and the specific version or model of a device. The PI portion of the UDI may include any one or more of the following: device lot or batch number, serial number, manufacturing date, the expiration date, and distinct identification code. National Drug Code (NDC) and National Health Related Items Code (NHRIC) numbers assigned to supplies are being replaced with UDI. Only the DI portion of the UDI is reported for supplies, when applicable, in Loop ID 2410 (LIN). Reporting of the DI portion of the UDI for implanted and explanted high risk medical devices is done by organizations that have mutually agreed to send and receive the information or when mandated by federal or state laws/regulations. Determination of which devices are high risk implantable medical devices are to be mutually agreed upon by willing trading partners. Organizations that agree to send and receive the complete UDI, DI and PI, can use the X12N 277 Health Care Claim Request for Additional Information and the X12N 275 Additional Information to Support a Health Care Claim or Encounter. |
2.1 Presentation ExamplesThe X12 standards are generic. For example, multiple trading communities use the same PER segment to specify administrative communication contacts. Each community decides which elements to use and which code values in those elements are applicable. This implementation guide uses a format that depicts both the generalized standard and the insurance industry-specific implementation. In this implementation guide, IMPLEMENTATION specifies the requirements for this implementation. X12 STANDARD is included as a reference only. The transaction set presentation is comprised of two main sections with subsections within the main sections: Transaction Set Listing There are two sub-sections under this general title. The first sub-section concerns this implementation of a generic X12 transaction set. The second sub-section concerns the generic X12 standard itself. This section lists the levels, loops, and segments contained in this implementation. It also serves as an index to the segment detail. This section is included as a reference. Segment Detail There are three sub-sections under this general title. This section repeats once for each segment used in this implementation providing segment specific detail and X12 standard detail. This section is included as a reference. This section is included as a reference. It provides a pictorial view of the standard and shows which elements are used in this implementation. This section specifies the implementation details of each data element. These illustrations (Figures 2.1 through 2.5) are examples and are not extracted from the Section 2 detail in this implementation guide. Annotated illustrations, presented below in the same order they appear in this implementation guide, describe the format of the transaction set that follows. Figure 2.1 - Transaction Set Key - Implementation Figure 2.2 - Transaction Set Key - Standard Figure 2.3 - Segment Key - Implementation Figure 2.4 - Segment Key - Diagram Figure 2.5 - Segment Key - Element Summary |
2.2.1 Industry UsageIndustry Usage describes when loops, segments, and elements are to be sent when complying with this implementation guide. The three choices for Usage are required, not used, and situational. To avoid confusion, these are named differently than the X12 standard Condition Designators (mandatory, optional, and relational).
|
2.2.1.1 Determining Transaction Compliance with Industry Usage RequirementsA transmitted transaction complies with the governing implementation guide when it satisfies the requirements as defined within the implementation guide. Specifically, the presence or absence of an item (loop, segment, or element) complies with the industry usage specified by this implementation guide according to the following table.
|
2.2.2 LoopsLoop requirements depend on the context or location of the loop within the transaction. See Appendix B for more information on loops.
|
3. ExamplesBusiness scenario examples for use of this transaction can be found on the X12 Examples website at http://examples.x12.org. The X12 Examples website provides convenient access to examples of X12 transaction transmissions, including the data stream and a description of the associated scenario. |
| Â | ||||
Appendix A. External Code SourcesPrior to this publication, X12 TR3s contained a subset of the overall Code Source Directory, formerly known as Appendix A of X12.3. External code lists are not part of the X12 standard and are provided for information purposes only. The full listing is available in Glass, X12's On-Line viewer. Read more about Glass here: https://glasshelp.x12.org/. Where an external code source is referenced in this publication, the implementer is required to use only the codes from that list. Codes must be reported as listed in the code source (e.g. with leading zeroes). Implementers must follow the instructions for code use that are supplied by the code set owner. | ||||
| Â | ||||
B.1.1 Referenced and Related StandardsThis technical report is based on the X12 EDI standard which comprises a series of interdependent publications. Implementers are advised to consult these publications when using this technical report. The following standards are required to interpret, understand, and use this technical report:
The following guideline is useful to interpret, understand, and use this technical report:
The following reference model is useful to interpret, understand, and use this technical report:
All of the documents above are available online using links to X12's Online Viewer. | ||||
| Â | ||||
B.1.1.1 Transmission Control SchematicRefer to X12.5 - Interchange Control Structures, Section 3.5 - Order of Control Segments, and Chapter 5 Interchange Segment Specifications. Similar transaction sets, called "functional groups," can be sent together within a transmission. Each functional group is prefaced by a group start segment; and a functional group is terminated by a group end segment. One or more functional groups are prefaced by an interchange header and followed by an interchange trailer. Figure B.1 - Transmission Control Schematic, illustrates this interchange control. Figure B.1 - Transmission Control Schematic | ||||
| Â | ||||
B.1.1.2 Constraints applicable to the suite of TR3sRefer to X12.6 - Application Control Structure, Section 3.2.8 - Minimums/Maximums. Data element minimum and maximum lengths are set by the X12 standard. This implementation guide may further restrict minimum and maximum lengths within the bounds set by the standard. Such restrictions may occur implicitly by virtue of the allowed qualifier for the data element, or they may be stated explicitly in a note attached to the element or in the general limitations below. | ||||
| Â | ||||
B.1.1.2.1 Maximum Length of Data Element 127 Reference IdentificationThe current X12 standard allows a maximum length greater than 50 characters for data element 127. For implementations governed by this implementation guide, unless another value is specified in an attached note, the maximum length of each occurrence of this data element is constrained to 50 characters. | ||||
| Â | ||||
B.1.1.2.2 Maximum Length of Data Element 782 Monetary AmountFor implementations governed by this implementation guide, unless another value is specified for an instance of Data Element 782 within Section 2 (Transaction Set), each occurrence of Data Element 782 (Monetary Amount) will be limited to a maximum length of 10 characters including reported or implied places for cents (implied value of 00 after the decimal point). Note that the decimal point and leading sign, if sent, are not part of the character count. EXAMPLE
| ||||
| Â | ||||
B.1.1.3 DecimalWhile the X12 standard supports usage of exponential notation, this guide prohibits that usage. | ||||
Appendix D. Change SummaryThis Implementation Guide (008020X324) defines the X12 requirements for the Health Care Claim: Institutional. It is based on version/release/subrelease 008020 of the X12 standards. |