Difference between revisions of "Rad Tech Minutes 2009.06.10"

From IHE Wiki
Jump to navigation Jump to search
(New page: ==Attendees== ==Minutes== * Resolve final comments on the 2009 supplements and vote to approve for publication :* [ftp://iheyr2:interop@ftp.ihe.net//Radiology/iheyr11-2009/Tech_Cmte/TF...)
 
Line 8: Line 8:
 
:* [ftp://iheyr2:interop@ftp.ihe.net//Radiology/iheyr11-2009/Tech_Cmte/TF_Supplement_Development/Draft_Supplements/IHE_Basic_Image_Review_Supplement/IHE-RAD_TF_Suppl_Basic_Image_Review_2009-06-10_DAC.doc.zip Basic Image Review]
 
:* [ftp://iheyr2:interop@ftp.ihe.net//Radiology/iheyr11-2009/Tech_Cmte/TF_Supplement_Development/Draft_Supplements/IHE_Basic_Image_Review_Supplement/IHE-RAD_TF_Suppl_Basic_Image_Review_2009-06-10_DAC.doc.zip Basic Image Review]
 
:* [ftp://iheyr2:interop@ftp.ihe.net//Radiology/iheyr11-2009/Tech_Cmte/TF_Supplement_Development/Draft_Supplements/IHE_PDI_Extensions_Supplement/IHE-RAD_TF_Suppl_PDI_Extensions_2009-06-09b_DAC.doc.zip Portable Data for Imaging Extensions]
 
:* [ftp://iheyr2:interop@ftp.ihe.net//Radiology/iheyr11-2009/Tech_Cmte/TF_Supplement_Development/Draft_Supplements/IHE_PDI_Extensions_Supplement/IHE-RAD_TF_Suppl_PDI_Extensions_2009-06-09b_DAC.doc.zip Portable Data for Imaging Extensions]
:* Enhanced MR Diffusion Imaging
+
:* [ftp://ftp.ihe.net/Radiology/iheyr11-2009/Tech_Cmte/TF_Supplement_Development/Draft_Supplements/Enhanced_DICOM_objects_Supplement/IHE-RAD_TF_Suppl_DIFF_2009-05-14.doc Enhanced MR Diffusion Imaging]
:* Enhanced CT/MR Perfusion Imaging
+
:* [ftp://ftp.ihe.net/Radiology/iheyr11-2009/Tech_Cmte/TF_Supplement_Development/Draft_Supplements/Enhanced_DICOM_objects_Supplement/IHE-RAD_TF_Suppl_PERF_2009-05-14.doc Enhanced CT/MR Perfusion Imaging]
:* Cross-enterprise Document Sharing for Imaging using XDS.b (XDS-I.b)
+
:* [ftp://iheyr2:interop@ftp.ihe.net/Radiology/iheyr11-2009/Tech_Cmte/TF_Supplement_Development/Draft_Supplements/XDS-I_using_XDS.b/IHE-RAD_TF_Suppl_XDS-I.b_TI_20090609.zip Cross-enterprise Document Sharing for Imaging using XDS.b (XDS-I.b)]
 
:** Comments received that warrant Committee discussion:
 
:** Comments received that warrant Committee discussion:
 
:# Sec 18.6, line 300 – We say that the ATNA Encryption option is required for all Secure Nodes/Apps grouped with an XDS-I.b actor.  That means DICOM transactions between the Img Doc Source and Img Doc Consumer must be encrypted.  However, in ITI TF-2: 3.19.6.3.1, it says “IHE permits DICOM and HL7 connections to use encryption none because these transactions are often internal….”.    Is it our intent for XDS-I.b to have stricter rules for DICOM transactions than ATNA?  If so, then the "hyperlink to images from reports" discussion in section 4.68.4.1.2.2 should remind implementers of the (implied) requirements due to TLS and the ATNA Encryption option.
 
:# Sec 18.6, line 300 – We say that the ATNA Encryption option is required for all Secure Nodes/Apps grouped with an XDS-I.b actor.  That means DICOM transactions between the Img Doc Source and Img Doc Consumer must be encrypted.  However, in ITI TF-2: 3.19.6.3.1, it says “IHE permits DICOM and HL7 connections to use encryption none because these transactions are often internal….”.    Is it our intent for XDS-I.b to have stricter rules for DICOM transactions than ATNA?  If so, then the "hyperlink to images from reports" discussion in section 4.68.4.1.2.2 should remind implementers of the (implied) requirements due to TLS and the ATNA Encryption option.

Revision as of 10:02, 10 June 2009

Attendees

Minutes

  • Resolve final comments on the 2009 supplements and vote to approve for publication
  1. Sec 18.6, line 300 – We say that the ATNA Encryption option is required for all Secure Nodes/Apps grouped with an XDS-I.b actor. That means DICOM transactions between the Img Doc Source and Img Doc Consumer must be encrypted. However, in ITI TF-2: 3.19.6.3.1, it says “IHE permits DICOM and HL7 connections to use encryption none because these transactions are often internal….”. Is it our intent for XDS-I.b to have stricter rules for DICOM transactions than ATNA? If so, then the "hyperlink to images from reports" discussion in section 4.68.4.1.2.2 should remind implementers of the (implied) requirements due to TLS and the ATNA Encryption option.
  2. ITI CP-142 (currently out for ballot) is going to split ITI TF-2 into two documents for the 2009 Final Text version (It’s getting too big). It is going to be split into Volume 2a and Volume 2b. All of the XDS.b transactions are going to land in 2b, so your volume references will need updating in this version (I think). And, volume 2 appendices are being moved to their own volume called to 2x. So now we will have, for example, ITI TF-2x: Appendix V – Web Services for IHE Transaction (in line 895 & 898 of your doc).
  • Publication Process
  • Other Tech Cmte Business
  • Next Meeting/Tcon

Radiology Technical Committee