Invoke Image Display Evaluation

Proposal

The Invoke Image Display profile has been nominated for advancement to Final Text. (Advocate: Andrei Leontiev) Per the Final Text Process, Items in blue text below warrant Committee discussion.

Technical Committee Checklist

• Are all significant CPs against the profile "closed"?

• No. CP-349 and CP-364 that are currently assigned, are raising significant shortcomings of the profile

• Are all significant CPs against the underlying standards "closed"?

• There are no IID related CPs in DICOM

• Have all significant comments been CP'd or rejected?

• CPs 349 and 364

• Have all open issues listed in the Supplement been closed?

• Yes

• Have all significant issues at Connectathon been dealt with?

• See the CPs mentioned above

• Gather feedback from implementers via a formal questionnaire to Connectathon participants

• See above

• Has the Connectathon Project Manager been queried and significant issues addressed?

• See above

Technical Committee Consensus

• It is proposed that the profile is not advanced to the Final Text until CPs 349 and 364 are finalized OR decision is made to apply Cps to the final text rather than the TI Supplement.

Planning Committee Checklist

• Has the profile been through a Connectathon in at least two regions?

• Yes

• Has the profile been successfully tested with all actors at least at one Connectathon?

• Yes

• Have different implementations of each actor in the profile been tested?

• Yes

• Have all the options been tested successfully at at least one Connectathon?

• Profile does not define any options
• Evaluation of options

• N/A

• Are there IHE-provided software testing tools to address all aspects of the profile?

• Have the standards underlying the profile been implemented? In similar use cases? In healthcare? In general IT?

• Yes, similar mechanisms using the HTTP-GET requests are currently used in actual implementations.

• (Do you have concrete reason to believe that this works robustly in the Real World) / (Are any products available for purchase that implement the profile?)

• The difference between Real World implementations from the definitions of the profile are only in the names of parameters, however, the existing implementations always provide mechanisms for user authentication that are NOT well addressed by the profile (see CP 364). This may be a significant impediment to actual implementation of the profile as written.

• Have all issues that may have been raised about the profile been resolved?

No

• Has there been sufficient interest in the profile to generate a one-page overview of the profile

• Yes, the profile overview page exists.