# ZTFOBJECT

ZKEYWORD: ALRM_MGR
ZNAME: Alarm Manager
ZTFDESCRIPTION:
  The Alarm Manager (AM) actor receives the alarm from the Alarm Reporter (AR), potentially analyzes the alarm, and dispatches the alarm to the Alarm Communicator (AC).


ZKEYWORD: ACM
ZNAME: Alarm Communication Management
ZTFDESCRIPTION:
  The Alarm Communication Management integration profile defines the communication of alarms from alarm source systems to alarm management systems and from alarm management systems to alarm historical systems.


ZKEYWORD: ALRM_ARCHIVER
ZNAME: Alarm Archiver
ZTFDESCRIPTION:
  The Alarm Archiver (AA) actor sends alarm subscription requests to the AM actor and receives report alarm responses from the AM actor.


ZKEYWORD: ALRM_COMMUNICATOR
ZNAME: Alarm Communicator
ZTFDESCRIPTION:
  The Alarm Communicator  (AC) actor receives the alarm from the Alarm Manager (AM) and sends the alarm to the client application in the endpoint device.


ZKEYWORD: APR
ZNAME: Antepartum Record
ZTFDESCRIPTION:
  The Antepartum Record Profile (APR) extends the description of the content structures for the Antepartum Summary (APS), and is based on the data elements from prenatal records currently in common use.


ZKEYWORD: OF
ZNAME: Department System Scheduler/Order Filler
ZTFDESCRIPTION:
  A department-based information system (for instance, Radiology or Laboratory) that provides functions related to the management of orders received from external systems or through the department system s user interface. Upon a defined workflow action, makes procedures available for charge posting. The action/event that actually causes charges to post is defined by the actor.


ZKEYWORD: APW
ZNAME: Pathology Workflow
ZTFDESCRIPTION:
  The Pathology Workflow Integration Profile establishes the continuity and integrity of basic pathology data acquired for examinations being ordered for an identified inpatient or outpatient


ZKEYWORD: IM
ZNAME: Image Manager/Archive
ZTFDESCRIPTION:
  A system that provides functions related to safe data storage and image data handling. It supplies image availability information to the Department System Scheduler. It is always grouped with an Image Archive to provide long term storage of images, presentation states, Key Image Notes, and Evidence Documents.


ZKEYWORD: ORT
ZNAME: Order Result Tracker
ZTFDESCRIPTION:
  A hospital or enterprise-wide system that stores observations of various types (test results, images, clinical examinations reports, radiology reports, surgical act reports) obtained for the patients, registers all state changes in the results notified by Order Fillers. This actor doesnt store standalone observations, but ordered observations. The observations are always stored within the context of the order that generated them, with all the information related to that order.


ZKEYWORD: EC
ZNAME: Evidence Creator
ZTFDESCRIPTION:
  A system that creates additional evidence objects such as images, presentation states, Key Image Notes, and/or Evidence Documents and transmits them to an Image Archive. It also makes requests for storage commitment to the Image Manager for the data previously transmitted. It may also retrieve worklist entries for post-processing steps from the Post-Processing Manager and provide notification of completion of the step, allowing the enterprise to track the status of post-processing work.


ZKEYWORD: ID
ZNAME: Image Display
ZTFDESCRIPTION:
  A part of a system that can access imaging evidence objects (images, Presentation States, Key Image Notes, Evidence Documents) through network query/retrieve or reading interchange media and allow the user to view these objects.


ZKEYWORD: OP
ZNAME: Order Placer
ZTFDESCRIPTION:
  A hospital or enterprise-wide system that generates orders for various departments and distributes those orders to the correct department.


ZKEYWORD: MOD
ZNAME: Acquisition Modality
ZTFDESCRIPTION:
  A system that acquires and creates medical images, e.g. a Computed Tomography scanner or Nuclear Medicine camera. A modality may also create Grayscale Softcopy Presentation States for the consistent viewing of images and create Key Image Notes.


ZKEYWORD: XRA
ZNAME: External Report Repository Access
ZTFDESCRIPTION:
  A system that performs retrieval of clinical reports containing information generated outside the Radiology department and presented as DICOM Structured Reporting Objects.


ZKEYWORD: ARI
ZNAME: Access to Radiology Information
ZTFDESCRIPTION:
  The Access to Radiology Information Integration Profile specifies a number of query transactions providing access to radiology information, including images and related reports, in a DICOM format as they were acquired or created. Such access is useful both to the radiology department and to other departments such as pathology, surgery and oncology. Non-radiology information (such as lab reports) may also be accessed if made available in DICOM format.


ZKEYWORD: RRD
ZNAME: Report Reader
ZTFDESCRIPTION:
  A part of a system that can access reports through network query/retrieve or reading interchange media and allow the user to view reports presented as DICOM Structured Report Objects.


ZKEYWORD: RRP
ZNAME: Report Repository
ZTFDESCRIPTION:
  A system that provides long-term storage of reports and their retrieval as DICOM Structured Reporting Objects.


ZKEYWORD: SN
ZNAME: Secure Node
ZTFDESCRIPTION:
  A system unit that validates the identity of any user and of any other node, and determines whether or not access to the system for this user and information exchange with the other node is allowed. Maintains the correct time.


ZKEYWORD: ATNA
ZNAME: Audit Trail and Node Authentication
ZTFDESCRIPTION:
  The ITI Audit Trail and Node Authentication (ATNA) Profile establishes the characteristics of a Basic Secure Node: It describes the security environment (user identification, authentication, authorization, access control, etc.) assumed for the node so that security reviewers may decide whether this matches their environments. It defines basic security requirements for the communications of the node using TLS or equivalent functionality. It defines basic auditing requirements for the node. The profile also establishes the characteristics of the communication of audit messages between the Basic Secure Nodes and Audit Repository nodes that collect audit information. 


ZKEYWORD: SA
ZNAME: Secure Application
ZTFDESCRIPTION:
  The difference between the Secure Node and the Secure Application is the extent to which the underlying operating system and other environment are secured.  A Secure Node includes all aspects of user authentication, file system protections, and operating environment security.  The Secure Application is a product that does not include the operating environment.  The Secure Application provides security features only for the application features.  See section 9.7 for the relationships among a Secure Node, Secure Application, and other actors.


ZKEYWORD: BPPC
ZNAME: Basic Patient Privacy Consents
ZTFDESCRIPTION:
  provides a mechanism by which an affinity domain can create a basic vocabulary of codes that identify affinity domain privacy consent policies with respect to information sharing


ZKEYWORD: DOC_SOURCE
ZNAME: Document Source
ZTFDESCRIPTION:
  The Document Source Actor is the producer and publisher of documents. It is responsible for sending documents to a Document Repository Actor. It also supplies metadata to the Document Repository Actor for subsequent registration of the documents with the Document Registry Actor.


ZKEYWORD: DOC_RECIPIENT
ZNAME: Document Recipient
ZTFDESCRIPTION:
   A system that receives a set of documents sent by another actor. Typically this document set will be made available to the intended recipient who will choose to either view it or integrate it into the Electronic Healthcare Record (EHR)


ZKEYWORD: PMI
ZNAME: Portable Media Importer
ZTFDESCRIPTION:
  This actor reads the DICOM information (DICOM FSR) contained on the media. This system provides the user the ability to select a set of DICOM instances and reconcile key patient and study attributes (when necessary) to facilitate inclusion of the imported data in the local information system(s).


ZKEYWORD: DOC_CONSUMER
ZNAME: Document Consumer
ZTFDESCRIPTION:
  The Document Consumer Actor queries a Document Registry Actor for documents meeting certain criteria, and retrieves selected documents from one or more Document Repository actors.


ZKEYWORD: EMBED_REPOS
ZNAME: Integrated Document Source/Repository
ZTFDESCRIPTION:
  The Integrated Document Source/Repository is an XDS combination of Document Source and Document Repository that does not expose the interface between the Source and Repository. That is, this Source only publishes documents to its own Repository. It does register documents with a Document Registry


ZKEYWORD: C105
ZNAME: Patient Level Quality Data Document Using HL7 Quality Reporting Document Architecture (QRDA)
ZTFDESCRIPTION:
  The HITSP Patient Level Quality Data Document Using HL7 Quality Reporting Document Architecture Component supports the communication of patient level quality data for quality measurement in a document sharing environment. Patient encounter data are compiled from both the local systems and from longitudinal data available through a Health Information Exchange (HIE) prior to communicating the retrieved data described in this construct for analysis. View the most current version as HTML here.


ZKEYWORD: C106
ZNAME: Measurement Criteria Document
ZTFDESCRIPTION:
  This Component supports communication of a quality measure (aka an "eMeasure"). Clinical concepts (e.g. "atrial fibrillation", "coronary artery disease") and parameters (e.g. "numerator", "denominator") in an eMeasure are formally defined to support consistent and unambiguous interpretation. The eMeasure is standardized as a structured document, where one can capture the complete narrative of the measureand a formalized computable representation of statements. View the most current version as HTML here


ZKEYWORD: C151
ZNAME: Clinical Research Document
ZTFDESCRIPTION:
  US HITSP: C151 Clinical Research Document. Defines the HITSP constraints applied to the IHE Quality, Research and Public Health (QRPH) Technical Framework Supplement 10 - Clinical Research Data Capture (CRD). The purpose of this IHE profile is to support a standard set of data in CCD format which the Form Filler provides for use in Clinical Research. In addition this profile references the ability to convert this output into a standard case report form, a Clinical Research Document


ZKEYWORD: C19
ZNAME: HITSP Entity Identity Assertion Component
ZTFDESCRIPTION:
  US HITSP: C19 Entity Identity Assertion Component. The Entity Identity Assertion Component provides the mechanisms to ensure that an entity is the person or application that claims the identity provided. An example of this Component is the validation and assertion of a consumer logging on to a Personal Health Record (PHR) system.


ZKEYWORD: C25
ZNAME: HITSP Anonymize Component
ZTFDESCRIPTION:
  HITSP Anonymize Component. The Anonymize Component provides specific instruction for anonymizing data that are prepared for repurposing data created as part of routine clinical care delivery. This construct defines the Component specification that provides the ability to anonymize patient identifiable information.


ZKEYWORD: C26
ZNAME: HITSP Nonrepudiation of Origin Component
ZTFDESCRIPTION:
  US HITSP: C26: Nonrepudiation of Origin Component. The Nonrepudiation of Origin Component provides the mechanisms to support Nonrepudiation of Origin, which refers to both the proof of the integrity and origin of documents in a high-assurance manner, which can be verified by any party. This Component does not provide Nonrepudiation of Receipt.


ZKEYWORD: C28
ZNAME: HITSP Emergency Encounter Summary Documents Component
ZTFDESCRIPTION:
  US HITSP: C28: Emergency Encounter Summary Documents Component. The Emergency Care Summary Document Using IHE Emergency Department Encounter Summary (EDES) Component is the collection of data from multiple sources (such as physicians, nurses, technologists, etc.) recording the assessments and care delivered by the ED team in response to an ED visit. It is a summary of the patient’s current health status and care tendered in the ED between arrival and ED departure. This Component specifies the use of the IHE Emergency Department Encounter Summary (EDES).


