IHE Patient Care Device Technical Framework

More documents

Recommendations

Info

IHE Patient Care Device Technical Framework, Vol. 2: Transactions________________________________________________________________________The appendices following the main body of this volume provide technical detailsassociated with the transactions.1.3 AudienceThe intended audience of this document is:• IT departments of healthcare institutions• Technical staff of vendors planning to participate in the IHE initiative• Experts involved in standards development• Those interested in integrating healthcare information systems and workflows1.4 Relationship to Standards102030The IHE Technical Framework identifies functional components of a distributedhealthcare environment (referred to as IHE actors), solely from the point of view of theirinteractions in the healthcare enterprise. At its current level of development, it defines acoordinated set of transactions based on ASTM, DICOM, HL7, IEEE, IETF, ISO, OASISand W3C standards. As the scope of the IHE initiative expands, transactions based onother standards may be included as required.In some cases, IHE recommends selection of specific options supported by thesestandards; however, IHE does not introduce technical choices that contradictconformance to these standards. If errors in or extensions to existing standards areidentified, IHE’s policy is to report them to the appropriate standards bodies forresolution within their conformance and standards evolution strategy.IHE is therefore an implementation framework, not a standard. Conformance claims forproducts must still be made in direct reference to specific standards. In addition, vendorswho have implemented IHE integration capabilities in their products may publish IHEIntegration Statements to communicate their products’ capabilities. Vendors publishingIHE Integration Statements accept full responsibility for their content. By comparing theIHE Integration Statements from different products, a user familiar with the IHE conceptsof actors and integration profiles can determine the level of integration between them.See Appendix H for the format of IHE PCD Integration Statements. IHE encouragesimplementers to ensure that products implemented in accordance with the IHE TechnicalFramework also meet the full requirements of the standards underlying IHE, allowing theproducts to interact, although possibly at a lower level of integration, with products thathave been implemented in conformance with those standards, but not in full accordancewith the IHE Technical Framework.Rev. 1.1 TI: 2006-08-157Copyright © 2005-2006: ACC, ACCE, HIMSS, and RSNA
1020IHE Patient Care Device Technical Framework, Vol. 2: Transactions________________________________________________________________________1.5 Relationship to Real-world ArchitecturesThe IHE actors and transactions described in the IHE Technical Framework areabstractions of the real-world healthcare information system environment. While some ofthe transactions are traditionally performed by specific product categories (e.g. HIS,Clinical Data Repository, Radiology Information Systems, Clinical Information Systemsor Cardiology Information Systems), the IHE Technical Framework intentionally avoidsassociating functions or actors with such product categories. For each Actor, the IHETechnical Framework defines only those functions associated with integratinginformation systems. The IHE definition of an Actor should therefore not be taken as thecomplete definition of any product that might implement it, nor should the frameworkitself be taken to comprehensively describe the architecture of a healthcare informationsystem.The reason for defining actors and transactions is to provide a basis for defining theinteractions among functional components of the healthcare information systemenvironment. In situations where a single physical product implements multiplefunctions, only the interfaces between the product and external functions in theenvironment are considered to be significant by the IHE initiative. Therefore, the IHEinitiative takes no position as to the relative merits of an integrated environment based ona single, all-encompassing information system versus one based on multiple systems thattogether achieve the same end. To illustrate most dramatically the possibilities of the IHETechnical Framework, however, the IHE demonstrations emphasize the integration ofmultiple vendors’ systems based on the IHE Technical Framework.1.6 Comments30HIMSS and RSNA welcome comments on this document and the IHE initiative. Theyshould be directed to the discussion server at http://ihe.rsna.org/ihetf/ or to:Chris CarrJoyce SensmeierDirector of InformaticsDirector of Professional Services820 Jorie Boulevard 230 East Ohio St., Suite 500Oak Brook, IL 60523 Chicago, IL 60611Email: ihe@rsna.orgEmail: ihe@himss.org1.7 Copyright PermissionHealth Level Seven, Inc. has granted permission to the IHE to reproduce tables from theHL7 standard. The HL7 tables in this document are copyrighted by Health Level Seven,Inc. All rights reserved.Use of copyrighted IEEE material in this technical framework from the ISO/IEEE 11073standards is covered by the IEEE-SA Royalty-free permission guidelines.Rev. 1.1 TI: 2006-08-158Copyright © 2005-2006: ACC, ACCE, HIMSS, and RSNA
Page 3 and 4: 10203040IHE Patient Care Device Tec
Page 7: IHE Patient Care Device Technical F
Page 11 and 12: IHE Patient Care Device Technical F
Page 33 and 34: 102030IHE Patient Care Device Techn
Page 35 and 36: 10IHE Patient Care Device Technical
Page 53 and 54: 1020IHE Patient Care Device Technic
Page 59 and 60:
IHE Patient Care Device Technical F
Page 61 and 62:
1020IHE Patient Care Device Technic
Page 63 and 64:
Page 65 and 66:
10IHE Patient Care Device Technical
Page 67 and 68:
102030IHE Patient Care Device Techn
Page 69 and 70:
Page 71 and 72:
1020IHE Patient Care Device Technic
Page 73 and 74:
10IHE Patient Care Device Technical
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Attribute Description Term Code Dat
Page 81 and 82:
elowChannel AttributesAttribute Des
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
102030405060IHE Patient Care Device
Page 97 and 98:
10203040IHE Patient Care Device Tec
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
show all

IHE Patient Care Device Technical Framework

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

Delete template?

Save as template?