Current development

The IHE ITI domain has selected the following work items for the 2019 cycle.

The item proposals are available on the ftp site

Maintenance of ITI Profiles Published in 2018 and earlier

In Fall 2018, the IT Infrastructure Domain counts 25 Final Text Profiles, 19 Trial Implementation Profiles, and 7 additional Trial Implementation Supplements that modify existing FT profiles. More new TI supplements are published every year than are moved to Final Text. This growing list of documents has to be maintained with a yearly significant list of change proposals by a finite number of ITI Technical committee members.

The 2018-19 cycle (on Sept.7) begins with 101 assigned CPs, 7 completed CPs in 2 CP ballots, and 9 completed CPs awaiting a future ballot.33 CPs are currently assigned to someone who is no longer active on the ITI Technical Committee. Key expertise has been lost due to contributors who cannot be involved anymore in ITI development (for example, the work on CPs enabling XDS-MU to go to Final Text).

The staggered publication is also an important element to be considered. In scheduling republication of approx. 4 documents per quarter, rather than doing all republications once a year, the publication workload would be better managed.

This situation is becoming critical and the audience for this proposal knows the value of ITI Technical Framework documentation to the other IHE domains and to the healthcare IT community.

The ITI Planning and Technical Committees should explicitly identify maintenance as a work item to evaluate against other work item proposals for new profiles and set aside Technical Committee resources to improve quality in existing documentation.

Alignment of XDM/XDR with the DirectTrust implementation guide for representing Message Context

This work item proposal has two main aims:

• Analyzing the gaps between the current IHE XDR/XDM specifications and the Implementation Guide for Message Context developed by the DirectTrust community. This review effort will enable to identify and issue recommendations of merging, or (at least) converging possibilities between the two set of specifications.
• Applying the changes identified to the IHE XDR/XDM specifications while extending the perimeter of the uses cases covered to fully take in consideration the use of Direct Secure Messaging (DSM).

The work item suggests that this effort will optimize interoperability by reducing the number of implementation options.

Facilities and Hierarchies in FHIR

FHIR does not have a good definition for facilities and has recommended using both Organization and Location to define a facility. There is also no defined way to handle multiple hierarchies for facilities. Furthermore there is a need to be clear on what data is provided for a facility instead of solely a Location or Organization.

In order to avoid multiple solutions that would not be compatible, this proposal suggests the following approaches:

• A larger CP for mCSD can be issued in order to clearly define how facilities are defined by using Location and Organization together.
• A whitepaper profiling how this can be achieved in a standard way.
• Any other option.

Add RESTful capabilities to DSUB

This proposal is in line with the work already carried out for Mobile access to Health Documents (MHD) with XDS on FHIR, in searching and retrieving documents through RESTful capabilities. It consists of studying how to subscribe or unsubscribe, from a mobile application, to receive notifications when a clinical document has been created. This work will be done in adding restful capabilities to the Document Metadata Subscription profile (DSUB).

Add restfull feed to ATNA

This proposal is in line with the work already carried out for example for Mobile access to Health Documents (MHD) with XDS on FHIR, in searching and retrieving documents through RESTful capabilities. It consists of auditing the access to clinical documents from mobile applications implementing this kind of new profiles for mobile. This work could be achieved in using FHIR, which offers the ability to POST the AuditEvent resource that is suitable to manage the audit of an event.

See Also

• Return to ITI Planning Committee
• Return to IT Infrastructure domain page

--