ZKEYWORD: C32
ZNAME: Registration and Medication History Document Component
ZTFDESCRIPTION:
  US HITSP: C32: Registration and Medication History Document Component. The Registration and Medication History Document Content Component describes the document content summarizing a consumer’s registration, medication and health data information contained within a Personal Health Record (PHR) for the purpose of information exchange. This component only deals with the exchange of summary information to and from the PHR.


ZKEYWORD: C34
ZNAME: HITSP Patient Level Quality Data Message Component
ZTFDESCRIPTION:
  The Patient Level Quality Data Message Component supports the process of sending patient data from a Quality Message Sender to a Quality Message Receiver for further analysis and aggregation. Patient data are captured as part of the normal process of care performed by healthcare providers such as hospitals, emergency departments and outpatient clinics.


ZKEYWORD: C35
ZNAME: HITSP EHR Lab Result Terminology Component
ZTFDESCRIPTION:
  The Lab Result Terminology Component defines the vocabulary for either message-based or document-based laboratory results reporting.


ZKEYWORD: C36
ZNAME: Lab Result Message Component
ZTFDESCRIPTION:
  US HITSP: C36: Lab Result Message Component. The Lab Result Message Component describes the use of a constrained Health Level Seven (HL7) Version 2.5.1 ORU – Unsolicited Observation Message for electronic laboratory results reporting.


ZKEYWORD: C37
ZNAME: Lab Report Document Component
ZTFDESCRIPTION:
  US HITSP: C37: Lab Report Document Component. The Lab Report Document Component prescribes the use of the standard Clinical Document Architecture Release 2 (CDA R2), as in the HL7 V3 2006 normative edition profiled by IHE LAB TF-3 for: transmission of complete, preliminary, final and updated laboratory results to the EHR system (local or remote) of the ordering clinician; transmission of complete, preliminary, final and updated (or notification) to the EHR system (local or remote) or other clinical data system of designated providers of care (with respect to a specific patient); transmission of laboratory result data from electronically enabled healthcare delivery and public health systems in standardized and anonymized format to authorized Public Health Agencies with less than one day lag time.


ZKEYWORD: C38
ZNAME: C38 Patient Level Quality Document Using IHE Medical Summary (XDS-MS)
ZTFDESCRIPTION:
  US HITSP: C38: Patient Level Quality Document Using IHE Medical Summary (XDS-MS). The Patient Level Quality Data Document Using IHE Medical Summary (XDS-MS) Component supports the communication of patient level quality data for quality measurement in a document sharing environment. The HITSP Patient Level Quality Data Document Using IHE Medical Summary (XDS-MS) Component constrains the IHE Medical Summary to support the communication of quality data for analysis and measurement. The specification includes constraints of location and vocabulary.


ZKEYWORD: C39
ZNAME: HITSP Encounter Message Component
ZTFDESCRIPTION:
  The Encounter Message Component supports the process of sending patient encounter data (excluding laboratory, radiology) from a Biosurveillance Message Sender to a Biosurveillance Message Receiver.


ZKEYWORD: C41
ZNAME: HITSP Radiology Result Message Component
ZTFDESCRIPTION:
  The Radiology Result Message Component supports the process of sending radiology result data from a Biosurveillance Message Sender to a Biosurveillance Message Receiver. Radiology result data are captured as part of the normal process of care performed by healthcare providers.


ZKEYWORD: C44
ZNAME: HITSP Secure Web Connection Component
ZTFDESCRIPTION:
  The Secure Web Connection Component provides the capability to access documents through a secure web browser.


ZKEYWORD: C47
ZNAME: HITSP Resource Utilization Message Component
ZTFDESCRIPTION:
  The Resource Utilization Component specifies the message and content necessary to report utilization and status of health provider resources to public health agencies. This specification reflects the current status of harmonization efforts between HL7 and OASIS.


ZKEYWORD: C48
ZNAME: HITSP Encounter Document Using IHE Medical Summary (XDS-MS)
ZTFDESCRIPTION:
  US HITSP: C48: Encounter Document Using IHE Medical Summary. The Encounter Document Using IHE Medical Summary (XDS-MS) Component supports the process of sending patient encounter data (excluding laboratory and radiology) in a document sharing functional flow scenario. Patient encounter data are captured as part of the normal process of care performed by healthcare providers, such as hospitals, emergency departments and outpatient clinics.


ZKEYWORD: C62
ZNAME: HITSP XDS-SD
ZTFDESCRIPTION:
  US HITSP: T62: XDS-SD. The Unstructured Document Component is provided for the capture and storage of patient identifiable, unstructured document content, such as text, PDF, and images rendered in PDF. It is based on the Cross-Enterprise Sharing of Scanned Documents (XDS-SD) profile from the Integrating the Healthcare Enterprise (IHE) IT Infrastructure Technical Framework (ITI-TF). View the most current version as HTML here.


ZKEYWORD: C70
ZNAME: Immunization Query and Response
ZTFDESCRIPTION:
  The Immunization Query and Response Component is used for a message based exchange of immunization information.  It specifies the use of HL7 Version 2.3.1 Query for Vaccination Record (VXQ), to send a query from the message sender (clinician system, schools, IIS) to the message receiver (immunization registry). View the most current version as HTML here.


ZKEYWORD: C72
ZNAME: HITSP Vaccination Message
ZTFDESCRIPTION:
  US HITSP: C72: Vaccination Message. The Immunization Message Component provides the capability to communicate an update to a patient's vaccination record. It is based upon the Centers for Disease Control and Prevention Implementation Guide for Immunizations Data Transaction using Version 2.3.1 of the Health Level Seven (HL7) Standard Protocol Implementation Guide Version 2.2 June 2006. View the most current version as HTML here


ZKEYWORD: C74
ZNAME: Remote Monitoring Observation Document Component
ZTFDESCRIPTION:
  The Remote Monitoring Observation Document Component describes the document content to convey medical information collected by remote monitoring management systems from monitorng devices and/or device intermediaries for the purpose of information exchange. The content may include administrative (e.g., registration, demographics, insurance, etc.) and clinical (results, vital signs, etc) information. This specification defines content in order to promote interoperability between participating systems. Such systems may include Remote Monitoring Management Systems, Personal Health Record Systems (PHRs), Electronic Health Record Systems (EHRs), Health Information Exchange infrastructure services and other persons and systems as identified and permitted. View the most current version as HTML here.


ZKEYWORD: C75
ZNAME: Healthcare Associated Infection (HAI) Report Component
ZTFDESCRIPTION:
  The Healthcare Associated Infection (HAI) Report Component specifies a standard for electronic submission of Healthcare Associated Infection (HAI) Reports to the National Healthcare Safety Network (NHSN) of the Centers for Disease Control and Prevention (CDC). HITSP has adopted the HL7 Implementation Guide for CDA Release 2: NHSN Healthcare Associated Infection (HAI) Reports, Release 1 for this construct. View the most current version as HTML here.


ZKEYWORD: C76
ZNAME: HITSP Case Report Pre-populate
ZTFDESCRIPTION:
  US HITSP: C76: Case Report Pre-populate. The Case Report Pre-Populate Component supports the Data Mapping needed for Public Health Case Reports. Initially the Component supports only those data attributes that are universal or pertain to Drug Safety reporting. For those attributes that are universal in case reporting, this component may be used in support of pre-populating the remaining report types. However, other public health specific attributes will be addressed in subsequent releases. View the most current version as HTML here.


ZKEYWORD: C78
ZNAME: HITSP Immunization Content
ZTFDESCRIPTION:
  US HITSP: C78: Immunization Content. The Immunization Document Component defines the immunization data content to be exchanged between healthcare entities such as immunization information systems, electronic medical records systems, personal healthcare record systems and other stakeholders. It is based upon the IHE Patient Care Coordination (PCC) Technical Framework Supplement 2008-2009, Immunization Content (IC), Trial Implementation Version 1.0. View the most current version as HTML here.


ZKEYWORD: C82
ZNAME: HITSP Common Alerting Protocol
ZTFDESCRIPTION:
  US HITSP: C82: Common Alerting Protocol. The Emergency Common Alerting Protocol Component selects the OASIS Common Alerting Protocol (CAP) v1.1 standard, and is used as a multicast notification message sent to an identified channel. The intended recipients are populations such as “all emergency departments in XXX county”, “within a geographic area”, etc. View the most current version as HTML here.


ZKEYWORD: C83
ZNAME: CDA Content Modules Component
ZTFDESCRIPTION:
  The CDA Content Modules Component defines the content modules for document based HITSP constructs utilizing clinical information. These Content modules are based on IHE PCC Technical Framework Volume II, Release 4. That technical framework contains specifications for document sections that are consistent with all implementation guides for clinical documents currently selected for HITSP constructs. View the most current version as HTML here.


ZKEYWORD: C84
ZNAME: Consult and History & Physical Note Component
ZTFDESCRIPTION:
  The Consult and History & Physical Note Component supports two types of commonly used clinical notes, a consult note, and a history and physical note. It is intended for use to support the exchange of information from a consulting provider to a referring provider; and may also be used to provide background information from a referring provider to a consulting provider (e.g., prior reports). View the most current version as HTML here.


ZKEYWORD: C87
ZNAME: Anonymize Public Health Case Reporting Data Component
ZTFDESCRIPTION:
  The Anonymize Public Health Case Reporting Data Component provides specific instructions for anonymizing data that was created as part of routine clinical care data delivery in preparation for repurposing data for public health case reporting. This construct defines the Component specification that provides the ability to anonymize patient identifiable information. Anonymization, according to the International Organization for Standardization (ISO), is the process that removes the association between the identifying data set and the data subject. View the most current version as HTML here.


ZKEYWORD: C88
ZNAME: Anonymize Immunizations and Response Management Data Component
ZTFDESCRIPTION:
  The Anonymize Immunizations and Response Management Data Component provides the ability to anonymize patient identifiable information for Immunization and Response Management. It provides specific instruction for anonymizing data that was created as part of routine clinical care delivery in preparation for repurposing the data . Anonymization, according to the International Organization for Standardization (ISO), is the process that removes the association between the identifying data set and the data subject. View the most current version as HTML here.


ZKEYWORD: CATH
ZNAME: Cardiac Catheterization Workflow
ZTFDESCRIPTION:
  The Cardiac Catheterization Workflow Integration Profile establishes the continuity and integrity of basic patient data in the context of the cardiac catheterization procedure. This profile deals specifically with consistent handling of patient identifiers and demographic data, including that of emergency patient presentation where the actual patient identity may not be established until after the beginning of the procedure, or even a significant time after the completion of the procedure. It also specifies the scheduling and coordination of procedure data across a variety of imaging, measurement, and analysis systems, and its reliable storage in an archive from where it is available to support subsequent workflow steps, such as reporting. It also provides central coordination of the completion status of steps of a potentially multi-phase (diagnostic and interventional) procedure.


ZKEYWORD: ADT
ZNAME: ADT Patient Registration
ZTFDESCRIPTION:
  A system responsible for adding and/or updating patient demographic and encounter information. In particular, it registers a new patient with the Order Placer and Department System.


ZKEYWORD: PPSM
ZNAME: Performed Procedure Step Manager
ZTFDESCRIPTION:
  A system that re-distributes the Modality Performed Procedure Step information from the Acquisition Modality or Image Creator to the Department System Scheduler/Order Filler and Image Manager.


