Difference between revisions of "PCC TF-1/Trailer"

From IHE Wiki
Jump to navigation Jump to search
m
Line 40: Line 40:
 
==Appendix C - How to Prepare an IHE Integration Statement==
 
==Appendix C - How to Prepare an IHE Integration Statement==
 
{{:How to Prepare an IHE Integration Statement}}
 
{{:How to Prepare an IHE Integration Statement}}
 +
 +
==Appendix D - Braden Scale for Predicting Pressure Sore Risk ==
 +
See [[Image:Braden.pdf]]
  
 
==Glossary==
 
==Glossary==
Line 45: Line 48:
  
 
; Actor : An entity within a use case diagram that can perform an action within a use case diagram. Possible actions are creation or consumption of a message
 
; Actor : An entity within a use case diagram that can perform an action within a use case diagram. Possible actions are creation or consumption of a message
 +
; Acuity Assessment :
 +
Also known as triage category, this is the acuity of the patient assigned during the process of ED triage. A number of evidenced based triage scales exist, including the Emergency Severity Index (ESI), Canadian Triage and Acuity Scale (CTAS), the Australasian Triage Scale (ATS), and the Manchester Triage System. In many emergency departments, patients may simply be classified as '''emergent, urgent or non-urgent'''.
 
; ADT:  Admit, Discharge & Transfer.
 
; ADT:  Admit, Discharge & Transfer.
 
; Affinity Domain Policy: Affinity Domain Policy that clearly defines the appropriate uses of the XDS Affinity Domain. Within this policy is a defined set of acceptable use Privacy Consent Policies that are published and understood.
 
; Affinity Domain Policy: Affinity Domain Policy that clearly defines the appropriate uses of the XDS Affinity Domain. Within this policy is a defined set of acceptable use Privacy Consent Policies that are published and understood.
 
; ASTM: Formerly the American Society of Testing and Materials, now ASTM International.  An SDO that develops a number of standards across a wide variety of industries, including healthcare.
 
; ASTM: Formerly the American Society of Testing and Materials, now ASTM International.  An SDO that develops a number of standards across a wide variety of industries, including healthcare.
 
; ATNA: Audit Trail and Node Authentication.  An IHE ITI profile.
 
; ATNA: Audit Trail and Node Authentication.  An IHE ITI profile.
−
; Care Context:
+
; Care Context: The participations surrounding the care provision act, and the attributes of that act.  Everything in the document header.  Data history, links to clinical reasoning.
−
The participations surrounding the care provision act, and the attributes of that act.  Everything in the document header.  Data history, links to clinical reasoning.
+
; Continuity of Care Document(CCD) : An HL7 Clinical Document Architecture (CDA) implementation alternative to ASTM ADJE2369 for institutions or organizations committed to HL7 standards. This specification was developed as a collaborative effort between ASTM and HL7. More information is available from http://www.hl7.org.
−
; CDA:  Clinical Document Architecture. An HL7 standard for the exchange for clinical documents.
+
; Continuity of Care Record (CCR) : A core data set of the most relevant administrative, demographic, and clinical information facts about a patient’s healthcare, covering one or more encounters. The CCR is Designation E2369-05 of the ASTM (American Society for Testing and Materials, International). More information is available from http://www.astm.org.  
−
; Content Binding: A content binding describe how the payload used in an IHE transaction is related to and/or constrained by the data elements contained within the content sent or received in those transactions.
+
; Clinical Document Architecture (CDA): An HL7 standard for the exchange for clinical documents.  It specifies the structure and semantics of clinical documents. More information is available from http://www.hl7.org.  
 +
; Content Binding: A content binding describes how the payload used in an IHE transaction is related to and/or constrained by the data elements contained within the content sent or received in those transactions.
 
; CRS: Care Record Summary.  An implementation guide that constrains CDA Release 2 for Care Record Summary documents.
 
; CRS: Care Record Summary.  An implementation guide that constrains CDA Release 2 for Care Record Summary documents.
 
; CT: Consistent Time Integration Profile.
 
; CT: Consistent Time Integration Profile.
 
; DICOM: Digital Imaging and Communication in Medicine
 
; DICOM: Digital Imaging and Communication in Medicine
 
; DSG: Digital Signatures.  An IHE ITI Profile.
 
; DSG: Digital Signatures.  An IHE ITI Profile.
−
; EDIS: Emergency Department Information System.
+
; EDIS: An Emergency Department Information System (EDIS) is an extended EHR system used to manage data in support of Emergency Department patient care and operations. The functions of an EDIS may be provided by a single application or multiple applications.  
 
