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

Significant Changes and Issues

Significant Changes

Significant Changes from Previous Revision

None, this is the first published revision.

Issues

Submit an Issue

IHE welcomes New Issues from the GitHub community. For those without GitHub access, issues can be submitted to the ITI Public Comment form.

As issues are submitted they will be managed on the ITI.Finance GitHub Issues, where discussion and workarounds can be found. These issues, when critical, will be processed using the normal IHE Change Proposal management and balloting. It is important to note that as soon as a Change Proposal is approved, it carries the same weight as a published Implementation Guide (i.e., it is testable at an IHE Connectathon from the time it is approved, even if it will not be integrated until several months later).

Open Issues

  • FAIS-001: Should there be a required grouping with ATNA actors or other security profiles?
  • FAIS-002: Should the operation transactions allow accepting a Bundle of multiple requests or only allow a single request (which may be a bundle of associated resources)?
  • FAIS-003: Should the cancel claim and re-process claim transactions use a Task resource?
  • FAIS-004: Should the Beneficiary Manager and Claims Manager be combined into one actor?
  • FAIS-005: Should there be a transaction to update a claim that is in progress? Currently the way to do this would be to cancel the claim and submit a new one. Should the re-process transaction be used for updates instead of only when the claim has been denied?
  • FAIS-006: Are there any experiences with these workflows that may require any changes to these transactions similar to open issue FAIS-005?
  • FAIS-007: Some countries required sensitive data to be sent in separate transactions to minimize risk, for example, personal data with health care or financial data. Does this need to be specifically addressed in this profile?

Closed Issues

None