Difference between revisions of "Frameworks"

From IHE Wiki
Jump to navigation Jump to search
Line 26: Line 26:
 
==[[IT Infrastructure| IHE IT Infrastructure]] Technical Framework==
 
==[[IT Infrastructure| IHE IT Infrastructure]] Technical Framework==
  
The Technical Framework with all 2006 CPs integrated can be found at:
+
Revision 3.0
ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2005-2006/TF/
+
December 9, 2006
 +
Copyright © 2006: ACC/HIMSS/RSNA
 +
Final Text Version
 +
 
 +
* [http://www.ihe.net/Technical_Framework/upload/ihe_iti_tf_3%5B1%5D.0_vol1_FT_2006-11-07.pdf Vol. 1 (ITI TF-1): Integration Profiles]
 +
* [http://www.ihe.net/Technical_Framework/upload/ihe_iti_tf_3%5B1%5D.0_vol1_FT_2006-11-07_tracked.pdf Vol. 1 (ITI TF-1): Integration Profiles (highlighting changes from Rev. 2.0)]
 +
* [http://www.ihe.net/Technical_Framework/upload/ihe_iti_tf_3.pdf Vol. 2 (ITI TF-2): Transactions]
 +
* [http://www.ihe.net/Technical_Framework/upload/ihe_iti_tf_3-2.pdf Vol. 2 (ITI TF-2): Transactions (highlighting changes from Rev. 2.0)]
 +
 
 +
Nine IHE IT Infrastructure Integration Profiles are specificied as Final Text in the Version 3.0 ITI Technical Framework:
 +
* Cross-Enterprise Document Sharing (XDS),
 +
* Patient Identifier Cross-Referencing (PIX),
 +
* Patient Demographics Query (PDQ),
 +
* Audit trail and Node Authenticaton (ATNA),
 +
* Consistent Time (CT),
 +
* Enterprise User Authentication (EUA),
 +
* Retrieve Information for Display (RID),
 +
* Patient Syncronized Applications (PSA), and
 +
* Personnel White Pages (PWP).
  
 
==[[Laboratory| IHE Laboratory]] Technical Framework==
 
==[[Laboratory| IHE Laboratory]] Technical Framework==

Revision as of 08:39, 20 March 2007

IHE Technical Frameworks define precisely the technical details of the Integration Profiles. These documents should be used by engineers to implement IHE functionality. Technical frameworks are typically published in several volumes. The first volume typically defines the Profile, the use cases, the actors involved and the requirements for conformance. The subsequent voume defines the transactions used in the Profiles. The last volume is usually researved for National / Regional extensions.

Change Proposals are modifications to specification documents. Change Proposals are typically discussed, balloted, then realeased for Trial Implementation. They are subsquently finalized and eventually incorporated into the Final technical Frameworks.

IHE Cardiology Technical Framework

  • Final
    • Version 2.1 Volume 1: Cardiology Profiles pdf
    • Version 2.1 Volume 2: Cardiology Transactions pdf
  • Out for Trial Implementation
    • Implantable Device Cardiac Observations (IDCO) pdf
    • Stress Testing Workflow (STRESS) - pdf
  • Out for Public Comment
    • Patient Demographics Query: Implantable Device Cardiac (PDQ-IDC) - pdf

IHE Eyecare Technical Framework

  • Final
    • NONE
  • Out for Trial Implementation
    • Version 1.0 Volume 1: Eye Care Profiles [1]
    • Version 1.0 Volume 2: Eye Care Transactions [2]
  • Out for Public Comment
    • NONE

IHE IT Infrastructure Technical Framework

Revision 3.0 December 9, 2006 Copyright © 2006: ACC/HIMSS/RSNA Final Text Version

Nine IHE IT Infrastructure Integration Profiles are specificied as Final Text in the Version 3.0 ITI Technical Framework:

  • Cross-Enterprise Document Sharing (XDS),
  • Patient Identifier Cross-Referencing (PIX),
  • Patient Demographics Query (PDQ),
  • Audit trail and Node Authenticaton (ATNA),
  • Consistent Time (CT),
  • Enterprise User Authentication (EUA),
  • Retrieve Information for Display (RID),
  • Patient Syncronized Applications (PSA), and
  • Personnel White Pages (PWP).

IHE Laboratory Technical Framework

IHE Patient Care Coordination Technical Framework

IHE Patient Care Devices Technical Framework

IHE Radiation Oncology Technical Framework

IHE Radiology Technical Framework

See Also

Past Versions of Technical Frameworks