ZKEYWORD: CHG
ZNAME: Charge Posting
ZTFDESCRIPTION:
  The Charge Posting Integration Profile specifies the exchange of information from the Department System Scheduler/Order Filler actor to the Charge Processor actor regarding charges associated with particular procedures, as well as communication between the ADT/Patient Registration and Charge Processor actors about patient demographics, accounts, insurance, and guarantors. The Charge Posted Transaction contains all of the required procedure data to generate a claim. Currently, these interfaces contain fixed field formatted or HL7-style data. The goal of including this transaction in the IHE Technical Framework is to standardize the Charge Posted Transaction to a Charge Processor, thus reducing system interface installation time between clinical systems and Charge Processors. Additionally, the Charge Posted Transaction reduces the need of the billing system to have knowledge of the radiology internals. The result is that the Charge Processor will receive more complete, timely and accurate data.


ZKEYWORD: IMPORTER
ZNAME: Importer
ZTFDESCRIPTION:
  A system that imports evidence documents such as images, presentation states, Key Image Notes or Evidence Documents from hardcopy or digital media.


ZKEYWORD: CHARGE_PRO
ZNAME: Charge Processor
ZTFDESCRIPTION:
  Receives the posted charges and serves component of the financial system. Further definition of this actor is beyond current IHE scope.


ZKEYWORD: PPM
ZNAME: Post-Processing Manager
ZTFDESCRIPTION:
  A system that provides functions related to post-processing worklist management. This involves the ability to schedule post-processing worklist items (scheduled procedure steps), provide worklist items to post-processing worklist clients, and update the status of scheduled and performed procedure steps as received from post-processing worklist clients.


ZKEYWORD: RM
ZNAME: Report Manager
ZTFDESCRIPTION:
  A system that provides functions related to report management. This involves the ability to handle content and state changes to reports and to create new DICOM Structured Reporting Objects based on these changes. In addition, the Report Manager generates and transmits verified, unsolicited text results to the Enterprise Report Repository.


ZKEYWORD: GUIDELINE_MGR
ZNAME: Guideline Manager
ZTFDESCRIPTION:
  The guideline manager actor is responsible for managing the guidelines used to create care plans, and for communicating those guidelines to other systems.


ZKEYWORD: CM
ZNAME: Care Management
ZTFDESCRIPTION:
  The Care Management Profile  provides a mechanism for EHR and other HIT systems to communicate information to Care Management systems in support of specialized care programs through the use of evidence based guidelines.


ZKEYWORD: CARE_MGR
ZNAME: Care Manager
ZTFDESCRIPTION:
  The care manager actor is responsible for supporting the management of the care of patients with respect to a specific health condition. It gathers information about the care provided and current health status of the patient. A Care Manager actor may be designed for management of a single condition, such as management of Diabetes, or may be a general purpose system supporting management of multiple conditions.


ZKEYWORD: CLIN_DATA_SOURCE
ZNAME: Clinical Data Source
ZTFDESCRIPTION:
  A Clinical Data Sources maintains patient information about vital  signs, problem and allergies, results from diagnostic tests (e.g., Lab, Imaging, or other test results), medications, immunizations or historical or planned visits and procedures.


ZKEYWORD: CPI
ZNAME: Consistent Presentation of Images
ZTFDESCRIPTION:
  The Consistent Presentation of Images Integration Profile specifies a number of transactions that maintain the consistency of presentation for grayscale images and their presentation state information (including user annotations, shutters, flip/rotate, display area, and zoom). It also defines a standard contrast curve, the Grayscale Standard Display Function, against which different types of display and hardcopy output devices can be calibrated. It thus supports hardcopy, softcopy and mixed environments.


ZKEYWORD: PS
ZNAME: Print Server
ZTFDESCRIPTION:
  A system that accepts and processes DICOM print requests as a DICOM Print SCP and performs image rendering on hardcopy media. The system must support pixel rendering according to the DICOM Grayscale Standard Display Function.


ZKEYWORD: PC
ZNAME: Print Composer
ZTFDESCRIPTION:
  A system that generates DICOM print requests to the Print Server. Print requests include presentation state information in the form of Presentation Look-Up Tables (Presentation LUTs). It may also read the DICOM information contained on interchange media.


ZKEYWORD: CRD
ZNAME: Clinical Research Data Capture
ZTFDESCRIPTION:
  CRD describes the content and format to be used within the Prepopulation Data transaction described within the RFD Integration Profile. The purpose of this profile is to support a standard set of data in CCD format which the Form Filler provides for use in Clinical Research. In addition this profile will reference the ability to convert this output into a standard case report form (Standard CRF) consisting of ODM and CDASH.


ZKEYWORD: FORM_FILLER
ZNAME: Form Filler
ZTFDESCRIPTION:
  The actor responsible for retrieving a form from a Form Manager, and for submitting form instance data to a Form Receiver.


ZKEYWORD: TIME_CLIENT
ZNAME: Time Client
ZTFDESCRIPTION:
  Establishes time synchronization with one or more Time Servers using the NTP protocol and either the NTP or SNTP algorithms.  Maintains the local computer system clock synchronization with UTC based on synchronization with the Time Servers.


ZKEYWORD: CT
ZNAME: Consistent Time
ZTFDESCRIPTION:
  Consistent Time Profile defines mechanisms to synchronize the time base between multiple actors and computers.  Various infrastructure, security, and acquisition profiles require use of a consistent time base on multiple computers.  The Consistent Time Profile provides median synchronization error of less than 1 second.  Configuration options can provide better synchronization. The Consistent Time profile specifies the use of the Network Time Protocol (NTP) defined in RFC 1305.


ZKEYWORD: DEV_OBS_FILTER
ZNAME: Device Observation Filter
ZTFDESCRIPTION:
  The Device Observation Filter (DOF) actor is responsible for providing PCD data filtering services based on publish/subscribe predicates negotiated with client applications implementing the Device Observation Consumer.


ZKEYWORD: DEC
ZNAME: Device Enterprise Communication
ZTFDESCRIPTION:
  The Device Enterprise Communication Integration Profile supports communication of vendor independent, multi-modality Patient Care Device data to Enterprise Applications using consistent semantics. It accomplishes this by mapping of PCD data from proprietary syntax and semantics into a single syntactic and semantic representation for communication to the enterprise The PCD data is time stamped with a consistent enterprise time.


ZKEYWORD: DEV_OBS_CONSUMER
ZNAME: Device Observation Consumer
ZTFDESCRIPTION:
  The actor responsible for receiving PCD data from the Device Observation Reporter, the Device Observation Filter, or both.


ZKEYWORD: DEV_OBS_REPORTER
ZNAME: Device Observation Reporter
ZTFDESCRIPTION:
  The Device Observation Reporter (DOR) actor receives data from PCDs, including those based on proprietary formats, and maps the received data to transactions providing consistent syntax and semantics.


ZKEYWORD: DRPT
ZNAME: Displayable Reports
ZTFDESCRIPTION:
  The Displayable Reports Profile describes mechanisms for the transmission of PDFformatted clinical reports between report creators, managers, repositories, and displays. This profile describes the departmental production of reports, which can be further distributed using the Retrieve Information for Display and Cross-Enterprise Document Sharing Profiles (defined in the IHE IT Infrastructure Domain).


ZKEYWORD: ERR
ZNAME: Enterprise Report Repository
ZTFDESCRIPTION:
  A system that receives Structured Report Export Transactions from the Report Manager and stores them.


ZKEYWORD: RC
ZNAME: Report Creator
ZTFDESCRIPTION:
  A system that generates and transmits draft (and optionally, final) reports, presenting them as DICOM Structured Reporting Objects.


ZKEYWORD: DRR
ZNAME: Document-based Referral Request
ZTFDESCRIPTION:
  In the Document-based Referral Request Integration Profile the referral request is described by documents that are transmitted using XDS, XDR or XDM.  The referral request document location can be conveyed either by a printed uniqueID, or optionally by a direct HL7 order message.


ZKEYWORD: DSG
ZNAME: Digital Signature
ZTFDESCRIPTION:
  DSG is document content profile that describes the digital signature content and how it is managed in XDS, as well as guidance on how other IHE domains (such as Patient Care Coordination) could create document content profiles for such purposes as e-referral and e-prescription.


ZKEYWORD: ECDR
ZNAME: Eye Care Displayable Reports
ZTFDESCRIPTION:
  The Displayable Reports Profile specifies transactions supporting the creation, query/retrieve, and reading of display-ready eye care reports. The ECDR Profile allows use of the DICOM Encapsulated Document IOD, which has emerged as a ubiquitous means of encoding documents ready for presentation, including graphical content. Furthermore, the ECRD Profile allows the reporting physician to control the "look" of the report, which is important for both clinical and business reasons.


ZKEYWORD: ECED
ZNAME: Eye Care Evidence Documents
ZTFDESCRIPTION:
  The Eye Care Evidence Documents Profile defines information such as observations, measurements, and results (i.e., evidence documents), to be output by devices, such as acquisition systems and other workstations; to be stored and managed by archival systems; and to be retrieved and presented or used by display and reporting systems.


ZKEYWORD: INFO_SRC
ZNAME: Information Source
ZTFDESCRIPTION:
  A system that responds to requests for specific information or documents and returns ready for presentation information to be displays on the requesting actor.


ZKEYWORD: ECG
ZNAME: Retrieve ECG for Display
ZTFDESCRIPTION:
  The Retrieve ECG for Display Integration Profile specifies a mechanism for broad access throughout the enterprise to electrocardiogram (ECG) documents for review purposes. The ECG documents include  diagnostic quality  waveforms, measurements and interpretations. This Integration Profile allows the display of this information without requiring specialized cardiology software or workstations, but with general purpose computer applications such as a Web browser. This Integration Profile is intended primarily for retrieving resting 12-lead ECGs, but may also retrieve ECG waveforms gathered during stress, Holter, and other diagnostic tests. This Integration Profile only addresses ECGs that are already stored in an information system. It does not address the process of ordering, acquiring, storing, or interpreting the ECGs.


ZKEYWORD: DISPLAY
ZNAME: Display
ZTFDESCRIPTION:
  A system that offers requesting of specific information or documents for display the healthcare information returned


ZKEYWORD: ECHO
ZNAME: Echocardiography Workflow
ZTFDESCRIPTION:
  The Echocardiography Workflow Integration Profile describes the workflow associated with digital echocardiography, specifically that of transthoracic echo (TTE), transesophageal echo (TEE), and stress echo. As does the Cath Workflow Integration Profile, this profile deals with patient identifiers, orders, scheduling, status reporting, multi-stage exams (especially stress echo), and data storage. It also specifically addresses the issues of acquisition modality devices that are only intermittently connected to the network, such as portable echo machines, and addresses echo-specific data requirements.


ZKEYWORD: ED
ZNAME: Evidence Documents
ZTFDESCRIPTION:
  The Evidence Documents Profile defines interoperable ways for observations, measurements, results and other procedure details recorded in the course of carrying out a procedure step to be output by devices, such as acquisition systems and other workstations; to be stored and managed by archival systems; and to be retrieved and presented by display and reporting systems. This allows detailed non-image information, such as measurements, CAD results, procedure logs, etc. to be made available as input to the process of generating a diagnostic report. The Evidence Documents may be used either as additional evidence for the reporting physician or in some cases for selected items in the Evidence Document to be included in the diagnostic report.


