Handling a 270/271 eligibility interface response means distinguishing four possible return types before parsing any benefit data. The CMS HETS application creates either an Eligibility Response (271), an Implementation Acknowledgement (999), an Interchange Acknowledgement (TA1), or a proprietary error response [2]. A developer who treats every return as a 271 will misread rejection paths and may present stale or invalid eligibility information. The source documents do not describe a single universal response contract. Instead, each companion guide defines its own boundaries for record ownership, timing, and error communication. This article examines those documented distinctions across Medicare HETS, Cigna Healthcare, and Colorado Medicaid, then proposes a hypothetical validation scenario that stays within the stated limits of the source material.

Response Types Are Not Interchangeable

The HETS 270/271 application returns a 271 only when the 270 request complies with X12 standard syntax requirements and all additional formatting rules in the companion guide [1]. If errors occur in the data segments between the Functional Group Header (GS) and Functional Group Trailer (GE), the application uses a 999 Implementation Acknowledgement to communicate rejection due to X12 compliance, formatting, or CMS-specific requirements [1]. This means the 999 is not a fallback eligibility answer; it signals that no eligibility determination was made.

Cigna Healthcare describes a similar layered approach. The payer will use both the TA1 Interchange Acknowledgement and 999 Functional Acknowledgement when necessary and appropriate [4]. In the Cigna process flow, a valid and authorized request proceeds to eligibility and benefit processing, while an invalid request produces an HTTP error, TA1, 999, or 271 response depending on where the failure occurs [4]. The distinction matters for interface design because each response type carries different payload expectations and different downstream handling logic.

Record Ownership and Data Freshness Boundaries

The HETS 271 response is explicitly time-bound. The data in a 271 response is considered true and accurate only at the time of the transaction [1]. The HETS 270/271 application data is updated once daily, early in the morning Eastern Time, and the 271 response is not updated further during the day [3]. Trading partners should not resubmit the same transaction multiple times in a day expecting different results [3]. This creates a clear ownership boundary: the interface can cache a response, but the cached record represents a point-in-time snapshot, not a live eligibility status.

The 271 response is also not a guarantee of payment [1]. Questions about Medicare Part A and Part B eligibility should go to the appropriate regional Medicare Administrative Contractor, while Medicare Advantage, Part D, and Medicare Secondary Payer questions should go to the plans identified in the 271 response [1]. For Medicare Advantage, each plan can have different out-of-pocket costs and specific rules for getting and billing services [3]. The interface therefore owns transport and parsing, but the clinical or financial interpretation belongs to downstream business processes and plan-specific rules.

A Suggested Validation Workflow for Response Handling

A hypothetical interface test could send a 270 with ISA15 set to T for test data. Cigna Healthcare documents that when ISA15 is T, the X12 request ISA10, ISA11, GS04, and GS05 date and time elements are returned in the X12 response, allowing regression test tools to validate expected date and time responses [4]. When ISA15 is P for production data, those fields are populated with the current date and time [4]. This distinction provides a concrete way to verify that a response parser correctly handles test versus production envelope values without inventing eligibility outcomes.

A second validation step could submit a syntactically valid 270 with a deliberately non-matching subscriber element to observe the AAA error path. The HETS documentation states that invalid or non-matching data elements are returned for AAA error codes 58, 62, 71, 72, and 73 [6]. The interface should then confirm that the AAA segment is parsed separately from normal EB benefit segments. This suggestion is not a claim that any specific implementation passes such a test; it is a workflow derived from the documented error behavior.

Error Communication Inside the 271

A syntactically valid 270 can still produce business-rule errors inside a 271 response. The HETS application uses the AAA error segment within the 271 response to communicate error conditions based on CMS business rules [6]. For 2100C Loop AAA error codes 58, 62, 71, 72, and 73, the application returns the invalid or non-matching data elements from the 270 request [6]. This is a distinct handling path from the 999: the transaction envelope is valid, but a specific subscriber or dependent data element failed a CMS business rule.

The Colorado Medical Assistance Program companion guide adds a different response-level detail. If more than one qualifier and value combination is included in the MSG segment, they will be concatenated with a pipe delimiter [7]. This affects how an interface should parse free-form message text when multiple copay or eligibility notes are returned. The Colorado guide also documents a Pending Eligibility code 7 added to EB01 mapping in August 2026 [7]. Such payer-specific mappings mean a generic 271 parser may need configuration tables rather than hard-coded code lists.

Timing Expectations Vary by Payer

Colorado Medicaid states that trading partners typically receive the 271 response file within 30 minutes or less of sending the 270 inquiry file, but due to system volume it may take up to 2 hours [7]. This is a batch-oriented expectation, distinct from the real-time mode described for HETS, where the trading partner transmits a 270 request and remains connected while the receiver processes the transaction and returns a 271 response [1]. An interface built for synchronous HETS-style handling may need a different timeout and retry model for Colorado Medicaid.

The HETS SOAP and MIME connectivity instructions add transport-level requirements that affect response handling. Trading partners transmitting with SOAP or MIME must include the X-Forwarded-For HTTP header in all their 270/271 requests [5]. For SOAP, the trading partner digitally signs the SOAP Body Payload and SOAP Header Timestamp using their private key, and CMS embeds its certificate in the 271 response so the trading partner can verify the response came from CMS [5]. These are authentication and integrity checks that occur before eligibility data is trusted.

Version and Deployment Boundaries

The source documents span multiple versions with different revision dates. The HETS companion guide appears as Version 15-1 dated May 2026 [1], Version 14-0 dated November 2025 [2], and Version 12-0 dated May 2025 [6]. The Cigna Healthcare companion guide is Version 3.0 dated August 2026 [4]. The Colorado guide is Version 2.4 with revision entries dated June 2026 and August 2026 [7]. These version boundaries mean that a response handling implementation validated against one document version may not reflect later changes.

The HETS SOAP and MIME connectivity instructions are Version 11.1 [5]. The document revision history for HETS shows changes such as directing SOAP or MIME submitters to the connectivity instructions for X.509 certificate requirements in May 2025 [6]. An interface team should track which companion guide version corresponds to the payer's current production environment. The documents do not state a universal versioning policy across all payers, so each trading partner relationship requires its own version check.