Rad Plan Future Agenda Topics: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
Pseifert (talk | contribs)
Kevino (talk | contribs)
 
(22 intermediate revisions by 3 users not shown)
Line 1: Line 1:
==Near Term Needs==
Feel free to add proposed agenda items here.


* CoChair Election
* Radiology Domain Application to IHE
* Prepare Profile Summary Pages for 1 or 2 profiles


=="Parking Lot"==
== Urgent: For Next Meeting ==
Review these from time to time for activation.
 
# Consider if/ when (and how) to update XDS-I to leverage "XDS.b technology".
''Try to indicate why it's urgent''
:* This question was raised in the past (shortly after the TI publication of XDS.b by ITI), and at the time the Committee's position was: "let's wait and see how stable the XDS.b specification is before doing anything."
 
:* The following feedback was solicited and recently received from Lynn Felhofer (IHE Project Manager - MIR) on the question of XDS.b stability:
* Engage with nhindirect.org
:*: ''We had widespread adoption of XDS.b at Chicago (17 Consumers, 5 Registries, 7 Repositories, 14 Sources); also for Oxford (13 Consumers, 14 Registries, 17 Repositories, 12 Sources).''
** They are looking for near-term practical steps forward for the U.S. NHIN
:*:<br/>
** A number of IHE/DICOM solutions fit the bill.
:*:''In Chicago, the vast majority of systems tested successfully.  The biggest struggle we had in the fall was that the NIST tools were being developed in parallel with vendors doing their implementation. This is because ITI finishes their specs in Aug, leaving no time for advanced tool development. So, all of the implementors learned together, and Bill released updates to the toolkit as vendors found problems.  If you subscribe to the XDS implementors google group, you witnessed this churn. That has largely subsided now, and I think the tools are pretty stable.''
** We should get them on radar early.
:*:<br/>
 
:*:''The other caveat is that we really just tested the 'simple case' for XDS.b this year (doc submit/retrieve).  Features like Folder Management, and Document Lifecycle (append, replace) aren't tested in the tools and were made optional connectathon tests for this year.  Next year they will be required.''
== Near Term: For Upcoming Meeting ==
:*:<br/>
 
:*:''Overall, XDS.b testing went better than I anticipated it would when the profile was finished back in August.  My personal opinion would be the profile is solid enough to consider it as a base for XDS-I. This fall's experience did result in several CPs against XDS.b;  the TF documentation will remain a bit of a challenge for implementors to assimilate until those CPs are incorporated into the profile.  Steve and I tried to address the documentation problem a bit by compiling a page that points to all of the pieces of documentation needed for XDS.b (and other profiles):'' http://ihewiki.wustl.edu/wiki/index.php/Summary_Of_IHE_Technical_Requirements
''Describe near term topic''
 
* Radiology entries in IHE Profile Catalog
** The Catalog is intended to be a go-to place for users searching for relevant profiles
** It also provides basic "one-pager" marketing materials for use at trade shows, conferences, etc.
** Half a dozen Rad profiles still need writeups
 
 
* XDS.b Document Management and Privacy
** Review the XDS.b options on the Document Consumer and Document Source
*** They address use cases that are analagous for Imaging Reports and Images
** Need to analyze RAD use cases and consider a work item to address them
*** Possibly by adopting/tweaking the XDS.b options (e.g., XDS.b named options for the Document Source)
** This overlaps heavily with the issues being considered by IHE Canada/Infoway
*** Try to involve David Heaney, Peter Bak, etc.
 
 
* Post-Processing and Reporting Workflow
** Review current status
** Discuss appropriate plans
** Consider using the [[Evaluation of Published Profiles]] Process to organize discussion
 
== "Parking Lot": For Someday ==
''Review these from time to time for activation''
 
* Targetted Webinar Invites
** Consider identifying profiles we want to specifically promote (e.g. new TI)
** Assemble a mailing list of likely implementers
** Send a targetted email identifying the profile and a bit of a business case and provide info to attend the webinar for the full story.
 
* NEMA DICOM Library
** Vendors who create objects have not been populating the library
** One reason may be lack of a carrot
** IHE has played with the idea of making Products (vs Prototypes) a more prominant part of Connectathon
** Combining these, perhaps vendors could sign up to do Product Testing vs Prototype Testing (similar to the current supportive vs comprehensive)
** One requirement for passing the Product level could be to post objects to the NEMA Library
 
* Marketing Review
** Review coverage at relevant conferences and supplement as necessary
*** RSNA
*** SIIM
*** AHRA
*** Europe?
*** Asia?
*** More?
 
* Consider refactoring XDS-I.b into:
** An XDS Content profile - for the sharing of the DICOM manifest and the PDF or CDA-wrapped reports
** A "workflow-type" Profile that orchestrates the sharing of the DICOM Manifest with the retrieval of the DICOM objects referenced by the manifest.
** Also consider if/ how XDS-SD (XDS for Scanned Documents) can be used in place of (or in conjunction with) the current specification for sharing reports.

Latest revision as of 18:18, 28 March 2010

Feel free to add proposed agenda items here.


Urgent: For Next Meeting

Try to indicate why it's urgent

  • Engage with nhindirect.org
    • They are looking for near-term practical steps forward for the U.S. NHIN
    • A number of IHE/DICOM solutions fit the bill.
    • We should get them on radar early.

Near Term: For Upcoming Meeting

Describe near term topic

  • Radiology entries in IHE Profile Catalog
    • The Catalog is intended to be a go-to place for users searching for relevant profiles
    • It also provides basic "one-pager" marketing materials for use at trade shows, conferences, etc.
    • Half a dozen Rad profiles still need writeups


  • XDS.b Document Management and Privacy
    • Review the XDS.b options on the Document Consumer and Document Source
      • They address use cases that are analagous for Imaging Reports and Images
    • Need to analyze RAD use cases and consider a work item to address them
      • Possibly by adopting/tweaking the XDS.b options (e.g., XDS.b named options for the Document Source)
    • This overlaps heavily with the issues being considered by IHE Canada/Infoway
      • Try to involve David Heaney, Peter Bak, etc.


  • Post-Processing and Reporting Workflow

"Parking Lot": For Someday

Review these from time to time for activation

  • Targetted Webinar Invites
    • Consider identifying profiles we want to specifically promote (e.g. new TI)
    • Assemble a mailing list of likely implementers
    • Send a targetted email identifying the profile and a bit of a business case and provide info to attend the webinar for the full story.
  • NEMA DICOM Library
    • Vendors who create objects have not been populating the library
    • One reason may be lack of a carrot
    • IHE has played with the idea of making Products (vs Prototypes) a more prominant part of Connectathon
    • Combining these, perhaps vendors could sign up to do Product Testing vs Prototype Testing (similar to the current supportive vs comprehensive)
    • One requirement for passing the Product level could be to post objects to the NEMA Library
  • Marketing Review
    • Review coverage at relevant conferences and supplement as necessary
      • RSNA
      • SIIM
      • AHRA
      • Europe?
      • Asia?
      • More?
  • Consider refactoring XDS-I.b into:
    • An XDS Content profile - for the sharing of the DICOM manifest and the PDF or CDA-wrapped reports
    • A "workflow-type" Profile that orchestrates the sharing of the DICOM Manifest with the retrieval of the DICOM objects referenced by the manifest.
    • Also consider if/ how XDS-SD (XDS for Scanned Documents) can be used in place of (or in conjunction with) the current specification for sharing reports.