ZKEYWORD: ED-CARD
ZNAME: Cardiology Evidence Documents
ZTFDESCRIPTION:
  The Evidence Documents Profile defines ways for data recorded in the course of carrying out a procedure step, such as observations, measurements, and results (i.e., evidence documents), to be output by devices, such as acquisition systems and other workstations; to be stored and managed by archival systems; and to be retrieved and presented or used by display and reporting systems. This allows detailed non-image information, such as measurements, CAD results, procedure logs, etc. to be made available as input to the process of generating a clinical Report, either as additional evidence for the reporting physician, or in some cases for selected items in the Evidence Document to be included in the report.


ZKEYWORD: EDES
ZNAME: Emergency Department Encounter Summary
ZTFDESCRIPTION:
  Emergency Department  Encounter Summary (EDES) as a summary of the patient's current health status and a summary of care rendered in the ED between arrival and ED departure. The EDES is not intended to replace the ED Chart as a complete, legal document of care, but is a collection of medical summaries with focused scope that can be used to fulfill a number of collaborative transfers of care. The ED Encounter Summary may include diagnostic tests performed during the ED encounter, as well as documentation of initial ED referral (a 2006 IHE work product), prehospital (EMS) records (IHE roadmap 2008), and the consultations of other providers.


ZKEYWORD: EDR
ZNAME: Emergency Department Referral
ZTFDESCRIPTION:
  This profile may be used to cover a wide variety of ED referral situations, for example, primary care provider to ED Referral, Long term care to ED referral, or even ED to ED referral (as in the case of transfer from a level 2 Critical care facility to a level 1 facility).


ZKEYWORD: EUA
ZNAME: Enterprise User Authentication
ZTFDESCRIPTION:
  Enterprise User Authentication (EUA) - Defines a means to establish one name per user that can then be used on all of the devices and software that participate in this integration profile. It greatly facilitates centralized user authentication management and provides users with the convenience and speed of a single sign-on. This profile leverages Kerberos (RFC 1510) and the HL7 CCOW standard (user subject).  User authentication is a necessary step for most application and data access operations and it is a workflow improvement for the users.  Future profiles will deal with other security issues, such as authorization management


ZKEYWORD: CONTXT_MGR
ZNAME: Context Manager
ZTFDESCRIPTION:
  This actor serves as a broker for the communication between two or more context participant actors (either Patient Context Participant or User Context Participant). It supports the passing of the user and patient subjects


ZKEYWORD: USER_CONTXT_PARTICIPANT
ZNAME: User Context Participant
ZTFDESCRIPTION:
  Receives notification of user context changes and follows them for the application that contains it.


ZKEYWORD: EYECARE
ZNAME: Eye Care Workflow
ZTFDESCRIPTION:
  The Eye Care Workflow Integration Profile establishes the continuity and integrity of basic patient and procedure data in the context of an eye clinic and/or an integrated hospital workflow scenario. This profile deals specifically with consistent handling of patient identifiers and demographic data. It also specifies the scheduling and coordination of procedure data to a wide variety of diagnostic imaging and testing equipment, and its reliable storage in an image management system from where it is available to support subsequent workflow steps, such as reporting. It also provides the ability for the acquisition devices to identify the actual procedure(s) that were performed. This enables further workflow steps such as automated billing.


ZKEYWORD: EYE-CHG
ZNAME: Eye Care Charge Posting
ZTFDESCRIPTION:
  The Charge Posting Integration Profile describes mechanisms to transfer charge information to the clinic or enterprise Charge Processing System. This section corresponds to Transaction RAD-35 of the IHE Technical Framework. Transaction RAD-35 is used by the Department System Scheduler/Order Filler and Charge Processor actors. This section also refers to RAD-36 of the IHE technical framework that is used by the ADT Patient Registration and Charge Processor Actors. This section will correlate the activities that occur in the eye care clinic with these IHE defined transactions. The standards used are Health Level Seven, Version 2.3.1: Chapter 6 - Financial Management DICOM 2004 PS 3.4 Modality Performed Procedure Step SOP Class.


ZKEYWORD: FSA
ZNAME: Functional Status Assessment
ZTFDESCRIPTION:
  The Functional Status Assessment Profile (FSA) supports the transfer of assessment information between practictioners during transfers of care across enterprises.<br/>In the context of clinical documentation, the functional status assessment describes the patient's current level of functioning at the time the document was created.


ZKEYWORD: FUS
ZNAME: Image Fusion
ZTFDESCRIPTION:
  The Image Fusion Integration Profile specifies communications between systems creating and registering image sets and systems displaying fused images. It defines how DICOM objects for spatial registration, blended presentation and the images themselves are created, stored, queried, retrieved, processed and displayed


ZKEYWORD: IDCO
ZNAME: Implantable Device - Cardiac - Observation
ZTFDESCRIPTION:
  IDCO specifies the creation, transmission, and processing of discrete data elements and report attachments associated with implantable cardiac device interrogations (observations) or messages.


ZKEYWORD: IRWF
ZNAME: Import Reconciliation Workflow
ZTFDESCRIPTION:
  The Import Reconciliation Workflow Integration Profile (IRWF) specifies how data Importers obtain local demographics, coerce patient and procedure attribute values in the imported data and report press/status of the importation process. The Profile complements the Scheduled Workflow Profile by using the existing workflow mechanisms for notification and storage of imported Evidence Objects.


ZKEYWORD: KIN
ZNAME: Key Image Note
ZTFDESCRIPTION:
  The Key Image Note Integration Profile specifies transactions that allow a user to mark one or more images in a study as significant by attaching to them a note managed together with the study. This note includes a title stating the purpose of marking the images and a user comment field. Physicians may attach Key Image Notes to images for a variety of purposes: referring physician access, teaching files selection, consultation with other departments, and image quality issues, etc.


ZKEYWORD: LBL
ZNAME: Laboratory Specimen Barcode Labeling
ZTFDESCRIPTION:
  The Laboratory Barcode Labeling Integration Profile supports this workflow: A robotic system delivers specimen containers pre-identified with a bar coded label, for the specimen collection related to a laboratory test order. This robotic system receives patient, test order and specimen data from another system (HIS, CIS, LIS), and issues a label for each (specimen, container) needed, with the specimen identifier bar coded on the label, and possibly other information printed on this label.  This workflow is supported by two new actors, Label Information Provider (LIP) and Label Broker (LB).  The Label Broker receives label information, and delivers these labels in appropriate operations, and may notify the status of this process. The Label Information Provider is usually grouped with the Order Filler or the Order Placer from the Laboratory TestingWorkflow Integration Profile.  The Label Broker may be notified passively with the labeling instructions or may query the Label Information Provider to get these instructions. This profile addresses only specimen container labeling within the scope of the Laboratory Domain. It does not address labeling workflows in other domains. 


ZKEYWORD: LB
ZNAME: Label Broker
ZTFDESCRIPTION:
  The Label Broker receives label information, and delivers these labels in appropriate operations, and may notify the status of this process. 


ZKEYWORD: CSC
ZNAME: Code Set Consumer
ZTFDESCRIPTION:
  A system which receives code sets from Code Set Master(s) and updates its internal tables to reflect the code set as maintained by the Code Set Master. This system may  also be an Order Placer, an Order Result Tracker, an Automation Manager, or an Order Filler.


ZKEYWORD: LCSD
ZNAME: Laboratory Code Set Distribution
ZTFDESCRIPTION:
  A set of common codes is generally used by multiple application systems in a laboratory workflow environment. These common codes need to be synchronized across the various applications at a given site. In many implementations, one application system will be the author (the "owner") of the code set. The responsibility for managing a code set may also be distributed among different systems. This profile provides a way for the owner of a code set (battery, test and observation codes) to send the code set to other applications. This profile involves all dedicated actors currently defined in the Laboratory Scheduled Workflow Integration Profile: Order Placer, Order Filler, Automation  Manager and Order Result Tracker.


ZKEYWORD: CSM
ZNAME: Code Set Master
ZTFDESCRIPTION:
  A system which owns (is responsible for the maintenance of) one or several code sets. This system may also be an Order Filler or an Enterprise Common Repository. Code sets can be sent on a routine basis (e.g. every week) or every time the code set changes. A code set may contain battery, test and observation codes.


ZKEYWORD: ANALYZER
ZNAME: Analyzer
ZTFDESCRIPTION:
  An actor which is an automated device which fulfills clinical tests on biologic specimen. An Analyzer performs analyzing for a specimen according to AWOS, and return the result to the AM.


ZKEYWORD: LDA
ZNAME: Laboratory Device Automation
ZTFDESCRIPTION:
  The LDA Integration Profile supports the workflow for the automated technical section of the clinical laboratory. It provides the transactions between the actors of this section (Automation Managers, Pre/Post-processors, Analyzers) to fulfill the Work Orders sent by the Order Filler, and send back the results produced for these Work Orders. 


ZKEYWORD: PRE_POST_PROCESSOR
ZNAME: Pre/Post-processor
ZTFDESCRIPTION:
  An actor which provides some pre- and post- processes to the specimen. This actor is categorized to two sub categories, one is pre-processor and the other one is post-processor. A Pre/Post-processor processes a specimen according to SWOS, and return the result to the AM.


ZKEYWORD: AM
ZNAME: Automation Manager
ZTFDESCRIPTION:
  A system or component that manages the automation in the laboratory or a part of it. Automation involves the integration or interfacing of automated or robotic transport systems, analytical instruments, and pre- or post-analytical process equipment such as automated centrifuges and aliquoters, decappers, recappers, sorters, and specimen storage and retrieval systems. This actor receives work orders from the Order Filler. It manages the processing of the ordered tests on the appropriate devices, and sends technically validated results back to the Order Filler. This actor must be considered even if it manages a small part of the analytical process; e.g. if it manages one single analytical instrument. Multiple Automation Managers can be related to one Order Filler. The Automation Manager can match unexpected results produced by an analyzer with the appropriate incoming Work Order, or create a new Work Order to fit the unsolicited observations and send them to the OF.


ZKEYWORD: POCDM
ZNAME: Point Of Care Data Manager
ZTFDESCRIPTION:
  This actor used in LPOCT profile is an application managing a set of POCRG and centralizing their results. The POCDM is ready to react to any conversation from a POCRG. The POCDM receives point of care observations from POCRG actors. It controls these observations within their context, stores them and forwards them to the Order Filler.


ZKEYWORD: LPOCT
ZNAME: Laboratory Point Of Care Testing
ZTFDESCRIPTION:
  Laboratory Point Of Care Testing (LPOCT) covers the workflow related to clinical laboratory tests performed on the point of care or on patientu2019s bedside, by ward staff.


ZKEYWORD: POCRG
ZNAME: Point Of Care Result Generator
ZTFDESCRIPTION:
  A system which receives code sets from Code Set Master(s) and updates its internal tables to reflect the code set as maintained by the Code Set Master. This system may 130 also be an Order Placer, an Order Result Tracker, an Automation Manager, or an Order Filler.


ZKEYWORD: LTW
ZNAME: Laboratory Testing Workflow
ZTFDESCRIPTION:
  The Laboratory Testing Workflow Integration Profile establishes the continuity and integrity of clinical laboratory testing and observation data inside a healthcare institution. It covers the workflow related to tests performed by the clinical laboratories of the institution, for both identified orders and  unknown orders, related to both identified patients and unidentified or misidentified patients.  This profiles replaces the two former profiles LSWF and LIR, which are kept in the LAB-TF release 2 for backward compatibility only. The profile involves a set of transactions, to maintain the consistency of ordering and patient information, to track the specimen collection and specimen acceptance and to deliver the laboratory  results at various steps of validation.   