; eMPI: Enterprise Master Patient Index.
 
; eMPI: Enterprise Master Patient Index.
 
; EMR: Electronic Medical Record, an Electronic Health Record system used within an enterprise to deliver care (also called EHR-CR by IHE-XDS).
 
; EMR: Electronic Medical Record, an Electronic Health Record system used within an enterprise to deliver care (also called EHR-CR by IHE-XDS).
Line 63: Line 69:
 
; EUA: Enterprise User Authentication Integration Profile.
 
; EUA: Enterprise User Authentication Integration Profile.
 
; Expected Actions: Actions which should occur as the result of a trigger event.
 
; Expected Actions: Actions which should occur as the result of a trigger event.
−
; Functional Role: Role an individual is acting under when they are executing a function. See ISO 21298
 
 
; HIMSS: Healthcare Information and Management Systems Society.
 
; HIMSS: Healthcare Information and Management Systems Society.
 
; HL7: Health Level Seven
 
; HL7: Health Level Seven
Line 70: Line 75:
 
; Interaction Diagram: A diagram that depicts data flow and sequencing of events.
 
; Interaction Diagram: A diagram that depicts data flow and sequencing of events.
 
; IT: Information Technology.
 
; IT: Information Technology.
 +
; Logical Observation Identifiers Names and Codes (LOINC®): A vocabulary developed by the Regenstrief Institute aimed at standardizing laboratory and clinical codes for use in clinical care, outcomes management, and research. Additional information found at [http://www.regenstrief.org/medinformatics/loinc/ http://www.regenstrief.org/medinformatics/loinc/].
 +
; Mode of Arrival : The method of transportation used to transport the patient to the Emergency Department.
 
; MPI: Master Patient Index.
 
; MPI: Master Patient Index.
 
; MRN: Medical Record Number.
 
; MRN: Medical Record Number.
 
; NAV: Notification of Document Availability
 
; NAV: Notification of Document Availability
 
; OID: Object Identifier. (See also <nowiki>'</nowiki>Globally Unique Identifier<nowiki>'</nowiki>).
 
; OID: Object Identifier. (See also <nowiki>'</nowiki>Globally Unique Identifier<nowiki>'</nowiki>).
−
; Patient Privacy Consent: The act of a patient consenting to a specific Privacy Consent Policy.
 
−
; Patient Privacy Consent Document: A document that follows the BPPC profile and captures the act of the patient consenting to a specific XDS Affinity Domain defined Privacy Consent Policy.
 
 
; Patient Identifier Cross-reference Domain: Consists of a set of Patient Identifier Domains known and managed by a Patient Identifier Cross-reference Manager Actor. The Patient Identifier Cross-reference Manager Actor is responsible for providing lists of "alias" identifiers from different Patient Identifier Domains.
 
; Patient Identifier Cross-reference Domain: Consists of a set of Patient Identifier Domains known and managed by a Patient Identifier Cross-reference Manager Actor. The Patient Identifier Cross-reference Manager Actor is responsible for providing lists of "alias" identifiers from different Patient Identifier Domains.
 
; Patient Identifier Domain: A single system or a set of interconnected systems that all share a common identification scheme for patients. Such a scheme includes: (1) a single identifier-issuing authority, (2) an assignment process of an identifier to a patient, (3) a permanent record of issued patient identifiers with associated traits, and (4) a maintenance process over time. The goal of Patient Identification is to reduce errors.
 
; Patient Identifier Domain: A single system or a set of interconnected systems that all share a common identification scheme for patients. Such a scheme includes: (1) a single identifier-issuing authority, (2) an assignment process of an identifier to a patient, (3) a permanent record of issued patient identifiers with associated traits, and (4) a maintenance process over time. The goal of Patient Identification is to reduce errors.
Line 82: Line 87:
 
; PDQ : Patient Demographics Query.  An IHE ITI Profile.
 
; PDQ : Patient Demographics Query.  An IHE ITI Profile.
 
; PHR: Personal Health Record
 
; PHR: Personal Health Record
−
; Privacy Consent Policy: One of the acceptable-use Privacy Consent Policies that are agreed to and understood in the Affinity Domain.
 
−
; Privacy Consent Policy Act Identifier: An Affinity Domain assigned identifier that uniquely defines the act of a patient consenting to a specific Affinity Domain: Privacy Consent Policy.
 
−
; Privacy Consent Policy Identifier: An Affinity Domain assigned identifier (OID) that uniquely identifies the Affinity Domain: Privacy Consent Policy.  There is one unique identifier (OID) for each Privacy Consent Policy within the Affinity Domain.
 
 
; Procedure: In the context of a "Pre-procedure History and Physical," the "procedure" is a surgery or an invasive examination of a patient that is required by quality review organizations to be preceded by a pre-procedure assessment of procedure risk and anesthesia risk. This assessment is typically referred to as a "Pre-operative" or "Pre-procedure History and Physical."
 
; Procedure: In the context of a "Pre-procedure History and Physical," the "procedure" is a surgery or an invasive examination of a patient that is required by quality review organizations to be preceded by a pre-procedure assessment of procedure risk and anesthesia risk. This assessment is typically referred to as a "Pre-operative" or "Pre-procedure History and Physical."
 
; Process Flow Diagram: A graphical illustration of the flow of processes and interactions among the actors involved in a particular example.
 
; Process Flow Diagram: A graphical illustration of the flow of processes and interactions among the actors involved in a particular example.
 
; Proposed disposition: the intended disposition (i.e. admission to ICU, discharge to home, transfer to psychiatric hospital), if known, that the referring provider expects the patient will end up after the emergency department intervention.
 
; Proposed disposition: the intended disposition (i.e. admission to ICU, discharge to home, transfer to psychiatric hospital), if known, that the referring provider expects the patient will end up after the emergency department intervention.
 +
; Referral Source  : An individual, group, or agency that determined the patient should seek care at the ED. Referral source may be used to determine appropriate discharge referrals and services, or to provide surveillance data for program and service planning, or to examine referral patterns.
 
; Role: The actions of an actor in a use case.
 
; Role: The actions of an actor in a use case.
 
; RSNA: Radiological Society of North America.
 
; RSNA: Radiological Society of North America.
 
; sig.: A Latin abbreviation for signetur used to represent the instruction following the medication name.
 
; sig.: A Latin abbreviation for signetur used to represent the instruction following the medication name.
 
; Scope: A brief description of the transaction.
 
; Scope: A brief description of the transaction.
−
; Structural Role: Role of an individual within an organization. See ISO 21298
+
SNOMED-CT®
 +
A comprehensive clinical terminology, originally created by the College of American Pathologists (CAP) and, as of April 2007, owned, maintained, and distributed by the International Health Terminology Standards Development Organisation (IHTSDO), a non-for-profit association in Denmark. The CAP continues to support SNOMED CT operations under contract to the IHTSDO and provides SNOMED-related products and services as a licensee of the terminology. More information available from http://www.ihtsdo.org/ or the United States National Library of Medicine at http://www.nlm.nih.gov/research/umls/Snomed/snomed_main.html
 
; Transport Mode: the method the patient employs, or is provided to get to the emergency department.
 
; Transport Mode: the method the patient employs, or is provided to get to the emergency department.
 
; Trigger Event: An event such as the reception of a message or completion of a process, which causes another action to occur.
 
; Trigger Event: An event such as the reception of a message or completion of a process, which causes another action to occur.
Line 98: Line 102:
 
; Universal ID: Unique identifier over time within the UID type. Each UID must belong to one of specifically enumerated species. Universal ID must follow syntactic rules of its scheme.
 
; Universal ID: Unique identifier over time within the UID type. Each UID must belong to one of specifically enumerated species. Universal ID must follow syntactic rules of its scheme.
 
; Use Case: A graphical depiction of the actors and operation of a system.
 
; Use Case: A graphical depiction of the actors and operation of a system.
−
; Wet Signature: Ink on paper signature.
 
 
; XUA: Cross Enterprise User Authentication
 
; XUA: Cross Enterprise User Authentication
 
; XDS: Cross Enterprise Document Sharing
 
; XDS: Cross Enterprise Document Sharing

Revision as of 13:32, 22 August 2007

Appendix A - Actor Descriptions

Actors are information systems or components of information systems that produce, manage, or act on information associated with operational activities in the enterprise.

Content Creator
The Content Creator Actor is responsible for the creation of content and transmission to a Content Consumer.
Content Consumer
A Content Consumer Actor is responsible for viewing, import, or other processing of content created by a Content Creator Actor.
Clinical Data Consumer
A clinical data consumer makes use of clinical patient data.
Vital Signs Data Repository
A Vital Signs Data Repository maintains patient vital signs data.
Problems and Allergies Repository
A Problems and Allergies Repository maintains patient problem and allergy data.
Diagnostic Data Repository
A Diagnostic Data Repository Repository maintains results from diagnostic tests (e.g., Lab, Imaging, or other test results).
Medications Data Repository
A Medications Data Repository maintains patient medication data.
Immunizations Data Repository
An Immunizations Data Repository maintains patient immunization data.
Professional Services Data Repository
A Professional Services Data Repository maintains data about historical or planned visits and procedures.

Appendix B - Transaction Descriptions

Transactions are interactions between actors that transfer the required information through standards-based messages. The PCC Technical Framework does not define any specific transactions, as these are assumed to be carried out through the use of transactions defined in other IHE Profiles.

Transaction Definitions

Transactions are interactions between actors that transfer the required information through standards-based messages.

Query Vital Signs
Request information about recent patient measurements, usually used to obtain vital signs measurements. The query may request all measurements, or those taken for a specific encounter, or date range, or may be for a specific set of measurements.
Query Problems and Allergies
Request information about problems or allergies known for a patient, usually to determine the patients current problems and allergies. The query may request information about all problems, all allergies, or may request information on a specific problem or allergy entry, entered during a specific encounter or date range.
Query Diagnostic Data
Request information about diagnostic results known for a patient. The query may request information about all diagnostic results, or may request information on a specific diagnostic result entry, or one entered for a specific encounter or date range.
Query Medications
Request information about medications given to, or being taken by a patient. The query may request information about all medications or may request information on a specific kind of medication or immunization, or one entered for a specific encounter or date range.
Query Immunizations
Request information about immunizations given to a patient. The query may request information about all immunizations, all immunizations or may request information on a specific kind of medication or immunization, or one entered for a specific encounter or date range.
Query Professional Services
Request information about procedures or visits relevant for a patient. The query may request information about procedures or visits, or may request information on a specific procedure or type of visit, or one entered for a specific encounter or date range.

Appendix C - How to Prepare an IHE Integration Statement

IHE Integration Statements are documents prepared and published by vendors to describe the conformance of their products with the IHE Technical Framework. They identify the specific IHE capabilities a given product supports in terms of IHE actors and integration profiles described in the technical frameworks of each domain.

Users familiar with these concepts can use Integration Statements to determine what level of integration a vendor asserts a product supports with complementary systems and what clinical and operational benefits such integration might provide. Integration Statements are intended to be used in conjunction with statements of conformance to specific standards (e.g., HL7, IETF, DICOM, W3C, etc.).

IHE provides a process for vendors to test their implementations of IHE actors and integration profiles. The IHE testing process, culminating in a multi-party interactive testing event called the Connectathon, provides vendors with valuable feedback and provides a baseline indication of the conformance of their implementations. The process is not intended to independently evaluate, or ensure, product compliance. In publishing the results of the Connectathon and facilitating access to vendors' IHE Integration Statements, IHE and its sponsoring organizations are in no way attesting to the accuracy or validity of any vendor's IHE Integration Statements or any other claims by vendors regarding their products.

IMPORTANT -- PLEASE NOTE: Vendors have sole responsibility for the accuracy and validity of their IHE Integration Statements. Vendors' Integration Statements are made available through IHE simply for consideration by parties seeking information about the integration capabilities of particular products. IHE and its sponsoring organizations have not evaluated or approved any IHE Integration Statement or any related product, and IHE and its sponsoring organizations shall have no liability or responsibility to any party for any claims or damages, whether direct, indirect, incidental or consequential, including but not limited to business interruption and loss of revenue, arising from any use of, or reliance upon, any IHE Integration Statement.


Structure and Content of an IHE Integration Statement

An IHE Integration Statement for a product shall include:

  1. The Vendor Name
  2. The Product Name (as used in the commercial context) to which the IHE Integration Statement applies.
  3. The Product Version to which the IHE Integration Statement applies.
  4. A publication date and optionally a revision designation for the IHE Integration Statement.
  5. The following statement: "This product implements all transactions required in the IHE Technical Framework to support the IHE Integration Profiles, Actors and Options listed below:"
  6. A list of IHE Integration Profiles supported by the product and, for each Integration Profile, a list of IHE Actors supported. For each integration profile/actor combination, one or more of the options defined in the IHE Technical Framework may also be stated. Profiles, Actors and Options shall use the names defined by the IHE Technical Framework Volume I. (Note: The vendor may also elect to indicate the version number of the Technical Framework referenced for each Integration Profile.)

Note that implementation of the integration profile implies implementation of all required transactions for an actor as well as selected options.

The statement shall also include references and/or internet links to the following information:

  1. Specific internet address (or universal resource locator [URL]) where the vendor's Integration Statements are posted
  2. URL where the vendor's standards conformance statements (e.g., HL7, DICOM, etc.) relevant to the IHE transactions implemented by the product are posted.
  3. URL of the IHE Initiative's web page for general IHE information www.himss.org/ihe.

An IHE Integration Statement is not intended to promote or advertise aspects of a product not directly related to its implementation of IHE capabilities.

Format of an IHE Integration Statement

Each Integration Statement shall follow the format shown below. Vendors may add a cover page and any necessary additional information in accordance with their product documentation policies.

IHE Integration Statement Date 12 Oct 2005
Vendor Product Name Version
Any Medical Systems Co. IntegrateRecord V2.3
This product implements all transactions required in the IHE Technical Framework to support the IHE Integration Profiles, Actors and Options listed below:
Integration Profiles Implemented Actors Implemented Options Implemented
Cross-Enterprise Sharing of Medical Summaries Document Consumer View Option
Audit Trail and Node Authentication Secure Node none
Patient Identity Cross-referencing Patient Identifier Cross-reference Consumer PIX Update Notification
Internet address for vendor's IHE information:www.anymedicalsystemsco.com/ihe
Links to Standards Conformance Statements for the Implementation
HL7 www.anymedicalsystemsco.com/hl7
Links to general information on IHE
In North America: www.ihe.het In Europe: www.ihe-europe.org In Japan: www.jira-net.or.jp/ihe-j

IHE Integration Statement template

An IHE Integration Statement template (MS Word version) is available here.

The IHE Product Registry

The assumption of an integration statement is that all actors listed are functionally grouped and conform to any profile specifications for such groupings. In case of exceptions the vendor must explicitly describe the functional groupings.

IHE has developed a new Web-based database of Integration Statements. The IHE Product Registry enables developers to create, manage and publish Integration Statements for their commercial and open source healthcare IT systems. It allows users to browse for these systems based on their conformance with specific IHE Actors and Profiles. The system is open for use by developers and users now!

Appendix D - Braden Scale for Predicting Pressure Sore Risk

See File:Braden.pdf

Glossary

The following terms are used in various places within this technical framework, and are defined below. The complete IHE Glossary is available on the IHE Wiki at http://wiki.ihe.net/index.php/IHE_Glossary .

Actor
An entity within a use case diagram that can perform an action within a use case diagram. Possible actions are creation or consumption of a message
Acuity Assessment

Also known as triage category, this is the acuity of the patient assigned during the process of ED triage. A number of evidenced based triage scales exist, including the Emergency Severity Index (ESI), Canadian Triage and Acuity Scale (CTAS), the Australasian Triage Scale (ATS), and the Manchester Triage System. In many emergency departments, patients may simply be classified as emergent, urgent or non-urgent.

ADT
Admit, Discharge & Transfer.
Affinity Domain Policy
Affinity Domain Policy that clearly defines the appropriate uses of the XDS Affinity Domain. Within this policy is a defined set of acceptable use Privacy Consent Policies that are published and understood.
ASTM
Formerly the American Society of Testing and Materials, now ASTM International. An SDO that develops a number of standards across a wide variety of industries, including healthcare.
ATNA
Audit Trail and Node Authentication. An IHE ITI profile.
Care Context
The participations surrounding the care provision act, and the attributes of that act. Everything in the document header. Data history, links to clinical reasoning.
Continuity of Care Document(CCD)
An HL7 Clinical Document Architecture (CDA) implementation alternative to ASTM ADJE2369 for institutions or organizations committed to HL7 standards. This specification was developed as a collaborative effort between ASTM and HL7. More information is available from http://www.hl7.org.
Continuity of Care Record (CCR)
A core data set of the most relevant administrative, demographic, and clinical information facts about a patient’s healthcare, covering one or more encounters. The CCR is Designation E2369-05 of the ASTM (American Society for Testing and Materials, International). More information is available from http://www.astm.org.
Clinical Document Architecture (CDA)
An HL7 standard for the exchange for clinical documents. It specifies the structure and semantics of clinical documents. More information is available from http://www.hl7.org.
Content Binding
A content binding describes how the payload used in an IHE transaction is related to and/or constrained by the data elements contained within the content sent or received in those transactions.
CRS
Care Record Summary. An implementation guide that constrains CDA Release 2 for Care Record Summary documents.
CT
Consistent Time Integration Profile.
DICOM
Digital Imaging and Communication in Medicine
DSG
Digital Signatures. An IHE ITI Profile.
EDIS
An Emergency Department Information System (EDIS) is an extended EHR system used to manage data in support of Emergency Department patient care and operations. The functions of an EDIS may be provided by a single application or multiple applications.
eMPI
Enterprise Master Patient Index.
EMR
Electronic Medical Record, an Electronic Health Record system used within an enterprise to deliver care (also called EHR-CR by IHE-XDS).
Estimated Time of Arrival
the time the patient being referred can be expected to arrive in the emergency department.
EUA
Enterprise User Authentication Integration Profile.
Expected Actions
Actions which should occur as the result of a trigger event.
HIMSS
Healthcare Information and Management Systems Society.
HL7
Health Level Seven
HIS
Hospital Information System.
IHE
Integrating the Healthcare Enterprise.
Interaction Diagram
A diagram that depicts data flow and sequencing of events.
IT
Information Technology.
Logical Observation Identifiers Names and Codes (LOINC®)
A vocabulary developed by the Regenstrief Institute aimed at standardizing laboratory and clinical codes for use in clinical care, outcomes management, and research. Additional information found at http://www.regenstrief.org/medinformatics/loinc/.
Mode of Arrival
The method of transportation used to transport the patient to the Emergency Department.
MPI
Master Patient Index.
MRN
Medical Record Number.
NAV
Notification of Document Availability
OID
Object Identifier. (See also 'Globally Unique Identifier').
Patient Identifier Cross-reference Domain
Consists of a set of Patient Identifier Domains known and managed by a Patient Identifier Cross-reference Manager Actor. The Patient Identifier Cross-reference Manager Actor is responsible for providing lists of "alias" identifiers from different Patient Identifier Domains.
Patient Identifier Domain
A single system or a set of interconnected systems that all share a common identification scheme for patients. Such a scheme includes: (1) a single identifier-issuing authority, (2) an assignment process of an identifier to a patient, (3) a permanent record of issued patient identifiers with associated traits, and (4) a maintenance process over time. The goal of Patient Identification is to reduce errors.
PDF
Portable Document Format.
PIX
Patient Identifier Cross Referencing. An IHE ITI Profile.
PDQ
Patient Demographics Query. An IHE ITI Profile.
PHR
Personal Health Record
Procedure
In the context of a "Pre-procedure History and Physical," the "procedure" is a surgery or an invasive examination of a patient that is required by quality review organizations to be preceded by a pre-procedure assessment of procedure risk and anesthesia risk. This assessment is typically referred to as a "Pre-operative" or "Pre-procedure History and Physical."
Process Flow Diagram
A graphical illustration of the flow of processes and interactions among the actors involved in a particular example.
Proposed disposition
the intended disposition (i.e. admission to ICU, discharge to home, transfer to psychiatric hospital), if known, that the referring provider expects the patient will end up after the emergency department intervention.
Referral Source
An individual, group, or agency that determined the patient should seek care at the ED. Referral source may be used to determine appropriate discharge referrals and services, or to provide surveillance data for program and service planning, or to examine referral patterns.
Role
The actions of an actor in a use case.
RSNA
Radiological Society of North America.
sig.
A Latin abbreviation for signetur used to represent the instruction following the medication name.
Scope
A brief description of the transaction.

SNOMED-CT® A comprehensive clinical terminology, originally created by the College of American Pathologists (CAP) and, as of April 2007, owned, maintained, and distributed by the International Health Terminology Standards Development Organisation (IHTSDO), a non-for-profit association in Denmark. The CAP continues to support SNOMED CT operations under contract to the IHTSDO and provides SNOMED-related products and services as a licensee of the terminology. More information available from http://www.ihtsdo.org/ or the United States National Library of Medicine at http://www.nlm.nih.gov/research/umls/Snomed/snomed_main.html

Transport Mode
the method the patient employs, or is provided to get to the emergency department.
Trigger Event
An event such as the reception of a message or completion of a process, which causes another action to occur.
UID
Unique Identifier (See also Globally Unique Identifier).
Universal ID
Unique identifier over time within the UID type. Each UID must belong to one of specifically enumerated species. Universal ID must follow syntactic rules of its scheme.
Use Case
A graphical depiction of the actors and operation of a system.
XUA
Cross Enterprise User Authentication
XDS
Cross Enterprise Document Sharing
Retrieved from "http://wiki.ihe.net/index.php?title=PCC_TF-1/Trailer&oldid=8842"