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

Finance and Insurance Service (FAIS) Home

Official URL: https://profiles.ihe.net/ITI/FAIS/ImplementationGuide/ihe.iti.fais				Version: 1.0.0
Active as of 2024-11-21				Computable Name: IHE_ITI_FAIS

The Finance and Insurance Service (FAIS) stores, categorizes, and facilitates the administration of centralized claims and finance data for patient care. The service receives claims/financial data from Point of Service (POS) applications (including financing applications acting as a point of service interface outside of other POS systems) and curates the management of them.

Organization of This Guide

This guide is organized into the following sections:

1. Volume 1:
   1. Introduction
   2. Actors, Transactions, and Content
   3. Actor Options
   4. Required Actor Groupings
   5. Overview
   6. Security Considerations
   7. Cross Profile Considerations
2. Volume 2: Transaction Detail
   1. Query Insurance Plan [ITI-121]
   2. Enroll Beneficiary [ITI-122]
   3. Check Enrollment Status [ITI-123]
   4. Check Coverage Eligibility [ITI-124]
   5. Check Coverage Eligibility Status [ITI-125]
   6. Submit Claim [ITI-126]
   7. Cancel Claim [ITI-127]
   8. Re-process Claim [ITI-128]
   9. Track Claim [ITI-129]
3. Other
   1. Changes to Other IHE Specifications
   2. Download and Analysis
   3. Test Plan

See also the Table of Contents and the index of Artifacts defined as part of this implementation guide.

Conformance Expectations

IHE uses the normative words: SHALL, SHOULD, and MAY according to standards conventions.

Must Support

The use of mustSupport in StructureDefinition profiles equivalent to the IHE use of R2 as defined in Appendix Z.

mustSupport of true - only has a meaning on items that are minimal cardinality of zero (0), and applies only to the source actor populating the data. The source actor SHALL populate the elements marked with MustSupport, if the concept is supported by the actor, a value exists, and security and consent rules permit. The consuming actors SHOULD handle these elements being populated or being absent/empty. Note that sometimes mustSupport will appear on elements with a minimal cardinality greater than zero (0), this is due to inheritance from a less constrained profile.