Integrated Reporting Applications
1.0.0 - Trial-Implementation International flag

This page is part of the Integrated Reporting Applications (v1.0.0: Publication) based on FHIR v5.0.0. This is the current published version. For a full list of available versions, see the Directory of published versions

Integrated Reporting Applications (IRA)

Official URL: Version: 1.0.0
Active as of 2023-10-04 Computable Name: IHE_RAD_IRA

The Integrated Reporting Applications (IRA) profile helps applications that are used together during reporting (e.g., image display, report creator, clinical applications, AI tools, etc.) to share information using a standard called FHIRcast. Each application can share what it is doing and the data it is creating, referred to as Context and Content, respectively. Other applications are notified so they can then intelligently synchronize their behavior or use the new data.

IMPORTANT: IRA is NOT yet recommended for production use.

Profiles released for Trial Implementation by IHE Radiology typically ARE expected to be stable enough for production use; however, this release of IRA is intended for experimental implementation and feedback.

IRA uses FHIR R5 for the resources used in FHIRcast events.

IRA uses FHIRcast 3.0.0 which is currently under development.

Experimental implementation feedback may result in backward incompatible changes to the profile.

Links to FHIRcast throughout this profile will be updated to the final version when the official version is published.

Significant Changes, Open and Closed Issues

Organization of This Guide

This guide is organized into the following sections:

  1. Volume 1: Profiles
    1. Introduction
    2. Actors and Transactions
    3. Actor Options
    4. Actor Required Groupings
    5. Overview
    6. Security Considerations
    7. Cross Profile Considerations
  2. Volume 2: Transaction Detail
    1. Subscribe to Reporting Session [RAD-146]
    2. Connect to Notification Channel [RAD-147]
    3. Open Report Context [RAD-148]
    4. Close Report Context [RAD-149]
    5. Update Report Content [RAD-150]
    6. Select Report Content [RAD-151]
    7. Unsubscribe Session [RAD-152]
    8. Get Current Context [RAD-153]
    9. Distribute Context Event [RAD-154]
    10. Generate SyncError Event [RAD-155]
    11. Notify Error [RAD-156]
  3. Examples

  4. Other

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 is 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.