Difference between revisions of "Rad Tech Minutes 08.07.15"
Jump to navigation
Jump to search
Chrisdcarr (talk | contribs) |
Chrisdcarr (talk | contribs) |
||
Line 14: | Line 14: | ||
'''Scheduled Worflow II:''' ''Reviewed the open issues in [ftp://ftp.ihe.net/Radiology/iheyr10-2008/Technical_Cmte/2008-07-15_tc_tcon/ihe_supp_SWFII_vol1_2008-06-03_draft__commentsToTC_CDi.doc Chris Lindop's draft document with comments from Christoph Dickmann] to expand discussion in preparation for creating revised version of profile.'' | '''Scheduled Worflow II:''' ''Reviewed the open issues in [ftp://ftp.ihe.net/Radiology/iheyr10-2008/Technical_Cmte/2008-07-15_tc_tcon/ihe_supp_SWFII_vol1_2008-06-03_draft__commentsToTC_CDi.doc Chris Lindop's draft document with comments from Christoph Dickmann] to expand discussion in preparation for creating revised version of profile.'' | ||
− | * Open Issues: | + | * '''Open Issues:''' |
'''1. Image Manager/Image Archive Actor Grouping''' | '''1. Image Manager/Image Archive Actor Grouping''' | ||
* The question is whether to modify the way Image Manager and Image Archive are defined to either add transactions between them or possibly remove Image Archive from the profile | * The question is whether to modify the way Image Manager and Image Archive are defined to either add transactions between them or possibly remove Image Archive from the profile | ||
− | * Use Cases for Defining Behaviors Between Image Manager and Image Archive: | + | ** Transactions between Image Manager and Image Archive might be non-DICOM (eg, HL7 or SQL) |
+ | * '''Use Cases for Defining Behaviors Between Image Manager and Image Archive:''' | ||
::1. Enable "plug and play" interoperability so sites could easily add or replace archives | ::1. Enable "plug and play" interoperability so sites could easily add or replace archives | ||
+ | ::::* | ||
::2. Allow replacement of Image Manager without migration/replacement of Archive | ::2. Allow replacement of Image Manager without migration/replacement of Archive | ||
::3. General purpose archive that could store reports and other medical documents as well as images | ::3. General purpose archive that could store reports and other medical documents as well as images | ||
− | ::4. Federation of Archives | + | ::4. Federation of Archives: Does this use case belong in a workflow profile? Federation of Image Managers is probably not feasible. |
Revision as of 17:09, 15 July 2008
Attendees
- Ruth Berge, GE
- Christoph Dickmann, Siemens
- Dick Donker, Philips
- Dave Heaney, McKesson
- Mike Henderson, Eastern Informatics
- Chris Lindop, GE
- Paul Seifert, Agfa
- Chris Carr, RSNA
Minutes
Scheduled Worflow II: Reviewed the open issues in Chris Lindop's draft document with comments from Christoph Dickmann to expand discussion in preparation for creating revised version of profile.
- Open Issues:
1. Image Manager/Image Archive Actor Grouping
- The question is whether to modify the way Image Manager and Image Archive are defined to either add transactions between them or possibly remove Image Archive from the profile
- Transactions between Image Manager and Image Archive might be non-DICOM (eg, HL7 or SQL)
- Use Cases for Defining Behaviors Between Image Manager and Image Archive:
- 1. Enable "plug and play" interoperability so sites could easily add or replace archives
- 2. Allow replacement of Image Manager without migration/replacement of Archive
- 3. General purpose archive that could store reports and other medical documents as well as images
- 4. Federation of Archives: Does this use case belong in a workflow profile? Federation of Image Managers is probably not feasible.
- 1. Enable "plug and play" interoperability so sites could easily add or replace archives