EDI 277 X364 - Data Reporting Acknowledgment

Functional Group HN

X12N Insurance Subcommittee

This X12 Transaction Set contains the format and establishes the data contents of the Health Care Information Status Notification Transaction Set (277) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by a health care payer or authorized agent to notify a provider, recipient, or authorized agent regarding the status of a health care claim or encounter or to request additional information from the provider regarding a health care claim or encounter, health care services review, or transactions related to the provisions of health care. This transaction set is not intended to replace the Health Care Claim Payment/Advice Transaction Set (835) and therefore, will not be used for account payment posting. The notification may be at a summary or service line detail level. The notification may be solicited or unsolicited.

Heading

1. 0100 · ST · Transaction Set Header · Max 1 · Mandatory

   To indicate the start of a transaction set and to assign a control number

2. 0200 · BHT · Beginning of Hierarchical Transaction · Max 1 · Mandatory

   To define the business hierarchical structure of the transaction set and identify the business application purpose and reference data, i.e., number, date, and time

Detail

1. 2000A Loop Mandatory Repeat 1

   1. 0100 · HL · Information Source Level · Max 1 · Mandatory

      To identify dependencies among and the content of hierarchically related groups of data segments

      This entity is the decision maker in the business transaction. For this business use, this entity is the data receiver or clearinghouse receiving the ASC X12 837 transaction. Examples of Data Receivers include payers, All Payer Claim Databases, and Health Insurance Exchanges.

   2. 2100A Loop Mandatory Repeat 1

      1. 0500 · NM1 · Information Source Name · Max 1 · Mandatory

         To supply the full name of an individual or organizational entity

   3. 2200A Loop Mandatory Repeat 1

      1. 0900 · TRN · Transmission Receipt Control Identifier · Max 1 · Mandatory

         To uniquely identify a transaction to an application

      2. 1200 · DTP · Information Source Receipt Date · Max 1 · Mandatory

         To specify any or all of a date, a time, or a time period

      3. 1200 · DTP · Information Source Process Date · Max 1 · Mandatory

         To specify any or all of a date, a time, or a time period

         The Information Source Process Date applies to the processing of the 837 claim transaction file through a processing system. This date may or may not be the same date as the Information Source Receipt Date.

   4. 2000B Loop Mandatory Repeat 1

      1. 0100 · HL · Information Receiver Level · Max 1 · Mandatory

         To identify dependencies among and the content of hierarchically related groups of data segments

         The Information Receiver is the entity that expects the response from the Information Source.

      2. 2100B Loop Mandatory Repeat 1

         1. 0500 · NM1 · Information Receiver Name · Max 1 · Mandatory

            To supply the full name of an individual or organizational entity

      3. 2200B Loop Mandatory Repeat 1

         1. 0900 · TRN · Information Receiver Application Trace Identifier · Max 1 · Mandatory

            To uniquely identify a transaction to an application

         2. 1000 · STC · Information Receiver Status Information · Max >1 · Mandatory

            To report the status, required action, and paid information of a claim or service line

            This segment will be used to convey information about an entire unit of work (e.g., single transaction of claims). Information contained at this level will be summary details pertaining to the unit of work being acknowledged. Examples include, but are not limited to, accepted for processing, and trading partner not authorized to submit to the Information Source's system.
            See Section 1.4.2 - Status Information (STC) Segment Usage for specific STC segment information, composites and code use.

         3. 1210 · QTY · Total Accepted Quantity · Max 1 · Optional

            To specify quantity information

            Required when at least one claim is accepted for this Information Receiver. If not required by this implementation guide, do not send.
            The purpose of this segment is to report the total number of claims accepted by the Information Source. Accepted claims include those where Loop ID 2200D STC03 = WQ (Accept) and/or EZ (Exception Occurred).

         4. 1210 · QTY · Total Rejected Quantity · Max 1 · Optional

            To specify quantity information

            Required when at least one claim is rejected for this Information Receiver. If not required by this implementation guide, do not send.
            The purpose of this segment is to report the total number of claims rejected for this Information Receiver (e.g., not accepted) by the Information Source.

         5. 1220 · AMT · Total Accepted Amount · Max 1 · Optional

            To indicate the total monetary amount

            Required when at least one claim is accepted for this Information Receiver. If not required by this implementation guide, do not send.
            The purpose of this segment is to report the total of the claim charge amount (Sum of Loop ID 2300 CLM02) of claims accepted by the Information Source. Accepted claims include those where Loop ID 2200D STC03 = WQ (Accept) and/or EZ (Exception Occurred).

         6. 1220 · AMT · Total Rejected Amount · Max 1 · Optional

            To indicate the total monetary amount

            Required when at least one claim is rejected for this Information Receiver. If not required by this implementation guide, do not send.
            The purpose of this segment is to report the total of the claim charge amount (Sum of Loop ID 2300 CLM02) of claims rejected by the Information Source.

      4. 2000C Loop Optional Repeat >1

         1. 0100 · HL · Billing/Service Provider Hierarchical Level · Max 1 · Mandatory

            To identify dependencies among and the content of hierarchically related groups of data segments

            Required when Loop ID 2200B STC03 is equal to `WQ' (Accept). If not required by this implementation guide, do not send.
            This loop and all subsequent loops are not used when Loop ID 2200B STC03 is equal to `U' (Reject).

         2. 2100C Loop Mandatory Repeat 1

            1. 0500 · NM1 · Billing/Service Provider Name · Max 1 · Mandatory

               To supply the full name of an individual or organizational entity

               This segment contains information which can be found in Loop 2010AA of the 837 implementation guides.

         3. 2200C Loop Optional Repeat 1

            1. 0900 · TRN · Billing/Service Provider Trace Identifier · Max 1 · Mandatory

               To uniquely identify a transaction to an application

               Because the TRN segment is syntactically required in order to use Loop 2200C, TRN02 can either be a sender assigned value or a default value of zero (0).
               Required when a secondary provider identifier needs to be reported in the Loop ID 2200C REF Billing/Service Provider Secondary Identifier segment, or to provide the status of a specific billing/service provider's group of claims in the Loop ID 2200C STC Billing/Service Provider Status Information. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.

            2. 1000 · STC · Billing/Service Provider Status Information · Max >1 · Optional

               To report the status, required action, and paid information of a claim or service line

               See Section 1.4.2 - Status Information (STC) Segment Usage for specific STC segment information, composites and code use.
               Required when needed to provide the status of a specific Billing/Service Provider's group of claims. If not required by this implementation guide, may be provided at the sender's discretion, but cannot be required by the receiver.

            3. 1100 · REF · Billing/Service Provider Secondary Identifier · Max 5 · Optional

               To specify identifying information

               Required when no billing/service provider identifier is sent in NM109 of this loop OR when an identification number in addition to that provided in NM109 of this loop is necessary for the processor to identify the entity. If not required by this implementation guide, do not send.

            4. 1210 · QTY · Total Accepted Quantity · Max 1 · Optional

               To specify quantity information

               The purpose of this segment is to report the total number of claims accepted by the Information Source for the Billing/Service Provider. Accepted claims include those where Loop ID 2200D STC03 = WQ (Accept) and/or EZ (Exception Occurred).
               Required when reporting status for a specific billing/service provider's group of claims and at least one claim is accepted. If not required by this implementation guide, do not send.

            5. 1210 · QTY · Total Rejected Quantity · Max 1 · Optional

               To specify quantity information

               The purpose of this segment is to report the total number of claims rejected by the Information Source for the Billing/Service Provider.
               Required when reporting status for a specific billing/service provider's group of claims and at least one claim is rejected. If not required by this implementation guide, do not send.

            6. 1220 · AMT · Total Accepted Amount · Max 1 · Optional

               To indicate the total monetary amount

               The purpose of this segment is to report the total dollar amount of claims (sum of CLM02) accepted by the Information Source for the Billing/Service Provider in this acknowledgment. Accepted claims include those where Loop ID 2200D STC03 = WQ (Accept) and/or EZ (Exception Occurred).
               Required when reporting status for a specific billing/service provider's group of claims and at least one claim is accepted. If not required by this implementation guide, do not send.

            7. 1220 · AMT · Total Rejected Amount · Max 1 · Optional

               To indicate the total monetary amount

               The purpose of this segment is to report the total dollar amount of claims (sum of CLM02) rejected by the Information Source for the Billing/Service Provider in this acknowledgment.
               Required when reporting status for a specific billing/service provider's group of claims and at least one claim is rejected. If not required by this implementation guide, do not send.

         4. 2000D Loop Optional Repeat >1

            1. 0100 · HL · Patient Level · Max 1 · Mandatory

               To identify dependencies among and the content of hierarchically related groups of data segments

               This HL level contains information about the Patient identified in the 837 transaction. See Section 1.4.1.1 - Defining the Patient Participant for information on identifying the Patient data from the 837 Transaction.
               Required when Loop ID 2200B STC03 is equal to `WQ' (Accept). If not required by this implementation guide, do not send.

            2. 2100D Loop Mandatory Repeat 1

               1. 0500 · NM1 · Patient Name · Max 1 · Mandatory

                  To supply the full name of an individual or organizational entity

            3. 2200D Loop Mandatory Repeat >1

               1. 0900 · TRN · Claim Status Tracking Number · Max 1 · Mandatory

                  To uniquely identify a transaction to an application

                  This segment is the patient control number submitted in the CLM01 of the 837.
                  This number must be returned exactly as submitted in the 837 up to the 20 character limit as defined in the 837 guide.

               2. 1000 · STC · Claim Level Status Information · Max >1 · Mandatory

                  To report the status, required action, and paid information of a claim or service line

                  See Section 1.4.2 - Status Information (STC) Segment Usage for specific STC segment information, composites and code use.

               3. 1100 · REF · Data Receiver Claim Control Number · Max 1 · Optional

                  To specify identifying information

                  Required when the Data Receiving Entity of the 837 assigns a specific number to the claim for processing and the number is available at the time of this acknowledgment. If not required by this implementation guide, do not send.

               4. 1100 · REF · Payer Claim Control Number · Max 1 · Optional

                  To specify identifying information

                  Required when acknowledging a Post Adjudicated Claim Data Reporting (PACDR) 837 and Loop ID 2320 SBR06 = `6'. If not required by this implementation guide, do not send.
                  This is the Other Payer Claim Control Number from Loop 2330B (REF*F8) when SBR06 = `6' in Loop 2320.

               5. 1100 · REF · Claim Identifier For Transmission Intermediaries · Max 1 · Optional

                  To specify identifying information

                  This number must be returned as received in the 837.
                  Required when the Claim Identifier Number For Transmission Intermediary was sent in the 837. If not required by this implementation guide, do not send.

               6. 1200 · DTP · Claim Level Service Date · Max 1 · Mandatory

                  To specify any or all of a date, a time, or a time period

                  For Institutional and Data Reporting claims, this is the statement period submitted in Loop ID 2300 (DTP01 = 434). For Professional claims this information is derived from the earliest service level dates in Loop ID 2400 (DTP01 = 472) to the latest service level date. For Dental claims this is the service date submitted in Loop ID 2300 (DTP01 = 472). If there is no service date in Loop ID 2300 (DTP01=472), then this is: the service date in Loop ID 2400 (DTP01=472), OR it is the treatment start in Loop ID ID 2400 (DTP01=196), OR the treatment end in Loop ID 2400 (DTP01=198), OR both the treatment start and treatment end dates in Loop ID 2400 listing the date range as from treatment start date to the treatment end date.

               7. 2220D Loop Optional Repeat >1

                  1. 1800 · SVC · Service Line Information · Max 1 · Mandatory

                     To supply payment and control information to a provider for a particular service

                     For Institutional claims, when both an NUBC revenue code and HCPCS or HIPPS code are reported, the HCPCS or HIPPS code is reported in SVC01-2 and the revenue code is reported in SVC04. When only a revenue code is used, it is reported in SVC01-2.
                     Required when a Reject Action Code (Loop ID 2220D STC03 = `U') is being assigned to a service line. OR Required when an Exception Occurred Action Code (Loop ID 2220D STC03 = `EZ') is being assigned to a service line. If not required by this implementation guide, do not send.

                  2. 1900 · STC · Service Line Level Status Information · Max >1 · Mandatory

                     To report the status, required action, and paid information of a claim or service line

                     See Section 1.4.2 - Status Information (STC) Segment Usage for specific STC segment information, composites and code use.

                  3. 2000 · REF · Line Item Control Number · Max 1 · Mandatory

                     To specify identifying information

                     This is the Line Item Control Number exactly as submitted in the 837 transaction for the original claim in Loop ID 2400, REF02 (REF01 = 6R). If a Line Item Control Number is not submitted, this will be the line sequence number Loop ID 2400 LX01.

                  4. 2000 · REF · Pharmacy Prescription Number · Max 1 · Optional

                     To specify identifying information

                     Required when a Pharmacy Prescription Number was sent in the 837 at the Service Line. If not required by this implementation guide, do not send.

                  5. 2100 · DTP · Service Line Date · Max 1 · Optional

                     To specify any or all of a date, a time, or a time period

                     Required when the Date of Service from the original submitted claim for a specific line item is present. If not required by this implementation guide, do not send.

2. 2700 · SE · Transaction Set Trailer · Max 1 · Mandatory

   To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)