ZKEYWORD: MAMMO
ZNAME: Mammography Image
ZTFDESCRIPTION:
  The Mammography Image Profile specifies how DICOM Mammography images and evidence objects are created, exchanged and used. It describes how Acquisition Modalities transfer Full Field Digital Mammography (FFDM) Images, how CAD system as as Evidence Creators, and how Image Displays should retrieve and make use of images and CAD results. It defines the basic display capabilities Image Displays are expected to provide, and which attributes should be used to implement those capabilities.


ZKEYWORD: ARCHIVE
ZNAME: Archive (including RT)
ZTFDESCRIPTION:
  A system that stores the RT SOP Classes in addition to the CT images and is capable of transmitting them.


ZKEYWORD: DOC_REGISTRY
ZNAME: Document Registry
ZTFDESCRIPTION:
  The Document Registry Actor maintains metadata about each registered document in a document entry. This includes a link to the Document in the Repository where it is stored. The Document Registry responds to queries from Document Consumer actors about documents meeting specific criteria. It also enforces some healthcare specific technical policies at the time of document registration.


ZKEYWORD: NOTIFICATION_SENDER
ZNAME: Notification Sender
ZTFDESCRIPTION:
  This actor sends notifications of availability for documents in an XDS registry, and receives acknowledgements of these notifications.


ZKEYWORD: NAV
ZNAME: Notification of Document Availability
ZTFDESCRIPTION:
  The NAV Profile defines a mechanism for point-to-point notifications between systems or users within an XDS Affinity Domain.  These notifications can be used to trigger various activities within applications that implement both XDS and NAV.  The Notification of Document Availability Profile specifies the use of SMTP and related standards for sending notifications, and the XML Digital Signature Core for creating a manifest of documents which are the subject of the notification.


ZKEYWORD: NOTIFICATION_RECEIVER
ZNAME: Notification Receiver
ZTFDESCRIPTION:
  This actor receives notifications of availability for documents in an XDS registry, and may optionally send acknowledgments of them.


ZKEYWORD: NMI
ZNAME: NM Image
ZTFDESCRIPTION:
  The NM Image Profile specifies how NM Images are to be stored by Acquisition Modalities and Evidence Creator workstations and how Image Displays should retrieve and make use of them. It defines the basic display capabilities Image Displays are expected to provide, (such as might be sufficient for a referring physician) but does not address advanced review features. It also defines how result screens, both static and dynamic, such as those created by NM Cardiac Processing Packages, should be stored using DICOM objects that can be displayed on general purpose Image Display systems. The NM Image Profile can be enhanced by combining it with other workflow profiles such as Scheduled Workflow, Post-Processing Workflow and Reporting Workflow which address how to schedule, manage and report the status of the steps in which NM Image objects are created.


ZKEYWORD: PES
ZNAME: Patient Encounter Supplier
ZTFDESCRIPTION:
  A system responsible for adding, updating and maintaining encounter information about a patient. It supplies new and updated information to the Patient Encounter Consumer. It must be grouped with either the Patient Demographics Source or the Patient Demographics Consumer. 


