Difference between revisions of "Frameworks"

From IHE Wiki
Jump to navigation Jump to search
(4 intermediate revisions by the same user not shown)
Line 2: Line 2:
 
==IHE Technical Frameworks==
 
==IHE Technical Frameworks==
  
IHE Technical Frameworks specify the technical details of the [[Profiles|'''Integration Profiles''']].   
+
IHE Technical Frameworks specify the technical details of the [[Profiles|'''IHE Profiles''']].   
  
 
Each [[Domains|IHE Domain]] publishes a Technical Framework used by engineers to implement IHE functionality. '''[[Official Templates]]''' are used for consistent layout and content.
 
Each [[Domains|IHE Domain]] publishes a Technical Framework used by engineers to implement IHE functionality. '''[[Official Templates]]''' are used for consistent layout and content.
  
 
Technical frameworks are published in '''volumes'''. The first volume typically defines each Profile, the use cases, the '''[[Actors|actors]]''' involved and the requirements for conformance. Subsequent volume(s) specify how to implement the transactions used in the Profiles. The last volume is usually reserved for National / Regional extensions.
 
Technical frameworks are published in '''volumes'''. The first volume typically defines each Profile, the use cases, the '''[[Actors|actors]]''' involved and the requirements for conformance. Subsequent volume(s) specify how to implement the transactions used in the Profiles. The last volume is usually reserved for National / Regional extensions.
 
 
  
 
===Official Publication===
 
===Official Publication===
Line 22: Line 20:
 
'''[[:Category:CPs| Change Proposals]]''' are fixes and clarifications which get incorporated into a Technical Framework.
 
'''[[:Category:CPs| Change Proposals]]''' are fixes and clarifications which get incorporated into a Technical Framework.
  
==General Introduction and Shared Appendices==
+
===IHE Technical Frameworks General Introduction and Shared Appendices===
 
