12.07.2015 Views

IHE Patient Care Device Technical Framework

IHE Patient Care Device Technical Framework

IHE Patient Care Device Technical Framework

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

102030<strong>IHE</strong> <strong>Patient</strong> <strong>Care</strong> <strong>Device</strong> <strong>Technical</strong> <strong>Framework</strong>, Vol. 2: Transactions________________________________________________________________________Users familiar with these concepts can use Integration Statements as an aid to determinewhat level of integration a vendor asserts a product supports with complementary systemsand what clinical and operational benefits such integration might provide. IntegrationStatements are intended to be used in conjunction with statements of conformance tospecific standards (e.g. HL7, DICOM, W3C, etc.).<strong>IHE</strong> provides a process for vendors to test their implementation of <strong>IHE</strong> Actors andIntegration Profiles. The <strong>IHE</strong> testing process, culminating in a multi-party interactivetesting event called the Connect-a-thon, provides vendors with valuable feedback andprovides a baseline indication of the conformance of their implementations. The processis not, however, intended to independently evaluate, or ensure, product compliance. Inpublishing the results of the Connect-a-thon, and facilitating access to vendors’ <strong>IHE</strong>Integration Statements, <strong>IHE</strong> and its sponsoring organizations are in no way attesting tothe accuracy or validity of any vendor’s <strong>IHE</strong> Integration Statements or any other claimsby vendors regarding their products.IMPORTANT -- PLEASE NOTE: Vendors have sole responsibility for the accuracy andvalidity of their <strong>IHE</strong> Integration Statements. Vendors’ Integration Statements are madeavailable through <strong>IHE</strong> simply for consideration by parties seeking information about theintegration capabilities of particular products. <strong>IHE</strong> and its sponsoring organizations havenot evaluated or approved any <strong>IHE</strong> Integration Statement or any related product, and <strong>IHE</strong>and its sponsoring organizations shall have no liability or responsibility to any party forany claims or damages, whether direct, indirect, incidental or consequential, includingbut not limited to business interruption and loss of revenue, arising from any use of, orreliance upon, any <strong>IHE</strong> Integration Statement.H.2 Structure and Content of an <strong>IHE</strong> IntegrationStatementAn <strong>IHE</strong> Integration Statement for a product shall include:4. The Vendor Name5. The Product Name (as used in the commercial context) to which the <strong>IHE</strong>Integration Statement applies.6. The Product Version to which the <strong>IHE</strong> Integration Statement applies.7. A publication date and optionally a revision designation for the <strong>IHE</strong> IntegrationStatement.8. The following statement:9. “This product is intended to implement all transactions required in the <strong>IHE</strong><strong>Technical</strong> <strong>Framework</strong> to support the <strong>IHE</strong> Integration Profiles, Actors andOptions listed below:”Rev. 1.1 TI: 2006-08-15100Copyright © 2005-2006: ACC, ACCE, HIMSS, and RSNA

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!