Finance and Insurance Service (FAIS)
1.0.0 - trial-use International flag

This page is part of the IHE ITI Finance and Insurance Services (v1.0.0: Publication) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions

2:3.124 Check Coverage Eligibility [ITI-124]

This section corresponds to transaction [ITI-124] of the IHE IT Infrastructure Technical Framework. Transaction [ITI-124] is used by the Coverage Requestor and Claims Manager Actors. The Check Coverage Eligibility [ITI-124] transaction is used to check the coverage for a patient.

2:3.124.1 Scope

This transaction is used by the Coverage Requestor to check if a product or service is covered for the patient. The request is received by the Claims Manager. The Claims Manager processes the request and returns a response with the status of the request.

2:3.124.2 Actor Roles

Table 2:3.124.2-1: Actor Roles

Actor Role
Coverage Requestor Sends the coverage eligibility request to the Claims Manager.
Claims Manager Receives and processes the request and returns a response to the Coverage Requestor

2:3.124.3 Referenced Standards

FHIR-R4 HL7 FHIR Release 4.0

2:3.124.4 Messages

Beneficiary RequestorClaims Manager[1]Check Coverage Eligibility Request:HTTP POST <Base>/CoverageEligibilityRequest/$submit[2]Check Coverage Eligibility Response:CoverageEligibilityResponse or Bundle
Figure 2:3.124.4-1: Interaction Diagram


2:3.124.4.1 Check Coverage Eligibility Request Message

This message uses the HTTP POST method on the target Claims Manager endpoint that is a FAIS CoverageEligibilityRequest $submit operation. It is sent from a Coverage Requestor.

2:3.124.4.1.1 Trigger Events

When a Coverage Requestor needs to check the coverage of a Patient on the Claims Manager, it submits the Check Coverage Eligibility Request Message.

2:3.124.4.1.2 Message Semantics

The Coverage Requestor invokes the FAIS CoverageEligibilityRequest $submit operation on the Claims Manager. The operation is invoked by submitting an HTTP POST request to the Claims Manager at the path:

POST [base]/CoverageEligibilityRequest/$submit

The HTTP body SHALL consist of either a FHIR CoverageEligibilityRequest resource conforming to the FAIS CoverageEligibilityRequest profile or a CoverageEligibilityRequest Bundle including referenced resources conforming to the FAIS CoverageEligibilityRequest Bundle profile.

2:3.124.4.1.3 Expected Actions

The Claims Manager SHALL process the CoverageEligibilityRequest and respond as per http://hl7.org/fhir/R4/operations.html#response, and if successful, with an HTTP 201 (CREATED) and a Check Coverage Eligibility Response Message.

The Claims Manager SHALL persist the CoverageEligibilityRequest resource and include a reference to it in the CoverageEligibilityResponse resource.

2:3.124.4.2 Check Coverage Eligibility Response Message

2:3.124.4.2.1 Trigger Events

The Claims Manager has a response or errors to report to the Coverage Requestor. This MAY include a queued response.

2:3.124.4.2.2 Message Semantics

The Check Coverage Eligibility Response conforms to the FAIS CoverageEligibilityResponse profile and is sent from the Claims Manager to the Coverage Requestor. If the disposition of the coverage eligibility request can’t be handled synchronously, then the outcome element SHALL be set to queued and CoverageEligibilityResponse SHALL include an id and persist on the Claims Manager so that the ITI-125 Check Coverage Eligibility Status transaction can be used to get updates on the response.

2:3.124.4.2.3 Expected Actions

How the Coverage Requestor processes the response is determined by the implementation and beyond the scope of this profile.

2:3.124.5 CapabilityStatement Resource

Server implementing this transaction SHALL provide a CapabilityStatement Resource as described in ITI TF-2: Appendix Z.3 indicating the transaction has been implemented.

2:3.124.6 Security Considerations

See FAIS Security Considerations.

2:3.124.6.1 Security Audit Considerations

Note that the same audit message is recorded by both the Coverage Requestor and Claims Manager. The difference being the Audit Source element. Both sides record to show consistency between the message sent by the Coverage Requestor and the action taken at the Claims Manager.

The actors involved SHALL record audit events according to the Audit Event for Check Coverage Eligibility Transaction. See Audit Example for Check Coverage Eligibility from the Coverage Requestor.