Information about the IHE General Introduction and Shared Appendices can be found [http://wiki.ihe.net/index.php/Official_Templates#General_Introduction_and_Shared_Appendices here]
 
Information about the IHE General Introduction and Shared Appendices can be found [http://wiki.ihe.net/index.php/Official_Templates#General_Introduction_and_Shared_Appendices here]
 
This section is in DRAFT state. Content presented is for feasibility testing only at this point.
 
===Appendix B Transactions===
 
 
{| class="wikitable collapsible autocollapse sortable"
 
! Transaction # !! Transaction Name !! Transaction Description !! Status
 
|-
 
| ARTI-01 || Basic Static Beam Storage || In the Basic Static Beam Storage transaction, a Static Beam Producer stores a treatment plan to the Archive. The treatment plan shall contain only static, non-MLC treatment beams. || Trial Implementation
 
|-
 
| ARTI-02 || Basic Static Beam Retrieval || In the Basic Static Beam Retrieval transaction, a Static Beam Consumer or a TMS receives a treatment plan from the Archive. The treatment plan shall contain only static, non-MLC treatment beams. || Trial Implementation
 
|-
 
| ARTI-03 || Basic Static MLC Beam Storage || In the Basic Static MLC Beam Storage transaction, a Static MLC Beam Producer stores a treatment plan to the Archive. The treatment plan shall contain only static, MLC treatment beams. || Trial Implementation
 
|-
 
| ARTI-04 || Basic Static MLC Beam Retrieval || In the Basic Static MLC Beam Retrieval transaction, a Static MLC Beam Consumer or a TMS receives a treatment plan from the Archive. The treatment plan shall contain only static, MLC treatment beams. || Trial Implementation
 
|-
 
| ARTI-05 || Arc Beam Storage || In the Arc Beam Storage transaction, an Arc Beam Producer stores a treatment plan to the Archive. The treatment plan shall contain only non-MLC arc treatment beams. || Trial Implementation
 
|-
 
| ARTI-06 || Arc Beam Retrieval || In the Arc Beam Retrieval transaction, an Arc Beam Consumer or a TMS receives a treatment plan from the Archive. The treatment plan shall contain only non-MLC arc treatment beams. || Trial Implementation
 
|-
 
| ARTI-07 || MLC Arc Beam Storage || In the MLC Arc Beam Storage transaction, an MLC Arc Beam Producer stores a treatment plan to the Archive. The treatment plan shall contain only MLC arc treatment beams. || Trial Implementation
 
|-
 
| ARTI-08 || MLC Arc Beam Retrieval || In the MLC Arc Beam Retrieval transaction, an MLC Arc Beam Consumer or a TMS receives a treatment plan from the Archive. The treatment plan shall contain only MLC arc treatment beams. || Trial Implementation
 
|-
 
| ARTI-09 || Conformal Arc Beam Storage || In the Conformal Arc Beam Storage transaction, a Conformal Arc Beam Producer stores a treatment plan to the Archive. The treatment plan shall contain only conformal arc treatment beams. || Trial Implementation
 
|-
 
| ARTI-10 || Conformal Arc Beam Retrieval || In the Conformal Arc Beam Retrieval transaction, an Conformal Arc Beam Consumer or a TMS receives a treatment plan from the Archive. The treatment plan shall contain only conformal arc treatment beams. || Trial Implementation
 
|-
 
| ARTI-11 || Hard Wedge Beam Storage || In the Hard Wedge Beam Storage transaction, a Hard Wedge Beam Producer stores a treatment plan to the Archive. The treatment plan shall contain only static treatment beams using physical wedges. || Trial Implementation
 
|-
 
| ARTI-12 || Hard Wedge Beam Retrieval || In the Hard Wedge Beam Retrieval transaction, a Hard Wedge Beam Consumer or a TMS receives a treatment plan from the Archive. The treatment plan shall contain only static treatment beams using physical wedges. || Trial Implementation
 
|-
 
| ARTI-13 || Virtual Wedge Beam Storage || In the Virtual Wedge Beam Storage transaction, a Virtual Wedge Beam Producer stores a treatment plan to the Archive. The treatment plan shall contain only static treatment beams using virtual wedges. || Trial Implementation
 
|-
 
| ARTI-14 || Virtual Wedge Beam Retrieval || In the Virtual Wedge Beam Retrieval transaction, a Virtual Wedge Beam Consumer or a TMS receives a treatment plan from the Archive. The treatment plan shall contain only static treatment beams using virtual wedges. || Trial Implementation
 
|-
 
| ARTI-15 || Motorized Wedge Beam Storage || In the Motorized Wedge Beam Storage transaction, a Motorized Wedge Beam Producer stores a treatment plan to the Archive. The treatment plan shall contain only static treatment beams using motorized wedges. || Trial Implementation
 
|}
 
  
 
==See Also==
 
==See Also==
 
'''[[Process#Technical Framework Development|Technical Framework Development Process]]''' for details on how they are organized and how they are developed.
 
'''[[Process#Technical Framework Development|Technical Framework Development Process]]''' for details on how they are organized and how they are developed.

Revision as of 13:39, 31 January 2017

IHE Technical Frameworks

IHE Technical Frameworks specify the technical details of the IHE Profiles.

Each IHE Domain publishes a Technical Framework used by engineers to implement IHE functionality. Official Templates are used for consistent layout and content.

Technical frameworks are published in volumes. The first volume typically defines each Profile, the use cases, the actors involved and the requirements for conformance. Subsequent volume(s) specify how to implement the transactions used in the Profiles. The last volume is usually reserved for National / Regional extensions.

Official Publication

www.ihe.net/Technical_Framework

Public Comment Drafts

http://www.ihe.net/Public_Comment/

Public Comment Resolutions

Public Comment Resolutions describe how each public comment was handled (accepted, revised, rejected).

Maintenance

Change Proposals are fixes and clarifications which get incorporated into a Technical Framework.

IHE Technical Frameworks General Introduction and Shared Appendices

Information about the IHE General Introduction and Shared Appendices can be found here

See Also

Technical Framework Development Process for details on how they are organized and how they are developed.