Difference between revisions of "IHERO ISO Documentation"

From IHE Wiki
Jump to navigation Jump to search
 
(13 intermediate revisions by the same user not shown)
Line 1: Line 1:
The following link describes the required ISO Documentation as specified by the 22-Jan-2008 Domain Coordination Committee teleconference http://wiki.ihe.net/index.php?title=IHE_Domain_Coordination_Committee_2008-01-22_Teleconference_Minutes#Website_and_Public_Information.  The section relevent to the IHE Profile Webpage for each Profile follows:
+
Each IHE Profile Webpage to be submitted to the ISO should include:
 
# One page summary of profile with links to the specification
 
# One page summary of profile with links to the specification
 
# '''''Briefly''''' explains the purpose, function, actors, transactions, etc of the profile.
 
# '''''Briefly''''' explains the purpose, function, actors, transactions, etc of the profile.
# [[Profile_Template|Template]] for a profile page: http://wiki.ihe.net/index.php?title=Profile_Template (update is pending)
 
 
# [[Medical_Summaries|Example]] of a profile page: http://wiki.ihe.net/index.php?title=Medical_Summaries (not perfect, but the best example so far)
 
# [[Medical_Summaries|Example]] of a profile page: http://wiki.ihe.net/index.php?title=Medical_Summaries (not perfect, but the best example so far)
 
# Link to the offical copies of the Technical Framework
 
# Link to the offical copies of the Technical Framework
 
# List of the volumes & sections & Appendices of the TF where the profile is defined
 
# List of the volumes & sections & Appendices of the TF where the profile is defined
# Each Domain Planning Committee responsible for maintaining these pages on the Wiki
 
# Sponsor responsible for establishing Profile Webpages and periodically migrating the Wiki list to the Web.
 
# Since it's a fair bit of work, the Domain Page links on the Website may be to the Profile Pages on the Wiki at the initial deadline and updated later.
 
 
<br>
 
<br>
There are 5 content pieces summarized in the following table along with who volunteered to provide the content.  A recently updated template for the ISO Profile Pages, http://wiki.ihe.net/index.php?title=Profile_Template, has been copied and pasted into the 3 profile pages below.  An recently updated example of a filled out profile is shown at
+
The IHE Radiation Oncology Technical Committee has published the following draft Technical Framework for Trial Implementation. The PDF document defines the RT Objects Integration Profile (e.g. Simple Planning).
http://wiki.ihe.net/index.php?title=Scheduled_Workflow_Profile.  Please click one of the profile links in the table to see the profile and edit the content that you volunteered to provide. <br>
 
<br>
 
The IHE Radiation Oncology Technical Committee has published this draft Technical Framework for Trial Implementation. The PDF document defines the RT Objects Integration Profile (e.g. Simple Planning).
 
 
 
