Difference between revisions of "PCC TF-1/Preface"
| Line 1: | Line 1: | ||
| − | = <span id='Preface1'>Preface to Volume 1</span> of the PCC Technical Framework = | + | == <span id='Preface1'>Preface to Volume 1</span> of the PCC Technical Framework == |
| − | == Intended Audience == | + | === Intended Audience === |
The intended audience of this document is: | The intended audience of this document is: | ||
* Healthcare professionals involved in informatics | * Healthcare professionals involved in informatics | ||
| Line 7: | Line 7: | ||
* Experts involved in standards development | * Experts involved in standards development | ||
* Those interested in integrating healthcare information systems and workflows | * Those interested in integrating healthcare information systems and workflows | ||
| − | == Related Information for the Reader== | + | === Related Information for the Reader=== |
The reader of volume 1 should read or be familiar with the following documents: | The reader of volume 1 should read or be familiar with the following documents: | ||
* Volume 1 of the Cross-Enterprise Document Sharing (XDS) Integration Profile documented in the ITI Infrastructure Technical Framework | * Volume 1 of the Cross-Enterprise Document Sharing (XDS) Integration Profile documented in the ITI Infrastructure Technical Framework | ||
| Line 25: | Line 25: | ||
* Patient Care Coordination - Overview of Profiles | * Patient Care Coordination - Overview of Profiles | ||
| − | == How this Volume is Organized == | + | === How this Volume is Organized === |
Section 2 describes the general nature, structure, purpose and function of the Technical Framework. | Section 2 describes the general nature, structure, purpose and function of the Technical Framework. | ||
Section 3 and the subsequent sections of this volume provide detailed documentation on each integration profile, including the Patient Care Coordination problem it is intended to address and the IHE actors and transactions it comprises. | Section 3 and the subsequent sections of this volume provide detailed documentation on each integration profile, including the Patient Care Coordination problem it is intended to address and the IHE actors and transactions it comprises. | ||
| Line 31: | Line 31: | ||
The appendices following the main body of the document provide a summary list of the actors and transactions, detailed discussion of specific issues related to the integration profiles and a glossary of terms and acronyms used. | The appendices following the main body of the document provide a summary list of the actors and transactions, detailed discussion of specific issues related to the integration profiles and a glossary of terms and acronyms used. | ||
| − | == Conventions Used in this Document== | + | === Conventions Used in this Document=== |
This document has adopted the following conventions for representing the framework concepts and specifying how the standards upon which the IHE Technical Framework is based should be applied. | This document has adopted the following conventions for representing the framework concepts and specifying how the standards upon which the IHE Technical Framework is based should be applied. | ||
| − | === Technical Framework Cross-references === | + | ==== Technical Framework Cross-references ==== |
When references are made to another section within a Technical Framework volume, a section number is used by itself. When references are made to other volumes or to a Technical Framework in another domain, the following format is used: | When references are made to another section within a Technical Framework volume, a section number is used by itself. When references are made to other volumes or to a Technical Framework in another domain, the following format is used: | ||
| Line 49: | Line 49: | ||
For example: PCC TF-1: 3.1 refers to Section 3.1 in volume 1 of the IHE Patient Care Coordination Technical Framework, ITI TF-2: 4.33 refers to Section 4.33 in volume 2 of the IHE IT Infrastructure Technical Framework. | For example: PCC TF-1: 3.1 refers to Section 3.1 in volume 1 of the IHE Patient Care Coordination Technical Framework, ITI TF-2: 4.33 refers to Section 4.33 in volume 2 of the IHE IT Infrastructure Technical Framework. | ||
| − | === IHE Actor and Transaction Diagrams and Tables === | + | ==== IHE Actor and Transaction Diagrams and Tables ==== |
Each integration profile is a representation of a real-world capability that is supported by a set of actors that interact through transactions. Actors are information systems or components of information systems that produce, manage, or act on categories of information required by operational activities in the enterprise. Transactions are interactions between actors that communicate the required information through standards-based messages. | Each integration profile is a representation of a real-world capability that is supported by a set of actors that interact through transactions. Actors are information systems or components of information systems that produce, manage, or act on categories of information required by operational activities in the enterprise. Transactions are interactions between actors that communicate the required information through standards-based messages. | ||
| Line 57: | Line 57: | ||
In some cases, a profile is dependent on a prerequisite profile in order to function properly and be useful. For example, Cross-Enterprise Sharing of Medical Summaries depends on Cross-Enterprise Document Sharing (XDS). These dependencies can be found by locating the desired profile in Table 2.6-1 to determine which profile(s) are listed as prerequisites. An actor must implement all required transactions in the prerequisite profiles in addition to those in the desired profile. | In some cases, a profile is dependent on a prerequisite profile in order to function properly and be useful. For example, Cross-Enterprise Sharing of Medical Summaries depends on Cross-Enterprise Document Sharing (XDS). These dependencies can be found by locating the desired profile in Table 2.6-1 to determine which profile(s) are listed as prerequisites. An actor must implement all required transactions in the prerequisite profiles in addition to those in the desired profile. | ||
| − | ===Process Flow Diagrams === | + | ====Process Flow Diagrams ==== |
The descriptions of integration profiles that follow include process flow diagrams that illustrate how the profile functions as a sequence of transactions between relevant actors. | The descriptions of integration profiles that follow include process flow diagrams that illustrate how the profile functions as a sequence of transactions between relevant actors. | ||
| Line 65: | Line 65: | ||
In some cases the sequence of transactions may be flexible. Where this is the case there will generally be a note pointing out the possibility of variations. Transactions are shown as arrows oriented according to the flow of the primary information handled by the transaction and not necessarily the initiator. | In some cases the sequence of transactions may be flexible. Where this is the case there will generally be a note pointing out the possibility of variations. Transactions are shown as arrows oriented according to the flow of the primary information handled by the transaction and not necessarily the initiator. | ||
| − | == Copyright Permissions == | + | === Copyright Permissions === |
Health Level Seven, Inc., has granted permission to the IHE to reproduce tables from the HL7 standard. The HL7 tables in this document are copyrighted by Health Level Seven, Inc. All rights reserved. Material drawn from these documents is credited where used. | Health Level Seven, Inc., has granted permission to the IHE to reproduce tables from the HL7 standard. The HL7 tables in this document are copyrighted by Health Level Seven, Inc. All rights reserved. Material drawn from these documents is credited where used. | ||
Revision as of 12:52, 27 April 2007
Preface to Volume 1 of the PCC Technical Framework
Intended Audience
The intended audience of this document is:
- Healthcare professionals involved in informatics
- IT departments of healthcare institutions
- Technical staff of vendors participating in the IHE initiative
- Experts involved in standards development
- Those interested in integrating healthcare information systems and workflows
Related Information for the Reader
The reader of volume 1 should read or be familiar with the following documents:
- Volume 1 of the Cross-Enterprise Document Sharing (XDS) Integration Profile documented in the ITI Infrastructure Technical Framework
(See http://www.ihe.net/Technical_Framework/index.cfm ).
- Volume 1 of the Notification of Document Availability (NAV) Integration Profile documented in the ITI Infrastructure Technical Framework
(See http://www.ihe.net/Technical_Framework/index.cfm ).
- Volume 1 of the Audit Trail and Node Authentication (ATNA) Integration Profile documented in the ITI Infrastructure Technical Framework
(See http://www.ihe.net/Technical_Framework/index.cfm ).
- HL7 Clinical Document Architecture Release 2: Section 1, CDA Overview.
- Care Record Summary – Implementation Guide for CDA Release 2 (US Realm): Section 1
- Presentations from IHE Workshop: Effective Integration of the Enterprise and the Health System - June 28–29, 2005: http://www.ihe.net/Participation/workshop_2005.cfm, June 2005:
- Leveraging IHE to Build RHIO Interoperability
- Cross-Enterprise Document Sharing (XDS)
- Notification of Document Availability (NAV)
- Patient Care Coordination
- Use Cases for Medical Summaries
- Patient Care Coordination - Overview of Profiles
How this Volume is Organized
Section 2 describes the general nature, structure, purpose and function of the Technical Framework. Section 3 and the subsequent sections of this volume provide detailed documentation on each integration profile, including the Patient Care Coordination problem it is intended to address and the IHE actors and transactions it comprises.
The appendices following the main body of the document provide a summary list of the actors and transactions, detailed discussion of specific issues related to the integration profiles and a glossary of terms and acronyms used.
Conventions Used in this Document
This document has adopted the following conventions for representing the framework concepts and specifying how the standards upon which the IHE Technical Framework is based should be applied.
Technical Framework Cross-references
When references are made to another section within a Technical Framework volume, a section number is used by itself. When references are made to other volumes or to a Technical Framework in another domain, the following format is used:
<domain designator> TF-<volume number>: <section number>
where:
- <domain designator>
- is a short designator for the IHE domain (PCC= Patient Care Coordination, ITI = IT Infrastructure, RAD = Radiology)
- <volume number>
- is the applicable volume within the given Domain Technical Framework (e.g., 1, 2, 3), and
- <section number>
- is the applicable section number.
For example: PCC TF-1: 3.1 refers to Section 3.1 in volume 1 of the IHE Patient Care Coordination Technical Framework, ITI TF-2: 4.33 refers to Section 4.33 in volume 2 of the IHE IT Infrastructure Technical Framework.
IHE Actor and Transaction Diagrams and Tables
Each integration profile is a representation of a real-world capability that is supported by a set of actors that interact through transactions. Actors are information systems or components of information systems that produce, manage, or act on categories of information required by operational activities in the enterprise. Transactions are interactions between actors that communicate the required information through standards-based messages.
The diagrams and tables of actors and transactions in subsequent sections indicate which transactions each actor in a given profile must support.
The transactions shown on the diagrams are identified both by their name and the transaction number as defined in PCC TF-2 (Volume 2 of the PCC Technical framework). The transaction numbers are shown on the diagrams as bracketed numbers prefixed with the specific Technical Framework domain. In some cases, a profile is dependent on a prerequisite profile in order to function properly and be useful. For example, Cross-Enterprise Sharing of Medical Summaries depends on Cross-Enterprise Document Sharing (XDS). These dependencies can be found by locating the desired profile in Table 2.6-1 to determine which profile(s) are listed as prerequisites. An actor must implement all required transactions in the prerequisite profiles in addition to those in the desired profile.
Process Flow Diagrams
The descriptions of integration profiles that follow include process flow diagrams that illustrate how the profile functions as a sequence of transactions between relevant actors.
These diagrams are intended to provide an overview so the transactions can be seen in the context of an institution’s or cross-institutions’ workflow. Certain transactions and activities not defined in detail by IHE are shown in these diagrams in italics to provide additional context on where the relevant IHE transactions fit into the broader scheme of healthcare information systems. These diagrams are not intended to present the only possible scenario. Often other actor groupings are possible, and transactions from other profiles may be interspersed.
In some cases the sequence of transactions may be flexible. Where this is the case there will generally be a note pointing out the possibility of variations. Transactions are shown as arrows oriented according to the flow of the primary information handled by the transaction and not necessarily the initiator.
Copyright Permissions
Health Level Seven, Inc., has granted permission to the IHE to reproduce tables from the HL7 standard. The HL7 tables in this document are copyrighted by Health Level Seven, Inc. All rights reserved. Material drawn from these documents is credited where used.