Finance and Insurance Service (FAIS), published by IHE IT Infrastructure Technical Committee. This guide is not an authorized publication; it is the continuous build for version 1.0.1-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/ITI.Finance/ and changes regularly. See the Directory of published versions

2:3.122 Enroll Beneficiary [ITI-122]

This section corresponds to transaction [ITI-122] of the IHE ITI Technical Framework. Transaction [ITI-122] is used by the Beneficiary Requestor and Beneficiary Manager Actors. The Enroll Beneficiary [ITI-122] transaction is used to enroll a patient in a particular coverage offered by the insurance plan.

2:3.122.1 Scope

This transaction is used by the Beneficiary Requestor to request that a patient be enrolled with a given coverage. The request is received by the Beneficiary Manager. The Beneficiary Manager processes the request and returns a response with the status of the request.

2:3.122.2 Actor Roles

Table 2:3.122.2-1: Actor Roles

2:3.122.3 Referenced Standards

FHIR-R4 HL7 FHIR Release 4.0

2:3.122.4 Messages

2:3.122.4.1 Enroll Beneficiary Request Message

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

2:3.122.4.1.1 Trigger Events

When a Beneficiary Requestor needs to enroll a Patient with a given Coverage on the Beneficiary Manager, it submits the Enrollment Request Message. The creation of the Coverage resource is beyond the scope of this profile, but it MAY be created by the Beneficiary Requestor based on an InsurancePlan the beneficiary is enrolling in that the Beneficiary Requestor retrieved from the Beneficiary Manager using the Query Insurance Plan [ITI-121] Transaction.

2:3.122.4.1.2 Message Semantics

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

POST [base]/EnrollmentRequest/$submit

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

2:3.122.4.1.3 Expected Actions

The Beneficiary Manager SHALL process the EnrollmentRequest and respond as per http://hl7.org/fhir/R4/operations.html#response, and if successful, with an HTTP 201 (CREATED) and an Enroll Beneficiary Response Message.

The Beneficiary Manager SHALL persist the EnrollmentRequest resource and include a reference to it in the EnrollmentResponse resource.

2:3.122.4.2 Enroll Beneficiary Response Message

2:3.122.4.2.1 Trigger Events

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

2:3.122.4.2.2 Message Semantics

The Enroll Beneficiary Response conforms to the FAIS EnrollmentResponse profile and is sent from the Beneficiary Manager to the Beneficiary Requestor. If the disposition of the enrollment can’t be handled synchronously, then the outcome element SHALL be set to queued and EnrollmentResponse SHALL include an id and persist on the Beneficiary Manager so that the ITI-123 Check Enrollment Status transaction can be used to get updates on the response.

2:3.122.4.2.3 Expected Actions

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

2:3.122.5 CapabilityStatement Resource

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

• Requirements CapabilityStatement for Beneficiary Requestor
• Requirements CapabilityStatement for Beneficiary Manager

2:3.122.6 Security Considerations

See FAIS Security Considerations.

2:3.122.6.1 Security Audit Considerations

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

The actors involved SHALL record audit events according to the Audit Event for Enroll Beneficiary Transaction. See Audit Example for Enroll Beneficiary from the Beneficiary Requestor.