--
--

--SET client_encoding = 'UTF8';
--SET standard_conforming_strings = off;
--SET check_function_bodies = false;
--SET client_min_messages = warning;
--SET escape_string_warning = off;

--SET search_path = public, pg_catalog;

--
-- Data for Name: tf_integration_profile; Type: TABLE DATA; Schema: public; Owner: gazelle
--

INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (7, '2008-04-17 12:10:28.718754', '0', 'ED-CARD', 'Cardiology Evidence Documents', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (10, '2008-04-17 12:10:28.72185', '0', 'KIN', 'Key Image Note', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (11, '2008-04-17 12:10:28.722505', '0', 'SINR', 'Simple Image and Numeric Report', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (12, '2008-04-17 12:10:28.723157', '0', 'ED', 'Evidence Documents', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (13, '2008-04-17 12:10:28.72391', '0', 'RID', 'Retrieve Information for Display', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (160, '2009-08-11 12:42:04.78', 'admin', 'IDCO', 'Implantable Device - Cardiac - Observation', 'IDCO specifies the creation, transmission, and processing of discrete data elements and report attachments associated with implantable cardiac device interrogations (observations) or messages.', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (15, '2008-04-17 12:10:28.725364', '0', 'PDI', 'Portable Data for Imaging', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (16, '2008-04-17 12:10:28.72619', '0', 'ARI', 'Access to Radiology Information', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (17, '2008-04-17 12:10:28.726844', '0', 'CPI', 'Consistent Presentation of Images', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (6, '2009-07-03 08:13:09.839', 'admin', 'DRPT', 'Displayable Reports', '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).', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (126, '2009-08-19 07:35:17.622', 'fourquetl', 'TP21', 'HITSP Query for Existing Data', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (2, '2009-07-08 16:20:08.383', 'admin', 'PWP', 'Personnel White Pages', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (4, '2009-07-08 16:21:57.949', 'admin', 'LDA', 'Laboratory Device Automation', '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. ', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (8, '2009-08-19 06:25:16.051', 'fourquetl', 'C36', 'Lab Result Message Component', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (19, '2008-04-17 12:10:28.728308', '0', 'XDS-MS', 'Cross-Enterprise Sharing of Medical Summaries', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (20, '2008-04-17 12:10:28.749911', '0', 'XDM', 'Cross-Enterprise Document Media Interchange', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (22, '2008-04-17 12:10:28.751778', '0', 'XDS-SD', 'Cross-Enterprise Document Sharing of Scanned Documents', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (23, '2008-04-17 12:10:28.753647', '0', 'BPPC', 'Basic Patient Privacy Consents', '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', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (24, '2008-04-17 12:10:28.754606', '0', 'EDR', 'Emergency Department Referral', '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).', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (26, '2008-04-17 12:10:28.756328', '0', 'XPHR', 'Exchange of Personal Health Record Content', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (21, '2009-07-03 08:14:51.169', 'admin', 'XDR', 'Cross-Enterprise Document Reliable Interchange', '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.', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (33, '2009-07-03 08:59:10.444', 'admin', 'QED', 'Query for Existing Data', '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. ', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (27, '2009-07-12 22:20:45.035', 'admin', 'DEC', 'Device Enterprise Communication', '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.', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (31, '2009-07-14 10:00:48.065', 'admin', 'EDES', 'Emergency Department Encounter Summary', '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.', 2);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (34, '2009-08-21 12:29:44.782', 'fourquetl', 'C28', 'HITSP Emergency Encounter Summary Documents Component', '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).', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (28, '2009-07-24 16:05:03.003', 'admin', 'XD-LAB', 'Sharing Lab Report', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (32, '2009-08-13 23:05:22.049', 'smoore', 'FSA', 'Functional Status Assessment', '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.', 3);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (155, '2009-08-21 21:41:56.619', 'fourquetl', 'T66', 'HITSP Sharing Value Sets - SVS', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (121, '2009-08-19 06:17:32.09', 'fourquetl', 'C19', 'HITSP Entity Identity Assertion Component', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (137, '2009-08-21 21:57:29.648', 'fourquetl', 'T16', 'HITSP T16: Consistent Time', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (37, '2008-04-17 12:10:28.775021', '0', 'HITSPIHE', 'HITSP Testing using IHE Profiles', 'HITSP Testing using IHE Profiles', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (39, '2008-04-17 12:10:28.790411', '0', 'XDS.b', 'Cross-Enterprise Clinical Documents Share (XDS.b)', '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>', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (40, '2008-04-17 12:10:28.740801', '0', 'PIX', 'Patient Identifier Cross-referencing for MPI', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (41, '2008-04-17 12:10:28.741754', '0', 'PDQ', 'Patient Demographics Query', '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).', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (42, '2008-04-17 12:10:28.742814', '0', 'PSA', 'Patient Synchronized Application ', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (9, '2009-08-19 06:26:07.172', 'fourquetl', 'C37', 'Lab Report Document Component', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (47, '2008-04-17 12:10:28.729005', '0', 'CT', 'Consistent Time', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (49, '2008-04-17 12:10:28.736696', '0', 'EUA', 'Enterprise User Authentication', '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', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (50, '2008-04-17 12:10:28.738894', '0', 'XUA', 'Cross Enterprise User Authentication', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (46, '2009-07-03 08:59:58.328', 'admin', 'DSG', 'Digital Signature', '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.', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (45, '2009-07-03 09:00:21.251', 'admin', 'PDQV3', 'Patient Demographic Query HL7 V3', '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).', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (44, '2009-07-03 09:02:43.549', 'admin', 'PIXV3', 'Patient Identifier Cross-Reference HL7 V3', '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.', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (48, '2009-07-08 17:27:41.641', 'admin', 'ATNA', 'Audit Trail and Node Authentication ', '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. ', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (149, '2009-08-19 07:50:10.711', 'fourquetl', 'TP22', 'Patient ID Cross-Referencing using IHE PIX', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (52, '2008-04-17 12:10:28.696413', '0', 'SWF', 'Scheduled Workflow', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (55, '2008-04-17 12:10:28.699382', '0', 'PIR', 'Patient Information Reconciliation', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (56, '2008-04-17 12:10:28.700224', '0', 'PGP', 'Presentation of Grouped Procedures', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (57, '2008-04-17 12:10:28.701117', '0', 'RWF', 'Reporting Workflow', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (58, '2008-04-17 12:10:28.701923', '0', 'NMI', 'NM Image', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (59, '2008-04-17 12:10:28.703586', '0', 'CHG', 'Charge Posting', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (54, '2009-07-08 17:22:43.023', 'admin', 'ECHO', 'Echocardiography Workflow', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (133, '2009-08-19 06:35:39.388', 'fourquetl', 'C82', 'HITSP Common Alerting Protocol', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (131, '2009-08-19 06:34:05.794', 'fourquetl', 'C62', 'HITSP XDS-SD', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (123, '2009-08-21 21:49:45.379', 'fourquetl', 'T15', 'HITSP Collect and Communicate Audit Trail', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (125, '2009-08-22 01:50:20.891', 'fourquetl', 'TP30', 'HITSP Manage Consent Directions Transaction Package', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (60, '2008-04-17 12:10:28.711804', '0', 'PWF', 'Post-Processing Workflow', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (63, '2008-04-17 12:10:28.746218', '0', 'IRWF', 'Import Reconciliation Workflow', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (64, '2008-04-17 12:10:28.74714', '0', 'MAMMO', 'Mammography Image', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (71, '2008-04-17 12:10:28.788402', '0', 'LTW', 'Laboratory Testing Workflow ', '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.   ', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (35, '2009-08-19 06:30:10.994', 'fourquetl', 'C32', 'Registration and Medication History Document Component', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (69, '2009-07-28 14:31:00.785', 'admin', 'ECED', 'Eye Care Evidence Documents', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (70, '2009-07-28 14:31:59.274', 'admin', 'ECDR', 'Eye Care Displayable Reports', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (66, '2009-07-08 17:37:26.997', 'admin', 'STRESS', 'Stress Testing Workflow', 'The Stress Testing Workflow Profile provides the mechanism for ordering and collecting multi-modality data during diagnostic Stress testing procedures.', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (68, '2009-07-28 14:31:37.047', 'admin', 'EYE-CHG', 'Eye Care Charge Posting', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (147, '2008-08-18 21:30:00', '0', 'TP13b', 'Manage Sharing of Documents (XDS.B Option)', 'US HITSP: TP13b: Manage Sharing of Documents (with reference to the IHE XDS.b supplement to suport Entity Identity)', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (130, '2009-08-19 06:27:15.271', 'fourquetl', 'C38', 'C38 Patient Level Quality Document Using IHE Medical Summary (XDS-MS)', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (154, '2009-08-19 06:29:25.572', 'fourquetl', 'C26', 'HITSP Nonrepudiation of Origin Component', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (144, '2009-08-21 23:09:25.816', 'fourquetl', 'T63', 'HITSP Emergency Message Distribution Element', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (143, '2009-08-21 23:37:10.809', 'fourquetl', 'T81', 'HITSP T81 Retrieval of Medical Knowledge', '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.', 7);

INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (73, '2008-04-17 12:10:28.713458', '0', 'LCSD', 'Laboratory Code Set Distribution', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (75, '2008-04-17 12:10:28.716779', '0', 'LPOCT', 'Laboratory Point Of Care Testing', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (84, '2009-08-11 21:46:52.01', 'furst', 'PIV', 'Point-of-Care Infusion Verification', '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.', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (87, '2009-07-02 13:18:56.457', 'admin', 'BIR', 'Basic Image Review', '', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (88, '2009-07-02 13:19:57.751', 'admin', 'PERF', 'CT/MR Perfusion with Imaging Contrast', '', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (77, '2009-07-03 09:09:03.825', 'admin', 'REM', 'Radiation Exposure Monitoring', '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.', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (80, '2009-07-03 09:11:35.413', 'admin', 'DRR', 'Document-based Referral Request', '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.', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (79, '2009-07-03 09:11:58.838', 'admin', 'SVS', 'Sharing Value Sets', '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.', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (85, '2009-07-03 09:14:50.722', 'admin', 'CRD', 'Clinical Research Data Capture', '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.', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (83, '2009-07-12 21:29:10.466', 'admin', 'ACM', 'Alarm Communication Management', '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.', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (81, '2009-07-13 21:24:24.80', 'admin', 'CM', 'Care Management', '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.', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (78, '2009-07-13 22:06:20.605', 'admin', 'APR', 'Antepartum Record', '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.', 2);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (132, '2009-08-19 06:33:01.223', 'fourquetl', 'C78', 'HITSP Immunization Content', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (82, '2009-07-13 23:32:43.073', 'admin', 'IC', 'Immunization Content', 'Immunization Content', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (86, '2009-07-14 11:21:48.719', 'admin', 'APW', 'Pathology Workflow', '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', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (134, '2009-08-19 06:36:31.182', 'fourquetl', 'C76', 'HITSP Case Report Pre-populate', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (89, '2009-07-02 13:20:37.184', 'admin', 'DIFF', 'MR Diffusion Imaging', '', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (90, '2009-07-02 13:21:40.997', 'admin', 'XDS-I.b', 'Cross-Enterprise Document Sharing for Imaging', '', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (92, '2009-07-02 13:24:11.841', 'admin', 'MPQ', 'Multi-Patient Queries', '', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (93, '2009-07-02 13:25:01.273', 'admin', 'XCPD', 'Cross Community Patient Discovery', '', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (1, '2009-07-03 08:12:55.703', 'admin', 'RFD', 'Retrieve Form for Data Capture', '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.', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (18, '2009-07-03 08:14:21.812', 'admin', 'XDS-I', 'Cross-enterprise Document Sharing for Imaging', '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.', 6);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (29, '2009-07-03 08:15:27.136', 'admin', 'XCA', 'Cross Community Access', '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.', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (38, '2009-07-03 08:59:36.715', 'admin', 'XDS.a', 'Cross-Enterprise Clinical Documents Share (XDS.a)', '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.', 6);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (51, '2009-07-03 09:01:23.948', 'admin', 'SEC', 'Basic Security', '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.', 6);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (62, '2009-07-03 09:03:36.394', 'admin', 'FUS', 'Image Fusion', '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', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (43, '2009-08-13 16:36:12.615', 'admin', 'PAM', 'Patient Administration Management', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (76, '2009-07-03 09:08:17.432', 'admin', 'MAWF', 'Mammography Acquisition Workflow', '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.', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (74, '2009-07-03 09:15:46.428', 'admin', 'TCE', 'Teaching File and Clinical Trial Export', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (94, '2009-07-08 14:32:32.52', 'admin', 'RTO', 'Radiation Therapy Objects', 'involves the flow of DICOM images and treatment planning data, from CT scan through dose display, for 3D conformal, external beam radiation therapy', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (95, '2009-07-08 14:35:36.30', 'admin', 'REG', 'Image Registration', '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.', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (96, '2009-07-08 15:25:25.686', 'admin', 'MDW', 'Managed Delivery Workflow', '', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (3, '2009-07-08 17:00:03.818', 'admin', 'NAV', 'Notification of Document Availability', '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.', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (91, '2009-07-17 11:23:46.618', 'admin', 'DSUB', 'Document Metadata Subscription', '', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (135, '2009-08-19 06:37:33.941', 'fourquetl', 'C72', 'HITSP Vaccination Message', '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', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (161, '2009-08-19 22:36:33.463', 'fourquetl', 'C25', 'HITSP Anonymize Component', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (53, '2009-07-08 17:21:28.167', 'admin', 'CATH', 'Cardiac Catheterization Workflow', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (14, '2009-07-08 17:28:26.981', 'admin', 'ECG', 'Retrieve ECG for Display', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (98, '2009-07-13 22:20:08.772', 'admin', 'APHP', 'Antepartum History and Physical', 'Antepartum History and Physical', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (99, '2009-07-13 22:20:42.031', 'admin', 'APE', 'Antepartum Education', 'Antepartum Education', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (100, '2009-07-13 22:21:18.966', 'admin', 'APL', 'Antepartum Laboratory', 'Antepartum Laboratory', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (97, '2009-07-13 23:00:30.97', 'admin', 'APS', 'Antepartum Summary', 'Antepartum Summary', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (106, '2009-07-13 23:34:36.066', 'admin', 'LDHP', 'Labor and Delivery Health and Physical', 'Labor and Delivery Health and Physical', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (107, '2009-07-13 23:35:01.747', 'admin', 'LDS', 'Labor and Delivery Summary', 'Labor and Delivery Summary', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (108, '2009-07-13 23:35:28.607', 'admin', 'MDS', 'Maternal Discharge Summary', 'Maternal Discharge Summary', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (109, '2009-07-13 23:43:22.369', 'admin', 'PPOC', 'Patient Plan of Care', 'Patient Plan of Care', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (110, '2009-07-14 09:46:47.719', 'admin', 'RCG', 'Request for Clinical Guidance', 'Request for Clinical Guidance', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (111, '2009-07-14 09:47:27.337', 'admin', 'ICP', 'Immunization Care Plan', 'Immunization Care Plan', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (61, '2009-07-14 10:06:39.459', 'admin', 'DWF', 'Departmental Workflow', '<p>The IHE Departmental Workflow  is centrally monitored by the Department System Scheduler/ Order Filler, but its execution may be managed by distributing further control into two levels.</p><p> The first is a set of one or more Worklist managers that are responsible for management of worklist items used to control the activities within a certain phase of a requested procedure. Worklist Managers are also responsible for conveying phase status and information availability to the Workflow Manager and other peer Worklist Managers. The Worklist Manager s method to generate worklist items is not explicitly described by IHE. Currently it is assumed that a Worklist Manager uses internal logic to generate worklist items. Generation of worklist items directly triggered by an actor other than the Worklist Manager is not defined in this concept paper, and would require additional communication between this other actor and the Worklist Manager. </p><p>The second level is a set of workflow participants that are entirely in charge of performing specific procedure steps. This level is defined in detail in the existing individual workflow profile already included in the IHE Radiology Technical Framework and is not described further in this paper.', 1);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (112, '2009-07-14 10:55:09.345', 'admin', 'MCH', 'Mother and Child Health', 'Mother and Child Health', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (113, '2009-07-14 11:05:41.459', 'admin', 'DSC', 'Drug Safety Content', 'Drug Safety Content', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (114, '2009-07-14 11:15:46.289', 'admin', 'RPE', 'Retrieve Protocol for Execution', 'Retrieve Protocol for Execution', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (115, '2009-07-14 11:23:05.618', 'admin', 'ARPH', 'Anatomic Pathology Reporting to Public Health', 'Anatomic Pathology Reporting to Public Health', 3);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (116, '2009-07-24 15:43:25.821', 'admin', 'ILW', 'Inter-Laboratory Workflow', 'Inter-Laboratory Workflow', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (67, '2009-07-28 14:30:12.554', 'admin', 'EYECARE', 'Eye Care Workflow', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (101, '2009-08-11 17:30:22.695', 'smoore', 'TN', 'Triage Note', 'Triage Note', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (102, '2009-08-11 17:30:53.294', 'smoore', 'NN', 'Nursing Note', 'Nursing Note', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (103, '2009-08-11 17:31:20.947', 'smoore', 'CTNN', 'Composite Triage and Nursing Note', 'Composite Triage and Nursing Note', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (5, '2008-04-17 12:10:28.752691', '0', 'XD-Star', 'XDM, XDR, XDS', 'XD-Star is a virtual profile that represents one of XDM, XDR, XDS. You cannot register for XD-Star, but will register for one or more of XDM, XDR, XDS', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (104, '2009-08-11 17:31:43.489', 'smoore', 'EDPN', 'ED Physician Note', 'ED Physician Note', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (136, '2009-08-19 06:38:28.161', 'fourquetl', 'C48', 'HITSP Encounter Document Using IHE Medical Summary (XDS-MS)', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (36, '2009-08-19 07:28:59.603', 'fourquetl', 'TP13', 'Manage Sharing of Documents Transaction Package with Doc Integrity Check', '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.', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (194, '2009-08-21 06:24:54.126', 'fourquetl', 'C144', 'Labor and Delivery Report', 'birthing Summary/delivery record', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (195, '2009-08-21 06:28:15.914', 'fourquetl', 'C145', 'Vaccine Forecast', 'HITSP Vaccine Forecast Component', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (196, '2009-08-21 06:32:22.124', 'fourquetl', 'C148 ', 'HITSP EMS Transfer of Care', 'HITSP EMS Transfer of Care', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (105, '2009-08-21 06:33:45.634', 'fourquetl', 'ETC', 'EMS Transfer of Care', 'US HITSP: EMS Transfer of care', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (146, '2009-08-19 19:51:46.903', 'fourquetl', 'TP13a', 'Manage Sharing of Documents (XDS.A Option)', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (165, '2009-08-20 16:00:53.245', 'fourquetc', 'C34', 'HITSP Patient Level Quality Data Message Component', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (166, '2009-08-20 16:02:54.347', 'fourquetc', 'C35', 'HITSP EHR Lab Result Terminology Component', 'The Lab Result Terminology Component defines the vocabulary for either message-based or document-based laboratory results reporting.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (167, '2009-08-20 16:05:01.155', 'fourquetc', 'C39', 'HITSP Encounter Message Component', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (168, '2009-08-20 16:07:27.634', 'fourquetc', 'C41', 'HITSP Radiology Result Message Component', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (169, '2009-08-20 16:09:27.088', 'fourquetc', 'C44', 'HITSP Secure Web Connection Component', 'The Secure Web Connection Component provides the capability to access documents through a secure web browser.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (170, '2009-08-20 16:11:17.771', 'fourquetc', 'C47', 'HITSP Resource Utilization Message Component', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (171, '2009-08-20 16:13:03.064', 'fourquetc', 'C70', 'Immunization Query and Response', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (172, '2009-08-20 16:15:09.608', 'fourquetc', 'C74', 'Remote Monitoring Observation Document Component', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (173, '2009-08-20 16:16:43.944', 'fourquetc', 'C75', 'Healthcare Associated Infection (HAI) Report Component', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (174, '2009-08-20 16:18:20.069', 'fourquetc', 'C80', 'Clinical Document and Message Terminology Component', 'The Clinical Document and Message Terminology Component defines the vocabularies and terminologies utilized by HITSP specifications for Clinical Documents and Messages used to support the interoperable transmission of information. View the most current version as HTML here.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (175, '2009-08-20 16:19:24.578', 'fourquetc', 'C83', 'CDA Content Modules Component', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (176, '2009-08-20 16:20:56.757', 'fourquetc', 'C84', 'Consult and History & Physical Note Component', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (177, '2009-08-20 16:24:27.038', 'fourquetc', 'C87', 'Anonymize Public Health Case Reporting Data Component', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (178, '2009-08-20 16:25:32.251', 'fourquetc', 'C88', 'Anonymize Immunizations and Response Management Data Component', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (179, '2009-08-20 16:26:37.565', 'fourquetc', 'C90', 'Clinical Genomic Decision Support Component', 'The Family History Decision Support for Genetic Risk Analysis Component is used to communicate genetic and family history information from healthcare IT applications to a clinical decision support system that provides an assessment of genetic risk of disease for a patient. It uses the HL7 Version 3 Standard: Clinical Genomics; Pedigree, Release 1 to support the communication of genetic and family history information to the clinical decision support system, and to support the communication of risk information from that system back to the originator. View the most current version as HTML here.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (180, '2009-08-20 16:27:12.05', 'fourquetc', 'C105', 'Patient Level Quality Data Document Using HL7 Quality Reporting Document Architecture (QRDA)', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (181, '2009-08-20 16:28:49.909', 'fourquetc', 'C106', 'Measurement Criteria Document', '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', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (182, '2009-08-20 17:10:16.121', 'fourquetc', 'TP14', 'HITSP Send Laboratory Result Message to Ordering Clinician and Providers of Care Transaction Package', 'The Send Laboratory Result Message Transaction supports: transmission of complete, preliminary, final and updated laboratory results to the EHR system (local or remote) of the ordering clinician; and 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).', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (183, '2009-08-20 17:11:26.093', 'fourquetc', 'TP43', 'HITSP Medication Orders Transaction Package', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (184, '2009-08-20 17:12:03.806', 'fourquetc', 'TP46', 'HITSP Medication Formulary and Benefits Information Transaction Package', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (185, '2009-08-20 17:12:57.779', 'fourquetc', 'TP89', 'Sharing Imaging Results Transaction Package', 'The Sharing Imaging Results Transaction Package supports the process of sharing medical imaging results data. Imaging results data are captured as part of the normal process of care performed by healthcare providers. This data can be made available through document sharing for both clinical care and public health purposes. View the most current version as HTML here', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (186, '2009-08-20 17:14:39.516', 'fourquetc', 'T14', 'HITSP Send Laboratory Result Message Transaction', '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) ', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (187, '2009-08-20 17:16:12.208', 'fourquetc', 'T18', 'HITSP View Laboratory Results from a Web Application Transaction', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (188, '2009-08-20 17:16:47.297', 'fourquetc', 'T24', 'HITSP Pseudonymize Transaction', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (189, '2009-08-20 17:17:33.999', 'fourquetc', 'T40', 'HITSP Patient Generic Health Plan Eligibility Verification Transaction', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (190, '2009-08-20 17:18:22.35', 'fourquetc', 'T42', 'HITSP Medication Dispensing Status Transaction', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (191, '2009-08-20 17:19:00.91', 'fourquetc', 'T68', 'Patient Health Plan Authorization Request and Response Transaction', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (192, '2009-08-20 17:19:36.283', 'fourquetc', 'T79', 'Pharmacy to Health Plan Authorization Request and Response Transaction', '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', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (193, '2009-08-20 17:20:14.729', 'fourquetc', 'T85', 'Administrative Transport to Health Plan', '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', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (198, '2009-08-21 12:23:23.173', 'fourquetl', 'C151', 'Clinical Research Document ', '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', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (200, '2009-08-21 12:28:51.122', 'fourquetl', 'C150', 'HITSP Mother and Child Health', 'US HITSP: C150 Mother and Child Health', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (201, '2009-08-21 12:32:18.125', 'fourquetl', 'TP149', 'HITSP Retrieve Protocol for Execution', 'US HITSP: TP149 Retrieve Protocol for Execution', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (203, '2009-08-21 12:39:08.023', 'fourquetl', 'C153', 'HITSP Anonymize Clinical Research Data', 'US HITSP: C153 HITSP Anonymize Clinical Research Data', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (202, '2009-08-21 12:41:22.825', 'fourquetl', 'C152', 'HITSP Clinical Research Data Acquisition', 'US HITSP: C152  Clinical Research Data Acquisition', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (124, '2009-08-21 21:58:13.543', 'fourquetl', 'T17', 'HITSP Secured Communication Channel Transaction', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (150, '2009-08-21 22:07:07.259', 'fourquetl', 'T23', 'HITSP Patient Demographics Query Transaction', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (138, '2009-08-21 22:49:29.217', 'fourquetl', 'T29', 'HITSP Notification of Document Availability Transaction', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (139, '2009-08-21 22:52:52.831', 'fourquetl', 'T31', 'HITSP Reliable Document Exchange', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (145, '2009-08-21 22:56:57.896', 'fourquetl', 'T33', 'Transfer of Documents on Media', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (142, '2009-08-21 23:10:32.086', 'fourquetl', 'T64', 'HITSP Personnel White Pages', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (140, '2009-08-21 23:22:38.213', 'fourquetl', 'T67', 'HITSP Document-based Referral - DRR', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (204, '2009-08-21 23:46:42.725', 'fourquetl', 'T73', 'HITSP Aggregate Device Information Communication', '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', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (148, '2009-08-22 01:45:56.702', 'fourquetl', 'TP50', 'HITSP Retrieve Form for Data Capture', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (151, '2009-08-22 01:47:22.445', 'fourquetl', 'TP49', 'HITSP Sharing Radiology Results Transaction Package', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (152, '2009-08-22 01:56:10.89', 'fourquetl', 'TP20', 'HITSP Access Control', '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.', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (206, '2009-08-22 02:13:13.106', 'fourquetl', 'T147', ' HITSP Multi-Patient Queries', 'US HITSP: T147 Multi-Patient Queries', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, keyword, name, description, integration_profile_status_type_id) VALUES (208, '2009-08-22 02:19:12.024', 'fourquetl', 'T146', 'HITSP Document Metadata Subscription', 'US HITSP: T146  Document Metadata Subscription', 5);


--
--

