Finance and Insurance Service (FAIS)
1.0.0 - trial-use
Finance and Insurance Service (FAIS)
1.0.0 - trial-use
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
This section corresponds to transaction [ITI-121] of the IHE IT Infrastructure Technical Framework. Transaction [ITI-121] is used by the Beneficiary Manager and Beneficiary Requestor Actors. The Query Insurance Plan [ITI-121] transaction is used to discover insurance plans to be used when enrolling beneficiaries.
This transaction is used by the Beneficiary Requestor to find insurance plans based on criteria it provides in the query parameters of the request message, or to retrieve a specific insurance plan. The request is received by the Beneficiary Manager. The Beneficiary Manager processes the request and returns a response of the matching insurance plans.
Table 2:3.121.2-1: Actor Roles
| Actor | Role |
|---|---|
| Beneficiary Requestor | Requests insurance plan(s) matching the supplied set of criteria from the Beneficiary Manager. |
| Beneficiary Manager | Returns information for insurance plan(s) matching the criteria provided by the Beneficiary Requestor |
The Search Insurance Plan message is a FHIR search interaction on the InsurancePlan Resource.
A Beneficiary Requestor triggers a Search Insurance Plan Request to a Beneficiary Manager when it needs to know what plans are available to use to enroll a beneficiary [ITI-122].
A Beneficiary Requestor initiates a search interaction using HTTP GET as defined at http://hl7.org/fhir/R4/http.html#search on the InsurancePlan resource. The query parameters are identified below. A Beneficiary Requestor MAY query any combination or subset of the parameters. The target is formatted as:
GET [base]/InsurancePlan?[parameter=value]
Where [base] is the URL of Beneficiary Manager.
A Beneficiary Manager SHALL support responding to a request for both the JSON and the XML messaging formats as defined in FHIR. A Beneficiary Requestor SHALL accept either the JSON or the XML messaging formats as defined in FHIR. See ITI TF-2: Appendix Z.6 for more details.
A Beneficiary Manager SHALL implement the parameters described below. A Beneficiary Manager MAY choose to support additional query parameters beyond the subset listed below. Any additional query parameters supported SHALL be supported according to the core FHIR specification.
See ITI TF-2: Appendix W for informative implementation material for this transaction.
The Beneficiary Manager will support the search parameters as defined in the capability statement for InsurancePlan.
The Beneficiary Requestor will support the search parameters as defined in the capability statement for InsurancePlan
The Beneficiary Manager SHALL process the query to discover the insurance
plan(s) that match the search parameters given, and if successful, with an HTTP 200 (OK) and a Search Insurance Plan Response Message
or an error as per http://hl7.org/fhir/R4/search.html#errors.
The Beneficiary Manager found Insurance Plans matching the query parameters specified by the Beneficiary Requestor as a result of a Search Insurance Plan Request.
The Beneficiary Manager SHALL support the search response message as defined at http://hl7.org/fhir/R4/http.html#search on the InsurancePlan, as defined at http://hl7.org/fhir/R4/insuranceplan.html
The “content-type” of the response will depend upon the requested response format indicated by the Beneficiary Requestor.
See ITI TF-2: Appendix Z.6 for more details on response format handling. See ITI TF-2: Appendix Z.7 for handling guidance for Access Denied.
A InsurancePlan Resource returned by the Beneficiary Manager SHALL be further constrained as described in the FAIS InsurancePlan profile.
The Beneficiary Requestor has received the response and continues with its workflow.
This message represents an HTTP GET from the Beneficiary Requestor to the Beneficiary Manager and provides a mechanism for retrieving a single InsurancePlan with a known resource id.
When the Beneficiary Requestor possesses the id of InsurancePlan (either through query, database lookup, or other mechanism) for which it requires additional or new information, it issues a Read Insurance Plan Request.
A Beneficiary Requestor initiates a read interaction using HTTP GET as defined at http://hl7.org/fhir/R4/http.html#read on the InsurancePlan Resource. The target is formatted as:
GET [base]/InsurancePlan/[resourceId]
Where [base] is the URL of Beneficiary Manager.
The resourceId included in the request always represents the unique id for the InsurancePlan within the scope of the URL. For example, while http://example1.org/ihe/InsurancePlan/1 and http://example2.com/ihe/InsurancePlan/1 both contain the same [resourceId], they reference two different resource instances.
Note: The use of “http” or “https” in URL does not override requirements to use TLS for security purposes.
A Beneficiary Manager SHALL support responding to a request for both the JSON and the XML messaging formats as defined in FHIR. A Beneficiary Requestor SHALL accept either the JSON or the XML messaging formats as defined in FHIR. See ITI TF-2: Appendix Z.6 for more details.
See ITI TF-2: Appendix W for informative implementation material for this transaction.
The Beneficiary Manager SHALL process the request to retrieve the
InsurancePlan that matches the given resource id, and if successful, with an HTTP 200 (OK) and a response as
defined at http://hl7.org/fhir/R4/http.html#read with the Read Insurance Plan Response Message or an error code as
defined at http://hl7.org/fhir/R4/http.html#Status-Codes.
The Beneficiary Manager found a InsurancePlan Resource matching the resource identifier specified by the Beneficiary Requestor.
The Read Insurance Plan Response is sent from the Beneficiary Manager to the Beneficiary Requestor as a single InsurancePlan, as defined at http://hl7.org/fhir/R4/insuranceplan.html and constrained by the FAIS InsurancePlan profile.
The “content-type” of the response will depend upon the requested response format indicated by the Beneficiary Requestor.
See ITI TF-2: Appendix Z.6 for more details on response format handling. See ITI TF-2: Appendix Z.7 for handling guidance for Access Denied.
If the Beneficiary Manager is unable to produce a response in the requested format, it SHALL respond with an HTTP 4xx error indicating that it was unable to fulfill the request. The Beneficiary Manager MAY be capable of servicing requests for response formats not listed, but SHALL, at minimum, be capable of producing XML and JSON encodings.
The Beneficiary Requestor has received the response and continues with its workflow.
Server implementing this transaction SHALL provide a CapabilityStatement Resource as described in ITI TF-2: Appendix Z.3 indicating the transaction has been implemented.
See FAIS Security 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 performing the Query Insurance Plan message SHALL record audit events according to the Audit Event for Query Insurance Plan Query Transaction. See Audit Example for Query Insurance Plan search from the Beneficiary Requestor.
The actors performing the Read Insurance Plan message SHALL record audit events according to the Audit Event for Query Insurance Plan Read Transaction. See Audit Example for Query Insurance Plan read message from the Beneficiary Requestor.
IG © 2024+ IHE IT Infrastructure Technical Committee. Package ihe.iti.fais#1.0.0 based on FHIR 4.0.1. Generated 2024-11-13
Links: Table of Contents |
QA Report
| New Issue | Issues
Version History |
|
Propose a change