IHERO ISO Documentation: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
Cfield (talk | contribs)
editor
981 edits
New page: ===Website and Public Information=== # ISO Referencing Requirements for IHE Technical Frameworks ## ISO Domain Document for each Domain ### Simple one page summary to introduce and point t...
 
Cfield (talk | contribs)
editor
981 edits
No edit summary
 
(44 intermediate revisions by the same user not shown)
Line 1: Line 1:
===Website and Public Information===
Each IHE Profile Webpage to be submitted to the ISO should include:
# ISO Referencing Requirements for IHE Technical Frameworks
# One page summary of profile with links to the specification
## ISO Domain Document for each Domain
# '''''Briefly''''' explains the purpose, function, actors, transactions, etc of the profile.
### Simple one page summary to introduce and point to our work
# [[Medical_Summaries|Example]] of a profile page: http://wiki.ihe.net/index.php?title=Medical_Summaries (not perfect, but the best example so far)
### "10 lines" on scope/goal of domain
# Link to the offical copies of the Technical Framework
### "5-10 lines" listing Sponsor Organizations, Affiliate Organizations
# List of the volumes & sections & Appendices of the TF where the profile is defined
### ? Do they need Secretariat contact information ?
<br>
### Link to a stable domain Web page: www.ihe.net/domain_name/
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).
### Develop for each domain; (can borrow material from each Domain Application)
### Review periodically (every few years)
### Submit to ISO for publication. (Word document submitted by Charles?)
## IHE Domain Webpage for each Domain (www.ihe.net/domain_name/)
### Radiology page as example: http://www.ihe.net/Radiology/
### "1-2 paragraphs" Brief overview of scope of domain, ie, what clinical/operational/technical infrastructure areas it addresses, types of systems that would typically implement such profiles
### List of published Profiles - Name, Acronym & One-line Description for each Profile
### Each Profile Name in the list is a link to a Profile Webpage.
### Keep the Domain Description short enough that the top of the Profile List is visible when you first go to the Domain Webpage.
### Feel free to group your profiles if you have a lot.  Don't have to group.  Group names are not Normative, just helpful.
### Develop Profile List on the Wiki for each Domain http://wiki.ihe.net/index.php?title=Profiles
### Each Domain Planning Committee responsible for maintaining the list on the Wiki
### Review/Update list every year (as new Profiles are added in Trial Implementation or Final Text)
### Sponsor responsible for establishing Domain Webpage and periodically migrating the Wiki list to the Web.
Extracted from the 22-Jan-2008 Domain Coordination Committee teleconference is the following information:
## IHE Profile Webpage for each Profile
### One page summary of profile with links to the specification
### '''''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)
### Link to the offical copies of the Technical Framework
### 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.


* Most of the work will be in development of one-page profile summaries
* [ftp://ftp.ihe.net/RadiationOncology/IHE_2007/IHE_RO_Volumes1and2_2007_v1.6_TI.pdf IHE-RO Technical Frameworks 1.6]
*'''Action:''' Domain Sponsors will be requested to work with their Planning Committee Co-chairs to develop ISO Domain Document and IHE Domain Webpage for their domain.
* [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>
*'''Action:''' Kevin O'Donnell will update profile template document on Wiki.
*'''Action:''' Domain Planning Committees will be requested to develop an IHE Profile Webpage for each Final Text & Trial Implementation profile in their domain.


'''Due date for all tasks is April 18.''' Chris Carr will communicate this request to the Domain Sponsors.
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).


Domains which complete all three pieces (ISO Domain Document, IHE Domain Webpage, Set of IHE Profile Webpages) will have their Technical Frameworks incorporated by ISO later this year. Those who do not will not.
* [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.
 
<br>
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"
! Document
! Who prepares first draft
! Reviewed by
|-
| [[IHERO_ISO_domain_document | IHE-RO ISO Domain Document]]
| Colin
|
|-
| [[IHERO_ISO_Domain_Webpage | IHE-RO ISO Domain Webpage]]
| Colin
|
|-
| [[Normal Treatment Planning-Simple |  Normal Treatment Planning-Simple (NTPL-S)]]
| Charles, Colin, May, Mika
|
|-
| [[Multimodality Registration for Radiation Oncology | Multimodality Registration for Radiation Oncology (MMR-RO)]]
| Colin, Sha, Shankar, Mika
|
|-
| [[RT Treatment Workflow | 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

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
Retrieved from "http://wiki.ihe.net/index.php?title=IHERO_ISO_Documentation&oldid=15791"