Difference between revisions of "Integration Statement"

From IHE Wiki
Jump to navigation Jump to search
 
(13 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
'''IHE Integration Statements''' are documents prepared and published by vendors to describe the intended conformance of their products with the [[Frameworks| IHE Technical Framework]]. Integration Statements tell consumers the specific IHE capabilities a given product is designed to support in terms of the key concepts of IHE: [[:Category:Actors| Actors]] and [[Profiles| Integration Profiles]].
 
'''IHE Integration Statements''' are documents prepared and published by vendors to describe the intended conformance of their products with the [[Frameworks| IHE Technical Framework]]. Integration Statements tell consumers the specific IHE capabilities a given product is designed to support in terms of the key concepts of IHE: [[:Category:Actors| Actors]] and [[Profiles| Integration Profiles]].
  
 +
[https://profiles.ihe.net/GeneralIntro/ch-F.html Appendix F] of the General Introduction to the IHE Technical Framework contains a complete description and purpose of an IHE Integration Statement, including an example. 
  
The '''[http://product-registry.ihe.net IHE Product Registry]''' is a Web-based database of Integration Statements.
+
An MS Word template for an IHE Integration Statement can be found at [[How_to_Prepare_an_IHE_Integration_Statement#IHE_Integration_Statement_template]].
  
Implementers can create, manage and publish Integration Statements for their commercial and open source healthcare IT systems.  
+
The '''[http://product-registry.ihe.net IHE Product Registry]''' is a Web-based database of Integration Statements. Implementers can create, manage and publish Integration Statements for their commercial and open source healthcare IT systems. Users can decide what Actors and Profiles are needed in their enterprise and then browse for systems that meet those conformance requirements.
  
Users can decide what Actors and Profiles are needed in their enterprise and then browse for systems that meet those conformance requirements.
+
''(This wiki page used to contain a list of organizations that published integration statements. That list is replaced by the Product Registry).
 
+
''
 
 
Vendors wishing to develop IHE Integration Statements to communicate the integration capabilities of their systems are invited to [http://www.ihe.net/Resources/upload/ihe_integration_statements.pdf use the form linked here.] The form includes important qualifications and instructions for publishing: please read and use it carefully.
 
  
  
''(This wiki page used to contain a list of organizations that published integration statements. That list is replaced by the Product Registry)
+
<!-- The form includes important qualifications and instructions for publishing: please read and use it carefully. -->
''
 

Latest revision as of 16:19, 9 March 2024

IHE Integration Statements are documents prepared and published by vendors to describe the intended conformance of their products with the IHE Technical Framework. Integration Statements tell consumers the specific IHE capabilities a given product is designed to support in terms of the key concepts of IHE: Actors and Integration Profiles.

Appendix F of the General Introduction to the IHE Technical Framework contains a complete description and purpose of an IHE Integration Statement, including an example.

An MS Word template for an IHE Integration Statement can be found at How_to_Prepare_an_IHE_Integration_Statement#IHE_Integration_Statement_template.

The IHE Product Registry is a Web-based database of Integration Statements. Implementers can create, manage and publish Integration Statements for their commercial and open source healthcare IT systems. Users can decide what Actors and Profiles are needed in their enterprise and then browse for systems that meet those conformance requirements.

(This wiki page used to contain a list of organizations that published integration statements. That list is replaced by the Product Registry).