Skip to content

parser / guides / 05

Read Cigna responses

This page describes how to read a 271 eligibility response from Cigna Healthcare by using interpretRoute with cignaProfile. The profile applies the 271 rules from the Cigna Healthcare 270/271 Companion Guide, version 3.0 (August 2026). The companion guide states that it applies to all Cigna Healthcare customers. The profile does the following:

  • Checks the payer in the response.
  • Gives each error that the companion guide lists its Cigna meaning.
  • Reads each member's plan network, provider participation, care management level, attribution, HRA balances, and partner arrangements.

Before you begin ​

Make sure that you have the following:

  • A 271 response to a 270 request that you sent to Cigna, either directly or through a clearinghouse.
  • The @ediocracy/parser package.

To have the library pick the profile from the 2100A payer ID in the response, use interpretRoute(entry) instead of passing cignaProfile. For more information, see Apply the payer's rules.

Read a response ​

The following example reads a file of 271 responses and prints the Cigna results for each member:

ts
import { readFile } from 'node:fs/promises';

import { readX12 } from '@ediocracy/parser';
import { read271s } from '@ediocracy/parser/271';
import { cignaProfile, interpretRoute } from '@ediocracy/parser/271/routes';

const text = await readFile('response.x12', 'utf8');

for (const entry of read271s(readX12(text))) {
    const result = interpretRoute(entry, cignaProfile);

    for (const finding of result.findings) {
        console.log('Finding:', finding.code, finding.message);
    }

    for (const error of result.errors) {
        console.log('Error:', error.condition ?? error.rejectReason, error.description);
    }

    for (const view of result.members) {
        console.log('Network:', view.network?.name, view.network?.description);
        console.log('Participation:', view.participation);
        console.log('Care management:', view.careManagement);
        console.log('Attribution:', view.attribution.map(row => row.status));
        console.log('HRA:', view.hraBalances.map(row => `${row.kind} ${row.amount ?? ''}`));
    }
}

For each item that read271s returns, interpretRoute(entry, profile) returns a RouteEligibility object. The object has the following fields:

  • eligibility: the unchanged result of interpret271 for the response.
  • errors: each error that the payer reported, in the same order as eligibility.requestErrors. When the companion guide lists an error, its entry includes the Cigna condition and description.
  • findings: the problems that the profile found in the response.
  • members: one CignaView object for each member, in the same order as eligibility.members.

Payer checks ​

The companion guide gives a Cigna tax ID for each Cigna company that sends responses. The guide's examples use two other tax IDs, and responses from the Stedi sandbox can contain Cigna's clearinghouse payer ID instead. cignaProfile accepts each of these IDs. It accepts each tax ID with or without the hyphen:

CompanyNM109 values
CGLIC06-1059331, 061059331, 06-0303370, 060303370
CHLIC59-1031071, 591031071, 59-1056496, 591056496
Cigna Behavioral Health41-1648670, 411648670
Cigna Dental Health59-2308055, 592308055
Clearinghouse payer ID62308

The profile reports unexpected-source when the 2100A NM1 segment doesn't meet all of the following conditions:

  • NM101 is PR.
  • NM108 is FI or PI.
  • NM109 is one of the values in the table.

The companion guide says that the response uses the separators that the request used, it gives no rules for the 2100B loop, and it names no placeholder member IDs. For these reasons, the profile never reports unexpected-delimiters, unexpected-receiver, or member-id-placeholder.

Errors ​

The companion guide lists the AAA03 codes that Cigna sends when it can't identify the member. Each condition has one code for a subscriber and one for a dependent:

Subscriber AAA03Dependent AAA03conditionMeaning
7567member-not-foundNo member matches the request.
7668multiple-members-foundMore than one member matches the request, and Cigna can't choose one.
7264member-id-not-matchedThe member ID is missing or doesn't match.
7365name-not-matchedThe member's name is missing or doesn't match.
5858birth-date-not-matchedThe date of birth is missing or doesn't match.

The companion guide doesn't list every error that Cigna sends, so the profile doesn't report an unlisted error as a finding. In errors, the entry for an unlisted error has condition and description set to undefined.

Cigna view ​

Each CignaView object contains the fields in the following table. Each list keeps its rows in the order that they appear in the response.

FieldContents
networkThe member's REF segment with REF01 set to N6. name is REF02, and description is REF03. undefined when there's no such segment.
participationin-network or out-of-network when a message on a row with EB01 set to 1 and EB03 set to 30 says that the provider is in or out of network. Otherwise, undefined.
careManagementThe first message on a row with EB01 set to 1 that is PHS or PHS+, or that ends in Care Management, exactly as Cigna sent it. Otherwise, undefined.
isCareLinktrue when a row with EB01 set to 1 and EB03 set to 30 has CareLink in EB05.
sharedRiskNetworksRows with EB01 set to N. manager is the name of the organization in the row's 2120 loop.
attributionPatient attribution rows. For more information, see Attribution.
hraBalancesHealth reimbursement arrangement (HRA) balances. For more information, see HRA balances.
partnersPartner arrangement rows. For more information, see Partners.

Attribution ​

An attribution row says whether Cigna assigns the member to the provider who sent the request. A row is an attribution row when it meets all of the following conditions:

  • EB01 is CB, D, or E.
  • EB06 is 25.
  • One of its messages starts with Attribution Status.

The status field comes from EB01: CB is yes, D is no, and E is not-applicable. The start and end fields are the dates in the DTP segments with DTP01 set to 356 and 357.

HRA balances ​

An HRA balance is a row with EB01 set to F and the message HRA Balance (kind is starting) or HRA remaining Balance (kind is remaining). The amount field is EB07.

Partners ​

When another organization shares the administration of the member's plan, Cigna sends a row with EB01 set to U. Each partner entry has the following fields:

  • name: the name in the row's 2120 loop. When the row has no 2120 loop, name is EB05.
  • phone: the first telephone number in the PER segments of the 2120 loop.
  • messages: the row's messages, exactly as Cigna sent them.

The profile doesn't read rows with EB01 set to I as partners, because Cigna also uses I for benefits that aren't covered.

Findings ​

The findings field uses codes from RouteFindingCode and CignaFindingCode. The profile reports the following codes:

  • unexpected-source: the 2100A NM1 segment doesn't meet the conditions in Payer checks.
  • attribution-status-mismatch: an attribution message says Yes, No, or Not applicable, but EB01 isn't the matching code: CB for Yes, D for No, or E for Not applicable. The row stays in attribution, and its status comes from EB01.

Limitations ​

The CignaView object doesn't include the following information. To get it, read eligibility.

  • Messages about the Client Specific Network on cost share rows
  • Place of service (III) rows
  • Which of a member's plans (medical, dental, or behavioral) a row belongs to