ZKEYWORD: PAM
ZNAME: Patient Administration Management
ZTFDESCRIPTION:
  The Patient Administration Management Integration Profile establishes the continuity and integrity of patient data, and additional information such as related persons (primary caregiver, guarantor, next of kin. It coordinates the exchange of patient registration and update information among systems that need to be able to provide current information regarding a patient's encounter status and location. This profile supports ambulatory and acute care use cases including patient identity feed, admission and discharge, and transfer and encounter management, as well as explicit and precise error reporting and application acknowledgment.


ZKEYWORD: PEC
ZNAME: Patient Encounter Consumer
ZTFDESCRIPTION:
  A system that uses patient encounter information provided by the Patient Encounter Source about a patient. It must be grouped with the Patient Demographics Consumer.


ZKEYWORD: PDI
ZNAME: Portable Data for Imaging
ZTFDESCRIPTION:
  The Portable Data for Imaging Integration Profile specifies actors and transactions that allow users to distribute imaging related information on interchange media. The intent of this profile is to provide reliable interchange of evidence objects and diagnostic reports for import, display or print by a receiving actor. A single physical transport means is specified that supports the multiple usage scenarios described in this profile. The CD format was chosen for supporting the described use cases.


ZKEYWORD: PDQ
ZNAME: Patient Demographics Query
ZTFDESCRIPTION:
  This profile provides ways for multiple distributed applications to query a central patient information server for a list of patients, based on user-defined search criteria. Patient demographics data can be entered directly into the application from which the user is querying by picking the appropriate record from a list of possible matches (called here a patient pick list).


ZKEYWORD: PGP
ZNAME: Presentation of Grouped Procedures
ZTFDESCRIPTION:
  The Presentation of Grouped Procedures Integration Profile (PGP) addresses what is sometimes referred to as the linked studies problem: viewing image subsets resulting from a single acquisition with each image subset related to a different requested procedure (e.g. CT chest, abdomen and pelvis). It provides a mechanism for facilitating workflow when viewing images and reporting on individual requested procedures that an operator has grouped (often for the sake of acquisition efficiency and patient comfort). A single acquired image set is produced, but the combined use of the scheduled workflow transactions and the consistent presentation of images allows separate viewing and interpretation of the image subsets related to each of the requested procedures.


ZKEYWORD: PIR
ZNAME: Patient Information Reconciliation
ZTFDESCRIPTION:
  The Patient Information Reconciliation Integration Profile extends the Scheduled Workflow Integration Profile by offering the means to match images acquired of an unidentified patient (for example, during a trauma case) or misidentified patient with the patient s admission and order history. In the example of the trauma case, this integration profile allows subsequent reconciliation of the patient record with images that are acquired (either without a prior registration or under a generic registration) before the patient s identity could be determined. Thus images can be acquired and interpreted immediately and later, when the patient s official registration and order information is entered into the ADT, Order Placer and Order Filler Systems, this information is matched with the acquired image set, greatly simplifying these exception-handling situations.


ZKEYWORD: IOP
ZNAME: Infusion Order Programmer
ZTFDESCRIPTION:
  The Infusion Order Programmer (IOP) actor sends the information comprising an order to the Infusion Order Consumer  (IOC).  The mechanism by which the IOP obtains the order information is outside the scope of this profile.


ZKEYWORD: PIV
ZNAME: Point-of-Care Infusion Verification
ZTFDESCRIPTION:
  The Point-of-Care Infusion Verification profile supports the electronic transfer of infusion parameters from a Barcode Point of Care (BPOC) system, also known as a Bar Code Medication Administration (BCMA) system, to an infusion pump.  This capability will reduce errors by eliminating keystroke errors and by increasing the use of automatic dosage checking facilitated by onboard drug libraries.  In addition to the reduction of medication administration errors, this integration may also increase caregiver productivity and provide more contextual information regarding infusion data.


ZKEYWORD: IOC
ZNAME: Infusion Order Consumer
ZTFDESCRIPTION:
  The Infusion Order Consumer  (IOC) actor receives the order information from the IOP actor and in turn programs the pump.  The mechanism by which the IOC programs the pump with the received information is outside the scope of this profile.


ZKEYWORD: PAT_IDENTITY_CONSUMER
ZNAME: Patient Identifier Cross-reference Consumer
ZTFDESCRIPTION:
  This actor allows a system in a Patient Identification Domain to find out the identification of a patient in a different Patient Identification Domain by using the services of a Patient Identity Cross-Reference Manager Actor. 


ZKEYWORD: PIX
ZNAME: Patient Identifier Cross-referencing for MPI
ZTFDESCRIPTION:
  The PIX profile supports the Cross-referencing of patient identifiers from multiple Patient Identification Domains. These Cross-referenced patient identifiers can then be used by "identity consumer" systems to correlate information about a single patient from sources that "know" the patient by different identifiers. This allows a Clinician to have more complete view of the patient information.


ZKEYWORD: PAT_IDENTITY_X_REF_MGR
ZNAME: Patient Identity Cross-reference Manager
ZTFDESCRIPTION:
  Serves a well-defined set of Patient Identification Domains. Based on information provided by in each Patient Identification Domain by a Patient Identification Source Actor, it manages the cross-referencing of patient identifiers across Patient Identification Domains.


ZKEYWORD: PAT_IDENTITY_SRC
ZNAME: Patient Identity Source
ZTFDESCRIPTION:
  Each Patient Identification Domain requires this Actor to assign patient identities and to notify a Patient Identity Cross-reference Manager Actor of all events related to patient identification (creation, update, merge, etc.). For example, the Registration (ADT) Actor defined by the radiology Scheduled Workflow Profile would likely be a Patient Identity Source.


ZKEYWORD: PAT_CONTXT_PARTICIPANT
ZNAME: Patient Context Participant
ZTFDESCRIPTION:
  This actor participates in a shared context environment by both setting the patient context and responding to context changes as communicated by the Context Manager Actor. This actor shall respond to all patient context changes. This actor shall set the patient context, if the application containing this actor has patient selection capability. 


ZKEYWORD: PSA
ZNAME: Patient Synchronized Application
ZTFDESCRIPTION:
  Patient Synchronized Applications supports viewing data for a single patient among otherwise independent and unlinked applications on a user s workstation.  Its implementation reduces the repetitive tasks of selecting the same patient in multiple applications.  It also improves patient safety by reducing the chance of medical errors caused by viewing the wrong patient s data.  Its ability to work with the Patient Identifier Cross-referencing for MPI - provides a seamless environment both for the clinician and the IT staff.   This profile leverages the HL7 CCOW standard specifically for patient subject context management.


ZKEYWORD: PWF
ZNAME: Post-Processing Workflow
ZTFDESCRIPTION:
  The Post-Processing Workflow Integration Profile addresses the need to schedule and track the status of the steps of the typical post-processing workflow, such as Computer-Aided Detection or Image Processing. Worklists for each of these tasks are generated and can be queried, work items can be selected and the resulting status returned from the system performing the work to the system managing the work.


ZKEYWORD: PWPD
ZNAME: Personnel White Pages Directory
ZTFDESCRIPTION:
  This actor has authoritative Personnel White Pages information on the human workforce members of the enterprise.


ZKEYWORD: PWP
ZNAME: Personnel White Pages
ZTFDESCRIPTION:
  The Personnel White Pages Profile provides access to basic human workforce user directory information. This information has broad use among many clinical and non-clinical applications across the healthcare enterprise.


ZKEYWORD: QED
ZNAME: Query for Existing Data
ZTFDESCRIPTION:
  The Query for Existing Data Profile (QED) supports dynamic queries for clinical data, , including vital signs, problems, medications, immunizations, diagnostic results, procedures and visit history. A wide variety of systems often need access to dynamic clinical information stored and maintained in an EMR system or other clinical data repository. This profile makes the information widely available to other systems within and across enterprises to support provision of better clinical care. The information made available by this profile can be used to support clinical care, quality reporting, financial transactions, public health reporting, clinical trials, drug interaction checking, and patient qualification for various protocols. 


ZKEYWORD: REG_DISPLAY
ZNAME: Registered Display
ZTFDESCRIPTION:
  A system that consumes multi-modality images, RT Structure Set objects, and Spatial Registration objects and allows the user to display the registered information


ZKEYWORD: REG
ZNAME: Image Registration
ZTFDESCRIPTION:
  The Image Registration Integration Profile specifies communications between systems creating and registering image sets. It defines how DICOM objects for spatial registration and the images themselves are created, stored, queried, retrieved, processed and displayed.


ZKEYWORD: REG_DOSE_DISPLAY
ZNAME: Registered Dose Display
ZTFDESCRIPTION:
  A system that consumes multi-modality images, RT Structure Set objects, RT Dose objects and Spatial Registration objects and allows the user to display the registered information.


ZKEYWORD: REG_CONTOURER
ZNAME: Registered Contourer
ZTFDESCRIPTION:
  A system that consumes multi-modality images, RT Structure Set objects, and Spatial Registration objects and allows the user to contour images in a registered display.


ZKEYWORD: DOSE_INFO_CONSUMER
ZNAME: Dose Information Consumer
ZTFDESCRIPTION:
  Responsible for supplemental handling of irradiation events, generally on an individual basis, e.g. display, analysis, or further processing.


ZKEYWORD: REM
ZNAME: Radiation Exposure Monitoring
ZTFDESCRIPTION:
  The Radiation Exposure Monitoring Integration Profile specifies communications between systems generating reports of irradiation events (generally acquisition modalities and workstations) and systems which receive, store, or process those reports (generally local dose information management systems and/or national/regional dose registers). It defines how DICOM SR objects for CT and projection X-ray dose objects are created, stored, queried, retrieved, de-identified, and may be processed and displayed.


ZKEYWORD: DOSE_REGISTER
ZNAME: Dose Register
ZTFDESCRIPTION:
  Collates information about irradiation events from a number of facilities, generally to perform analysis.


ZKEYWORD: DOSE_INFO_REPORTER
ZNAME: Dose Information Reporter
ZTFDESCRIPTION:
  Responsible for the aggregation, analysis, reporting and business logic related to irradiation events, which may include meeting facility obligations to de-identify and submit data to various dose registers.


ZKEYWORD: RFD
ZNAME: Retrieve Form for Data Capture
ZTFDESCRIPTION:
  The Retrieve Form for Data-capture Profile (RFD) provides a method for gathering data within a user's current application to meet the requirements of an external system. RFD supports the retrieval of forms from a form source, display and completion of a form, and return of instance data from the display application to the source application.


ZKEYWORD: RID
ZNAME: Retrieve Information for Display
ZTFDESCRIPTION:
  Retrieve Information for Display enables simple and rapid access to patient information for better care.  It supports access to existing persistent documents in well-known presentation formats such as CDA, PDF, JPEG, etc.  It also supports access to specific key patient-centric information such as allergies, current medications, summary of reports, etc. for presentation to a clinician.  It complements workflows from within the users on-screen workspace or application. By linking it with two other IHE profiles - Enterprise User Authentication and Patient Identifier Cross-referencing for MPI, this profile s reach can extend across organization boundaries.  This IHE Integration Profile leverages HTTP, Web Services, IT presentation formats and HL7 CDA.


ZKEYWORD: RTO
ZNAME: Radiation Therapy Objects
ZTFDESCRIPTION:
  involves the flow of DICOM images and treatment planning data, from CT scan through dose display, for 3D conformal, external beam radiation therapy


ZKEYWORD: CONTOURER
ZNAME: Contourer
ZTFDESCRIPTION:
  A system that consumes CT and creates RT Structure Set. If the Contourer consumes multiple series CT or has an internal requirement for resampling, it also will generate a single series CT to which the RT Structure Set maps.


ZKEYWORD: DOSIMETRIC_PLANNER
ZNAME: Dosimetric Planner
ZTFDESCRIPTION:
  A system that consumes (single series) CT, an RT Structure Set, a Geometric Plan, and creates a Dosimetric Plan and an RT Dose.


ZKEYWORD: RWF
ZNAME: Reporting Workflow
ZTFDESCRIPTION:
  The Reporting Workflow Profile addresses the need to schedule, distribute and track the status of the reporting workflow tasks such as interpretation,  transcription and verification. Worklists for each of these tasks are generated and can be queried; workitems can be selected and the resulting status returned from the system performing the work to the system managing the work.


ZKEYWORD: SEC
ZNAME: Basic Security
ZTFDESCRIPTION:
  The Basic Security Integration Profile establishes basic security measures that can, as part of an institution s overall security policies and procedures in the enterprise, help protect the confidentiality of patient information. It also provides institutions with a mechanism to consolidate audit trail events on user activity across several systems interconnected in a secure manner.


ZKEYWORD: SINR
ZNAME: Simple Image and Numeric Report
ZTFDESCRIPTION:
  The Simple Image and Numeric Report Integration Profile facilitates the growing use of digital dictation, voice recognition, and specialized reporting packages, by separating the functions of reporting into discrete actors for creation, management, storage and viewing. Separating these functions while defining transactions to exchange the reports between them enables a vendor to include one or more of these functions in an actual system.


ZKEYWORD: STRESS
ZNAME: Stress Testing Workflow
ZTFDESCRIPTION:
  The Stress Testing Workflow Profile provides the mechanism for ordering and collecting multi-modality data during diagnostic Stress testing procedures.


ZKEYWORD: SVS
ZNAME: Sharing Value Sets
ZTFDESCRIPTION:
  The Sharing Value Sets (SVS) profile provides a means through which healthcare systems producing clinical or administrative data, such as diagnostic imaging equipment, laboratory reporting systems, primary care physician office EMR systems, or national healthcare record systems, can receive a common, uniform nomenclature managed centrally.  Shared nomenclatures are essential to achieving semantic interoperability.


ZKEYWORD: SWF
ZNAME: Scheduled Workflow
ZTFDESCRIPTION:
  The Scheduled Workflow Integration Profile establishes the continuity and integrity of basic radiological data. It specifies a number of transactions that maintain the consistency of patient and ordering information as well as defining the scheduling and imaging acquisition procedure steps. This profile also makes it possible to determine whether images associated with a particular performed procedure step have been stored (archived) and are available to enable subsequent workflow steps, such as reporting.


ZKEYWORD: T14
ZNAME: HITSP Send Laboratory Result Message Transaction
ZTFDESCRIPTION:
  This Transaction specification supports: •	Transmission of complete, preliminary, final and updated laboratory results to the EHR system (local or remote) of the ordering clinician  •	Transmission of complete, preliminary, final and updated laboratory results (or notification of the availability of laboratory results) to the EHR system (local or remote) or other clinical data system of designated providers of care (with respect to a specific patient) 


ZKEYWORD: T15
ZNAME: HITSP Collect and Communicate Audit Trail
ZTFDESCRIPTION:
  US HITSP: T15: Collect and Communicate Audit Trail. The Collect and Communicate Security Audit Trail Transaction is a means to provide assurance that security policies are being followed or enforced and that risks are being mitigated. This document describes the mechanisms to define and identify security relevant events and the data to be collected and communicated as determined by policy, regulation or risk analysis. It also provides the mechanism to determine the record format to support analytical reports that are needed.


ZKEYWORD: T16
ZNAME: HITSP T16: Consistent Time
ZTFDESCRIPTION:
  US HITSP: T16: Consistent Time. The Consistent Time Transaction provides a mechanism to ensure that all of the entities that are communicating within the network have synchronized system clocks.


ZKEYWORD: T17
ZNAME: HITSP Secured Communication Channel Transaction
ZTFDESCRIPTION:
  US HITSP: T17: Secured Communication Channel Transaction. The Secured Communication Channel Transaction provides the mechanisms to ensure the authenticity, integrity, and confidentiality of transmissions, and the mutual trust between communicating parties. Its objectives include providing: mutual node authentication to assure each node of the others’ identity; transmission integrity to guard against improper information modification or destruction while in transit; and transmission confidentiality to ensure that information in transit is not disclosed to unauthorized individuals, entities, or processes.


ZKEYWORD: T18
ZNAME: HITSP View Laboratory Results from a Web Application Transaction
ZTFDESCRIPTION:
  The View Laboratory Results from a Web Application Transaction allows a user to view a laboratory report through a secure browser. This Transaction uses the HITSP/C44 - Secure Web Connection Component. It may not define all functions, constructs and standards necessary to implement a conforming system in a real world environment. In particular, an implementer must provide the technical infrastructure and security framework necessary to support operations in accordance with law, regulation, best practices and business agreements.


ZKEYWORD: DOC_REPOSITORY
ZNAME: Document Repository
ZTFDESCRIPTION:
  The Document Repository is responsible for both the persistent storage of these documents as well as for their registration with the appropriate Document Registry. It assigns a URI to documents for subsequent retrieval by a Document Consumer.


ZKEYWORD: T23
ZNAME: HITSP Patient Demographics Query Transaction
ZTFDESCRIPTION:
  US HITSP: T23: HITSP Patient Demographics Transaction. The Patient Demographics Query Transaction is intended to provide a ‘list patients and their demographics’ query / ‘patient(s) and their demographics identified’ response message pair (QBP^Q22, RSP^K22) for use wherever such needs exist. This Transaction document extracts the Health Level Seven (HL7) version 2.5 Query and Response data mapping. The underlying basis for this extraction can be found in the Integrating the Healthcare Enterprise IT Infrastructure Technical Framework, Patient Demographics Query integration profile.


ZKEYWORD: HITSP_Pseudoymisation_SVC
ZNAME: HITSP Pseudonymization Services
ZTFDESCRIPTION:
  Module or service that can be invoked by Patient Identifier Cross-Reference (PIX) Manager (see next section) to return pseudo-identifier upon request


ZKEYWORD: T24
ZNAME: HITSP Pseudonymize Transaction
ZTFDESCRIPTION:
  The Pseudonymize Transaction describes a framework for including Pseudonymization Services where the use of “dummy” or pseudo references to specific patients or providers is requred. Pseudo-identifiers are intended to allow accessibility to clinical information, while safeguarding any information that may compromise the privacy of the individual patient or provider. Using pseudo-identifiers can assist in compliance with HIPAA regulations regarding suppression of patient identification information.


ZKEYWORD: T29
ZNAME: HITSP Notification of Document Availability Transaction
ZTFDESCRIPTION:
  US HITSP: T29: Notification of Document Availability Transaction. The NAV Integration Profile introduces a mechanism allowing notifications to be sent point-to-point to systems within a Cross-Enterprise Document Sharing Affinity Domain (See “IHE IT Infrastructure Cross-Enterprise Document Sharing (XDS) Integration Profile”), eliminating the need for manual steps or polling mechanisms for a Document Consumer to be aware that documents of interest have been registered with an XDS Document Registry Actor.


ZKEYWORD: T31
ZNAME: HITSP Reliable Document Exchange
ZTFDESCRIPTION:
  US HITSP: T31: Reliable Document Exchange. The Document Reliable Interchange Transaction provides a standards-based mechanism for conveying a set of medical documents in a point-to-point network-based communication. This Transaction uses the IHE Cross-Enterprise Document Reliable Interchange (XDR) Integration Profile, a companion to the IHE Cross-Enterprise Document Sharing (XDS) Integration Profile. Cross-Enterprise Document Reliable Interchange (XDR) uses the XDS defined metadata formats in a simpler environment in which the communicating parties have agreed to a point-to-point interchange rather than communicating via document sharing.


ZKEYWORD: T33
ZNAME: Transfer of Documents on Media
ZTFDESCRIPTION:
  US HITSP: T33: Transfer of Documents on Media. The Transfer of Documents on Media Transaction describes both the type of media (CD-ROM, USB Memory, and e-Mail) that may be used to write the documents and provides a directory structure that must be followed in order for the contents to be successfully accessed and processed by systems. An example might be to transport data from one healthcare provider to another healthcare provider, or a healthcare consumer may wish to move the contents of a Personal Health Record (PHR) using physical media or e-Mail. This Transaction uses the IHE Cross-Enterprise Document Media Interchange Integration Profile developed by Integrating the Healthcare Enterprise (IHE), a companion to the IHE Cross-Enterprise Document Sharing (XDS) Integration Profile.


ZKEYWORD: HITSP_Eligibility_info_Source
ZNAME: Eligibility Information Source
ZTFDESCRIPTION:
  The system which holds and maintains the information regarding the individual’s insurance eligibility, coverage and benefits, and responds to the queries initiated by the Eligibility Information Receiver


ZKEYWORD: T40
ZNAME: HITSP Patient Generic Health Plan Eligibility Verification Transaction
ZTFDESCRIPTION:
  The Patient Health Plan Eligibility Verification Transaction is intended to provide the status of a health plan covering the individual, along with details regarding patient liability for deductible, co-pay and co-insurance amounts for a defined base set of generic benefits or services. The base set of benefits includes, but is not limited to, coverage status and patient liability for medical, chiropractic, dental, hospital inpatient, hospital outpatient, emergency, physician office visit, pharmacy and vision services that are included in the patient’s generic health plan benefit.


ZKEYWORD: HITSP_Eligibility_info_receiver
ZNAME: Eligibility Information Receiver
ZTFDESCRIPTION:
  The system that initiates an inquiry to the Eligibility Information Source about an individual’s insurance eligibility, coverage and benefits


ZKEYWORD: HITSP_Med_Status_Receiver
ZNAME: HITSP Medication Status Receiver
ZTFDESCRIPTION:
  The Medication Status Receiver receives a dispensing status (RXFILL message) from a Medication Status Dispenser about a previously performed medication order / prescription


ZKEYWORD: T42
ZNAME: HITSP Medication Dispensing Status Transaction
ZTFDESCRIPTION:
  This Medication Dispensing Status Transaction provides a medication prescriber the dispensing status of an ordered prescription (dispensed, partially dispensed, not dispensed). This transaction is used for original prescriptions, refills and renewals. It uses the NCPDP SCRIPT Standard Implementation Guide Version 10.1 RXFILL message to provide the status.


ZKEYWORD: HITSP_Med_Status_Dispenser
ZNAME: HITSP Medication Status Dispenser
ZTFDESCRIPTION:
  The Medication Status Dispenser provides a dispensing status (RXFILL message) to a Medication Status Receiver about a preciously performed medication order / prescription


ZKEYWORD: T63
ZNAME: HITSP Emergency Message Distribution Element
ZTFDESCRIPTION:
  US HITSP: T63: Emergency Message Distribution Element. The Emergency Message Distribution Element Transaction selects the Emergency Data Exchange Language (EDXL) Distribution Element (DE) v1.0 standard, and is a multicast notification message sent to an identified population (assume this is not to the general public, but to specifically identified populations, such as emergency departments). View the most current version as HTML here.


ZKEYWORD: T64
ZNAME: HITSP Personnel White Pages
ZTFDESCRIPTION:
  US HITSP: T64: Personnel White Pages. The Identify Communication Recipients Transaction is intended to serve the purpose of identification of communication recipients and the subsequent purpose of delivery of alerts and bi-directional communications (e.g., public health agencies notifying a specific group of service providers about an event.) The method and criteria by which individuals are added to a directory is a policy decision, which is out of scope for this construct. It uses the Integrating the Healthcare Enterprise (IHE) Personnel White Pages profile which provides access to basic directory information for identifying one or more recipients. View the most current version as HTML here.


ZKEYWORD: T66
ZNAME: HITSP Sharing Value Sets - SVS
ZTFDESCRIPTION:
  US HITSP: T66: Sharing Value Sets - SVS. The Retrieve Value Set Transaction is used to transform human or computer vocabularies. For example, it can be used to convert the initial capture of a human-readable concept into a computer vocabulary captured in a document or message that will be communicated. It may also be used in the reverse, to take computer vocabulary and convert to human-readable form. View the most current version as HTML here.


ZKEYWORD: T67
ZNAME: HITSP Document-based Referral - DRR
ZTFDESCRIPTION:
  US HITSP: T67: Document-based Referral Request - DRR. The Clinical Referral Request Transport Transaction will be used to transport the provider to provider (clinical) referral request interaction. It is based on the Integrating the Healthcare Enterprise (IHE) Document-based Referral Request (DRR) profile which is used to bundle a referral request document with other relevant clinical documents of interest and optionally to send a trigger message to the receiving provider system. View the most current version as HTML here.


ZKEYWORD: HITSP_Info_Rcvr_Health_Plan_Auth
ZNAME: HITSP Information Receiver for Health Plan Authorization
ZTFDESCRIPTION:
  The system that initiates a request to the Information Source for Health Plan Authorization about an individuals health insurance requirements to obtain an authorization approval for purposes of benefit coverage determination in order to refer a patient for healthcare services


ZKEYWORD: T68
ZNAME: Patient Health Plan Authorization Request and Response Transaction
ZTFDESCRIPTION:
  The Patient Health Plan Authorization Request and Response Transaction provides a mechanism for a healthcare provider (other than a retail pharmacy) to request approval from a health plan to authorize certain healthcare services, when required by the patient’s health plan contract. The information exchanged includes, but is not limited to, approval status for coverage, allowed service provider(s), and certification dates for services that are included in the patient’s health plan benefits. The response from the health plan indicates that the health plan has determined that the particular service(s) will or will not be covered, and what is the level of coverage if that information is available from the health plan. View the most current version as HTML here.


ZKEYWORD: HITSP_Info_Src_Health_Plan_Auth
ZNAME: HITSP Information Source for Health Plan Authorization
ZTFDESCRIPTION:
  The system which holds and maintains the information regarding the individual’s health insurance requirements related to an authorization for benefit coverage


ZKEYWORD: T73
ZNAME: HITSP Aggregate Device Information Communication
ZTFDESCRIPTION:
  US HITSP: T73. The Aggregate Device Information Communication Transaction allows a system serving as a device intermediary such as a home hub, a cell phone, a set top box, or a monitoring station to which one or more monitoring devices are connected to forward a set of observations through a local or remote connection to a remote monitoring management system where these device captured observations will be reviewed by a person managing the care of the patient under remote monitoring


ZKEYWORD: T79
ZNAME: Pharmacy to Health Plan Authorization Request and Response Transaction
ZTFDESCRIPTION:
  The Pharmacy to Health Plan Authorization Request and Response Transaction provides a mechanism for a pharmacy to request approval from a health plan to authorize certain healthcare products and services, as required by the patient’s health plan contract. The health plan responds to the pharmacy’s request for the approval of products and/or services. The information exchanged includes, but is not limited to, approval status for coverage of the products and/or services that are included in the patient’s health plan benefits and/or authorization limitations. View the most current version as HTML here


ZKEYWORD: KNOWLEDGE_RESOURCE
ZNAME: Knowledge Resource
ZTFDESCRIPTION:
  The system that holds the information requested and responds to the request from the Knowledge Requestor


ZKEYWORD: T81
ZNAME: HITSP T81 Retrieval of Medical Knowledge
ZTFDESCRIPTION:
  US HITSP: T81 Retrieval of Medical Knowledge. The Retrieval of Medical Knowledge Transaction enables the request and receipt of additional knowledge about a medical concept based on specific context parameters. This transaction does not prescribe the knowledge content of the message returned but provides the specifications for the query for and receipt of additional knowledge. It uses the Health Level 7 (HL7) Context-Aware Information Retrieval (Infobutton) Specification: URL Implementation Guide as the base standard for implementation. View the most current version as HTML here.


ZKEYWORD: KNOWLEDGE_REQUESTOR
ZNAME: Knowledge Requestor
ZTFDESCRIPTION:
  KnA system that formulates and sends a contextual request for ancillary information about a medical concept. Takes the parameters and sends to the resource available


ZKEYWORD: T85
ZNAME: Administrative Transport to Health Plan
ZTFDESCRIPTION:
  The Administrative Transport to Health Plan Transaction will be used as the transport for administrative transactions between a provider and a health plan. Examples include a pharmacy obtaining health plan eligibility, and a physician requesting referral or authorization information from a health plan. This construct is based on the CAQH Phase II CORE #270 Connectivity Rule v2.0.0, which addresses the message envelope metadata, the message envelope standards, and the submitter authentication standards for administrative transactions, as well as communications-level errors, and acknowledgements. View the most current version as HTML here


ZKEYWORD: EXPORT_MANAGER
ZNAME: Export Manager
ZTFDESCRIPTION:
  A system that can de-identify and pseudonymize the attributes, and optionally the pixel data, of a selected list of instances, before exporting them.


ZKEYWORD: TCE
ZNAME: Teaching File and Clinical Trial Export
ZTFDESCRIPTION:
  The Teaching File and Clinical Trial Export Profile addresses the need to select DICOM instances, series or studies (which may contain images, key image notes, reports, evidence documents and presentation states) that need to be exported for teaching files or clinical trials.  It defines an actor for making the Export Selection, which would typically be grouped with an Image Display or Acquisition Modality, and an actor for processing the selection, which is required to support a configurable means of de-identifying the exported instances. Additional options are provided for de-identification of pixel data, remapping of identifiers to pseudonymous values, export of additional teaching file information, and delaying export for a variety of reasons.


ZKEYWORD: RECEIVER
ZNAME: Receiver
ZTFDESCRIPTION:
  A system that can receive exported instances over the network, whose behavior is otherwise unspecified, unless grouped with other actors.


ZKEYWORD: EXPORT_SELECTOR
ZNAME: Export Selector
ZTFDESCRIPTION:
  A system that allows a user to select one or more instances, series or studies for export, for a specific purpose, with a specific disposition, optionally with the inclusion of additional information.


ZKEYWORD: TP13
ZNAME: Manage Sharing of Documents Transaction Package with Doc Integrity Check
ZTFDESCRIPTION:
  US HITSP: TP13: Manage Sharing of Documents Transaction Package with Doc The Manage Sharing of Documents Transaction Package supports the sharing of patient records in the form of source attested objects called documents. A healthcare document is a composite of structured and coded health information, both narrative and tabular, that describes acts, observations and services for the purpose of exchange. No assumption is made by this construct in terms of the format and structure of the content of documents shared.


ZKEYWORD: TP13a
ZNAME: Manage Sharing of Documents (XDS.A Option)
ZTFDESCRIPTION:
  US HITSP: TP13a: Manage Sharing of Documents (XDS.A Option). The Manage Sharing of Documents Transaction Package supports the sharing of patient records in the form of source attested objects called documents. A healthcare document is a composite of structured and coded health information, both narrative and tabular, that describes acts, observations and services for the purpose of exchange. No assumption is made by this construct in terms of the format and structure of the content of documents shared.


ZKEYWORD: TP13b
ZNAME: Manage Sharing of Documents (XDS.B Option)
ZTFDESCRIPTION:
  US HITSP: TP13b: Manage Sharing of Documents (with reference to the IHE XDS.b supplement to suport Entity Identity)


ZKEYWORD: TP20
ZNAME: HITSP Access Control
ZTFDESCRIPTION:
  US HITSP: TP20: Access Control. The Access Control Transaction Package provides the mechanism for security authorizations which control the enforcement of security policies including: role-based access control; entity based access control; context based access control; and the execution of consent directives. An example of this is a functional role that has the permission to perform an act (e.g., consumer updating a Personal Health Record (PHR). In an emergency, this construct must support the capability to alter access privileges to the appropriate level (failsafe/emergency access), which may include override of non-emergency consents.


ZKEYWORD: HITSP_Service_User
ZNAME: HITSP Service User
ZTFDESCRIPTION:
  The entity represents any individual entity (such as an EHR/PHR system) that needs to make a service request of a Service Provider. The Entity may also be known as a principal and/or entity, which represents an application, a machine, or any other type of entity that may act as a requester in a transaction. A principal is typically represented in a transaction with a digital identity and the principal may have multiple valid digital identities to use with different transactions. Any Service User may also be a Service Provider


ZKEYWORD: TP21
ZNAME: HITSP Query for Existing Data
ZTFDESCRIPTION:
  US HITSP: TP21: Query for Existing Data. The Query for Existing Data Transaction Package is based on the IHE Query for Existing Data Integration Profile (QED) which supports dynamic queries for clinical data, including vital signs, problems, medications, immunizations, diagnostic results, procedures and visit history. A wide variety of systems often needs access to dynamic clinical information stored and maintained in an EMR system or other clinical data repository. The construct makes the information widely available to other systems within and across enterprises to support provision of better clinical care.


ZKEYWORD: TP22
ZNAME: Patient ID Cross-Referencing using IHE PIX
ZTFDESCRIPTION:
  US HITSP: TP22: Patient ID Cross-Referencing using IHE PIX. The Patient ID Cross-Referencing Transaction Package is used for identifying and cross-referencing different attributes for the same patient. It contains a query for cross-reference and patient identity feed transactions. These transactions are used to identify patients from a list of potentials, and/or to communicate patient demographic data.


ZKEYWORD: TP30
ZNAME: HITSP Manage Consent Directions Transaction Package
ZTFDESCRIPTION:
  US HITSP: TP30: Manage Consent Directives Transaction Package. The Manage Consent Directives Transaction Package describes the messages needed to capture, manage, and communicate rights granted or withheld by a consumer to one or more identified entities in a defined role to access, collect, use or disclose individually identifiable health information (IIHI), and also supports the delegation of the patient’s right to consent. The transactions described in this construct are intended to be carried out by HITSP/TP13 - Manage Sharing of Documents.


ZKEYWORD: HITSP_Med_Order_Pscr
ZNAME: HITSP Medication Order Prescriber
ZTFDESCRIPTION:
  The Medication Order Prescriber initiates requests for medication orders/prescriptions. This includes the ability to: create new orders, refill orders, change orders and cancel orders. These requests are sent to the Medication Order Filler.


ZKEYWORD: TP43
ZNAME: HITSP Medication Orders Transaction Package
ZTFDESCRIPTION:
  The Medication Orders Transaction Package is used to define transactions between prescribers (who write prescriptions) and dispensers (who fill prescriptions). It is used for new prescriptions, refill requests, prescription change requests and prescription cancellations. Orders/prescriptions may occur in many different real world settings, such as inpatient, long term care and ambulatory settings. View the most current version as HTML here.


ZKEYWORD: HITSP_Med_Ord_Flr
ZNAME: HITSP Medication Order Filler
ZTFDESCRIPTION:
  The Medication Order Filler responds to the requests for medication orders/prescriptions. This includes the ability to respond to: new orders, refill orders, change orders and cancel orders. These responses are sent to the Medication Order Prescriber.


ZKEYWORD: HITSP_Med_Form_Bene_Rcvr
ZNAME: HITSP Medication Formulary and Benefits Retriever
ZTFDESCRIPTION:
  The entity that is asking about an individual’s formulary and benefits information. It initiates queries to the Medication Formulary and Benefits Source


ZKEYWORD: TP46
ZNAME: HITSP Medication Formulary and Benefits Information Transaction Package
ZTFDESCRIPTION:
  The Medication Formulary and Benefits Information Transaction Package addresses two tasks. The first task is to perform an eligibility check for a specific patient’s pharmacy benefits. The second task is to obtain the medication formulary and benefit information.


ZKEYWORD: HITSP_Med_Form_Bene_Src
ZNAME: HITSP Medication Formulary and Benefits Source
ZTFDESCRIPTION:
  The entity that maintains individual’s formulary and benefits information. It responds to queries from the Medication Formulary and Benefits Retriever


ZKEYWORD: IMG_DOC_CONSUMER
ZNAME: Imaging Document Consumer
ZTFDESCRIPTION:
  The Imaging Document Source actor is the producer and publisher of imaging documents. It is responsible for providing imaging documents and meta-data to the Document Repository actor, which subsequently registers the imaging documents with the Document Registry actor. It also supports the retrieval services for DICOM SOP Instances referenced in a published imaging manifest document.


ZKEYWORD: TP49
ZNAME: HITSP Sharing Radiology Results Transaction Package
ZTFDESCRIPTION:
  US HITSP: TP49: Sharing Radiology Results Transaction Package. The Sharing Imaging Results Transaction Package supports the sharing of radiology result data in a document sharing functional flow scenario.


ZKEYWORD: TP50
ZNAME: HITSP Retrieve Form for Data Capture
ZTFDESCRIPTION:
  US HITSP: TP50: Retrieve Form for Data Capture. The Retrieve Form for Data Capture Transaction Package enables capture of supplemental data variables not typically maintained in an electronic health record or laboratory information system through a more seamless integration with the local information system. This allows for the local system to retrieve a form specific to the identified potential public health threat. In the context of quality, it allows for the local system to capture supplemental data elements required for quality reporting that may not be available to the electronic health record.


ZKEYWORD: XCA
ZNAME: Cross Community Access
ZTFDESCRIPTION:
  The Cross Community Access profile supports the means to query and retrieve patient relevant medical data held by other communities.  A community is defined as a coupling of facilities/enterprises that have agreed to work together using a common set of policies for the purpose of sharing clinical information via an established mechanism.  Facilities/enterprises may host any type of healthcare application such as EHR, PHR, etc.  A community is identifiable by a globally unique id called the homeCommunityId.   Membership of a facility/enterprise in one community does not preclude it from being a member in another community.  Such communities may be XDS Affinity Domains which define document sharing using the XDS profile or any other communities, no matter what their internal sharing structure.


ZKEYWORD: XD-LAB
ZNAME: Sharing Lab Report
ZTFDESCRIPTION:
  The Sharing Lab Report content integration profile is focussed on the sharing of sets of laboratory results in the form of a laboratory report structured document.


ZKEYWORD: XDM
ZNAME: Cross-Enterprise Document Media Interchange
ZTFDESCRIPTION:
  Cross-Enterprise Document Media Interchange (XDM) provides document interchange using a common file and directory structure over several standard media. This permits the patient to use physical media to carry medical documents. This also permits the use of person-to-person email to convey medical documents.


ZKEYWORD: XDR
ZNAME: Cross-Enterprise Document Reliable Interchange
ZTFDESCRIPTION:
  Cross-Enterprise Document Reliable Interchange (XDR) provides document interchange using a reliable messaging system. This permits direct document interchange between EHRs, PHRs, and other healthcare IT systems in the absence of a document sharing infrastructure such as XDS.


ZKEYWORD: XDS.a
ZNAME: Cross-Enterprise Clinical Documents Share (XDS.a)
ZTFDESCRIPTION:
  The Cross-Enterprise Clinical Document Sharing IHE Integration Profile facilitates the registration, distribution and access across health enterprises of patient electronic health records. Cross-Enterprise Document Sharing (XDS) is focused on providing a standards-based specification for managing the sharing of documents between any healthcare enterprise, ranging from a private physician office to a clinic to an acute care in-patient facility.


ZKEYWORD: XDS.b
ZNAME: Cross-Enterprise Clinical Documents Share (XDS.b)
ZTFDESCRIPTION:
  The XDS.b Integration Profile is part of the family of XDS profiles. It supports these features (in comparison to XDS.a): <ul><li>Change in the XDS metadata form from ebXML Reg/Rep RIM 2.1 to version 3.0</li><li>A new repositoryUniqueId attribute added to the XDS metadata</li><li>Definition of a new transaction &quot;Retrieve Document Set&quot; as a new binding for the XDS.a Retrieve Document [ITI-17] transaction</li><li>Definition of updated bindings for existing transactions to reflect changes in the web services specifications</li></ul>


ZKEYWORD: XDS-I
ZNAME: Cross-enterprise Document Sharing for Imaging
ZTFDESCRIPTION:
  The Cross-enterprise Document Sharing for Imaging (XDS-I) Integration Profile specifies actors and transactions that allow users to share imaging information across enterprises. This profile depends on the IHE IT-Infrastructure Cross-Enterprise Document Sharing (XDS) profile. XDS for Imaging (XDS-I) defines the information to be shared such as sets of DICOM instances (including images, evidence documents, and presentation states), diagnostic imaging reports provided in a ready-for-display.


ZKEYWORD: XDS-MS
ZNAME: Cross-Enterprise Sharing of Medical Summaries
ZTFDESCRIPTION:
  a mechanism to automate the sharing process between care providers of Medical Summaries, a class of clinical documents that contain the most relevant portions of information about the patient intended for a specific provider or a broad range of potential providers in different settings. Medical Summaries are commonly created and consumed by electronic medical record systems at points in time of transfers of care such as referrals or discharge.


ZKEYWORD: XDS-SD
ZNAME: Cross-Enterprise Document Sharing of Scanned Documents
ZTFDESCRIPTION:
  XDS-SD defines how to couple legacy information, represented within a structured HL7 CDA R2 header, with a PDF or plaintext formatted document containing clinical information. Furthermore, this profile defines elements of the CDA R2 header necessary to minimally annotate these documents.


ZKEYWORD: XPHR
ZNAME: Exchange of Personal Health Record Content
ZTFDESCRIPTION:
  The Exchange of Personal Health Record Content (XPHR) integration profile describes the content and format of summary information extracted from a PHR system used by a patient for import into healthcare provider information systems, and visa versa. The purpose of this profile is to support interoperability between PHR systems used by patients and the information systems used by healthcare providers. This profile does not address all the data exchange requirements of PHR systems. A PHR system may leverage other IHE Integration and Content Profiles for interoperability in addition to the XPHR Content Profile. For example, a PHR Systems may implement XDS-MS to import medical summaries produced by EHR systems, XDS-I to import imaging information, XDS-Lab to import laboratory reports, et cetera.


ZKEYWORD: XUA
ZNAME: Cross Enterprise User Authentication
ZTFDESCRIPTION:
  provides user identity in transactions that cross enterprise boundaries, specifically the XDS profile that creates an Affinity Domain. When transactions cross enterprise boundaries the mechanisms found in the EUA and PWP profile are insufficient and often nonfunctional. Enterprises may choose to have their own user directory and their own unique method of authenticating. To provide accountability in these cross enterprise transactions there is a need to identify the requesting user in a way that the receiver can make access decisions and proper audit entries.