* [http://www.ihe.net/Technical_Framework/upload/IHE_RO_TF_v1.pdf Vol. 1: Overview and Vol. 2: Transactions]
 
 
 
Section 3.1, and Appendix A and B of Volume 1 of the technical framework contain the technical details (very detailed) of what resulted from the Use Case.  Volume 2 of the technical frame contains the details on what each transaction for the profile is.  E.g. transaction RO-1 is the retrieval from the archive of a single CT image series.  Each transaction is completely defined.  Stringing a number of transactions together is how a useful clinical function happens.  The intermediate step of having a profile which describes this 'useful clinical function' is missing, I think because a planning committee wasn't there to do their job.  So, if you can 'reverse engineer' the profile from the technical framework (looking at the transactions and actors) and create a understandable one page summary, that would be great.  Creating an understandable list of the actors and transactions would be a good start.  Then stringing together the transactions to perform some useful clinical function is the next step.<br>
 
  
The following year, IHE Radiation Oncology Technical Committee published the following supplements of the IHE-RO Technical Framework v. 2.0 for Trial ImplementationThe following PDF documents are proposed modifications to the technical framework to support the proposed profiles (e.g. image registration or work flow).
+
* [ftp://ftp.ihe.net/RadiationOncology/IHE_2007/IHE_RO_Volumes1and2_2007_v1.6_TI.pdf IHE-RO Technical Frameworks 1.6]
 +
* [http://www.ihe.net/Technical_Framework/upload/IHE_RO_TF_v1.pdf Vol. 1: Overview and Vol. 2: Transactions] Section 3.1, and Appendix A and B of Volume 1 of the technical framework contain the technical details (very detailed) of what resulted from the Use Case.  Volume 2 of the technical frame contains the details on what each transaction for the profile is.  E.g. transaction RO-1 is the retrieval from the archive of a single CT image series.  Each transaction is completely defined.  Stringing a number of transactions together is how a useful clinical function happens. <br>
  
* [http://www.ihe.net/Technical_Framework/upload/IHE_RO_TF_Supplement_Image_Registration_PublicComment_2007_08_20.pdf Image Registration]
+
The following year, the IHE Radiation Oncology Technical Committee published the following supplements of the IHE-RO Technical Framework v. 2.0 for Trial Implementation. The following PDF documents are proposed modifications to the technical framework to support the proposed profiles (e.g. image registration or work flow).
* [http://www.ihe.net/Technical_Framework/upload/IHE_RO_TF_Supplement_Treatment_Delivery_Workflow_PublicComment_2007_08_20.pdf Managed Delivery Workflow]
 
  
Chapter 4 and Appendix A&B of the Technical Framework V2 addendum for Image Registration contains information relevant to the Image Registration Profile.<br>
+
* [http://www.ihe.net/Technical_Framework/upload/IHE_RO_TF_Supplement_Image_Registration_PublicComment_2007_08_20.pdf Image Registration]  Chapter 4 and Appendix A&B of the Technical Framework V2 addendum for Image Registration contains information relevant to the Image Registration Profile.
 +
* [http://www.ihe.net/Technical_Framework/upload/IHE_RO_TF_Supplement_Treatment_Delivery_Workflow_PublicComment_2007_08_20.pdf Managed Delivery Workflow]  Chapter 3&4 and Appendix A&B of the Technical Framework V2 addendum for Work Flow contains information relevant to the Work Flow Profile.
  
Chapter 3&4 and Appendix A&B of the Technical Framework V2 addendum for Work Flow contains information relevant to the Work Flow Profile. <br>
 
As with the Simple Planning Profile, I think the Profile needs to be 'reverse engineered' from the Technical Framework documentation.<br>
 
 
<br>
 
<br>
Drafts of the IHE-RO Domain Document and Webpage are available for comments.  If you have reviewed any of the documents, please update the appropriate cell in the following table.
+
Drafts of all wiki pages are available for comments.  If you have reviewed any of the documents, please update the appropriate cell in the following table.
  
 
{| style="width:70%" border="1" cellpadding="3"
 
{| style="width:70%" border="1" cellpadding="3"
Line 45: Line 33:
 
|-
 
|-
 
| [[Normal Treatment Planning-Simple |  Normal Treatment Planning-Simple (NTPL-S)]]
 
| [[Normal Treatment Planning-Simple |  Normal Treatment Planning-Simple (NTPL-S)]]
| Charles, May, Mika
+
| Charles, Colin, May, Mika
|
 
|-
 
| [[IHERO_ISO_Multimodality_registration_profile | IHE-RO ISO_Multimodality Registration Profile (MMR-RO)]]
 
| Colin, Sha, Shankar, Mika
 
 
|
 
|
 
|-
 
|-
 
| [[Multimodality Registration for Radiation Oncology | Multimodality Registration for Radiation Oncology (MMR-RO)]]
 
| [[Multimodality Registration for Radiation Oncology | Multimodality Registration for Radiation Oncology (MMR-RO)]]
 
| Colin, Sha, Shankar, Mika
 
| Colin, Sha, Shankar, Mika
|
 
|-
 
| [[IHERO_ISO_Treatment_workflow_profile | IHE-RO ISO Treatment Workflow Profile (TRWF)]]
 
| Mika, Mike, Prabhahar
 
 
|
 
|
 
|-
 
|-
 
| [[RT Treatment Workflow | RT Treatment Workflow (TRWF)]]
 
| [[RT Treatment Workflow | RT Treatment Workflow (TRWF)]]
| Mika, Mike, Prabhahar
+
| Colin, Mika, Mike, Prabhahar
 
|
 
|
 
|}
 
|}
In order to meet the due date for the final documents for submission to ISO is April 18, 2008, we need sto meet the following timeline:
+
In order to meet the due date for the final documents for submission to ISO is April 18, 2008, we need to meet the following timelines:
* Tuesday April 8solicit comments from the rest of the group working on the other profile pages along with Bruce, Stewart etc.
+
* Monday April 7Ask for comments from IHE-RO volunteer profile editors (and Bruce, Stuart, etc.)
* Monday April 14: ask from comments from IHE (Chris, Kevin, ??)
+
* Friday April 11: Finalize IHE-RO draft
* Thursday April 17: ready for submission to ISO on Friday April 18.
+
* Monday April 14: Ask for comments from IHE (Chris, Kevin, ??)
 +
* Thursday April 17: Final version of IHE-RO ISO documentation
 +
* Friday April 17: IHE submits documentation to ISO

Latest revision as of 09:58, 6 April 2008

Each IHE Profile Webpage to be submitted to the ISO should include:

  1. One page summary of profile with links to the specification
  2. Briefly explains the purpose, function, actors, transactions, etc of the profile.
  3. Example of a profile page: http://wiki.ihe.net/index.php?title=Medical_Summaries (not perfect, but the best example so far)
  4. Link to the offical copies of the Technical Framework
  5. List of the volumes & sections & Appendices of the TF where the profile is defined


The IHE Radiation Oncology Technical Committee has published the following draft Technical Framework for Trial Implementation. The PDF document defines the RT Objects Integration Profile (e.g. Simple Planning).

  • IHE-RO Technical Frameworks 1.6
  • Vol. 1: Overview and Vol. 2: Transactions Section 3.1, and Appendix A and B of Volume 1 of the technical framework contain the technical details (very detailed) of what resulted from the Use Case. Volume 2 of the technical frame contains the details on what each transaction for the profile is. E.g. transaction RO-1 is the retrieval from the archive of a single CT image series. Each transaction is completely defined. Stringing a number of transactions together is how a useful clinical function happens.

The following year, the IHE Radiation Oncology Technical Committee published the following supplements of the IHE-RO Technical Framework v. 2.0 for Trial Implementation. The following PDF documents are proposed modifications to the technical framework to support the proposed profiles (e.g. image registration or work flow).

  • Image Registration Chapter 4 and Appendix A&B of the Technical Framework V2 addendum for Image Registration contains information relevant to the Image Registration Profile.
  • Managed Delivery Workflow Chapter 3&4 and Appendix A&B of the Technical Framework V2 addendum for Work Flow contains information relevant to the Work Flow Profile.


Drafts of all wiki pages are available for comments. If you have reviewed any of the documents, please update the appropriate cell in the following table.

Document Who prepares first draft Reviewed by
IHE-RO ISO Domain Document Colin
IHE-RO ISO Domain Webpage Colin
Normal Treatment Planning-Simple (NTPL-S) Charles, Colin, May, Mika
Multimodality Registration for Radiation Oncology (MMR-RO) Colin, Sha, Shankar, Mika
RT Treatment Workflow (TRWF) Colin, Mika, Mike, Prabhahar

In order to meet the due date for the final documents for submission to ISO is April 18, 2008, we need to meet the following timelines:

  • Monday April 7: Ask for comments from IHE-RO volunteer profile editors (and Bruce, Stuart, etc.)
  • Friday April 11: Finalize IHE-RO draft
  • Monday April 14: Ask for comments from IHE (Chris, Kevin, ??)
  • Thursday April 17: Final version of IHE-RO ISO documentation
  • Friday April 17: IHE submits documentation to ISO