Difference between revisions of "Frameworks"

From IHE Wiki
Jump to navigation Jump to search
(Undo revision 48448 by AveMaria (Talk))
Line 8: Line 8:
  
 
==Official Publication==
 
==Official Publication==
 
 
[http://www.ihe.net/Technical_Framework/index.cfm www.ihe.net/Technical_Framework]
 
[http://www.ihe.net/Technical_Framework/index.cfm www.ihe.net/Technical_Framework]
  
Line 14: Line 13:
 
==Public Comment Drafts==
 
==Public Comment Drafts==
 
[http://www.ihe.net/Technical_Framework/public_comment.cfm www.ihe.net/Technical_Framework/public_comment.cfm]
 
[http://www.ihe.net/Technical_Framework/public_comment.cfm www.ihe.net/Technical_Framework/public_comment.cfm]
 +
 +
 +
==Public Comment Resolutions==
 +
'''[[Public Comment Resolutions]]''' describe how each public comment was handled (accepted, revised, rejected).
  
  

Revision as of 15:02, 1 September 2011

IHE Technical Frameworks

IHE Technical Frameworks specify the technical details of the Integration Profiles. Each IHE Domain publishes Technical Framework which are used by engineers to implement IHE functionality.

Technical frameworks are published in volumes. The first volume typically defines the 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

www.ihe.net/Technical_Framework/public_comment.cfm


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.


See Also

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