Difference between revisions of "Evaluation of Invoke Image Display"

From IHE Wiki
Jump to navigation Jump to search
(Created page with "Profile wiki page: Invoke Image Display Answers to the following checklist for IID ** Are all significant CPs against the profile "closed"? There is one outstanding CP (...")
 
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
Profile wiki page: [[Invoke Image Display]]
 
Profile wiki page: [[Invoke Image Display]]
 +
 +
== Technical Committee Evaluation (Preliminary answers) ==
  
 
Answers to the following checklist for IID
 
Answers to the following checklist for IID
−
** Are all significant CPs against the profile "closed"?
+
* Are all significant CPs against the profile "closed"?
 +
 
 +
There is one outstanding CP (CP-RAD-349) that suggests adding "close" and "logout" commands in the API. This CP might be related to security. Need to review.
  
−
There is one outstanding CP (CP-RAD-349) that suggests adding "close" and "logout" commands in the API
+
See [https://docs.google.com/spreadsheets/d/1TmSwnn4AIiXqFLc_AtzP0dNd9LUWnA-ZcCjBMKpLzp4/edit#gid=0 CP Tracking Spreadsheet]
  
−
** Are all significant CPs against the underlying standards "closed"?
+
* Are all significant CPs against the underlying standards "closed"?
  
 
Yes
 
Yes
  
−
** Have all significant comments been CP'd or rejected?
+
* Have all significant comments been CP'd or rejected?
  
−
Yes
+
Yes. Need to review the newly submitted CP from Marco.
 
   
 
   
−
** Have all open issues listed in the Supplement been closed?
+
* Have all open issues listed in the Supplement been closed?
  
 
Yes
 
Yes
  
−
** Have all significant issues at Connectathon been dealt with?  
+
* Have all significant issues at Connectathon been dealt with?  
  
 
Yes
 
Yes
  
−
*** Gather feedback from implementers via a [ftp://ftp.ihe.net/Connectathon/IHE%20Vendor%20Questionnaire%20V0.4.doc formal questionnaire to Connectathon participants]
+
* Gather feedback from implementers via a [ftp://ftp.ihe.net/Connectathon/IHE%20Vendor%20Questionnaire%20V0.4.doc formal questionnaire to Connectathon participants]
−
** Has the Connectathon Project Manager been queried and significant issues addressed?
+
 
 +
Informal feedback gathering only
 +
 
 +
* Has the Connectathon Project Manager been queried and significant issues addressed?
 +
 
 +
Yes. See Marco's CP.
 +
 
 +
* Debate checklist exceptions (failure of any of the above is cause for discussion)
 +
* Record checklist findings and debate conclusion
 +
 
 +
== Planning Committee Consensus (Preliminary answers) ==
 +
 
 +
* Has the profile been through a Connectathon in at least two regions?
  
 
Yes. Tested in Bochum 2016, NA 2016, NA 2015, Vienna 2014
 
Yes. Tested in Bochum 2016, NA 2016, NA 2015, Vienna 2014
  
 
[https://docs.google.com/spreadsheets/d/1d2A_iT-xvkvXhmpxH3CLNbDpWi6D36ebgH7VPMtZXKM/edit#gid=1702388284 Connectathon test results summary]
 
[https://docs.google.com/spreadsheets/d/1d2A_iT-xvkvXhmpxH3CLNbDpWi6D36ebgH7VPMtZXKM/edit#gid=1702388284 Connectathon test results summary]
 +
 +
* 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?
 +
 +
No option defined.
 +
 +
* Are there IHE-provided software testing tools to address all aspects of the profile?
 +
 +
The profile testing has been well covered by executing the URL to see if the viewer can be launched properly. No additional tooling required.
 +
 +
* Have the standards underlying the profile been implemented? In similar use cases? In healthcare? In general IT?
 +
 +
Yes. HTTP(S) URL is widely used between EMR and PACS to launch an image viewer.
 +
 +
* (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?)
 +
 +
Yes. URL is widely used between EMR and PACS in real world deployment.
 +
 +
* Have all issues that may have been raised about the profile been resolved?
 +
 +
Two outstanding CPs (CP-RAD-349 and one new submitted)
 +
 +
* Has there been sufficient interest in the profile to generate a one-page [[Profiles|overview of the profile]]
 +
 +
David has already created one [[Invoke Image Display]]
  
 
* Debate checklist exceptions (failure of any of the above is cause for discussion)
 
* Debate checklist exceptions (failure of any of the above is cause for discussion)
−
* Record checklist findings and debate conclusion
+
* Record checklist findings and conclusions of the debate in your meeting minutes

Latest revision as of 10:06, 4 May 2016

Profile wiki page: Invoke Image Display

Technical Committee Evaluation (Preliminary answers)

Answers to the following checklist for IID

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

There is one outstanding CP (CP-RAD-349) that suggests adding "close" and "logout" commands in the API. This CP might be related to security. Need to review.

See CP Tracking Spreadsheet

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

Yes

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

Yes. Need to review the newly submitted CP from Marco.

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

Yes

  • Have all significant issues at Connectathon been dealt with?

Yes

Informal feedback gathering only

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

Yes. See Marco's CP.

  • Debate checklist exceptions (failure of any of the above is cause for discussion)
  • Record checklist findings and debate conclusion

Planning Committee Consensus (Preliminary answers)

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

Yes. Tested in Bochum 2016, NA 2016, NA 2015, Vienna 2014

Connectathon test results summary

  • 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?

No option defined.

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

The profile testing has been well covered by executing the URL to see if the viewer can be launched properly. No additional tooling required.

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

Yes. HTTP(S) URL is widely used between EMR and PACS to launch an image viewer.

  • (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?)

Yes. URL is widely used between EMR and PACS in real world deployment.

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

Two outstanding CPs (CP-RAD-349 and one new submitted)

David has already created one Invoke Image Display

  • Debate checklist exceptions (failure of any of the above is cause for discussion)
  • Record checklist findings and conclusions of the debate in your meeting minutes
Retrieved from "http://wiki.ihe.net/index.php?title=Evaluation_of_Invoke_Image_Display&oldid=94438"