Difference between revisions of "Rad Tech Minutes 2009.01.27-30"
Jump to navigation
Jump to search
Chrisdcarr (talk | contribs) (New page: ==Participants== ==Minutes== 1. HL7 2.5 Refactoring 2. Joint ITI/WG 26 DICOM Webservices Review and Discussion * Radiology presented an update on its current relevant activities and i...) |
Chrisdcarr (talk | contribs) |
||
Line 18: | Line 18: | ||
:* Moving Radiology to shared model of ITI XDS for Web services | :* Moving Radiology to shared model of ITI XDS for Web services | ||
− | ::* | + | ::* Radiology should replace DICOM/Wado transport mechanisms with Web Services image retrieve transaction as compatible as possible with document retrieve method in XDS.b |
+ | :::* DICOM WG27 will help with specification of those transactions; ITI needs to coordinate with DWG27 to review divergences between the transactions defined for radiology and the general XDS retrieve model (retrieve document set) | ||
+ | :::* Need to consider responsiveness needs of the use case (synch/asynch; pipeline/non-pipeline queries and responses) | ||
+ | :::* DICOM WG27 need to review "Appendix V" being developed by ITI to make sure that the Web services profiled "fit" imaging model; perform "gap" analysis and provide feedback to ITI | ||
+ | :::* Same model likely to be used for inter- and intraenterprise access | ||
+ | ::::* Intra model has higher performance requirements | ||
+ | ::::* Intra model has more precise query requirements | ||
+ | |||
::* Can Radiology simplify the "three-layer" model of XDS-I: registry/repository (with manifest only)/image source by enabling storage of images themselves in the repository layer | ::* Can Radiology simplify the "three-layer" model of XDS-I: registry/repository (with manifest only)/image source by enabling storage of images themselves in the repository layer | ||
− | :::* Images need to be | + | ::* Need new queries based on Web services (using their query engine) to address specific issues of discovering and retrieving imaging studies: DICOM WG 20 is working on new query standards |
+ | :::* Images need to be indexed (via manifest) so that large studies don't appear as multiple query entries | ||
+ | :::* Manifest provides useful information about | ||
+ | :::* Currently not all general query keys are included in the radiology manifest to fit into optimized XDS.b model | ||
+ | ::* Point-to-point push of images/reports | ||
+ | ::* Notification | ||
+ | ::* Security mechanisms: role-based access control and authentication | ||
+ | ::* Updates and image management functions | ||
::* Expanding beyond the Affinity Domain model | ::* Expanding beyond the Affinity Domain model |
Revision as of 12:34, 27 January 2009
Participants
Minutes
1. HL7 2.5 Refactoring
2. Joint ITI/WG 26 DICOM Webservices Review and Discussion
- Radiology presented an update on its current relevant activities and its use cases for image sharing
- Currently revising XDS-I profile to use XDS.b only
- Tracking progress of supplemental profiles in ITI needed to support Web services model--such as XUA for role-based access control--but not currently confident that these solutions are ready for implementation
- Radiology Use Cases for Image Sharing
- Access to prior images and reports
- Access to diagnostic images and reports for referring physicians
- Point-to-point transfer of images and reports from site to site or from a site to an outside provider of longitudinal patient record, such as a Personal Health Record system vendor
- Remote reading model employed frequently requires access by radiologist to multiple image sources
- Moving Radiology to shared model of ITI XDS for Web services
- Radiology should replace DICOM/Wado transport mechanisms with Web Services image retrieve transaction as compatible as possible with document retrieve method in XDS.b
- DICOM WG27 will help with specification of those transactions; ITI needs to coordinate with DWG27 to review divergences between the transactions defined for radiology and the general XDS retrieve model (retrieve document set)
- Need to consider responsiveness needs of the use case (synch/asynch; pipeline/non-pipeline queries and responses)
- DICOM WG27 need to review "Appendix V" being developed by ITI to make sure that the Web services profiled "fit" imaging model; perform "gap" analysis and provide feedback to ITI
- Same model likely to be used for inter- and intraenterprise access
- Intra model has higher performance requirements
- Intra model has more precise query requirements
- Can Radiology simplify the "three-layer" model of XDS-I: registry/repository (with manifest only)/image source by enabling storage of images themselves in the repository layer
- Need new queries based on Web services (using their query engine) to address specific issues of discovering and retrieving imaging studies: DICOM WG 20 is working on new query standards
- Images need to be indexed (via manifest) so that large studies don't appear as multiple query entries
- Manifest provides useful information about
- Currently not all general query keys are included in the radiology manifest to fit into optimized XDS.b model
- Point-to-point push of images/reports
- Notification
- Security mechanisms: role-based access control and authentication
- Updates and image management functions
- Expanding beyond the Affinity Domain model