-- 00_functions_data.sql
DROP FUNCTION IF EXISTS comma_cat(text, text) CASCADE ;
CREATE FUNCTION comma_cat(text, text) RETURNS text AS $_$select case WHEN $2 is null or $2 = '' THEN $1 WHEN $1 is null or $1 = '' THEN $2 ELSE $1 || ', ' || $2 END$_$ LANGUAGE sql; 
ALTER FUNCTION public.comma_cat(text, text) OWNER TO gazelle;
CREATE AGGREGATE list ( BASETYPE = text, SFUNC = comma_cat, STYPE = text, INITCOND = '');
ALTER AGGREGATE public.list(text) OWNER TO gazelle;
-- 00_cmn_application_preference_data.sql
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value)VALUES (1, 'java.lang.String', 'Application name', 'application_name', 'EVSClient');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (2, 'java.lang.String', 'Admin (name) used to manage the application', 'application_admin_name', 'Eric Poiseau');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (3, 'java.lang.String', 'Admin (email) used to manage the application', 'application_admin_email', 'technical.manager@ihe-europe.net');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (4, 'java.lang.String', 'Account (email address) where are sent all emails as BCC (for emails history/checking in)', 'application_email_account_for_history', 'net.gazelle.dev@gmail.com');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (5, 'java.lang.String', 'Default time zone used by the application', 'time_zone', 'UTC+01');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (6, 'java.lang.String', 'URL basename used to reach the application', 'application_url_basename', 'EVSClient');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (7, 'java.lang.String', 'Issue Tracker Website URL - Used by some links in the application to report a problem (eg. of value = http://sumo.irisa.fr:8080/jira/ )', 'application_issue_tracker_url', 'http://gazelle.ihe.net/jira');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (8, 'java.lang.String', 'Gazelle Release Notes URL - Used by some links in the application to detail each Gazelle Release : improvements, bug fixed (eg. of value = http://sumo.irisa.fr/europe2009/gazelle_release_notes.html )', 'application_gazelle_release_notes_url', 'http://gazelle.ihe.net/?eq=node/80');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (9, 'java.lang.String', 'Application zone (possible values :  "EUROPE", "NA" , "JAPAN") - Rendered pages depend on the zone (homepage, contacts, informations... )', 'application_zone', 'EUROPE');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (10, 'java.lang.String', 'Application profile (possible values :  "dev", "prod") - Rendered pages/components depend on the profile value ', 'application_profile', 'dev');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (11, 'java.lang.String', 'Application build time (Ant)', 'application_build_time', '01/07/2011 14:17:06');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (12, 'java.lang.String', 'This value does NOT change. It indicates if DB has been dropped and SQL imported during deployment ? ', 'application_db_drop_and_import', 'create-drop');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (13, 'java.lang.String', 'This value does NOT change. It indicates if Drools has beeen loaded at startup ? (to improve speed deployment)', 'application_drools_loaded_at_startup', 'true');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (14, 'java.lang.String', 'ABSOLUTE PATH TO Gazelle home path. Here is where are stored generated datas, reports and other required binaries for application', 'gazelle_home_path', '/opt/EVSClient_dev');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (15, 'java.lang.String', 'RELATIVE PATH TO gazelle_home_path. This value normally does NOT change. It corresponds to Gazelle data path inside "gazelle_home_path". Here is where data (invoices, integration statements... will be stored).', 'data_path', 'data');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (16, 'java.lang.String', 'RELATIVE PATH TO gazelle_home_path. This value normally does NOT change. It corresponds to Gazelle reports path inside "gazelle_home_path". Here is where are stored required reports', 'reports_path', 'reports');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (17, 'java.lang.String', 'RELATIVE PATH TO gazelle_home_path. This value normally does NOT change. It corresponds to Gazelle bin path inside "gazelle_home_path". Here is where are stored required binaries', 'bin_path', 'bin');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (18, 'java.lang.String', 'root oid for validated object', 'root_oid', '1.1.1.1.1.1.');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (19, 'java.lang.String', 'path to the repository where cda files are stored', 'cda_repository', '/opt/EVSClient_dev/validatedObjects/CDA');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (20, 'java.lang.String', 'path to the repository where HL7v3 messages are stored', 'hl7v3_repository', '/opt/EVSClient_dev/validatedObjects/HL7v3');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (21, 'java.lang.String', 'path to the repository where Audit messages are stored', 'atna_repository', '/opt/EVSClient_dev/validatedObjects/ATNA');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (22, 'java.lang.String', 'path to the repository where Assertions are stored', 'saml_repository', '/opt/EVSClient_dev/validatedObjects/SAML');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (23, 'java.lang.String', 'path to the repository where DICOM objects are stored', 'dicom_repository', '/opt/EVSClient_dev/validatedObjects/DICOM');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (24, 'java.lang.String', 'path to the repository where tls files are stored', 'tls_repository', '/opt/EVSClient_dev/validatedObjects/TLS');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (9999, 'java.lang.String', 'Checking Flag : if this value is inserted in the database, it means that database has been successfully populated during deployment', 'application_database_initialization_flag', 'database_successfully_initialized');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (25, 'java.lang.String', '', 'gazelle_hl7v2_validator_url', 'http://gazelle.ihe.net/GazelleHL7v2Validator');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (26, 'java.lang.String', 'email of the person monitoring the application', 'monitor_email', 'anne-gaelle.berge@ihe-europe.net');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (27, 'java.lang.String', '', 'xdw_repository', '/opt/EVSClient_dev/validatedObjects/xdw');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (28, 'java.lang.String', 'tutu', 'xds_repository', '/opt/EVSClient_dev/validatedObjects/xds');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (29, 'java.lang.String', '', 'pdf_repository', '/opt/EVSClient_dev/validatedObjects/pdf');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (30, 'java.lang.String', 'URL used to reach the application', 'application_url', 'http://localhost:8080/EVSClient');
INSERT INTO cmn_application_preference (id, class_name, description, preference_name, preference_value) VALUES (31, 'java.lang.String', '', 'svs_repository', '/opt/EVSClient_dev/validatedObjects/SVS');
-- 01_referenced_standard_data.sql
INSERT INTO evsc_referenced_standard (id, description, extension, label, name, version, path_to_xsl) VALUES (2, 'version 2.4 of HL7 standard', 'None', 'HL7v2.4', 'HL7', '2.4', NULL);
INSERT INTO evsc_referenced_standard (id, description, extension, label, name, version, path_to_xsl) VALUES (3, 'version 2.5 of HL7 standard', 'None', 'HL7v2.5', 'HL7', '2.5', NULL);
INSERT INTO evsc_referenced_standard (id, description, extension, label, name, version, path_to_xsl) VALUES (5, 'epSOS specific CDA', 'epSOS', 'CDA-epSOS', 'CDA', NULL, 'http://gazelle.ihe.net/xsl/cda.xsl');
INSERT INTO evsc_referenced_standard (id, description, extension, label, name, version, path_to_xsl) VALUES (9, 'Digital Imaging And Communication in Medicine', 'None', 'DICOM', 'DICOM', 'None', NULL);
INSERT INTO evsc_referenced_standard (id, description, extension, label, name, version, path_to_xsl) VALUES (10, 'version 2.5.1 of HL7 standard', 'None', 'HL7v2.5.1', 'HL7', '2.5.1', NULL);
INSERT INTO evsc_referenced_standard (id, description, extension, label, name, version, path_to_xsl) VALUES (11, 'version 2.6 of HL7 standard', 'None', 'HL7v2.6', 'HL7', '2.6', NULL);
INSERT INTO evsc_referenced_standard (id, description, extension, label, name, version, path_to_xsl) VALUES (13, '', 'epSOS', 'XDS-epSOS', 'XDS', '', NULL);
INSERT INTO evsc_referenced_standard (id, description, extension, label, name, version, path_to_xsl) VALUES (14, '', 'IHE', 'XDS-IHE', 'XDS', '', NULL);
INSERT INTO evsc_referenced_standard (id, description, extension, label, name, version, path_to_xsl) VALUES (12, '', 'None', 'XDW', 'XDW', '', 'http://gazelle.ihe.net/xsl/XDW.xsl');
INSERT INTO evsc_referenced_standard (id, description, extension, label, name, version, path_to_xsl) VALUES (1, 'version 2.3.1 of HL7 standard', 'None', 'HL7v2.3.1', 'HL7', '2.3.1', NULL);
INSERT INTO evsc_referenced_standard (id, description, extension, label, name, version, path_to_xsl) VALUES (16, '', '', 'PDF', 'PDF', '', '');
INSERT INTO evsc_referenced_standard (id, description, extension, label, name, version, path_to_xsl) VALUES (4, 'CDA', 'IHE', 'CDA-IHE', 'CDA', '', 'http://gazelle.ihe.net/xsl/cda.xsl');
INSERT INTO evsc_referenced_standard (id, description, extension, label, name, version, path_to_xsl) VALUES (8, 'security assertion markup language', '', 'SAML', 'SAML', '2.0', '');
INSERT INTO evsc_referenced_standard (id, description, extension, label, name, version, path_to_xsl) VALUES (7, 'audit messages for ATNA', '', 'ATNA', 'ATNA', 'RFC3881', '');
INSERT INTO evsc_referenced_standard (id, description, extension, label, name, version, path_to_xsl) VALUES (6, '', '', 'HL7v3', 'HL7', '3', '');

-- 01_revinfo_data.sql
INSERT INTO revinfo(rev,revtstmp) VALUES (1,null);
-- 01_tf_actor_data.sql
SET escape_string_warning = off;
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1, '2008-04-17 12:09:39.127654', '0', false, 'A system unit that receives and collects audit records from multiple systems.', 'ARR', 'Audit Record Repository');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (2, '2008-04-17 12:09:39.186361', '0', false, 'Receives the posted charges and serves component of the financial system. Further definition of this actor is beyond current IHE scope.', 'CHARGE_PRO', 'Charge Processor');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (3, '2008-04-17 12:09:39.18789', '0', false, 'A system that receives Structured Report Export Transactions from the Report Manager and stores them.', 'ERR', 'Enterprise Report Repository');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (4, '2008-04-17 12:09:39.188887', '0', false, 'A system that performs retrieval of clinical reports containing information generated outside the Radiology department and presented as DICOM Structured Reporting Objects.', 'XRA', 'External Report Repository Access');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (5, '2008-04-17 12:09:39.189807', '0', false, 'A system that provides functions related to post-processing worklist management. This involves the ability to schedule post-processing worklist items (scheduled procedure steps), provide worklist items to post-processing worklist clients, and update the status of scheduled and performed procedure steps as received from post-processing worklist clients.', 'PPM', 'Post-Processing Manager');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (6, '2008-04-17 12:09:39.190791', '0', false, 'A system that accepts and processes DICOM print requests as a DICOM Print SCP and performs image rendering on hardcopy media. The system must support pixel rendering according to the DICOM Grayscale Standard Display Function.', 'PS', 'Print Server');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (7, '2008-04-17 12:09:39.191785', '0', false, 'A system that generates and transmits draft (and optionally, final) reports, presenting them as DICOM Structured Reporting Objects.', 'RC', 'Report Creator');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (8, '2008-04-17 12:09:39.193617', '0', false, 'A system that provides functions related to report management. This involves the ability to handle content and state changes to reports and to create new DICOM Structured Reporting Objects based on these changes. In addition, the Report Manager generates and transmits verified, unsolicited text results to the Enterprise Report Repository.', 'RM', 'Report Manager');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (9, '2008-04-17 12:09:39.194567', '0', false, 'A system that provides long-term storage of reports and their retrieval as DICOM Structured Reporting Objects.', 'RRP', 'Report Repository');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (10, '2008-04-17 12:09:39.195462', '0', false, 'A system unit that validates the identity of any user and of any other node, and determines whether or not access to the system for this user and information exchange with the other node is allowed. Maintains the correct time.', 'SN', 'Secure Node');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (11, '2008-04-17 12:09:39.19634', '0', false, 'A system unit that knows, maintains and distributes the correct time in the enterprise.', 'TS', 'Time Server');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (12, '2008-04-17 12:09:39.197174', '0', false, 'A system responsible for adding and/or updating patient demographic and encounter information. In particular, it registers a new patient with the Order Placer and Department System.', 'ADT', 'ADT Patient Registration');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (13, '2008-04-17 12:09:39.198068', '0', false, 'A department-based information system (for instance, Radiology or Laboratory) that provides functions related to the management of orders received from external systems or through the department system s user interface. Upon a defined workflow action, makes procedures available for charge posting. The action/event that actually causes charges to post is defined by the actor.', 'OF', 'Department System Scheduler/Order Filler');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (14, '2008-04-17 12:09:39.199032', '0', false, 'A system that re-distributes the Modality Performed Procedure Step information from the Acquisition Modality or Image Creator to the Department System Scheduler/Order Filler and Image Manager.', 'PPSM', 'Performed Procedure Step Manager');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (15, '2008-04-17 12:09:39.199924', '0', false, 'A hospital or enterprise-wide system that generates orders for various departments and distributes those orders to the correct department.', 'OP', 'Order Placer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (16, '2008-04-17 12:09:39.200796', '0', false, 'A system that acquires and creates medical images, e.g. a Computed Tomography scanner or Nuclear Medicine camera. A modality may also create Grayscale Softcopy Presentation States for the consistent viewing of images and create Key Image Notes.', 'MOD', 'Acquisition Modality');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (17, '2008-04-17 12:09:39.201676', '0', true, 'A system that provides functions related to safe data storage and image data handling. It supplies image availability information to the Department System Scheduler. It is always grouped with an Image Archive to provide long term storage of images, presentation states, Key Image Notes, and Evidence Documents.', 'IM', 'Image Manager/Archive');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (19, '2008-04-17 12:09:39.203426', '0', false, 'Provide local management of user authentification.', 'CAA', 'Client Authentification Agent');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (20, '2008-04-17 12:09:39.204301', '0', false, 'This actor serves as a broker for the communication between two or more context participant actors (either Patient Context Participant or User Context Participant). It supports the passing of the user and patient subjects', 'CONTXT_MGR', 'Context Manager');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (21, '2008-04-17 12:09:39.205218', '0', false, 'A system that offers requesting of specific information or documents for display the healthcare information returned', 'DISPLAY', 'Display');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (22, '2008-04-17 12:09:39.206089', '0', false, 'A system that responds to requests for specific information or documents and returns ready for presentation information to be displays on the requesting actor.', 'INFO_SRC', 'Information Source');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (23, '2008-04-17 12:09:39.206908', '0', false, 'Provides central authentication of enterprise users.', 'KER_AUTH_SVR', 'Kerberos Authentification Server');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (24, '2008-04-17 12:09:39.207797', '0', false, 'Receives user authentication information for further use by the service that contains this actor', 'KER_SVR', 'Kerberized Server');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (25, '2008-04-17 12:09:39.208714', '0', false, 'This actor participates in a shared context environment by both setting the patient context and responding to context changes as communicated by the Context Manager Actor. This actor shall respond to all patient context changes. This actor shall set the patient context, if the application containing this actor has patient selection capability. ', 'PAT_CONTXT_PARTICIPANT', 'Patient Context Participant');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (26, '2008-04-17 12:09:39.209621', '0', false, 'A part of a system that can access reports through network query/retrieve or reading interchange media and allow the user to view reports presented as DICOM Structured Report Objects.', 'RRD', 'Report Reader');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (27, '2008-04-17 12:09:39.210476', '0', false, 'Serves a well-defined set of Patient Identification Domains. Based on information provided by in each Patient Identification Domain by a Patient Identification Source Actor, it manages the cross-referencing of patient identifiers across Patient Identification Domains.', 'PAT_IDENTITY_X_REF_MGR', 'Patient Identity Cross-reference Manager');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (28, '2008-04-17 12:09:39.211601', '0', false, 'Establishes time synchronization with one or more Time Servers using the NTP protocol and either the NTP or SNTP algorithms.  Maintains the local computer system clock synchronization with UTC based on synchronization with the Time Servers.', 'TIME_CLIENT', 'Time Client');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (29, '2008-04-17 12:09:39.212498', '0', false, 'Receives notification of user context changes and follows them for the application that contains it.', 'USER_CONTXT_PARTICIPANT', 'User Context Participant');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (151, '2009-08-05 15:22:56.907', 'smoore', false, 'Access Control Service', 'ACS', 'Access Control Service');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (152, '2009-08-05 15:24:32.581', 'smoore', false, 'Service Provider', 'SERVICE_PROVIDER', 'Service Provider');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (137, '2009-07-08 14:51:42.362', 'admin', false, 'A system that determines and corrects patient position then delivers therapeutic radiation.', 'PD_SYSTEM', 'Positioning and Delivery System');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (139, '2009-07-14 11:41:14.06', 'admin', false, 'Report Sender', 'RPT_SENDER', 'Report Sender');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (140, '2009-07-14 11:41:31.737', 'admin', false, 'Report Receiver', 'RPT_RECEIVER', 'Report Receiver');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (31, '2008-04-17 12:09:39.214412', '0', false, 'A hospital or enterprise-wide system that stores observations of various types (test results, images, clinical examinations reports, radiology reports, surgical act reports) obtained for the patients, registers all state changes in the results notified by Order Fillers. This actor doesnt store standalone observations, but ordered observations. The observations are always stored within the context of the order that generated them, with all the information related to that order.', 'ORT', 'Order Result Tracker');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (32, '2008-04-17 12:09:39.215207', '0', false, 'A part of a system that can access imaging evidence objects (images, Presentation States, Key Image Notes, Evidence Documents) through network query/retrieve or reading interchange media and allow the user to view these objects.', 'ID', 'Image Display');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (33, '2008-04-17 12:09:39.21611', '0', false, 'A system that generates DICOM print requests to the Print Server. Print requests include presentation state information in the form of Presentation Look-Up Tables (Presentation LUTs). It may also read the DICOM information contained on interchange media.', 'PC', 'Print Composer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (34, '2008-04-17 12:09:39.216887', '0', false, 'This actor assembles the content of the media and writes it to the physical medium.', 'PMC', 'Portable Media Creator');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (35, '2008-04-17 12:09:39.217876', '0', false, 'This actor reads the DICOM information (DICOM FSR) contained on the media. This system provides the user the ability to select a set of DICOM instances and reconcile key patient and study attributes (when necessary) to facilitate inclusion of the imported data in the local information system(s).', 'PMI', 'Portable Media Importer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (36, '2008-04-17 12:09:39.218681', '0', false, 'This actor allows a user to associate information with a patient at the point of care.', 'PDC', 'Patient Demographics Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (37, '2008-04-17 12:09:39.21943', '0', false, 'A repository of patient information that can be searched on demographic or visit-related fields.', 'PDS', 'Patient Demographics Supplier');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (38, '2008-04-17 12:09:39.220407', '0', false, 'This actor has a use for information that can be found in the Personnel White Pages Directory.', 'PWPC', 'Personnel White Pages Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (39, '2008-04-17 12:09:39.22139', '0', false, 'This actor has authoritative location information.', 'DNS', 'DNS Server');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (40, '2008-04-17 12:09:39.222369', '0', false, 'This actor has authoritative Personnel White Pages information on the human workforce members of the enterprise.', 'PWPD', 'Personnel White Pages Directory');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (41, '2008-04-17 12:09:39.223228', '0', false, 'The Document Source Actor is the producer and publisher of documents. It is responsible for sending documents to a Document Repository Actor. It also supplies metadata to the Document Repository Actor for subsequent registration of the documents with the Document Registry Actor.', 'DOC_SOURCE', 'Document Source');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (42, '2008-04-17 12:09:39.224079', '0', false, 'The Document Consumer Actor queries a Document Registry Actor for documents meeting certain criteria, and retrieves selected documents from one or more Document Repository actors.', 'DOC_CONSUMER', 'Document Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (43, '2008-04-17 12:09:39.224927', '0', false, 'The Document Registry Actor maintains metadata about each registered document in a document entry. This includes a link to the Document in the Repository where it is stored. The Document Registry responds to queries from Document Consumer actors about documents meeting specific criteria. It also enforces some healthcare specific technical policies at the time of document registration.', 'DOC_REGISTRY', 'Document Registry');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (44, '2008-04-17 12:09:39.225791', '0', false, 'The Document Repository is responsible for both the persistent storage of these documents as well as for their registration with the appropriate Document Registry. It assigns a URI to documents for subsequent retrieval by a Document Consumer.', 'DOC_REPOSITORY', 'Document Repository');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (45, '2008-04-17 12:09:39.226691', '0', false, 'Each Patient Identification Domain requires this Actor to assign patient identities and to notify a Patient Identity Cross-reference Manager Actor of all events related to patient identification (creation, update, merge, etc.). For example, the Registration (ADT) Actor defined by the radiology Scheduled Workflow Profile would likely be a Patient Identity Source.', 'PAT_IDENTITY_SRC', 'Patient Identity Source');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (47, '2008-04-17 12:09:39.228497', '0', true, '', 'SNC', 'Secure Node Client');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (48, '2008-04-17 12:09:39.229334', '0', true, '', 'SNS', 'Secure Node Server');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (50, '2008-04-17 12:09:39.231043', '0', false, 'A system which owns (is responsible for the maintenance of) one or several code sets. This system may also be an Order Filler or an Enterprise Common Repository. Code sets can be sent on a routine basis (e.g. every week) or every time the code set changes. A code set may contain battery, test and observation codes.', 'CSM', 'Code Set Master');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (51, '2008-04-17 12:09:39.231924', '0', false, 'A system which receives code sets from Code Set Master(s) and updates its internal tables to reflect the code set as maintained by the Code Set Master. This system may  also be an Order Placer, an Order Result Tracker, an Automation Manager, or an Order Filler.', 'CSC', 'Code Set Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (52, '2008-04-17 12:09:39.232757', '0', false, 'A system which receives code sets from Code Set Master(s) and updates its internal tables to reflect the code set as maintained by the Code Set Master. This system may 130 also be an Order Placer, an Order Result Tracker, an Automation Manager, or an Order Filler.', 'POCRG', 'Point Of Care Result Generator');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (53, '2008-04-17 12:09:39.23364', '0', false, 'This actor used in LPOCT profile is an application managing a set of POCRG and centralizing their results. The POCDM is ready to react to any conversation from a POCRG. The POCDM receives point of care observations from POCRG actors. It controls these observations within their context, stores them and forwards them to the Order Filler.', 'POCDM', 'Point Of Care Data Manager');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (54, '2008-04-17 12:09:39.234491', '0', true, 'The Integrated Document Source/Repository is an XDS combination of Document Source and Document Repository that does not expose the interface between the Source and Repository. That is, this Source only publishes documents to its own Repository. It does register documents with a Document Registry', 'EMBED_REPOS', 'Integrated Document Source/Repository');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (55, '2008-04-17 12:09:39.235333', '0', false, 'This actor sends notifications of availability for documents in an XDS registry, and receives acknowledgements of these notifications.', 'NOTIFICATION_SENDER', 'Notification Sender');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (56, '2008-04-17 12:09:39.236195', '0', false, 'This actor receives notifications of availability for documents in an XDS registry, and may optionally send acknowledgments of them.', 'NOTIFICATION_RECEIVER', 'Notification Receiver');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (57, '2008-04-17 12:09:39.237298', '0', false, 'This actor has authoritative identity information on the human user that is operating the X-Service User actor.', 'X_ID_PROVIDER', 'X-Identity Provider');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (60, '2008-04-17 12:09:39.240907', '0', false, 'A system that uses patient encounter information provided by the Patient Encounter Source about a patient. It must be grouped with the Patient Demographics Consumer.', 'PEC', 'Patient Encounter Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (61, '2008-04-17 12:09:39.241849', '0', false, 'This actor is shown for completeness, but is really part of the SMTP Infrastructure of the Internet.', 'SMTP_AETHER', 'SMTP Aether');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (157, '2009-08-21 22:16:06.352', 'fourquetl', false, 'An authorized entity that is receiving a laboratory result message', 'HITSP_Lab_result_msg_receiver', 'Laboratory Result Message Receiver');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (173, '2009-08-24 14:55:11.839', 'furst', false, 'Sending actor in IDCO profile.', 'IDCR', 'Implantable Device - Cardiac - Reporter');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (141, '2009-07-14 14:49:43.421', 'admin', false, 'Protocol Executor', 'PROT_EXECUTOR', 'Protocol Executor');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (145, '2009-07-24 15:33:35.522', 'admin', false, 'Subcontractor', 'SUBCONTRACTOR', 'Subcontractor');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (62, '2008-04-17 12:09:39.242866', '0', false, 'The Imaging Document Source actor is the producer and publisher of imaging documents. It is responsible for providing imaging documents and meta-data to the Document Repository actor, which subsequently registers the imaging documents with the Document Registry actor. It also supports the retrieval services for DICOM SOP Instances referenced in a published imaging manifest document.', 'IMG_DOC_SOURCE', 'Imaging Document Source');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (63, '2008-04-17 12:09:39.243666', '0', false, 'The Imaging Document Source actor is the producer and publisher of imaging documents. It is responsible for providing imaging documents and meta-data to the Document Repository actor, which subsequently registers the imaging documents with the Document Registry actor. It also supports the retrieval services for DICOM SOP Instances referenced in a published imaging manifest document.', 'IMG_DOC_CONSUMER', 'Imaging Document Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (64, '2008-04-17 12:09:39.244501', '0', false, 'A system that allows a user to select one or more instances, series or studies for export, for a specific purpose, with a specific disposition, optionally with the inclusion of additional information.', 'EXPORT_SELECTOR', 'Export Selector');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (65, '2008-04-17 12:09:39.245429', '0', false, 'A system that can de-identify and pseudonymize the attributes, and optionally the pixel data, of a selected list of instances, before exporting them.', 'EXPORT_MANAGER', 'Export Manager');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (66, '2008-04-17 12:09:39.246245', '0', false, 'A system that can receive exported instances over the network, whose behavior is otherwise unspecified, unless grouped with other actors.', 'RECEIVER', 'Receiver');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (67, '2008-04-17 12:09:39.247148', '0', false, 'This actor allows a system in a Patient Identification Domain to find out the identification of a patient in a different Patient Identification Domain by using the services of a Patient Identity Cross-Reference Manager Actor. ', 'PAT_IDENTITY_CONSUMER', 'Patient Identifier Cross-reference Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (68, '2008-04-17 12:09:39.248047', '0', false, 'A system or component that manages the automation in the laboratory or a part of it. Automation involves the integration or interfacing of automated or robotic transport systems, analytical instruments, and pre- or post-analytical process equipment such as automated centrifuges and aliquoters, decappers, recappers, sorters, and specimen storage and retrieval systems. This actor receives work orders from the Order Filler. It manages the processing of the ordered tests on the appropriate devices, and sends technically validated results back to the Order Filler. This actor must be considered even if it manages a small part of the analytical process; e.g. if it manages one single analytical instrument. Multiple Automation Managers can be related to one Order Filler. The Automation Manager can match unexpected results produced by an analyzer with the appropriate incoming Work Order, or create a new Work Order to fit the unsolicited observations and send them to the OF.', 'AM', 'Automation Manager');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (69, '2008-04-17 12:09:39.248965', '0', false, 'An actor which is an automated device which fulfills clinical tests on biologic specimen. An Analyzer performs analyzing for a specimen according to AWOS, and return the result to the AM.', 'ANALYZER', 'Analyzer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (70, '2008-04-17 12:09:39.250008', '0', false, 'An actor which provides some pre- and post- processes to the specimen. This actor is categorized to two sub categories, one is pre-processor and the other one is post-processor. A Pre/Post-processor processes a specimen according to SWOS, and return the result to the AM.', 'PRE_POST_PROCESSOR', 'Pre/Post-processor');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (71, '2008-04-17 12:09:39.250837', '0', false, 'A system that imports evidence documents such as images, presentation states, Key Image Notes or Evidence Documents from hardcopy or digital media.', 'IMPORTER', 'Importer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (75, '2008-04-17 12:09:39.254261', '0', false, ' A system that receives HL7 messages, routes them to one or more configured actors, and handles transport level acknowledgements.  The HL7 Message Router may also provide modification of the messages in accordance with specific profiles.', 'HL7_MSG_ROUTER', 'HL7 Message Router');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (76, '2008-04-17 12:09:39.255104', '0', false, ' A system that receives a set of documents sent by another actor. Typically this document set will be made available to the intended recipient who will choose to either view it or integrate it into the Electronic Healthcare Record (EHR)', 'DOC_RECIPIENT', 'Document Recipient');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (77, '2008-04-17 12:09:39.255947', '0', false, 'The Device Observation Reporter (DOR) actor receives data from PCDs, including those based on proprietary formats, and maps the received data to transactions providing consistent syntax and semantics.', 'DEV_OBS_REPORTER', 'Device Observation Reporter');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (78, '2008-04-17 12:09:39.2569', '0', false, 'The Device Observation Filter (DOF) actor is responsible for providing PCD data filtering services based on publish/subscribe predicates negotiated with client applications implementing the Device Observation Consumer.', 'DEV_OBS_FILTER', 'Device Observation Filter');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (79, '2008-04-17 12:09:39.257835', '0', false, 'The actor responsible for receiving PCD data from the Device Observation Reporter, the Device Observation Filter, or both.', 'DEV_OBS_CONSUMER', 'Device Observation Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (80, '2008-04-17 12:09:39.258655', '0', false, 'The Content Creator creates content in a content integration profile', 'CONTENT_CREATOR', 'Content Creator');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (81, '2008-04-17 12:09:39.259485', '0', false, 'The Content Consumer consumes content in a content integration profile', 'CONTENT_CONSUMER', 'Content Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (82, '2008-04-17 12:09:39.26033', '0', false, 'The actor responsible for retrieving a form from a Form Manager, and for submitting form instance data to a Form Receiver.', 'FORM_FILLER', 'Form Filler');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (83, '2008-04-17 12:09:39.261297', '0', false, 'The actor responsible for receiving form instance data for archival purposes.', 'FORM_ARCHIVER', 'Form Archiver');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (84, '2008-04-17 12:09:39.262141', '0', false, 'The actor that supplies a form based upon a request that supplies a unique form identification.', 'FORM_MANAGER', 'Form Manager');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (85, '2008-04-17 12:09:39.263144', '0', false, 'The actor that receives form instance data.', 'FORM_RECEIVER', 'Form Receiver');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (86, '2008-04-17 12:09:39.263995', '0', false, 'The difference between the Secure Node and the Secure Application is the extent to which the underlying operating system and other environment are secured.  A Secure Node includes all aspects of user authentication, file system protections, and operating environment security.  The Secure Application is a product that does not include the operating environment.  The Secure Application provides security features only for the application features.  See section 9.7 for the relationships among a Secure Node, Secure Application, and other actors.', 'SA', 'Secure Application');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (91, '2008-04-17 12:09:39.267661', '0', false, 'A clinical data consumer makes use of clinical patient data.', 'CLIN_DATA_CONSUMER', 'Clinical Data Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (89, '2009-07-03 10:03:15.078', 'admin', false, '', 'INIT_GATEWAY', 'Initiating Gateway');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (87, '2009-07-03 09:59:51.791', 'admin', false, 'X-Service User', 'X-SERVICE-USER', 'X-Service User');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (90, '2009-07-03 10:05:36.066', 'admin', false, '', 'RESP_GATEWAY', 'Responding Gateway');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (99, '2008-04-17 12:09:39.274393', '0', false, 'Dummy actor', '--', 'None');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (100, '2008-04-17 12:09:39.275233', '0', false, 'An actor that provides the actor Label broker with label information', 'LIP', 'Label Information Provider');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (101, '2008-04-17 12:09:39.276108', '0', false, 'The Label Broker receives label information, and delivers these labels in appropriate operations, and may notify the status of this process. ', 'LB', 'Label Broker');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (142, '2009-07-14 14:52:42.475', 'admin', false, 'Protocol Definition Manager', 'PROT_DEF_MGR', 'Protocol Definition Manager');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (143, '2009-07-14 14:53:11.099', 'admin', false, 'Protocol State Manager', 'PROT_STATE_MGR', 'Protocol State Manager');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (144, '2009-07-24 15:33:18.194', 'admin', false, 'Requester', 'REQUESTER', 'Requester');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (102, '2008-04-17 12:09:39.276959', '0', false, 'A system responsible for adding, updating and maintaining encounter information about a patient. It supplies new and updated information to the Patient Encounter Consumer. It must be grouped with either the Patient Demographics Source or the Patient Demographics Consumer. ', 'PES', 'Patient Encounter Supplier');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (103, '2008-08-04 10:34:00', '0', false, 'A Clinical Data Sources maintains patient information about vital  signs, problem and allergies, results from diagnostic tests (e.g., Lab, Imaging, or other test results), medications, immunizations or historical or planned visits and procedures.', 'CLIN_DATA_SOURCE', 'Clinical Data Source');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (104, '2008-08-04 15:00:00', '0', false, 'Responsible for supplemental handling of irradiation events, generally on an individual basis, e.g. display, analysis, or further processing.', 'DOSE_INFO_CONSUMER', 'Dose Information Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (105, '2008-08-04 15:00:00', '0', false, 'Responsible for the aggregation, analysis, reporting and business logic related to irradiation events, which may include meeting facility obligations to de-identify and submit data to various dose registers.', 'DOSE_INFO_REPORTER', 'Dose Information Reporter');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (106, '2008-08-04 15:00:00', '0', false, 'Collates information about irradiation events from a number of facilities, generally to perform analysis.', 'DOSE_REGISTER', 'Dose Register');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (107, '2008-08-05 15:35:00', '0', false, 'Provides Resolved Value Sets ', 'VALUE_SET_REPOSITORY', 'Value Set Repository');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (108, '2008-08-05 15:35:00', '0', false, 'Retrieves Resolved Value Sets based on its OID and possibly its version if the latter is available.', 'VALUE_SET_CONSUMER', 'Value Set Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (111, '2008-10-25 12:00:00', '0', false, 'The guideline manager actor is responsible for managing the guidelines used to create care plans, and for communicating those guidelines to other systems.', 'GUIDELINE_MGR', 'Guideline Manager');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (112, '2008-10-25 12:00:00', '0', false, 'The care manager actor is responsible for supporting the management of the care of patients with respect to a specific health condition. It gathers information about the care provided and current health status of the patient. A Care Manager actor may be designed for management of a single condition, such as management of Diabetes, or may be a general purpose system supporting management of multiple conditions.', 'CARE_MGR', 'Care Manager');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (113, '2008-10-25 12:00:00', '0', false, 'The Alarm Reporter (AR) actor sources the alarm to Alarm Manager (AM).', 'ALRM_RPT', 'Alarm Reporter');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (114, '2008-10-25 12:00:00', '0', false, 'The Alarm Manager (AM) actor receives the alarm from the Alarm Reporter (AR), potentially analyzes the alarm, and dispatches the alarm to the Alarm Communicator (AC).', 'ALRM_MGR', 'Alarm Manager');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (115, '2008-10-25 12:00:00', '0', false, 'The Alarm Communicator  (AC) actor receives the alarm from the Alarm Manager (AM) and sends the alarm to the client application in the endpoint device.', 'ALRM_COMMUNICATOR', 'Alarm Communicator');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (116, '2008-10-25 12:00:00', '0', false, 'The Alarm Archiver (AA) actor sends alarm subscription requests to the AM actor and receives report alarm responses from the AM actor.', 'ALRM_ARCHIVER', 'Alarm Archiver');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (117, '2008-10-25 12:00:00', '0', false, 'The Infusion Order Programmer (IOP) actor sends the information comprising an order to the Infusion Order Consumer  (IOC).  The mechanism by which the IOP obtains the order information is outside the scope of this profile.', 'IOP', 'Infusion Order Programmer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (118, '2008-10-25 12:00:00', '0', false, 'The Infusion Order Consumer  (IOC) actor receives the order information from the IOP actor and in turn programs the pump.  The mechanism by which the IOC programs the pump with the received information is outside the scope of this profile.', 'IOC', 'Infusion Order Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (88, '2009-07-03 09:59:17.447', 'admin', false, 'X-Service Provider', 'X-SERVICE-PROVIDER', 'X-Service Provider');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (98, '2009-07-03 10:02:49.691', 'admin', false, '', 'HITSP-ACTOR', 'Generic HITSP Actor');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (110, '2009-07-03 10:03:38.847', 'admin', false, '', 'REFERRAL_DISPATCHER', 'Referral Dispatcher');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (109, '2009-07-03 10:04:02.438', 'admin', false, '', 'REFERRAL_REQUESTOR', 'Referral Requestor');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (156, '2009-08-21 22:17:13.411', 'fourquetl', false, 'The holder of a laboratory result who is communicating a laboratory result message to another actor', 'HITSP_Lab_result_msg_sender', 'HITSP Laboratory Result Message Sender');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (120, '2009-07-02 14:57:24.907', 'admin', false, '', 'PMS', 'Portable Media Sender');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (121, '2009-07-02 15:05:02.937', 'admin', false, '', 'DM_NOTIF_BROKER', 'Document Metadata Notification Broker');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (18, '2008-04-17 12:09:39.202551', '0', false, 'A system that creates additional evidence objects such as images, presentation states, Key Image Notes, and/or Evidence Documents and transmits them to an Image Archive. It also makes requests for storage commitment to the Image Manager for the data previously transmitted. It may also retrieve worklist entries for post-processing steps from the Post-Processing Manager and provide notification of completion of the step, allowing the enterprise to track the status of post-processing work.', 'EC', 'Evidence Creator');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (122, '2009-07-02 15:05:55.662', 'admin', false, '', 'DM_PUBLISHER', 'Document Metadata Publisher');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (123, '2009-07-02 15:07:08.214', 'admin', false, '', 'DM_SUBSCRIBER', 'Document Metadata Subscriber ');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (124, '2009-07-02 15:08:27.462', 'admin', false, '', 'DM_NOTIF_RECIPIENT', 'Document Metadata Notification Recipient');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (119, '2009-07-03 10:02:03.379', 'admin', false, 'Legacy Acquisition Modality Importer', 'LEGACY_MOD', 'Legacy Acquisition Modality Importer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (126, '2009-07-08 14:07:53.538', 'admin', false, 'A system that consumes CT and creates RT Structure Set. If the Contourer consumes multiple series CT or has an internal requirement for resampling, it also will generate a single series CT to which the RT Structure Set maps.', 'CONTOURER', 'Contourer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (127, '2009-07-08 14:12:02.889', 'admin', false, 'A system that consumes (single series) CT and RT Structure Set and creates a Geometric Plan', 'GEOMETRIC_PLANNER', 'Geometric Planner');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (128, '2009-07-08 14:12:40.896', 'admin', false, 'A system that consumes (single series) CT, an RT Structure Set, a Geometric Plan, and creates a Dosimetric Plan and an RT Dose.', 'DOSIMETRIC_PLANNER', 'Dosimetric Planner');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (129, '2009-07-08 14:13:33.507', 'admin', false, 'A system that consumes a Dosimetric Plan, CT, Structure Set and an RT Dose and displays the dose', 'DOSE_DISPLAYER', 'Dose Displayer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (130, '2009-07-08 14:17:23.236', 'admin', false, 'A system that stores the RT SOP Classes in addition to the CT images and is capable of transmitting them.', 'ARCHIVE', 'Archive (including RT)');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (131, '2009-07-08 14:38:02.216', 'admin', false, 'A system that consumes multi-modality images and generates 1 or more Spatial Registration objects.', 'REGISTRATOR', 'Registrator');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (132, '2009-07-08 14:39:14.751', 'admin', false, 'A system that consumes multi-modality images, RT Structure Set objects, and Spatial Registration objects and allows the user to display the registered information', 'REG_DISPLAY', 'Registered Display');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (133, '2009-07-08 14:40:04.34', 'admin', false, 'A system that consumes multi-modality images, RT Structure Set objects, RT Dose objects and Spatial Registration objects and allows the user to display the registered information.', 'REG_DOSE_DISPLAY', 'Registered Dose Display');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (134, '2009-07-08 14:40:31.728', 'admin', false, 'A system that consumes multi-modality images, RT Structure Set objects, and Spatial Registration objects and allows the user to contour images in a registered display.', 'REG_CONTOURER', 'Registered Contourer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (135, '2009-07-08 14:48:41.188', 'admin', false, '', 'TMS', 'Treatment Management System');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (136, '2009-07-08 14:49:26.411', 'admin', false, 'A system that delivers therapeutic radiation to a correctly positioned patient.', 'TDD', 'Treatment Delivery Device');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (155, '2009-08-10 16:23:35.665', 'admin', false, 'description', 'NEW_ACTOR', 'New Actor 1');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (147, '2009-08-02 12:51:05.371', 'admin', false, 'Alert Message Receiver', 'ALERT_MSG_RECEIVER', 'Alert Message Receiver');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (169, '2009-08-22 00:21:28.486', 'fourquetl', false, 'The Medication Order Filler responds to the requests for medication orders/prescriptions. This includes the ability to respond to: new orders, refill orders, change orders and cancel orders. These responses are sent to the Medication Order Prescriber.', 'HITSP_Med_Ord_Flr', 'HITSP Medication Order Filler');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (149, '2009-08-02 22:35:23.614', 'admin', false, 'Alert Message Transmitter', 'ALERT_MSG_TRANSMITTER', 'Alert Message Transmitter');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (138, '2009-08-14 13:58:45.666', 'smoore', false, 'Decision Support Service', 'DECISION_SUPPORT', 'Decision Support Service');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (146, '2009-08-19 22:28:02.116', 'fourquetl', false, 'KnA system that formulates and sends a contextual request for ancillary information about a medical concept. Takes the parameters and sends to the resource available', 'KNOWLEDGE_REQUESTOR', 'Knowledge Requestor');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (148, '2009-08-19 22:29:17.204', 'fourquetl', false, 'The system that holds the information requested and responds to the request from the Knowledge Requestor', 'KNOWLEDGE_RESOURCE', 'Knowledge Resource');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (174, '2009-08-24 14:54:33.856', 'furst', false, 'Receiving actor in IDCO profile.', 'IDCC', 'Implantable Device - Cardiac - Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (158, '2009-08-21 22:32:54.59', 'fourquetl', false, 'The Web Application the healthcare professional uses to view a laboratory report Web', 'HITSP_Web_Application', 'Web Application');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (159, '2009-08-21 22:38:06.56', 'fourquetl', false, 'Module or service that can be invoked by Patient Identifier Cross-Reference (PIX) Manager (see next section) to return pseudo-identifier upon request', 'HITSP_Pseudoymisation_SVC', 'HITSP Pseudonymization Services');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (160, '2009-08-21 22:59:10.259', 'fourquetl', false, 'The system that initiates an inquiry to the Eligibility Information Source about an individual’s insurance eligibility, coverage and benefits', 'HITSP_Eligibility_info_receiver', 'Eligibility Information Receiver');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (161, '2009-08-21 23:00:13.989', 'fourquetl', false, 'The system which holds and maintains the information regarding the individual’s insurance eligibility, coverage and benefits, and responds to the queries initiated by the Eligibility Information Receiver', 'HITSP_Eligibility_info_Source', 'Eligibility Information Source');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (162, '2009-08-21 23:05:21.379', 'fourquetl', false, 'The Medication Status Receiver receives a dispensing status (RXFILL message) from a Medication Status Dispenser about a previously performed medication order / prescription', 'HITSP_Med_Status_Receiver', 'HITSP Medication Status Receiver');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (163, '2009-08-21 23:06:20.383', 'fourquetl', false, 'The Medication Status Dispenser provides a dispensing status (RXFILL message) to a Medication Status Receiver about a preciously performed medication order / prescription', 'HITSP_Med_Status_Dispenser', 'HITSP Medication Status Dispenser');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (164, '2009-08-21 23:27:17.382', 'fourquetl', false, 'The system that initiates a request to the Information Source for Health Plan Authorization about an individuals health insurance requirements to obtain an authorization approval for purposes of benefit coverage determination in order to refer a patient for healthcare services', 'HITSP_Info_Rcvr_Health_Plan_Auth', 'HITSP Information Receiver for Health Plan Authorization');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (165, '2009-08-21 23:28:49.527', 'fourquetl', false, 'The system which holds and maintains the information regarding the individual’s health insurance requirements related to an authorization for benefit coverage', 'HITSP_Info_Src_Health_Plan_Auth', 'HITSP Information Source for Health Plan Authorization');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (166, '2009-08-21 23:40:02.292', 'fourquetl', false, 'A provider sending a request to a health plan has a client role', 'HITSP_Admin_Transport_Client', 'HITSP Administrative Transport Client');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (167, '2009-08-21 23:41:01.854', 'fourquetl', false, 'A health plan responding to a request from a provider has a server role', 'HITSP_Admin_Transport_Svr', 'HITSP Administrative Transport Server');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (170, '2009-08-22 00:29:57.131', 'fourquetl', false, 'The entity that is asking about an individual’s formulary and benefits information. It initiates queries to the Medication Formulary and Benefits Source', 'HITSP_Med_Form_Bene_Rcvr', 'HITSP Medication Formulary and Benefits Retriever');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (171, '2009-08-22 00:31:49.02', 'fourquetl', false, 'The entity that maintains individual’s formulary and benefits information. It responds to queries from the Medication Formulary and Benefits Retriever', 'HITSP_Med_Form_Bene_Src', 'HITSP Medication Formulary and Benefits Source');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (172, '2009-08-22 01:53:28.733', 'fourquetl', false, 'The entity represents any individual entity (such as an EHR/PHR system) that needs to make a service request of a Service Provider. The Entity may also be known as a principal and/or entity, which represents an application, a machine, or any other type of entity that may act as a requester in a transaction. A principal is typically represented in a transaction with a digital identity and the principal may have multiple valid digital identities to use with different transactions. Any Service User may also be a Service Provider', 'HITSP_Service_User', 'HITSP Service User');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (168, '2009-09-14 14:53:59.46', 'smoore', false, 'The Medication Order Prescriber initiates requests for medication orders/prescriptions. This includes the ability to: create new orders, refill orders, change orders and cancel orders. These requests are sent to the Medication Order Filler.', 'HITSP_Med_Order_Pscr', 'HITSP Medication Order Prescriber');
SET escape_string_warning = off;
-- 01_tf_domain_data.sql
SET escape_string_warning = off;
INSERT INTO tf_domain (id, last_changed, last_modifier_id, description, keyword, name) VALUES (1, NULL, NULL, 'IHE Radiology addresses information sharing, workflow and patient care in radiology, including mammography and nuclear medicine.', 'RAD', 'Radiology');
INSERT INTO tf_domain (id, last_changed, last_modifier_id, description, keyword, name) VALUES (2, NULL, NULL, 'The IT Infrastructure Domain supplies infrastructure for sharing healthcare information. An infrastructure interoperability component represents a common IT function that is used as a building block for a variety of use cases... a necessary ingredient, but rarely visible to the end user!! These components may be embedded in an application, but are often deployed as a shared resource within a RHIO or Health Information Exchange.', 'ITI', 'IT-Infrastructure');
INSERT INTO tf_domain (id, last_changed, last_modifier_id, description, keyword, name) VALUES (4, NULL, NULL, 'IHE Cardiology addresses information sharing, workflow and patient care in cardiology, including electrophysiology and nuclear medicine.', 'CARD', 'Cardiology');
INSERT INTO tf_domain (id, last_changed, last_modifier_id, description, keyword, name) VALUES (5, NULL, NULL, 'IHE Patient Care Coordination (PCC) domain was established in July 2005 to deal with integration issues that cross providers, patient problems or time. It deals with general clinical care aspects such as document exchange, order processing, and coordination with other specialty domains. PCC also addresses workflows that are common to multiple specialty areas and the integration needs of specialty areas that do not have a separate domain within IHE.', 'PCC', 'Patient Care Coordination');
INSERT INTO tf_domain (id, last_changed, last_modifier_id, description, keyword, name) VALUES (6, NULL, NULL, 'IHE Radiation Oncology addresses information sharing, workflow, and patient care in radiation oncology.', 'RO', 'Radiation Oncology');
INSERT INTO tf_domain (id, last_changed, last_modifier_id, description, keyword, name) VALUES (7, NULL, NULL, 'The Patient Care Device Domain is concerned with use cases in which at least one actor is a regulated patient-centric point-of-care medical device that communicates with at least one other actor such as a medical device or information system.', 'PCD', 'Patient Care Devices');
INSERT INTO tf_domain (id, last_changed, last_modifier_id, description, keyword, name) VALUES (8, NULL, NULL, 'IHE Eye Care is sponsored by the American Academy of Ophthalmology (AAO) and manages the Eye Care Profiles and the Eye Care Technical Frameworks.', 'EYE', 'Eye Care');
INSERT INTO tf_domain (id, last_changed, last_modifier_id, description, keyword, name) VALUES (9, NULL, NULL, 'IHE Quality, Research and Public Health Domain (QRPH) addresses the infrastructure necessary to share information relevant to quality improvement in electronic patient care and health care records.', 'QRPH', 'Quality Research Public Health');
INSERT INTO tf_domain (id, last_changed, last_modifier_id, description, keyword, name) VALUES (10, NULL, NULL, 'IHE Anatomic Pathology addresses information sharing, workflow and patient care in Pathology, including anatomical pathology.', 'PATH', 'Pathology');
INSERT INTO tf_domain (id, last_changed, last_modifier_id, description, keyword, name) VALUES (3, '2009-07-24 16:03:39.684', 'admin', 'IHE Laboratory addresses information sharing and workflow related to in vitro diagnostic testing in clinical laboratories as well as on the point of care.', 'LAB', 'Laboratory');
INSERT INTO tf_domain (id, last_changed, last_modifier_id, description, keyword, name) VALUES (11, '2010-01-20 23:25:36.916', 'epoiseau', 'Domain that holds all the HISTP defined profiles', 'HITSP', 'HITSP');
SET escape_string_warning = off;
-- 01_tf_integration_profile_option_data.sql
SET escape_string_warning = off;
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (1, '2008-04-17 12:10:01.085139', '0', 'None', 'NONE', 'None', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (3, '2008-04-17 12:10:01.087951', '0', 'Assisted Acquisition Protocol Setting', 'ASST_ACQ_PROT_SET', 'Assisted Acquisition Protocol Setting', 'Rad TF-2:4.6');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (4, '2008-04-17 12:10:01.089286', '0', 'PPS Exception Management', 'PPS_EXC_MGT', 'PPS Exception Management', 'Rad TF-2:4.7');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (5, '2008-04-17 12:10:01.090053', '0', 'Performed Work Status Update Recieve', 'WRK_STAT_UPD_RCV', 'Performed Work Status Update Recieve', 'Rad TF-2:4.20-21');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (6, '2008-04-17 12:10:01.090763', '0', 'Patient Based Worklist Query', 'PAT_QUERY', 'Patient Based Worklist Query', 'Rad TF-2:4.5');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (8, '2008-04-17 12:10:01.09234', '0', 'Modality Group Case', 'MOD_GROUP_CASE', 'Modality Group Case', 'Rad TF-2:4.6');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (9, '2008-04-17 12:10:01.093083', '0', 'Billing and Material Management', 'BILL_AND_MAT_MGT', 'Billing and Material Management', 'Rad TF-4:4.7');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (10, '2008-04-17 12:10:01.093872', '0', 'Creator Performed Procedure Step', 'CRT_PPS', 'Creator Performed Procedure Step', 'Rad TF-2:4.20-21');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (11, '2008-04-17 12:10:01.094741', '0', 'Enhanced SR', 'ENHANCED_SR', 'Enhanced SR', 'Rad TF-2:4.27.4');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (12, '2008-04-17 12:10:01.095466', '0', 'Multiple Sources', 'MULTIPLE_SRCS', 'Multiple Sources', 'Rad TF-1:7.3.1');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (13, '2008-04-17 12:10:01.096217', '0', 'Persistent Document', 'PERSISTENT_DOCUMENT', 'Persistent Document', 'ITI TF-2:3.12');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (14, '2008-04-17 12:10:01.096977', '0', 'Summary of All Reports', 'SUMMARY_REPORTS', 'Summary of All Reports', 'ITI TF-2:3.11');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (15, '2008-04-17 12:10:01.097743', '0', 'Summary of Laboratory Reports', 'SUMMARY_LAB_REPORTS', 'Summary of Laboratory Reports', 'ITI TF-2:3.11');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (17, '2008-04-17 12:10:01.099211', '0', 'Summary of Cardiology Reports', 'SUMMARY_CARDIO_REPORTS', 'Summary of Cardiology Reports', 'ITI TF-2:3.11');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (18, '2008-04-17 12:10:01.099937', '0', 'Summary of Surgery Reports', 'SUMMARY_SURGERY_REPORTS', 'Summary of Surgery Reports', 'ITI TF-2:3.11');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (19, '2008-04-17 12:10:01.100622', '0', 'Summary of Intensive Care Reports', 'SUMMARY_IC_REPORTS', 'Summary of Intensive Care Reports', 'ITI TF-2:3.11');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (20, '2008-04-17 12:10:01.101332', '0', 'Summary of Emergency Reports', 'SUMMARY_EMERGENCY_REPORTS', 'Summary of Emergency Reports', 'ITI TF-2:3.11');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (21, '2008-04-17 12:10:01.102032', '0', 'Summary of Discharge Reports', 'SUMMARY_DISCHARGE_REPORTS', 'Summary of Discharge Reports', 'ITI TF-2:3.11');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (22, '2008-04-17 12:10:01.102743', '0', 'Summary of Prescriptions', 'SUMMARY_PRESCRIPTION', 'Summary of Prescriptions', 'ITI TF-2:3.11');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (23, '2008-04-17 12:10:01.103459', '0', 'List of Allergies and Adverse Reactions', 'LIST_ALLERGIES', 'List of Allergies and Adverse Reactions', 'ITI TF-2:3.11');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (24, '2008-04-17 12:10:01.104163', '0', 'List of Medications', 'LIST_MEDICATIONS', 'List of Medications', 'ITI-TF-2:3.11');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (25, '2008-04-17 12:10:01.104851', '0', 'Departmental Appointment Notification', 'DEPARTMENTAL_APPOINTMENT_NOTIFICATION', 'Departmental Appointment Notification', 'Rad TF-3:4.48');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (26, '2008-04-17 12:10:01.105551', '0', 'Instance Availability Notification', 'INST_AVAILABILITY_NOTIFICATION', 'Instance Availability Notification', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (27, '2008-04-17 12:10:01.106213', '0', 'Result Screen Export Option', 'RESULT_SCREEN_EXPORT', 'Result Screen Export Option', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (28, '2008-04-17 12:10:01.106943', '0', 'Review Option', 'REVIEW', 'Review Option', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (29, '2008-04-17 12:10:01.108312', '0', 'Web Content', 'WEB_CONTENT', 'Web Content', 'Rad TF-1:15.4.2');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (30, '2008-04-17 12:10:01.109089', '0', 'Patient Demographics and Visit Query', 'PAT_DEMO_VISIT_QUERY', 'Patient Demographics and Visit Query', 'ITI TF-2:3.22');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (32, '2008-04-17 12:10:01.110593', '0', 'SSL-Simple Authentication', 'SSL_SIMPLE_AUTH', 'SSL-Simple Authentication', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (33, '2008-04-17 12:10:01.111355', '0', 'ATNA Encryption', 'ATNA_ENCRYPTION', 'ATNA Encryption', 'ITI TF-1:9.5');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (34, '2008-04-17 12:10:01.112092', '0', 'Echocardiography', 'ECHO', 'Echocardiography', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (35, '2008-04-17 12:10:01.112829', '0', 'Intermittently Connected Modality', 'INTERMITTENT_MOD', 'Intermittently Connected Modality', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (36, '2008-04-17 12:10:01.113593', '0', 'Stress Echo', 'STRESS_ECHO', 'Stress Echo', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (37, '2008-04-17 12:10:01.114367', '0', 'Multi-modality Procedure Update', 'MULTI_MOD', 'Multi-modality Procedure Update', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (38, '2008-04-17 12:10:01.115108', '0', 'Cardiac Cath', 'CARDIAC_CATH', 'Cardiac Cath', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (39, '2008-04-17 12:10:01.115828', '0', 'Authentication for User Context', 'AUTH_FOR_USER_CONTEXT', 'Authentication for User Context', 'ITI TF-2:3.6');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (40, '2008-04-17 12:10:01.116597', '0', 'Off-Line transaction mode.', 'OFFLINE_TRANSACTION', 'Off-Line transaction mode.', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (41, '2008-04-17 12:10:01.117347', '0', 'Query Registry Transaction.', 'QUERY_REGISTRY', 'Query Registry Transaction.', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (43, '2008-04-17 12:10:01.118655', '0', 'SNTP.', 'SNTP', 'SNTP.', 'ITI TF-2:3.21.4-1');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (44, '2008-04-17 12:10:01.119253', '0', 'Secure NTP.', 'SECURED_SNTP', 'Secure NTP.', 'ITI TF-2:3.31.4-1');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (45, '2008-04-17 12:10:01.11992', '0', 'Wait for an incoming Work Order from OF to match the results', 'WAIT_FOR_INCOMING_WORK_ORDER', 'Wait for an incoming Work Order from OF to match the results', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (46, '2008-04-17 12:10:01.120518', '0', 'Active submission of unsolicited results to the OF', 'ACTIVE_SUBMISSION_OF_UNSOLICITED_RESULTS', 'Active submission of unsolicited results to the OF', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (47, '2008-04-17 12:10:01.121074', '0', 'Patient identity checking', 'LPOCT_PID_CHECKING', 'Patient identity checking', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (48, '2008-04-17 12:10:01.133223', '0', 'Availability of PPS-Referenced Instances', 'AVAILABILITY_OF_PPS_REFERENCED_INSTANCES', 'Availability of PPS-Referenced Instances', 'Rad TF-3:4.49');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (49, '2008-04-17 12:10:01.134098', '0', 'Acknowledgement Request with SMTP Option', 'ACK_REQUEST_WITH_SMTP', 'Acknowledgement Request with SMTP Option', 'ITI TF-2:3.28');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (50, '2008-04-17 12:10:01.134795', '0', 'Acknowledgement Request with POP3 Option', 'ACK_REQUEST_WITH_POP3', 'Acknowledgement Request with POP3 Option', 'ITI TF-2:3.28');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (135, '2008-04-17 12:10:01.195623', '0', 'XDS Affinity Domain Option', 'XDS_AFFINITY_DOMAIN', 'XDS Affinity Domain Option', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (52, '2008-04-17 12:10:01.136206', '0', 'Receive Notification with SMTP Option', 'RECEIVE_NOTIFICATION_WITH_SMTP', 'Receive Notification with SMTP Option', 'ITI TF-2:3.28');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (53, '2008-04-17 12:10:01.137133', '0', 'Receive Notification with POP3 Option', 'RECEIVE_NOTIFICATION_WITH_POP3', 'Receive Notification with POP3 Option', 'ITI TF-2:3.28');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (54, '2008-04-17 12:10:01.138196', '0', 'Receive Notification with IMAP Option', 'RECEIVE_NOTIFICATION_WITH_IMAP', 'Receive Notification with IMAP Option', 'ITI TF-2:3.28');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (55, '2008-04-17 12:10:01.138948', '0', 'Send Acknowledgement', 'SEND_ACK', 'Send Acknowledgement', 'ITI TF-2:3.28');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (56, '2008-04-17 12:10:01.139656', '0', 'Merge', 'MERGE', 'Merge', 'ITI TF-2:3.30');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (57, '2008-04-17 12:10:01.140329', '0', 'Link / Unlink', 'LINK_UNLINK', 'Link / Unlink', 'ITI TF-2:3.30');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (58, '2008-04-17 12:10:01.141049', '0', 'Inpatient / Outpatient Encounter Management', 'IN_OUT_PATIENT_ENCOUNTER_MGMT', 'Inpatient / Outpatient Encounter Management', 'ITI TF-2:3.31');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (59, '2008-04-17 12:10:01.141752', '0', 'Pending Event Management', 'PENDING_EVT_MGMT', 'Pending Event Management', 'ITI TF-2:3.31');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (60, '2008-04-17 12:10:01.142414', '0', 'Advance Encounter Management', 'ADV_ENCOUNTER_MGMT', 'Advance Encounter Management', 'ITI TF-2:3.31');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (61, '2008-04-17 12:10:01.143128', '0', 'Temporary Patient Transfer Tracking', 'TEMP_PATIENT_TRANSFER_TRACKING', 'Temporary Patient Transfer Tracking', 'ITI TF-2:3.31');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (62, '2008-04-17 12:10:01.143932', '0', 'Historic Movement', 'HISTORIC_MVT', 'Historic Movement', 'ITI TF-2:3.31');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (63, '2008-04-17 12:10:01.144974', '0', 'DICOM Storage', 'DICOM_STORAGE', 'DICOM Storage', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (64, '2008-04-17 12:10:01.145673', '0', 'Encapsulated Reports', 'ENCAPSULATED_REPORTS', 'Encapsulated Reports', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (2, '2009-07-02 15:56:52.187', 'admin', 'Image Availability Query', 'IMAGE_AVAIL', 'Image Availability Query', 'Rad TF-2:4.11');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (16, '2009-07-03 10:10:46.197', 'admin', 'Summary of Radiology Reports', 'SUMMARY_RAD_REPORTS', 'Summary of Radiology Reports', 'ITI TF-2:3.11');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (65, '2008-04-17 12:10:01.146423', '0', 'By-Reference Reports', 'BY_REF_REPORTS', 'By-Reference Reports', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (66, '2008-04-17 12:10:01.147115', '0', 'Set of DICOM Instances', 'SET_OF_DICOM_INSTANCES', 'Set of DICOM Instances', 'Rad TF-1:18.2.1');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (67, '2008-04-17 12:10:01.147807', '0', 'PDF Report', 'PDF_REPORT', 'PDF Report', 'Rad TF-1:18.2.2');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (68, '2008-04-17 12:10:01.148452', '0', 'Text Report', 'TEXT_REPORT', 'Text Report', 'Rad TF-1:18.2.3');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (69, '2008-04-17 12:10:01.149073', '0', 'Multipart Text/PDF Report', 'MULTIPART_TEXT_PDF_REPORT', 'Multipart Text/PDF Report', 'Rad TF-1:18.2.4');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (70, '2008-04-17 12:10:01.149757', '0', 'Additional Teaching File Information', 'ADDITIONAL_TEACHING_FILE_INFO', 'Additional Teaching File Information', 'Rad TF-1:7.2.3, Rad TF-3:4.52-53');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (71, '2008-04-17 12:10:01.150379', '0', 'Delay for Reason', 'DELAY_FOR_REASON', 'Delay for Reason', 'Rad TF-1:7.2.4, Rad TF-3:4.51.4.1.5');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (72, '2008-04-17 12:10:01.150991', '0', 'De-identify Pixel Data ', 'DE-IDENTIFY_PIXEL_DATA', 'De-identify Pixel Data ', 'Rad TF-1:7.2.1, Rad TF-3:4.51.4.1.4.4');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (73, '2008-04-17 12:10:01.151597', '0', 'Remap Identifiers', 'REMAP_IDENTIFIERS', 'Remap Identifiers', 'Rad TF-1:7.2.2, Rad TF-3:4.51.4.1.3');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (74, '2008-04-17 12:10:01.152213', '0', 'PIX Update Notification', 'PIX_UPDATE_NOTIFICATION', 'PIX Update Notification', 'ITI TF-2:3.10');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (75, '2008-04-17 12:10:01.153023', '0', 'Discharge Summary Option', 'PCC_DISCHARGE_SUMMARY_OPTION', 'Discharge Summary Option', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (76, '2008-04-17 12:10:01.154078', '0', 'Referral Option', 'PCC_REFERRAL_OPTION', 'Referral Option', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (77, '2008-04-17 12:10:01.154888', '0', 'View Option', 'PCC_VIEW_OPTION', 'View Option', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (78, '2008-04-17 12:10:01.155708', '0', 'Document Import Option', 'PCC_DOC_IMPORT_OPTION', 'Document Import Option', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (79, '2008-04-17 12:10:01.15648', '0', 'Section Import Option', 'PCC_SECTION_IMPORT_OPTION', 'Section Import Option', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (80, '2008-04-17 12:10:01.157203', '0', 'Discrete Data Import Option', 'PCC_DISCRETE_DATA_IMPORT_OPTION', 'Discrete Data Import Option', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (81, '2008-04-17 12:10:01.15793', '0', 'Multiple Document Submission', 'MULTIPLE_DOCUMENT_SUBMISSION', 'Multiple Document Submission', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (82, '2008-04-17 12:10:01.15866', '0', 'Document Life Cycle Management', 'DOC_LIFE_CYCLE_MGT', 'Document Life Cycle Management', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (83, '2008-04-17 12:10:01.159547', '0', 'Folder Management', 'FOLDER_MGT', 'Folder Management', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (84, '2008-04-17 12:10:01.160314', '0', 'Cath Evidence', 'CATH_EVIDENCE', 'Cath Evidence', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (85, '2008-04-17 12:10:01.161019', '0', 'Echo Evidence', 'ECHO_EVIDENCE', 'Echo Evidence', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (86, '2008-04-17 12:10:01.161712', '0', 'Scheduled Import - Uses MWL', 'SCHED_IMPORT', 'Scheduled Import - Uses MWL', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (87, '2008-04-17 12:10:01.162429', '0', 'Unscheduled Import - No MWL', 'UNSCHED_IMPORT', 'Unscheduled Import - No MWL', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (90, '2008-04-17 12:10:01.164487', '0', 'Stress ECG', 'STRESS_ECG', 'Stress ECG', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (91, '2008-04-17 12:10:01.165175', '0', 'Cardiac NM Option', 'CARDIAC_NM', 'Cardiac NM Option', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (92, '2008-04-17 12:10:01.165838', '0', 'General NM Option', 'GENERAL_NM', 'General NM Option', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (93, '2008-04-17 12:10:01.166542', '0', 'MPR Option', 'NM_MPR', 'MPR Option', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (94, '2008-04-17 12:10:01.167326', '0', 'USB Document Storage', 'USB', 'USB Document Storage', 'ITI TF1 16.2.3');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (95, '2008-04-17 12:10:01.168008', '0', 'CDR Document Storage', 'CD_R', 'CDR Document Storage', 'ITI TF1 16.2.4');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (96, '2008-04-17 12:10:01.168681', '0', 'ZIP file sent over email', 'ZIP_OVER_EMAIL', 'ZIP file sent over email', 'ITI TF1 16.2.5');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (98, '2008-04-17 12:10:01.170106', '0', 'Privacy Option', 'PRIVACY_OPTION', 'Privacy Option', 'ITI TF-2 3.15.4.1.1');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (99, '2008-04-17 12:10:01.170792', '0', 'Initialize PHR', 'INITIALIZE_PHR', 'Initialize PHR', 'PCC TF-x 4.5.3');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (100, '2008-04-17 12:10:01.171455', '0', 'View Extract', 'VIEW_EXTRACT', 'View Extract', 'PCC TF-x 4.5.2.1');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (101, '2008-04-17 12:10:01.172163', '0', 'Extract Document Import', 'EXTRACT_DOC_IMPORT', 'Extract Document Import', 'PCC TF-x 4.5.2.2');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (102, '2008-04-17 12:10:01.172881', '0', 'Extract Section Import', 'EXTRACT_SECTION_IMPORT', 'Extract Section Import', 'PCC TF-x 4.5.2.3');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (103, '2008-04-17 12:10:01.173596', '0', 'Extract Discrete Data Import', 'EXTRACT_DISCRETE_IMPORT', 'Extract Discrete Data Import', 'PCC TF-x 4.5.2.4');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (104, '2008-04-17 12:10:01.174297', '0', 'Create Update', 'CREATE_UPDATE', 'Create Update', 'PCC TF-x 4.5.2.5');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (106, '2008-04-17 12:10:01.175678', '0', 'Radiology Audit Trail Option', 'RAD_AUDIT_TRAIL_OPTION', 'Radiology Audit Trail Option', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (107, '2008-04-17 12:10:01.176386', '0', 'HL7 V3', 'HL7V3', 'HL7 V3', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (108, '2008-04-17 12:10:01.17707', '0', 'Eye Care Image Option', 'EYE_CARE_IMAGE_OPTION', 'Eye Care Image Option', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (109, '2008-04-17 12:10:01.177919', '0', 'Encapsulated PDF Option for Evidence Documents', 'ENCAPSULATED_PDF_FOR_EV_DOCS', 'Encapsulated PDF Option for Evidence Documents', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (110, '2008-04-17 12:10:01.178684', '0', 'Eye Care Measurement Option', 'EYE_CARE_MEASUREMENT_OPTION', 'Eye Care Measurement Option', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (111, '2008-04-17 12:10:01.179404', '0', 'Archive Form Option', 'ARCHIVE_FORM', 'Archive Form Option', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (112, '2008-04-17 12:10:01.180137', '0', 'Data Clarifications Option', 'DATA_CLARIFICATIONS', 'Data Clarifications Option', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (114, '2008-04-17 12:10:01.181448', '0', 'PIXV3 Update Notification Transaction', 'PIXV3_UPDATE_NOTIFICATION', 'PIXV3 Update Notification Transaction', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (115, '2008-04-17 12:10:01.18207', '0', 'Patient Identity Feed (HL7 V2)', 'PAT_IDENTITY_FEED', 'Patient Identity Feed (HL7 V2)', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (116, '2008-04-17 12:10:01.182674', '0', 'Patient Identity Feed (HL7 V3)', 'PAT_IDENTITY_FEED_HL7V3', 'Patient Identity Feed (HL7 V3)', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (117, '2008-04-17 12:10:01.183274', '0', 'Triage Note / ED Nursing Note / ED Physician Note', 'EDES_TRIAGE_NOTE', 'Triage Note / ED Nursing Note / ED Physician Note', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (118, '2008-04-17 12:10:01.183867', '0', 'Composite Triage Note / ED Nursing Note / ED Physician Note', 'EDES_COMPOSITE_TRIAGE_NOTE', 'Composite Triage Note / ED Nursing Note / ED Physician Note', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (119, '2008-04-17 12:10:01.184452', '0', 'Braden Scale', 'BRADEN_SCALE', 'Braden Scale', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (120, '2008-04-17 12:10:01.185024', '0', 'Geriatric Depression Score', 'GERIATRIC_DEPRESSION_SCORE', 'Geriatric Depression Score', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (121, '2008-04-17 12:10:01.185627', '0', 'Minimum Data Set', 'MINIMUM_DATA_SET', 'Minimum Data Set', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (122, '2008-04-17 12:10:01.186232', '0', 'FSA XDS-MS', 'FSA_XDSMS', 'FSA XDS-MS', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (123, '2008-04-17 12:10:01.186862', '0', 'FSA XPHR', 'FSA_XPHR', 'FSA XPHR', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (124, '2008-04-17 12:10:01.18757', '0', 'FSA EDR', 'FSA_EDR', 'FSA EDR', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (125, '2008-04-17 12:10:01.188426', '0', 'QED Vital Signs', 'QED_VITAL_SIGNS', 'QED Vital Signs', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (126, '2008-04-17 12:10:01.189054', '0', 'QED Problems and Allergies', 'QED_PROBLEMS_ALLERGIES', 'QED Problems and Allergies', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (128, '2008-04-17 12:10:01.190684', '0', 'QED Medications', 'QED_MEDICATIONS', 'QED Medications', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (129, '2008-04-17 12:10:01.191389', '0', 'QED Immunizations', 'QED_IMMUNIZATIONS', 'QED Immunizations', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (130, '2008-04-17 12:10:01.19212', '0', 'QED Professional Services', 'QED_PROFESSIONAL_SERVICES', 'QED Professional Services', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (131, '2008-04-17 12:10:01.192805', '0', 'Basic Patient Privacy Enforcement', 'BPPC_ENFORCEMENT', 'Basic Patient Privacy Enforcement', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (132, '2008-04-17 12:10:01.193514', '0', 'Basic Patient Privacy Proof', 'BPPC_PROOF', 'Basic Patient Privacy Proof', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (133, '2008-04-17 12:10:01.194179', '0', 'Basic Patient Privacy Acknowledgment', 'BPPC_ACK', 'Basic Patient Privacy Acknowledgment', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (127, '2009-08-22 15:32:25.959', 'smoore', 'QED Diagnostic Results', 'QED_DIAGNOSTIC_RESULTS', 'QED Diagnostic Results', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (88, '2009-08-25 14:20:12.833', 'admin', 'Partial View: indicates if the image is part of a mosaic for covering the entire breast', 'PARTIAL_VIEW', 'Partial View', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (89, '2009-08-25 14:21:01.266', 'admin', 'PIX-based Reconciliation', 'PIX_BASED_RECON', 'PIX-based Reconciliation', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (134, '2008-04-17 12:10:01.194936', '0', 'Basic Patient Privacy Acknowledgment with Scanned Document', 'BPPC_ACK_SCANNED_DOC', 'Basic Patient Privacy Acknowledgment with Scanned Document', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (136, '2008-04-17 12:10:01.196328', '0', 'Stress Test Evidence', 'STRESS_TEST_EVIDENCE', 'Stress Test Evidence', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (137, '2008-04-17 12:10:01.197088', '0', 'CTA/MRA Evidence', 'CTA-MRA_EVIDENCE', 'CTA/MRA Evidence', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (138, '2008-04-17 12:10:01.197775', '0', 'Document Replace', 'DOC_REPLACE', 'Document Replace', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (139, '2008-04-17 12:10:01.198476', '0', 'Document Addendum', 'DOC_ADDENDUM', 'Document Addendum', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (140, '2008-04-17 12:10:01.199157', '0', 'Document Transformation', 'DOC_TRANSFORMATION', 'Document Transformation', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (141, '2008-04-17 12:10:01.199899', '0', 'Query for labeling instructions', 'QUERY_FOR_LABEL_INSTRUCTIONS', 'Query for labeling instructions', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (142, '2008-04-17 12:10:01.21203', '0', 'Query mode WOS', 'QUERY_MODE_WOS', 'Query mode WOS', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (143, '2008-04-17 12:10:01.212846', '0', 'Download mode WOS', 'DL_MODE_WOS', 'Download mode WOS', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (144, '2008-04-17 12:10:01.213484', '0', 'Management of Pre/Post-processor', 'MGT_PRE_POST_PROC', 'Management of Pre/Post-processor', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (145, '2008-04-17 12:10:01.214085', '0', 'Subscribe to PCD Data', 'SUBSCRIBE_PCD_DATA', 'Subscribe to PCD Data', 'PCD 1:2.1');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (146, '2008-08-18 15:30:00', '0', 'Asynchronous Web Services Exchange', 'ASYNCH_WEB_SVCS_EXCHANGE', 'Asynchronous Web Services Exchange', 'ITI 1:10.2.4');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (147, '2008-08-18 15:30:00', '0', 'Pediatric Demographics', 'PEDIATRIC_DEMOG', 'Pediatric Demographics', 'ITI 1:5.2.1');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (148, '2008-10-25 12:00:00', '0', 'Care Record', 'CARE_RECORD', 'Care Record', 'PCC 1:2.16');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (149, '2008-10-25 12:00:00', '0', 'HL7 Version 2 Option', 'HL7_V2', 'HL7 Version 2 Option', 'PCC 1:2.16');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (150, '2008-10-25 12:00:00', '0', 'Guideline Management', 'GUIDELINE_MGMT', 'Guideline Management', 'PCC 1:2.16');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (151, '2008-10-25 12:00:00', '0', 'Subscribe to Alarm Status', 'SUBSCRIBE_ALARM_STATUS', 'Subscribe to Alarm Status', 'PCD 1:X.1');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (153, '2008-10-25 12:00:00', '0', 'Rosetta Terminology Management', 'ROSETTA_TERM', 'Rosetta Terminology Management', 'PCD 1:X.1');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (156, '2008-10-28 08:00:00', '0', 'HTTP_BINDING Option', 'HTTP_BINDING', 'HTTP_BINDING Option', 'SVS reference');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (157, '2008-10-28 08:00:00', '0', 'SOAP_BINDING Option', 'SOAP_BINDING', 'SOAP_BINDING Option', 'SVS reference');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (158, '2009-07-02 15:15:36.14', 'admin', 'Appointment Notification', 'APPT_NOTIFICATION', 'Appointment Notification', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (159, '2009-07-02 15:20:42.70', 'admin', 'Instructions for performing a procedure - placer order management', 'PROCEDURE_INSTRUCTIONS_PLACER_ORDER_MGMT', 'Instructions for performing a procedure - placer order management', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (160, '2009-07-02 15:20:56.616', 'admin', 'Instructions for performing a procedure - filler order management', 'PROCEDURE_INSTRUCTIONS_FILLER_ORDER_MGMT', 'Instructions for performing a procedure - filler order management', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (161, '2009-07-02 15:28:32.768', 'admin', 'Patient Instructions Option', 'PATIENT_INSTRUCTIONS', 'Patient Instructions Option', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (164, '2009-07-02 15:40:42.747', 'admin', 'Legacy Acquisition Modality Importer Storage', 'LEGACY_ACQ_MI_STORAGE', 'Legacy Acquisition Modality Importer Storage', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (7, '2009-07-02 15:56:23.649', 'admin', 'Broad Worklist Query', 'BROAD_QUERY', 'Broad Worklist Query', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (167, '2009-07-02 16:02:20.265', 'admin', 'DVD Media', 'DVD', 'DVD Media', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (168, '2009-07-02 16:04:07.737', 'admin', 'Privacy Protection Using PBE', 'PRIVACY_PROTECTION_PBE', 'Privacy Protection Using PBE', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (169, '2009-07-02 16:04:57.186', 'admin', 'Privacy Protection Using PKI', 'PRIVACY_PROTECTION_PKI', 'Privacy Protection Using PKI', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (170, '2009-07-02 16:05:51.428', 'admin', 'Sending Software', 'SENDING_SOFTWARE', 'Sending Software', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (171, '2009-07-02 16:06:37.618', 'admin', 'Basic Viewer', 'BASIC_VIEWER', 'Basic Viewer', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (174, '2009-07-02 16:13:30.568', 'admin', 'Health Data Locator Option', 'HEALTH_DATA_LOCATOR', 'Health Data Locator Option', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (162, '2009-07-03 10:09:32.48', 'admin', 'Relative Image Position Coding', 'RELATIVE_IMG_POS_CODING', 'Relative Image Position Coding Option', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (163, '2009-07-03 10:12:41.112', 'admin', 'Stereo Relationship Option', 'STEREO_RELATIONSHIP', 'Stereo Relationship Option', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (178, '2009-07-08 12:38:07.564', 'admin', 'Basic Patient Privacy Acknowledgement View', 'BPPC_ACK_VIEW', 'Basic Patient Privacy Acknowledgement View', 'ITI TF-3:5.1.2 and 5.1.3');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (182, '2009-07-14 11:00:06.538', 'admin', 'Health at Birth', 'QRPH_HEALTH_BIRTH', 'Health at Birth', 'QRPH 2: 6.3.1.Y');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (183, '2009-07-14 11:00:45.378', 'admin', 'Child Growth Health', 'QRPH_CHILD_GROWTH_HEALTH', 'Child Growth Health', 'QRPH 2: 6.3.1.Z');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (184, '2009-07-14 11:49:05.743', 'admin', 'Batch sending (Anatomic Pathology)', 'PAT_BATCH', 'Batch', 'PAT 2: Z');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (185, '2009-07-14 14:35:25.967', 'admin', 'Laboratory Code Set Management', 'LAB_CODE_SET_MGMT', 'Laboratory Code Set Management', 'Lab 2:18');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (173, '2009-07-16 14:59:06.991', 'admin', 'XHTML forms for RFD', 'XHTML', 'XHTML', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (172, '2009-07-16 14:59:40.819', 'admin', 'Xforms for RFD', 'XFORMS', 'Xforms', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (186, '2009-07-24 15:48:17.112', 'admin', 'Input for Invoicing', 'INPUT_FOR_INVOICING', 'Input for Invoicing', 'LAB ILW Supplement');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (187, '2009-07-24 15:48:44.254', 'admin', 'Non-coded orders', 'NON_CODED_ORDERS', 'Non-coded orders', 'Lab ILW Supplement');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (188, '2009-07-24 15:51:50.758', 'admin', 'Test addition approval', 'TEST_ADD_APPROVAL', 'Test addition approval', 'LAB ILW Supplement');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (200, '2009-08-25 09:53:31.826', 'admin', 'Archive CRD data using ITI-41', 'ARCHIVE_CRD', 'Archive CRD', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (189, '2009-08-25 09:54:05.357', 'admin', 'Document Metatdata Publish Recipient', 'DOC_METADATA_PUB_REC', 'Document Metatdata Publish Recipient', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (205, '2009-08-25 09:59:45.227', 'admin', 'USB Media for PDI', 'USB_MEDIA', 'USB Media for PDI', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (180, '2009-08-25 14:19:26.13', 'admin', 'NM Option for Stress', 'NUCLEAR_MEDICINE', 'NM Option for Stress', 'RAD TF-2: 4.16');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (204, '2009-08-25 14:19:49.163', 'admin', 'OBX - Encapsulated PDF or Ref Pointer for IDCO', 'OBX_PDF_OR_REF_POINTER', 'OBX - Encapsulated PDF or Ref Pointer for IDCO', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (201, '2009-08-25 14:21:29.293', 'admin', 'PV1 Patient Visit for IDCO', 'PV1_Patient_Visit', 'PV1 Patient Visit for IDCO', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (179, '2009-08-25 14:22:35.639', 'admin', 'Request Referral: Indicates support for ITT-50 ', 'REQUEST_REFERRAL', 'Request Referral', 'ITI TF-2b: 3.50');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (190, '2009-08-25 14:26:08.322', 'admin', 'Revoke Option', 'REVOKE', 'Revoke Option', 'ITI TF-1: 27.2.2');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (181, '2009-08-25 14:26:28.968', 'admin', 'Report Fac-Simile For Order Group', 'RPT_FAX_FOR_ORDER_GROUP', 'Report Fac-Simile For Order Group', 'LAB TF 2:4');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (177, '2009-08-25 14:26:54.279', 'admin', 'ZIP over Email Response', 'ZIP_OVER_EMAIL_RESPONSE', 'ZIP over Email Response', 'ITI TF-1: 16.2.4');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (196, '2009-08-25 14:27:20.71', 'admin', 'User Specifiable Lighting Condition', 'USER_SPEC_LIGHT_COND', 'User Specifiable Lighting Condition', 'RAD TF-2: 4.23.4.2.4');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (199, '2009-08-25 14:28:10.429', 'admin', 'Retrieve sub-topic medical knowledge', 'T81-subtopic-med-knowledge', 'Retrieve sub-topic medical knowledge', '');
INSERT INTO tf_integration_profile_option (id, last_changed, last_modifier_id, description, keyword, name, reference) VALUES (51, '2010-01-29 16:52:52.234', 'jbmeyer', 'Acknowledgement Request with IMAP Option', 'ACK_REQUEST_WITH_IMAP', 'Acknowledgement Request with IMAP Option', 'ITI TF-2:3.28');
SET escape_string_warning = off;
-- 01_tf_integration_profile_status_type_data.sql
SET escape_string_warning = off;
INSERT INTO tf_integration_profile_status_type (id, last_changed, last_modifier_id, description, keyword, name) VALUES (1, '2007-08-20 00:00:00', '0', '', 'WP', 'White Paper');
INSERT INTO tf_integration_profile_status_type (id, last_changed, last_modifier_id, description, keyword, name) VALUES (2, '2007-08-20 00:00:00', '0', '', 'PROPOSED', 'Proposed');
INSERT INTO tf_integration_profile_status_type (id, last_changed, last_modifier_id, description, keyword, name) VALUES (3, '2007-08-20 00:00:00', '0', '', 'PC', 'Public Comment');
INSERT INTO tf_integration_profile_status_type (id, last_changed, last_modifier_id, description, keyword, name) VALUES (4, '2007-08-20 00:00:00', '0', '', 'TI', 'Trial Implementation');
INSERT INTO tf_integration_profile_status_type (id, last_changed, last_modifier_id, description, keyword, name) VALUES (5, '2007-08-20 00:00:00', '0', '', 'FT', 'Final Text');
INSERT INTO tf_integration_profile_status_type (id, last_changed, last_modifier_id, description, keyword, name) VALUES (6, '2007-08-20 00:00:00', '0', '', 'DEPRECATED', 'Deprecated');
INSERT INTO tf_integration_profile_status_type (id, last_changed, last_modifier_id, description, keyword, name) VALUES (7, '2009-08-04 15:27:49.235764', '0', NULL, 'HITSP', 'HITSP Construct');
SET escape_string_warning = off;
-- 01_tf_integration_profile_type_data.sql
SET escape_string_warning = off;
INSERT INTO tf_integration_profile_type (id, last_changed, last_modifier_id, description, keyword, name) VALUES (1, '2007-06-27 18:22:12.742508', NULL, '', 'EHR_ACCESS', 'EHR Access');
INSERT INTO tf_integration_profile_type (id, last_changed, last_modifier_id, description, keyword, name) VALUES (2, '2007-06-27 18:22:12.800775', NULL, '', 'IDENTITY_MANAGEMENT', 'Identity Management');
INSERT INTO tf_integration_profile_type (id, last_changed, last_modifier_id, description, keyword, name) VALUES (3, '2007-06-27 18:22:12.802213', NULL, '', 'SECURITY', 'Security');
INSERT INTO tf_integration_profile_type (id, last_changed, last_modifier_id, description, keyword, name) VALUES (4, '2007-06-27 18:22:12.80334', NULL, '', 'WORKFLOW', 'Workflow');
INSERT INTO tf_integration_profile_type (id, last_changed, last_modifier_id, description, keyword, name) VALUES (5, '2007-06-27 18:22:12.804416', NULL, '', 'NULL', '');
SET escape_string_warning = off;
-- 01_tf_transaction_option_type_data.sql
SET escape_string_warning = off;
INSERT INTO tf_transaction_option_type (id, last_changed, last_modifier_id, description, keyword, name) VALUES (1, '2007-08-20 00:00:00', '0', '', 'R', 'Required');
INSERT INTO tf_transaction_option_type (id, last_changed, last_modifier_id, description, keyword, name) VALUES (2, '2007-08-20 00:00:00', '0', '', 'O', 'Optional');
INSERT INTO tf_transaction_option_type (id, last_changed, last_modifier_id, description, keyword, name) VALUES (3, '2009-07-13 21:29:38.974411', '0', '', 'C', 'Conditional');
SET escape_string_warning = off;
-- 01_tf_transaction_status_type_data.sql
SET escape_string_warning = off;
INSERT INTO tf_transaction_status_type (id, last_changed, last_modifier_id, keyword, name, description) VALUES (1, '2007-08-20 00:00:00', '0', 'WP', 'White Paper', '');
INSERT INTO tf_transaction_status_type (id, last_changed, last_modifier_id, keyword, name, description) VALUES (2, '2007-08-20 00:00:00', '0', 'PROPOSED', 'Proposed', '');
INSERT INTO tf_transaction_status_type (id, last_changed, last_modifier_id, keyword, name, description) VALUES (3, '2007-08-20 00:00:00', '0', 'PC', 'Public Comment', '');
INSERT INTO tf_transaction_status_type (id, last_changed, last_modifier_id, keyword, name, description) VALUES (4, '2007-08-20 00:00:00', '0', 'TI', 'Trial Implementation', '');
INSERT INTO tf_transaction_status_type (id, last_changed, last_modifier_id, keyword, name, description) VALUES (5, '2007-08-20 00:00:00', '0', 'FT', 'Final Text', '');
INSERT INTO tf_transaction_status_type (id, last_changed, last_modifier_id, keyword, name, description) VALUES (6, '2007-08-20 00:00:00', '0', 'DEPRECATED', 'Deprecated', '');
SET escape_string_warning = off;
-- 01_user_role_data.sql
insert into evsc_user_role (id, name, conditional) values (1, 'admin', false);
insert into evsc_user_role (id, name, conditional) values (2, 'member', false);
insert into evsc_user_role (id, name, conditional) values (3, 'guest', true);
insert into user_role_group (role_id, member_of_role) values (1, 2);
-- 01_validation_service_data.sql
INSERT INTO evsc_validation_service (id, available, description, keyword, name, provider, wsdl, engine, xsl_location) VALUES (8, true, NULL, 'HL7v2_GAZELLE', 'Gazelle HL7v2.x validator', 'IHE Europe', 'http://131.254.209.20:8080/GazelleHL7v2Validator-GazelleHL7v2Validator-ejb/GazelleHL7v2ValidationWS?wsdl', NULL, NULL);
INSERT INTO evsc_validation_service (id, available, description, keyword, name, provider, wsdl, engine, xsl_location) VALUES (7, true, 'calls TLS validation from PKI project', 'TLS', 'TLS certificate Validator', 'IHE Europe', 'http://131.254.209.14:8080/gazelle-pki-gazelle-pki-ejb/CertificateValidator?wsdl', '', 'http://gazelle.ihe.net/xsl/tlsResultStylesheet.xsl');
INSERT INTO evsc_validation_service (id, available, description, keyword, name, provider, wsdl, engine, xsl_location) VALUES (18, true, '', 'JHOVE', 'JHOVE', 'Harvard', '', '', 'http://gazelle.ihe.net/xsl/JhoveResultStylesheet.xsl');
INSERT INTO evsc_validation_service (id, available, description, keyword, name, provider, wsdl, engine, xsl_location) VALUES (19, true, '', 'MB-SVS', 'MB SVS', '', 'http://192.168.20.102:8080/SVSSimulator-SVSSimulator-ejb/ModelBasedValidation?wsdl', 'model-based', 'http://gazelle.ihe.net/xsl/xdwDetailedResult.xsl');
INSERT INTO evsc_validation_service (id, available, description, keyword, name, provider, wsdl, engine, xsl_location) VALUES (3, true, 'calls Gazelle web services ', 'Gazelle', 'Gazelle', 'INRIA', 'http://jumbo.irisa.fr:8080/SchematronValidator-SchematronValidator-ejb/GazelleObjectValidatorWS?wsdl', 'schematron', 'http://gazelle.ihe.net/xsl/schematronResultStylesheet4EVSC.xsl');
INSERT INTO evsc_validation_service (id, available, description, keyword, name, provider, wsdl, engine, xsl_location) VALUES (6, false, 'calls hl7CupWS (HAPI) from InriaHL7Validator project', 'HAPI', 'HL7v2.x HAPI Validator', 'INRIA', 'http://maki.irisa.fr:8080/InriaHL7Validator-dev-InriaHL7Validator-ejb/InriaHL7CupWS?wsdl', NULL, NULL);
INSERT INTO evsc_validation_service (id, available, description, keyword, name, provider, wsdl, engine, xsl_location) VALUES (11, true, 'model-based validator for XDS', 'MB-XDS', 'model-based validator for XDS', 'IHE Europe', 'http://131.254.209.20:8080/XDStarClient-XDStarCommon-ejb/XDSMetadataValidatorWS?wsdl', 'model-based', 'http://gazelle.ihe.net/xsl/xdwDetailedResult.xsl');
INSERT INTO evsc_validation_service (id, available, description, keyword, name, provider, wsdl, engine, xsl_location) VALUES (9, true, '', 'MB-XDW', 'XDW model-based validator', 'IHE Europe', 'http://gazelle.ihe.net/XDWSimulatorWS/XDWValidatorWS?wsdl', 'model-based', 'http://gazelle.ihe.net/xsl/xdwDetailedResult.xsl');
INSERT INTO evsc_validation_service (id, available, description, keyword, name, provider, wsdl, engine, xsl_location) VALUES (10, true, 'fdsfds', 'MB-CDA', 'MB CDA', 'IHE Europe', 'http://192.168.20.103:8081/CDAGenerator-CDAGenerator-ejb/CDAValidatorWS?wsdl', 'model-based', 'http://gazelle.ihe.net/xsl/mbcdaDetailedResult.xsl');
INSERT INTO evsc_validation_service (id, available, description, keyword, name, provider, wsdl, engine, xsl_location) VALUES (2, false, 'calls NIST web service ', 'HL7v2_NIST', 'HL7 V2 Validation', 'NIST', 'http://xreg2.nist.gov:8080/HL7WS/services/MessageValidation', '', '');
INSERT INTO evsc_validation_service (id, available, description, keyword, name, provider, wsdl, engine, xsl_location) VALUES (1, true, 'calls hl7CupWS from InriaHL7Validator project', 'HL7v2_INRIA', 'HL7v2.x Validator', 'INRIA', 'http://maki.irisa.fr:8080/InriaHL7Validator-dev-InriaHL7Validator-ejb/InriaHL7CupWS?wsdl', '', '');
INSERT INTO evsc_validation_service (id, available, description, keyword, name, provider, wsdl, engine, xsl_location) VALUES (5, true, 'Dicom 3 tools validator', 'dicom3tools', 'Dicom 3 tools', 'David Clunie', '/opt/EVSClient_dev/bin/dicom3tools', '', '');
INSERT INTO evsc_validation_service (id, available, description, keyword, name, provider, wsdl, engine, xsl_location) VALUES (4, true, '', 'pixelmed', 'Pixelmed', '', '', '', '');
INSERT INTO evsc_validation_service (id, available, description, keyword, name, provider, wsdl, engine, xsl_location) VALUES (14, true, '', 'dcmcheck', 'dcmcheck', '', '', '', '');
INSERT INTO evsc_validation_service (id, available, description, keyword, name, provider, wsdl, engine, xsl_location) VALUES (15, true, '', 'dcm4che', 'dcm4che', '', '', '', '');
INSERT INTO evsc_validation_service (id, available, description, keyword, name, provider, wsdl, engine, xsl_location) VALUES (16, true, '', 'DCCHECK', 'DCCHECK', '', '', '', '');
INSERT INTO evsc_validation_service (id, available, description, keyword, name, provider, wsdl, engine, xsl_location) VALUES (17, true, '', 'DVTK', 'DVTK', '', '', '', '');
-- 02_user_user_role_data.sql
INSERT INTO evsc_user_user_role (role_id, user_id) VALUES (1, 1);
INSERT INTO evsc_user_user_role (role_id, user_id) VALUES (1, 2);
-- 05_tf_transaction_data.sql
SET escape_string_warning = off;
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (208, '2009-07-08 15:09:45.669', 'admin', 'In the Store Position Registration Results to Archive transaction, when a patient registration workitem has been completed by a PPS or PDS, the results of the registration operation are stored to the Archive. These results may subsequently be referenced in the Output Information Sequence of the corresponding Unified Procedure Step.', 'RO-23', 'Store Position Registration Results to Archive', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (209, '2009-07-08 15:10:16.697', 'admin', 'In the Store Position Registration Results to Archive transaction, when a treatment delivery workitem has been completed by a PDS or TDD, the results of the treatment delivery operation are stored to the Archive. These results may subsequently be referenced in the Output Information Sequence of the corresponding Unified Procedure Step', 'RO-24', 'Store Delivery Results to Archive', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (210, '2009-07-08 15:10:53.752', 'admin', 'In the UPS Completed/Canceled transaction, a PPS, PDS, or TDD signals to the TMS that the selected work item has either been completed or canceled.', 'RO-25', 'UPS Completed/Canceled', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (211, '2009-07-08 15:11:24.347', 'admin', 'In the UPS Progress Update transaction, a PDS or TDD signals to the TMS changes in the progress of the work item that is currently in progress.', 'RO-26', 'UPS Progress Update', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (201, '2009-07-08 15:24:36.941', 'admin', 'In the Registered Dose Retrieve Transaction, the requested Dose is transferred from the Archive to the Registered Dose Display actors.', 'RO-16', 'Registered Dose Retrieve', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (170, '2009-07-11 16:58:27.616', 'admin', 'This transaction contains the information from the Infusion Order Placer, such as caregiver, patient, and pump identification, medication, volume, and rate, for the infusion being programmed.', 'PCD-3', 'Communicate Infusion Order', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (42, '2009-07-12 23:43:29.147', 'admin', 'Based on a query from a Report Creator worklist client, a worklist is generated by the Report Manager containing reporting task workitems that satisfy the query. Workitems are returned in the form of a list of General Purpose Scheduled Procedure Steps.', 'RAD-46', 'Query Reporting Worklist', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (8, '2009-07-12 23:52:55.565', 'admin', 'An Acquisition Modality notifies the Performed Procedure Step Manager of the completion of a Procedure Step and the PPS Manager informs the Department System and Image Manager.', 'RAD-7', 'Modality Procedure Step Completed', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (212, '2009-07-13 19:04:07.916', 'admin', '', 'PCC-11', 'V2 Care Management Update', 'PCC 2: x', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (213, '2009-07-14 09:45:04.857', 'admin', 'Request for Clinical Guidance', 'PCC-12', 'Request for Clinical Guidance', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (214, '2009-07-14 11:42:58.186', 'admin', 'Public Health Reporting', 'PAT-10', 'Public Health Reporting', 'PAT 2: Z', 3);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (216, '2009-07-14 14:56:01.571', 'admin', 'Enter Patient Request', 'QRPH-Y2', 'Enter Patient Request', 'QRPH TF-2:3.Y2', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (217, '2009-07-14 14:56:40.478', 'admin', 'Patient Screening Visits Scheduled', 'QRPH-Y3', 'Patient Screening Visits Scheduled', 'QRPH TF-2:3.Y3', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (219, '2009-07-14 14:58:37.734', 'admin', 'Enroll Patient Request', 'QRPH-Y5', 'Enroll Patient Request', 'QRPH TF-2:3.Y5', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (220, '2009-07-14 14:59:29.645', 'admin', 'Patient Study Visits Scheduled', 'QRPH-Y6', 'Patient Study Visits Scheduled', 'QRPH TF-2:3.Y6', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (221, '2009-07-14 15:00:06.162', 'admin', 'Record Patient Study Visit', 'QRPH-Y7', 'Record Patient Study Visit', 'QRPH TF-2:3.Y7', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (222, '2009-07-14 15:00:38.09', 'admin', 'Amend Protocol Definition', 'QRPH-Y8', 'Amend Protocol Definition', 'QRPH TF-2:3.Y8', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (223, '2009-07-14 15:02:17.552', 'admin', 'Alert Protocol State', 'QRPH-Y9', 'Alert Protocol State', 'QRPH TF-2:3.Y9', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (215, '2009-07-14 15:04:16.723', 'admin', 'Retrieve Protocol Def', 'QRPH-Y1', 'Retrieve Protocol Def', 'QRPH TF-2:3.Y1', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (218, '2009-07-14 16:48:10.407', 'admin', 'Record Patient Screening Visit', 'QRPH-Y4', 'Record Patient Screening Visit', 'QRPH TF-2:3.Y.4', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (224, '2009-07-24 15:35:26.643', 'admin', 'Sub-order Management', 'LAB-35', 'Sub-order Management', 'Lab Supplement ILW 2:3.35', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (225, '2009-07-24 15:36:02.657', 'admin', 'Sub-order Results Delivery', 'LAB-36', 'Sub-order Results Delivery', 'Lab Supplement ILW 2:3.36', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (178, '2009-07-03 09:56:19.103', 'admin', 'Provide & Register Imaging Doc Set-MTOM/XOP', 'RAD-68', 'Provide & Register Imaging Doc Set-MTOM/XOP', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (179, '2009-07-03 09:56:36.026', 'admin', 'Retrieve Imaging Doc Set', 'RAD-69', 'Retrieve Imaging Doc Set', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (182, '2009-07-17 11:25:30.948', 'admin', 'Document Metadata Notify', 'ITI-53', 'Document Metadata Notify', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (184, '2009-07-30 08:45:08.249', 'admin', 'Cross Gateway Patient Discovery', 'ITI-55', 'Cross Gateway Patient Discovery', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (181, '2009-07-17 11:27:14.76', 'admin', 'Document Metadata Publish', 'ITI-54', 'Document Metadata Publish', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (180, '2009-07-17 10:45:57.667', 'admin', 'Document Metadata Subscribe', 'ITI-52', 'Document Metadata Subscribe', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (185, '2009-07-30 09:14:02.618', 'admin', 'Patient Location Query', 'ITI-56', 'Patient Location Query', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (183, '2009-07-30 12:47:07.951', 'admin', 'Multi-Patient Stored Query', 'ITI-51', 'Multi-Patient Stored Query', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (186, '2009-07-08 13:58:13.802', 'admin', 'In the Single/Contoured Image Series Retrieve transaction, the Archive sends a series of CT-Images to the Contourer, Geometric Planner, or Dosimetric Planner.', 'RO-1', 'Single/Contoured Image Series Retrieval', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (187, '2009-07-08 13:59:15.474', 'admin', 'In the Structure Set Storage Transaction, the Contourer stores a Structure Set on an Archive to make it available', 'RO-2', 'Structure Set Storage', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (188, '2009-07-08 13:59:49.707', 'admin', 'In the Geometric Plan Storage transaction, the Geometric Planner sends the newly created Geometric Plan to the Archive.', 'RO-3', 'Geometric Plan Storage', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (189, '2009-07-08 14:00:38.618', 'admin', 'In this transaction, the Dosimetric Planner sends the plan containing the references to the structure set to the Archive', 'RO-4', 'Dosimetric Plan Storage', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (190, '2009-07-08 14:01:12.434', 'admin', 'In the Dose Storage transaction, the Dosimetric planner sends the newly created Dose to the Archive.', 'RO-5', 'Dose Storage', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (191, '2009-07-08 14:01:46.757', 'admin', 'In the Multi-Series Image Retrieve Transaction, the Archive stores CT Images from multiple series (but a single study) on a Contourer to make these Images available for contouring', 'RO-6', 'Multi-Series Image Retrieve', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (192, '2009-07-08 14:02:59.504', 'admin', 'In the Structure Set Retrieval Transaction, the Archiver stores a Structure Set on a Contourer, Geometric Planner, Dosimetric Planner, or Dose Displayer.', 'RO-7', 'Structure Set Retrieval', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (193, '2009-07-08 14:03:27.831', 'admin', 'In the Geometric Plan Retrieve Transaction, the requested Geometric Plan is transferred from the Archive to the Dosimetric Planner.', 'RO-8', 'Geometric Plan Retrieve', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (194, '2009-07-08 14:04:02.571', 'admin', 'In this transaction, the Dose Displayer retrieves the plan containing the references to the structure set to the Archive', 'RO-9', 'Dosimetric Plan Retrieve', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (195, '2009-07-08 14:04:32.942', 'admin', 'In the Dose Retrieve Transaction, the requested Dose is transferred from the Archive to the Dose Displayer', 'RO-10', 'Dose Retrieve', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (196, '2009-07-08 14:05:51.795', 'admin', 'In the Resampled/Combined CT Series Storage Transaction, the Contourer stores CT Images which have been combined or resampled into a single series on the Archive.', 'RO-11', 'Resampled/Combined CT Series Storage', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (114, '2008-04-17 12:10:05.591817', '0', 'A system importing DICOM Objects or digitized hardcopy sends imported DICOM Composite Objects to the Image Archive', 'RAD-61', 'Imported Objects Stored', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (29, '2008-04-17 12:10:05.511802', '0', 'Synchronize the local time with the time maintained by the Time Server.', 'RAD-33', 'Maintain Time-Deprecated', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (197, '2009-07-08 15:02:11.31', 'admin', 'In the Spatial Registrations Stored transaction, the Registrator sends Spatial Registration instances to the Archive. Spatial registration objects define how the pixel coordinates of one image data set are transformed to another coordinate system (for example to a coordinate system defined by another image data set thus allowing each dataset to be spatially aligned).', 'RO-12', 'Spatial Registrations Stored', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (171, '2009-07-11 17:37:01.204', 'admin', 'This transaction is used by the Alarm Reporter to report both unsolicited and subscribed alarms to Alarm Management and by Alarm Management to report subscribed or queried alarms to the Alarm Query actor.', 'PCD-4', 'Report Alarm', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (172, '2009-07-11 17:37:35.189', 'admin', 'This transaction is used by Alarm Management to report one or more dissemination status updates to the Alarm Reporter.', 'PCD-5', 'Report Alarm Status', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (173, '2009-07-11 17:39:30.387', 'admin', 'This transaction is used by Alarm Management to disseminate the alarm to Alarm Communication.', 'PCD-6', 'Disseminate Alarm', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (174, '2009-07-11 17:40:17.324', 'admin', 'This transaction is used by Alarm Communication to report one or more dissemination status updates to Alarm Management.', 'PCD-7', 'Report Dissemination Alarm Status', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (175, '2009-07-11 17:41:23.075', 'admin', '', 'PCD-8', 'Subscribe to Alarm', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (198, '2009-07-08 15:02:54.726', 'admin', 'A Registration Display receives from an Archive one or more Spatial Registration objects carrying the transformation information to be applied to two image data sets intended for further processing or registered display.', 'RO-13', 'Utililze Spatial Registrations', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (199, '2009-07-08 15:03:33.48', 'admin', 'In the Registered Structure Set Storage Transaction, the Registered Contourer stores a Structure Set on an Archive to make it available.', 'RO-14', 'Registered Structure Set Storage', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (200, '2009-07-08 15:04:09.859', 'admin', 'In the Registered Structure Set Retrieval Transaction, the Archive stores a Structure Set on a Registered Contourer or Registered Dose Displayer.', 'RO-15', 'Registered Structure Set Retrieval', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (202, '2009-07-08 15:05:54.229', 'admin', 'In the Worklist Query for Positioning and Delivery transaction, a PDS requests and receives a patient positioning and treatment delivery worklist from a TMS.', 'RO-17', 'Worklist Query for Positioning and Delivery', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (203, '2009-07-08 15:06:39.887', 'admin', 'In the Retrieve Workitem Input Objects from Archive transaction, a PPS, PDS, or TDD requests and receives from the Archive any SOP Class Instances required for performing desired procedure steps returned by a previous query. Each SOP instance must have been supplied in the Input Information Sequence of one or more of the returned worklist items.', 'RO-18', 'Retrtieve Workitem Input Objects from Archive', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (204, '2009-07-08 15:07:17.80', 'admin', 'In the UPS in Progress transaction, a PPS, PDS, or TDD signals to the TMS that responsibility has been taken for the performing of the selected work item.', 'RO-19', 'UPS In Progress', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (205, '2009-07-08 15:07:51.538', 'admin', 'In the Retrieve Workitem Input Objects from TMS transaction, a PDS or TDD requests and receives requests and receives SOP Class instances from the TMS, in order to support execution of the requested work item. These requested instances are of a “transient” nature, typically generated ‘on-the-fly’ by the TMS', 'RO-20', 'Retrieve Workitem Input Objects from TMS', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (206, '2009-07-08 15:08:26.407', 'admin', 'In the UPS Final Update transaction, a PPS, PDS, or TDD signals to the TMS changes in the properties of the work item that is currently in progress, prior to the UPS being signaled as completed or canceled.', 'RO-21', 'UPS Final Update', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (207, '2009-07-08 15:09:04.361', 'admin', 'In the Store Position Acquisition Results to Archive transaction, when a patient position acquisition workitem has been completed by a PPS or PDS, the results of the acquisition are stored to the Archive. These results may subsequently be referenced in the Output Information Sequence of the corresponding Unified Procedure Step.', 'RO-22', 'Store Position Acquisition Results to Archive', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (139, '2008-04-17 12:10:05.611553', '0', 'Patient Identity Feed HL7 V3', 'ITI-44', 'Patient Identity Feed HL7 V3', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (141, '2008-04-17 12:10:05.613036', '0', 'PIXV3 Update Notification', 'ITI-46', 'PIXV3 Update Notification', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (143, '2008-08-04 10:40:00', '0', 'Request information about recent patient information, used to obtain vital signs measurements, problems and allergies, diagnostic results, medications, immunizations, or procedures or visits relevant for a patient. The query may request information about some or all of the above topics, or may request information on a specific topic, or one entered for a specific encounter or date range.', 'PCC-1', 'Query Existing Data', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (149, '2008-04-17 12:10:05.619175', '0', 'This transaction is used by the Label Information Provider to send label delivery instructions to the Label Broker.  ', 'LAB-61', 'Label delivery request', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (150, '2008-04-17 12:10:05.619955', '0', 'This transaction is used by the Label Broker to query the specimen container labeling instructions from the Label Information Provider.', 'LAB-62', 'Query for label delivery instruction', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (151, '2008-04-17 12:10:05.620748', '0', '<p>This transaction is embedded within all network communications activity. All DICOM, HL7, and HTML connections shall comply with the IHE specification for bi-directional authentication and authorization of communications of Protected Healthcare Information (PHI). IHE does not specify how other protocols that transfer PHI shall perform bi-directional authentication and authorization, but requires that other protocols perform such authentication and authorization.</p>', 'ITI-19', 'Authenticate Node', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (152, '2008-04-17 12:10:05.62155', '0', 'Code set distribution (battery, test, observation).', 'LAB-51', 'Laboratory Code Set Management ', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (153, '2008-08-04 13:30:00', '0', 'An Acquisition Modality sends Dose objects to an Image Manager/Archive for storage so they can be later used for monitoring or analysis of patient radiation exposure.', 'RAD-62', 'Store Dose Information', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (154, '2008-08-04 13:30:00', '0', 'A Dose Information Reporter sends Dose objects to a Dose Register for subsequent compilation, monitoring and analysis of population radiation exposure and current practices. Dose objects will often be de-identified prior to submission.', 'RAD-63', 'Submit Dose Information', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (155, '2008-08-04 13:30:00', '0', 'A Dose Information Reporter or Dose Information Consumer requests and receives from the Image Manager/Archive a list of instance metadata describing Dose objects matching a specified filter.', 'RAD-64', 'Query Dose Information', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (156, '2008-08-04 13:30:00', '0', 'A Dose Information Reporter or Dose Information Consumer requests and receives from the Image Manager/Archive specified instances of Dose objects.', 'RAD-65', 'Retrieve Dose Information', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (157, '2008-08-04 13:30:00', '0', 'In this transaction, the Acquisition Modality or the Evidence Creator transmit a specific DICOM Key Object Selection (Image Rejection Note) to the Image Manager/ Image Archive for marking referenced images as "rejected".', 'RAD-66', 'Image Rejection Note Stored', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (116, '2008-04-17 12:10:05.593525', '0', 'The Portable Media Creator sends information to media reading actors by means of Interchange Media where it stores the information.', 'ITI-32', 'Distribute Document Set on Media', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (142, '2010-02-09 15:26:19.348', 'aberge', 'Patient Demographics Query HL7 V3', 'ITI-47', 'Patient Demographics Query HL7 V3', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (158, '2008-08-05 15:40:00', '0', 'This transaction is used by the Value Set Consumer to retrieve a Resolved Value Set from the Value Set Repository.  The Value Set Consumer has previously obtained the Resolved Value Set OID by means outside of the scope of this transaction. Appendix B of the IHE ITI Technical Framework Volume 2 has further information about obtaining and managing OIDs which are used as the Value Set Unique ID.', 'ITI-48', 'Retrieve Value Set', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (165, '2008-11-05 11:00:00', '0', 'This transaction contains all the messages required between the Order Placer and the Order Filler for the management of the life cycle of the order. Its main goal is to keep a consistent vision of the order, (content and status), between the two actors.', 'PAT-1', 'Placer Order Management', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (159, '2009-07-03 09:54:58.631', 'admin', 'Convey Printed Referral Request', 'ITI-49', 'Convey Printed Referral Request', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (160, '2009-07-03 09:55:15.53', 'admin', 'Request Referral', 'ITI-50', 'Request Referral', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (164, '2009-07-13 19:03:51.484', 'admin', 'V3 Care Management Update', 'PCC-10', 'V3 Care Management Update', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (166, '2008-11-05 11:00:00', '0', 'This transaction contains all the messages required between the Order Filler and the Order Placer for the notification of a new filler order, as well as the creation of the placer order that reflects it. Its main goal is to ensure that each filler order will be represented by a placer order, and will have both a filler order number and a placer order number.', 'PAT-2', 'Filler Order Management', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (167, '2008-11-05 11:00:00', '0', 'This transaction carries the results of an Order, as well as status changes, modifications, cancellations of these results, from the Order Filler to the Order Result Tracker.', 'PAT-3', 'Order Results Management', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (168, '2008-11-05 11:00:00', '0', 'The Department System Scheduler/Order Filler sends the Image Manager and Report Manager scheduled procedure information or procedure update.', 'PAT-4', 'Procedure Scheduled and Updated', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (169, '2008-11-05 11:00:00', '0', 'Based on a query entered at the Acquisition Modality, a modality worklist is generated listing all the items that satisfy the query. This list of Scheduled Procedure Steps with selected demographic information and information about specimen is returned to the Acquisition Modality.', 'PAT-5', 'Query Modality Worklist', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (74, '2009-07-03 09:36:45.711', 'admin', '<p>A Document Repository Actor initiates the Register Document Set transaction. This transaction allows a Document Repository Actor to register one or more documents with a Document Registry, by supplying metadata about each document to be registered. This document metadata will be used to create an XDS Document Entry in the registry. The Document Registry Actor ensures that document metadata is valid before allowing documents to be registered. If one or more documents fail the metadata validation, the Register Document Set transaction fails as a whole.</p><p> To support composite documents, an XDS Document may be a multipart document. The Document Repository must handle multi-part data sets as an  opaque entity . The Document Repository does not need to analyze or process its multi-part structure nor the content of any parts in the context of the XDS Integration Profile. </p>', 'ITI-14', 'Register Document Set', '', 6);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (93, '2009-07-03 09:37:29.519', 'admin', 'An Imaging Document Source actor initiates the Provide and Register Imaging Document Set transaction. For each document in the Submission Set, the Imaging Document Source actor provides both the documents as an opaque octet stream and the corresponding meta-data to the Document Repository. The Document Repository is responsible to persistently store these documents, and to register them in the Document Registry using the Register Documents transaction by forwarding the document meta-data received from the Imaging Document Source Actor. [RAD-54, derived from ITI-15].', 'RAD-54', 'Provide and Register Imaging Document Set', '', 6);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (177, '2009-07-03 09:55:50.212', 'admin', 'Media Information Stored', 'RAD-67', 'Media Information Stored', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (104, '2008-04-17 12:10:05.583271', '0', 'This transaction contains the messages used to download a Work Order Step (WOS) from the Automation Manager to the Analyzer or Pre/Post-processor, according to a "push method". It includes "cnew WOS", "update WOS", "cancel WOS" and the related applicative acknowledgements. This transaction is used with Analyzers and Pre/Post-processor which work in download mode.', 'LAB-21', 'WOS Download', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (105, '2008-04-17 12:10:05.584107', '0', 'This transaction contains the message used by the Analyzer or Pre/Post-processor to query the Automation Manager with one or more specimen (or location) identifiers, and the reply message from the Automation Manager delivering one or more WOS dedicated to each of these specimen. This transaction implements the "pull method" for requesting WOS.', 'LAB-22', 'WOS Query', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (106, '2008-04-17 12:10:05.584947', '0', 'This transaction contains the messages used by the Analyzer to report the status of an AWOS (such as "specimen arrived", "first run failed", "second run started", "AWOS complete" ...) and to send the tests results when the AWOS is complete. It also includes the related applicative acknowledgements from the Automation Manager.', 'LAB-23', 'AWOS Status Change', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (107, '2008-04-17 12:10:05.586035', '0', 'This transaction contains the messages used by the Pre or Post-Processor to report all the status changes of the SWOS, and the related applicative acknowledgements. Status changes include: "specimen arrived", "SWOS complete", "SWOS failed"...', 'LAB-26', 'SWOS Status Change', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (108, '2008-04-17 12:10:05.586922', '0', 'An Image Display requests and retrieves a particular image or set of images or other evidence from the Image Archive. [CARD-4, derived from RAD-16 and RAD-44]', 'CARD-4', 'Retrieve Images/Evidence', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (109, '2008-04-17 12:10:05.587822', '0', 'An Acquisition Modality or Evidence Creator stores transformation information for registering two image data sets in the same coordinate system for further processing or fused display.', 'RAD-56', 'Spatial Registrations Stored', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (110, '2008-04-17 12:10:05.588633', '0', 'An Acquisition Modality or Evidence Creator stores presentation information on registered image data sets for fused display.', 'RAD-57', 'Blending Presentation States Stored', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (111, '2008-04-17 12:10:05.589436', '0', 'An Image Display retrieves from an Image Archive the transformation information to be applied to image data sets for further processing or fused display.', 'RAD-58', 'Retrieve Spatial Registrations', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (112, '2008-04-17 12:10:05.59023', '0', 'The Performed Procedure Step Manager receives progress notification of an importation Procedure Step and in turn notifies the Order Filler, Image Manager and the Report Manager', 'RAD-59', 'Import Procedure Step in Progress', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (113, '2008-04-17 12:10:05.591027', '0', 'The Performed Procedure Step Manager receives completion notification of an importation Procedure Step and in turn notifies the Order Filler, Image Manager and the Report Manager', 'RAD-60', 'Import Procedure Step Completed', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (162, '2010-02-09 10:25:08.538', 'aberge', 'Request Guideline Data', 'PCC-8', 'Request Guideline Data', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (163, '2010-02-09 10:27:02.65', 'aberge', 'Care Management Data Query', 'PCC-9', 'Care Management Data Query', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (117, '2009-08-11 12:22:34.72', 'admin', 'Transmit PCD data to enterprise clients from a Device Observation Reporter or  Observation Filter and Receive PCD data by a Device Observation Consumer.', 'PCD-1', 'Communicate PCD Data', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (118, '2009-08-11 12:22:54.89', 'admin', 'Defines predicate for communication of PCD data from DOF to a Device Observation Consumer.', 'PCD-2', 'Subscribe to PCD Data', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (230, '2009-09-09 22:26:56.898', 'smoore', 'Communicate IDC Observation', 'PCD-9', 'Communicate IDC Observation', '', 4);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (120, '2008-04-17 12:10:05.597281', '0', 'Based on a query entered at the Acquisition Modality, a modality worklist is generated listing all the items that satisfy the query. This list of Scheduled Procedure Steps with selected demographic information is returned to the Acquisition Modality [EYECARE-1, derived from RAD-5].', 'EYE-1', 'Eye: Query Modality Worklist', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (121, '2008-04-17 12:10:05.59809', '0', 'An Acquisition Modality sends acquired or generated images, waveforms, or other evidence documents to the Image Archive. [EYECARE- 2, derived from RAD-8]', 'EYE-2', 'Eye: Modality Images/Evidence Stored', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (122, '2008-04-17 12:10:05.598824', '0', 'An Image Display requests and retrieves a particular image or set of images from the Image Archive. [EYECARE-3, derived from RAD-16]', 'EYE-3', 'Eye: Retrieve Images', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (123, '2008-04-17 12:10:05.599619', '0', 'A user of Evidence Documents (i.e. Image Display, Evidence Creators, etc.) queries the Image Archive for a list of entries representing Evidence Documents. [EYECARE-4, derived from RAD-44]', 'EYE-4', 'Eye: Query Evidence Documents', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (124, '2008-04-17 12:10:05.600416', '0', 'An Image Display queries the Image Archive for a list of entries representing images by patient, study, series, or instance. [EYECARE-5, derived from RAD-14]', 'EYE-5', 'Eye: Query Images', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (125, '2008-04-17 12:10:05.601197', '0', 'An Acquisition Modality notifies the Performed Procedure Step Manager of the completion of a Procedure Step and the PPS Manager informs the Department System Scheduler/Order Filler and Image Manager.  [EYECARE-6, derived from RAD-7]', 'EYE-6', 'Eye: Modality Procedure Step Completed', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (126, '2008-04-17 12:10:05.602113', '0', 'Displayable Report Storage', 'EYE-7', 'Eye: Displayable Report Storage', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (129, '2008-04-17 12:10:05.604289', '0', 'Retrieve Form', 'ITI-34', 'Retrieve Form', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (130, '2008-04-17 12:10:05.605087', '0', 'Submit Form', 'ITI-35', 'Submit Form', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (131, '2008-04-17 12:10:05.605753', '0', 'Archive Form', 'ITI-36', 'Archive Form', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (132, '2008-04-17 12:10:05.606443', '0', 'Retrieve Clarifications', 'ITI-37', 'Retrieve Clarifications', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (135, '2008-04-17 12:10:05.608627', '0', 'Provide X-User Assertion', 'ITI-40', 'Provide X-User Assertion', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (136, '2008-04-17 12:10:05.60936', '0', 'Provide and Register Document Set-b', 'ITI-41', 'Provide and Register Document Set-b', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (78, '2008-04-17 12:10:05.551565', '0', 'A POCRG sends to the POCDM a message containing: its own ID, the care unit ID, the ordering provider ID, the operator ID, the patient/visit ID (or QC ID) and other information related to the test to start. The POCDM identifies the operator, and checks the patient identification. It then sends the answer back to the POCRG. The answer may be positive and carry the patient&aposs identity, or negative and carry the reject reason.', 'LAB-30', 'Initiates point of care testing for a patient specimen on a persistently connected POCRG', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (79, '2008-04-17 12:10:05.552446', '0', 'The POCRG sends an observation set to the POCDM. The POCDM checks the content of this observation set, stores it and acknowledges it to the POCRG.', 'LAB-31', 'POCT observations produced.', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (80, '2008-04-17 12:10:05.553151', '0', 'The POCRG sends an observation set to the POCDM. The POCDM checks the content of this observation set, stores it and acknowledges it to the POCRG.', 'LAB-32', 'POCT observations accepted.', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (81, '2008-04-17 12:10:05.553927', '0', 'A Report Creator sends a preliminary, final, or corrected clinical report to the Report Manager, or a Report Manager sends a preliminary, final, or corrected clinical report to the Enterprise Report Repository.', 'CARD-7', 'Encapsulated Report Submission', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (82, '2008-04-17 12:10:05.554703', '0', 'A Report Manager sends a reference to a report to the Enterprise Report Repository for storage.', 'CARD-8', 'Report Reference Submission', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (83, '2008-04-17 12:10:05.555406', '0', 'A Report Manager sends a preliminary, final, or corrected clinical report to the Report Repository.', 'CARD-9', 'Encapsulated Report Storage', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (84, '2008-04-17 12:10:05.556212', '0', 'A Report Reader requests a list of clinical reports known by the Report Repository matching a set of selection criteria.', 'CARD-10', 'Encapsulated Report Query', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (85, '2008-04-17 12:10:05.556983', '0', 'A Report Reader requests and retrieves a clinical report from the Report Repository.', 'CARD-11', 'Encapsulated Report Retrieve', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (88, '2008-04-17 12:10:05.559376', '0', 'This transaction provides for sending of acknowledgements to document availability notices in an XDS Affinity Domain.', 'ITI-27', 'Send Acknowledgment', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (90, '2008-04-17 12:10:05.560984', '0', 'This transaction will generate a Cross-Enterprise Authentication Assertion and pass it to a relying service.', 'ITI-29', 'Assert X-User Identity', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (73, '2009-07-03 09:38:18.524', 'admin', 'A Document Source Actor initiates the Provide and Register Document Set Transaction. For each document in the submitted set, the Document Source Actor provides both the documents as an opaque octet stream and the corresponding metadata to the Document Repository. The Document Repository is responsible to persistently store these documents, and to register them in the Document Registry using the Register Documents transaction by forwarding the document metadata received from the Document Source Actor.', 'ITI-15', 'Provide and Register Document Set', '', 6);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (31, '2008-04-17 12:10:05.513362', '0', 'The Department System Scheduler/Order Filler sends descriptions of potential procedure and material changes.', 'RAD-35', 'Charge Posted', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (138, '2010-02-08 11:58:43.655', 'aberge', 'Retrieve Document Set', 'ITI-43', 'Retrieve Document Set', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (128, '2010-02-09 10:11:12.275', 'aberge', 'Retrieve Displayable Report', 'EYE-9', 'Eye: Retrieve Displayable Report', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (87, '2010-02-09 12:11:33.574', 'aberge', 'This transaction provides for receipt of document availability notices in an XDS Affinity Domain.', 'ITI-26', 'Receive Notification', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (89, '2010-02-09 12:15:41.475', 'aberge', 'This transaction provides for receipt of acknowledgements of document availability notices in an XDS Affinity Domain.', 'ITI-28', 'Receive Acknowledgement', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (86, '2010-02-09 12:15:57.945', 'aberge', 'This transaction provides for sending of document availability notices in an XDS Affinity Domain.', 'ITI-25', 'Send Notification', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (133, '2010-02-09 15:11:07.493', 'aberge', 'Cross Gateway Query', 'ITI-38', 'Cross Gateway Query', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (134, '2010-02-09 15:14:24.364', 'aberge', 'Cross Gateway Retrieve', 'ITI-39', 'Cross Gateway Retrieve', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (75, '2009-07-03 09:38:57.347', 'admin', 'The Query Registry transaction is issued by the Document Consumer Actor on behalf of a care provider (EHR-CR) to a Document Registry. The Document Registry Actor searches the registry to locate documents that meet the provider s specified query criteria. It will return a list of document entries that contain metadata found to meet the specified criteria including the locations and identifier of each corresponding document in one or more Document Repositories.', 'ITI-16', 'Query Registry', '', 6);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (76, '2009-07-03 09:39:13.841', 'admin', '<p>A Document Consumer Actor initiates the Retrieve Document transaction. The Document Repository will return the document that was specified by the Document Consumer. </p><p>To support composite documents, an XDS Document may be a multipart document. In this case, the Document Consumer must take appropriate actions to make the multipart content accessible to the user.</p>', 'ITI-17', 'Retrieve Document', '', 6);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (91, '2009-07-13 15:56:17.022', 'admin', 'The Patient Demographics Supplier registers or updates a patient and forwards the demographic information (i.e. all information directly related to the patient, such as ID, address, next of kin, guarantoru2026) to other systems implementing Patient Demographics Consumer.', 'ITI-30', 'Patient Identity Management', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (92, '2008-04-17 12:10:05.573861', '0', 'The Patient Encounter Source registers or updates an encounter (inpatient, outpatient, pre-admit...) and forwards the information to other systems implementing Patient Encounter Consumer. This information will include the patients location and care providers for a particular (usually current) encounter', 'ITI-31', 'Patient Encounter Management', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (115, '2009-08-10 16:53:52.732', 'admin', 'Observations, measurements, or reports are sent using an HL7 Observations message', 'CARD-12', 'Send Observations ', 'As of 2009, this is replaced with a transaction in the PCD domain', 6);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (94, '2008-04-17 12:10:05.575635', '0', 'A WADO Retrieve transaction is issued by an Imaging Document Consumer to an Imaging Document Source to retrieve DICOM objects over HTTP/HTTPS protocol [RAD-55].', 'RAD-55', 'WADO Retrieve', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (95, '2008-04-17 12:10:05.576386', '0', 'An Export Selector sends to an Export Manager instances that are to be de-identified, pseudonymized and exported.', 'RAD-50', 'Store Instances', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (96, '2008-04-17 12:10:05.577183', '0', 'An Export Selector sends to an Export Manager an instance of a Key Object Selection Document that references a list of instances that are to be de-identified, pseudonymized and exported', 'RAD-51', 'Store Export Selection', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (97, '2008-04-17 12:10:05.577926', '0', 'An Export Selector sends to an Export Manager instances containing additional information about the instances that are to be exported.', 'RAD-52', 'Store Additional Teaching File Information', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (98, '2008-04-17 12:10:05.578657', '0', 'An Export Manager sends to a Received instances that have been exported', 'RAD-53', 'Export Instances', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (47, '2008-04-17 12:10:05.525513', '0', 'Allows a Context Participant Actor to locate and establish communication with the Context Manager Actor.', 'ITI-5', 'Join Context', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (48, '2008-04-17 12:10:05.526266', '0', 'Includes all messages required to initiate and finalize a context change transaction: -Initiation of a context change request from the instigating participant actor. -Delivery of survey results to instigating actor and display of associated replies. -Communication of context change decision to the Context Manager Actor', 'ITI-6', 'Change Context', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (49, '2008-04-17 12:10:05.527044', '0', 'Allows Context Participant Actor to notify the Context manager Actor that it is breaking off communication.', 'ITI-7', 'Leave Context', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (50, '2008-04-17 12:10:05.527995', '0', 'Allows a Patient Identity Source Actor to notify a Patient Identity Cross-Referencing Actor of all events related to patient identification (creation, update, merge, etc.).', 'ITI-8', 'Patient Identity Feed', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (51, '2008-04-17 12:10:05.528844', '0', 'This transaction allows a Patient Identity Consumer to find out the identification of a patient in different Patient Identification Domains by using the services of a Patient Identity Cross-reference Manager Actor. ', 'ITI-9', 'PIX Query', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (52, '2008-04-17 12:10:05.529763', '0', 'Allows a Patient Identity Consumer to be notified by the Patient Identity Cross-reference Manager Actor of changes to the identification of a patient in Patient Identification Domains the Consumer is interested in.', 'ITI-10', 'PIX Update Notification', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (53, '2008-04-17 12:10:05.530696', '0', 'A request issued by a display system for specific information related to a patient returned in a ready for presentation information format', 'ITI-11', 'Retrieve Specific Information for Display', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (54, '2008-04-17 12:10:05.531522', '0', 'A display system requests an instance of a uniquely identified persistent document under custodianship by an information source and returns its content ready for presentation.', 'ITI-12', 'Retrieve Document for Display', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (55, '2008-04-17 12:10:05.53232', '0', 'Accounts for all messages required to propagate a context change to a responding participant actor: -Survey of all other Context Participant Actors by the Context Manager Actor and display by the instigating Participant Actor of any associated replies. -Notification of context change result from the Context manager Actor to the Context Participant Actors. -Retrieval of the context data by the Context Participant Actors', 'ITI-13', 'Follow Context', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (56, '2008-04-17 12:10:05.533074', '0', 'This transaction contains all the messages required between the Order Placer and the Order Filler for the management of the life cycle of the order. Its main goal is to keep a consistent vision of the order, (content and status), between the two actors.', 'LAB-1', 'Lab Placer Order Management', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (57, '2008-04-17 12:10:05.533877', '0', 'This transaction contains all the messages required between the Order Filler and the Order Placer for the notification of a new filler order, as well as the creation of the placer order that reflects it. Its main goal is to ensure that each filler order will be represented by a placer order, and will have both a filler order number and a placer order number.', 'LAB-2', 'Lab Filler Order Management', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (58, '2008-04-17 12:10:05.534682', '0', 'This transaction carries changes of the observation results and order status from Order Filler to Order Result Tracker i.e. corrections, cancellations.', 'LAB-3', 'Order Results Management', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (32, '2008-04-17 12:10:05.514297', '0', 'The ADT Patient Registration Actor informs Charge Processor about creation, modification and ending of patient s account.', 'RAD-36', 'Account Management', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (100, '2010-02-10 10:10:10.207', 'aberge', 'An Image Display or an Imaging Document Consumer requests and retrieves the Grayscale Softcopy Presentation State (GSPS) information for a particular image or image set', 'RAD-17', 'Retrieve Presentation States', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (101, '2010-02-10 10:17:05.911', 'aberge', 'A Report Reader or an Imaging Document Consumer requests and retrieves a diagnostic report from the Report Repository, External Report Repository Access or an Imaging Document Source.', 'RAD-27', 'Retrieve Reports', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (102, '2010-02-10 10:22:11.493', 'aberge', 'An Image Display or an Imaging Document Consumer requests and retrieves a Key Image Note from the Image Archive or an Imaging Document Source, respectively.', 'RAD-31', 'Retrieve Key Image Note', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (59, '2008-04-17 12:10:05.535492', '0', 'This transaction contain all the messages required between Order Filler and Automation Manager for the execution of a work order containing a subset of tests of the filler order. The main goal of this transaction is to distribute the work to the Automation Manager, and to keep this actor informed of all patient and order updates. This transaction will be based on a push mechanism, the query mechanism never being used in this transaction.', 'LAB-4', 'Work Order Management', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (60, '2008-04-17 12:10:05.536324', '0', 'This transaction carries the technically validated test results from the Automation Manager to the Order Filler.', 'LAB-5', 'Test Result Management', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (61, '2008-04-17 12:10:05.537129', '0', 'An Acquisition Modality notifies the Performed Procedure Step Manager of the start of a new Procedure Step and the PPS Manager informs the Department System Scheduler/Order Filler and Image Manager. [CARD- 1, derived from RAD-6]', 'CARD-1', 'Card Modality Procedure Step In Progress', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (62, '2008-04-17 12:10:05.537971', '0', 'An Acquisition Modality sends acquired or generated images, waveforms, or other evidence documents to the Image Archive. [CARD-2, derived from RAD-8 and RAD-43]', 'CARD-2', 'Card Modality Images/Evidence Stored', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (63, '2008-04-17 12:10:05.539068', '0', 'A requestor (Acquisition Modality) requests that the Image Manager confirm ownership for the specified DICOM objects (images, waveforms, evidence documents, or any combination thereof) that the requestor stored in the Image Archive, thus allowing the sender to delete those objects now owned by the Image Manager. [CARD-3, derived from RAD-10]', 'CARD-3', 'Card Storage Commitment', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (64, '2008-04-17 12:10:05.539843', '0', 'A Display queries an Information Source for a list of entries representing ECG documents by patient and time period. [CARD-5, derived from ITI-11]', 'CARD-5', 'Retrieve ECG List', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (65, '2008-04-17 12:10:05.540677', '0', 'A Display queries an Information Source for a specific ECG document by document id. [CARD-6, derived from ITI-12]', 'CARD-6', 'Retrieve ECG Document for Display', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (66, '2008-04-17 12:10:05.541611', '0', 'Department System Scheduler/Order Filler sends the Order Placer actor the date and time of the appointment(s) related to one or more Scheduled Procedure Step(s).', 'RAD-48', 'Appointment Notification', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (67, '2008-04-17 12:10:05.542435', '0', 'The Image Manager/Image Archive notifies interested workflow actors (such as the Department System Scheduler/Order Filler, Post- Processing Manager and Report Manager) about the availability status of instances at specified storage locations.', 'RAD-49', 'Instance Availability Notification', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (68, '2008-04-17 12:10:05.543275', '0', 'A source actor (Portable Media Creator) writes image data, other evidence objects and reports onto a piece of interchange media. The media is physically transported to another actor (Portable Media Importer, Image Display, Report Reader, Display or Print Composer) which then imports, displays or prints the evidence objects and reports. The media can also be provided to a patient or a referring physician for web-based viewing.', 'RAD-47', 'Distribute Imaging Information on Media', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (69, '2008-04-17 12:10:05.544115', '0', 'Look up and return patient demographic and visit information in a single patient demographics source, based upon matches with full or partial demographic/visit information entered by the user.', 'ITI-22', 'Patient Demographics and Visit Query ', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (70, '2008-04-17 12:10:05.544909', '0', 'Look up and return patient demographic information in a single patient demographics source, based upon matches with full or partial demographic information entered by the user.', 'ITI-21', 'Patient Demographics Query', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (71, '2008-04-17 12:10:05.545726', '0', 'This transaction will find the LDAP Directory by querying the DNS.', 'ITI-23', 'Find Personnel White Pages', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (72, '2008-04-17 12:10:05.546512', '0', 'This transaction provides for read-only access to the Personnel White Pages directory.', 'ITI-24', 'Query Personnel White Pages', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (77, '2008-04-17 12:10:05.55062', '0', '<p>The delivery of an audit event description from any secure node to the Audit Repository.</p>', 'ITI-20', 'Record Audit Event', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (10, '2008-04-17 12:10:05.496436', '0', 'An Acquisition Modality sends acquired or generated images to the Image Archive.', 'RAD-9', 'Modality Presentation State Stored', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (11, '2008-04-17 12:10:05.497234', '0', 'An Acquisition Modality or Image Creator requests that the Image Manager take responsibility for the specified DICOM objects (images, GSPS objects, Key Image Notes, Evidence Documents or any combination thereof) that the requestor stored in the Image Archive.', 'RAD-10', 'Storage Commitment', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (13, '2008-04-17 12:10:05.498938', '0', 'The ADT Patient Registration System informs the Order Placer and the Department System Scheduler/Order Filler of new information for a particular patient. The Department System Scheduler may then further inform the Image Manager.', 'RAD-12', 'Patient Update', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (14, '2008-04-17 12:10:05.499786', '0', 'The Department System Scheduler/Order Filler sends the Image Manager updated order or procedure information.', 'RAD-13', 'Procedure Update', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (15, '2008-04-17 12:10:05.5006', '0', 'An Image Display queries the Image Archive for a list of entries representing images by patient, study, series, or instance.', 'RAD-14', 'Query Images', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (16, '2008-04-17 12:10:05.501381', '0', 'An Image Display queries the Image Archive for a list of entries representing image Grayscale Softcopy Presentation States (GSPS) by patient, study, series, or instance.', 'RAD-15', 'Query Presentation States', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (17, '2008-04-17 12:10:05.502158', '0', 'An Image Creator sends new images to the Image Archive.', 'RAD-18', 'Creator Images Stored', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (18, '2008-04-17 12:10:05.502994', '0', 'An Image Creator requests that the Image Archive store the created Grayscale Softcopy Presentation State objects.', 'RAD-19', 'Creator Presentation State Stored', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (19, '2008-04-17 12:10:05.503778', '0', 'An Image Creator notifies the Performed Procedure Step Manager of the start of a new Procedure Step and the PPS Manager informs the Department System and Image Manager.', 'RAD-20', 'Creator Procedure Step In Progress', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (20, '2008-04-17 12:10:05.504562', '0', 'An Image Creator notifies the Performed Procedure Step Manager of the completion of a Procedure Step and the PPS Manager informs the Department System and Image Manager.', 'RAD-21', 'Creator Procedure Step Completed', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (21, '2008-04-17 12:10:05.505381', '0', 'A Print Composer sends a print request to the Print Server specifying Presentation LUT information.', 'RAD-23', 'Print Request with LUT', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (22, '2008-04-17 12:10:05.506166', '0', 'A Report Creator sends a draft or final report to the Report Manager.', 'RAD-24', 'Report Submission', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (23, '2008-04-17 12:10:05.506955', '0', 'A Report Manager sends a draft or final Report to the Report Repository.', 'RAD-25', 'Report Issuing', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (25, '2008-04-17 12:10:05.508628', '0', 'A Report Manager composes an HL7 Result transaction by mapping from DICOM SR and transmits it to the Enterprise Report Repository for storage.', 'RAD-28', 'Structured Report Export', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (26, '2008-04-17 12:10:05.509409', '0', 'An Acquisition Modality or an Image Creator sends a Key Image Note to the Image Archive', 'RAD-29', 'Key Image Note Stored', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (27, '2008-04-17 12:10:05.510234', '0', 'An Image Display queries the Image Archive for a list of entries representing Key Image Notes by patient, study, series, or instance.', 'RAD-30', 'Query Key Image Notes', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (28, '2008-04-17 12:10:05.511025', '0', 'Any two actors exchange certificates in order to validate the identity of another node.', 'RAD-32', 'Authenticate Node', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (33, '2008-04-17 12:10:05.515127', '0', 'Based on a query from a worklist client (Image Creator), a worklist is generated by the worklist manager (Post-Processing Manager) containing either Post-Processing or Computer Aided Detection (CAD) workitems that satisfy the query. Workitems are returned in the form of a list of General Purpose Scheduled Procedure Steps.', 'RAD-37', 'Worklist Provided', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (34, '2008-04-17 12:10:05.515867', '0', 'A worklist client (Image Creator) notifies the worklist provider (Post-Processing Manager) that it has claimed the workitem (i.e. started a General Purpose Scheduled Procedure Step).', 'RAD-38', 'Workitem Claimed', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (35, '2008-04-17 12:10:05.516629', '0', 'A worklist client (Image Creator) notifies the worklist provider (Post-Processing Manager) that it has started work (i.e. created a General Purpose Performed Procedure Step).', 'RAD-39', 'Workitem Performed Procedure Step In Process', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (36, '2008-04-17 12:10:05.517326', '0', 'A worklist client (Image Creator) notifies the worklist provider (Post-Processing Manager) of the completion of a General Purpose Performed Procedure Step.', 'RAD-40', 'Workitem Performed Procedure Step Completed', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (30, '2009-07-03 09:41:02.042', 'admin', 'Create and transmit an Audit Record.', 'RAD-34', 'Record Audit Event-Deprecated', '', 6);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (24, '2009-07-13 13:20:42.255', 'admin', 'A Report Reader provides a set of criteria to select the list of entries representing reports by patient, study, series, or report known by the Report Repository or External Report Repository Access.', 'RAD-26', 'Query Reports', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (12, '2009-07-13 14:15:24.047', 'admin', 'The Department System Scheduler/Order Filler asks the Image Manager if a particular image or image series is available.', 'RAD-11', 'Images Availability Query', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (231, '2009-08-19 22:22:00.097', 'fourquetl', 'The Retrieval of Medical Knowledge Transaction specifies the query and receipt of ancillary medical knowledge', 'T81-1', 'Retrieve topic medical knowledge', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (37, '2008-04-17 12:10:05.518114', '0', 'A worklist client (Image Creator) notifies the worklist provider (Post-Processing Manager) that it has finished the workitem (i.e. completed a General Purpose Scheduled Procedure Step).', 'RAD-41', 'Workitem Completed', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (38, '2008-04-17 12:10:05.518803', '0', 'The worklist provider informs other interested actors of the on-going status and completion of performed work.', 'RAD-42', 'Performed Work Status Update', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (39, '2008-04-17 12:10:05.519489', '0', 'An Acquisition Modality or Image Creator sends measured or derived diagnostic evidence in the form of a DICOM Structured Report to the Image Archive.', 'RAD-43', 'Evidence Document Stored', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (40, '2008-04-17 12:10:05.52017', '0', 'An Image Display queries the Image Archive for a list of entries representing Evidence Documents.', 'RAD-44', 'Query Evidence Documents', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (41, '2008-04-17 12:10:05.520873', '0', '', 'RAD-22', 'Intentionally unassigned', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (43, '2008-04-17 12:10:05.522261', '0', 'NTP transactions used to maintain time synchronization.', 'ITI-1', 'Maintain Time', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (44, '2008-04-17 12:10:05.523264', '0', 'The Client Authentication Agent requests user authentication from the Kerberos Authentication Server.  When the user is authenticated, the Kerberos Authentication Server returns a Ticket Granting Ticket (TGT) to optimize future activity.', 'ITI-2', 'Get User Authentication', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (45, '2008-04-17 12:10:05.523976', '0', 'Obtain a ticket using Kerberos protocol for use with a service. Service identity option is specific for each protocol. For example HOST for HTTP.', 'ITI-3', 'Get Service Ticket', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (46, '2008-04-17 12:10:05.52476', '0', 'The Kerberized Communication transaction is an aspect of the connection between a local client and a remote server.', 'ITI-4', 'Kerberized Communication', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (137, '2010-02-08 11:51:20.171', 'aberge', 'Register Document Set-b', 'ITI-42', 'Register Document Set-b', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (140, '2010-02-08 11:59:41.996', 'aberge', 'PIXV3 Query', 'ITI-45', 'PIXV3 Query', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (127, '2010-02-09 10:02:20.287', 'aberge', 'Query Displayable Report', 'EYE-8', 'Eye: Query Displayable Report', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (161, '2010-02-09 10:20:40.054', 'aberge', 'Guideline Notification', 'PCC-7', 'Guideline Notification', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (119, '2010-02-09 15:13:35.025', 'aberge', 'The Query Registry transaction is issued by the Document Consumer Actor on behalf of a care provider (EHR-CR) to a Document Registry. The Document Registry Actor searches the registry to locate documents that meet the provider s specified query criteria. It will return a list of document entries that contain metadata found to meet the specified criteria including the locations and identifier of each corresponding document in one or more Document Repositories. The stored query uses parameters and not direct SQL', 'ITI-18', 'Registry Stored Query', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (99, '2010-02-10 10:02:36.822', 'aberge', 'An Image Display or an Imaging Document Consumer requests and retrieves a particular image or set of images from the Image Archive or an Imaging Document Source, respectively.', 'RAD-16', 'Retrieves Images', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (103, '2010-02-10 10:24:51.941', 'aberge', 'A user of Evidence Documents (Image Display, Report Creator or Report Reader) or an Imaging Document Consumer requests and retrieves an Evidence Document from the Image Archive or an Imaging Document Source, respectively.', 'RAD-45', 'Retrieve Evidence Documents', '', 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (1, '2008-04-17 12:10:05.468281', '0', 'Dummy transaction', 'NULL', 'None', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (2, '2008-04-17 12:10:05.489126', '0', 'The ADT system registers and/or admits a patient and forwards the information to other information systems.', 'RAD-1', 'Patient Registration', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (3, '2008-04-17 12:10:05.490583', '0', 'The Order Placer informs the Order Filler of the initiation or cancellation of an order. The Placer/Filler Order Management transaction will sometimes be referred to as -New when a new order is being initiated, or as -Cancel when an existing order is canceled.', 'RAD-2', 'Placer Order Management', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (4, '2008-04-17 12:10:05.491425', '0', 'The Order Filler informs the Order Placer of the initiation, cancellation, or change in the status of an order. The Placer/Filler Order Management transaction will sometimes be referred to as -New when a new order is being initiated, or as -Cancel when an existing order is canceled.', 'RAD-3', 'Filler Order Management', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (5, '2008-04-17 12:10:05.492304', '0', 'Schedule information is sent from the Department System Scheduler/Order Filler to the Image Manager.', 'RAD-4', 'Procedure Scheduled', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (6, '2008-04-17 12:10:05.493115', '0', 'Based on a query entered at the Acquisition Modality, a modality worklist is generated listing all the items that satisfy the query. This list of Scheduled Procedure Steps with selected demographic information is returned to the Acquisition Modality.', 'RAD-5', 'Modality Worklist Provided', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (7, '2008-04-17 12:10:05.493963', '0', 'An Acquisition Modality notifies the Performed Procedure Step Manager of the start of a new Procedure Step and the PPS Manager informs the Department System and Image Manager.', 'RAD-6', 'Modality Procedure Step In Progress', NULL, 5);
INSERT INTO tf_transaction (id, last_changed, last_modifier_id, description, keyword, name, reference, transaction_status_type_id) VALUES (9, '2008-04-17 12:10:05.495644', '0', 'An Acquisition Modality sends acquired or generated images to the Image Archive.', 'RAD-8', 'Modality Images Stored', NULL, 5);
SET escape_string_warning = off;
-- 10_tf_actor_aud_data.sql
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,1, '2008-04-17 12:09:39.127654', '0', 'ARR', 'Audit Record Repository', 'A system unit that receives and collects audit records from multiple systems.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,2, '2008-04-17 12:09:39.186361', '0', 'CHARGE_PRO', 'Charge Processor', 'Receives the posted charges and serves component of the financial system. Further definition of this actor is beyond current IHE scope.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,3, '2008-04-17 12:09:39.18789', '0', 'ERR', 'Enterprise Report Repository', 'A system that receives Structured Report Export Transactions from the Report Manager and stores them.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,4, '2008-04-17 12:09:39.188887', '0', 'XRA', 'External Report Repository Access', 'A system that performs retrieval of clinical reports containing information generated outside the Radiology department and presented as DICOM Structured Reporting Objects.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,5, '2008-04-17 12:09:39.189807', '0', 'PPM', 'Post-Processing Manager', 'A system that provides functions related to post-processing worklist management. This involves the ability to schedule post-processing worklist items (scheduled procedure steps), provide worklist items to post-processing worklist clients, and update the status of scheduled and performed procedure steps as received from post-processing worklist clients.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,6, '2008-04-17 12:09:39.190791', '0', 'PS', 'Print Server', 'A system that accepts and processes DICOM print requests as a DICOM Print SCP and performs image rendering on hardcopy media. The system must support pixel rendering according to the DICOM Grayscale Standard Display Function.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,7, '2008-04-17 12:09:39.191785', '0', 'RC', 'Report Creator', 'A system that generates and transmits draft (and optionally, final) reports, presenting them as DICOM Structured Reporting Objects.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,8, '2008-04-17 12:09:39.193617', '0', 'RM', 'Report Manager', 'A system that provides functions related to report management. This involves the ability to handle content and state changes to reports and to create new DICOM Structured Reporting Objects based on these changes. In addition, the Report Manager generates and transmits verified, unsolicited text results to the Enterprise Report Repository.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,9, '2008-04-17 12:09:39.194567', '0', 'RRP', 'Report Repository', 'A system that provides long-term storage of reports and their retrieval as DICOM Structured Reporting Objects.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,10, '2008-04-17 12:09:39.195462', '0', 'SN', 'Secure Node', 'A system unit that validates the identity of any user and of any other node, and determines whether or not access to the system for this user and information exchange with the other node is allowed. Maintains the correct time.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,11, '2008-04-17 12:09:39.19634', '0', 'TS', 'Time Server', 'A system unit that knows, maintains and distributes the correct time in the enterprise.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,12, '2008-04-17 12:09:39.197174', '0', 'ADT', 'ADT Patient Registration', 'A system responsible for adding and/or updating patient demographic and encounter information. In particular, it registers a new patient with the Order Placer and Department System.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,13, '2008-04-17 12:09:39.198068', '0', 'OF', 'Department System Scheduler/Order Filler', 'A department-based information system (for instance, Radiology or Laboratory) that provides functions related to the management of orders received from external systems or through the department system s user interface. Upon a defined workflow action, makes procedures available for charge posting. The action/event that actually causes charges to post is defined by the actor.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,14, '2008-04-17 12:09:39.199032', '0', 'PPSM', 'Performed Procedure Step Manager', 'A system that re-distributes the Modality Performed Procedure Step information from the Acquisition Modality or Image Creator to the Department System Scheduler/Order Filler and Image Manager.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,15, '2008-04-17 12:09:39.199924', '0', 'OP', 'Order Placer', 'A hospital or enterprise-wide system that generates orders for various departments and distributes those orders to the correct department.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,16, '2008-04-17 12:09:39.200796', '0', 'MOD', 'Acquisition Modality', 'A system that acquires and creates medical images, e.g. a Computed Tomography scanner or Nuclear Medicine camera. A modality may also create Grayscale Softcopy Presentation States for the consistent viewing of images and create Key Image Notes.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,17, '2008-04-17 12:09:39.201676', '0', 'IM', 'Image Manager/Archive', 'A system that provides functions related to safe data storage and image data handling. It supplies image availability information to the Department System Scheduler. It is always grouped with an Image Archive to provide long term storage of images, presentation states, Key Image Notes, and Evidence Documents.', true);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,19, '2008-04-17 12:09:39.203426', '0', 'CAA', 'Client Authentification Agent', 'Provide local management of user authentification.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,20, '2008-04-17 12:09:39.204301', '0', 'CONTXT_MGR', 'Context Manager', 'This actor serves as a broker for the communication between two or more context participant actors (either Patient Context Participant or User Context Participant). It supports the passing of the user and patient subjects', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,21, '2008-04-17 12:09:39.205218', '0', 'DISPLAY', 'Display', 'A system that offers requesting of specific information or documents for display the healthcare information returned', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,22, '2008-04-17 12:09:39.206089', '0', 'INFO_SRC', 'Information Source', 'A system that responds to requests for specific information or documents and returns ready for presentation information to be displays on the requesting actor.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,23, '2008-04-17 12:09:39.206908', '0', 'KER_AUTH_SVR', 'Kerberos Authentification Server', 'Provides central authentication of enterprise users.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,24, '2008-04-17 12:09:39.207797', '0', 'KER_SVR', 'Kerberized Server', 'Receives user authentication information for further use by the service that contains this actor', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,25, '2008-04-17 12:09:39.208714', '0', 'PAT_CONTXT_PARTICIPANT', 'Patient Context Participant', 'This actor participates in a shared context environment by both setting the patient context and responding to context changes as communicated by the Context Manager Actor. This actor shall respond to all patient context changes. This actor shall set the patient context, if the application containing this actor has patient selection capability. ', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,26, '2008-04-17 12:09:39.209621', '0', 'RRD', 'Report Reader', 'A part of a system that can access reports through network query/retrieve or reading interchange media and allow the user to view reports presented as DICOM Structured Report Objects.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,27, '2008-04-17 12:09:39.210476', '0', 'PAT_IDENTITY_X_REF_MGR', 'Patient Identity Cross-reference Manager', 'Serves a well-defined set of Patient Identification Domains. Based on information provided by in each Patient Identification Domain by a Patient Identification Source Actor, it manages the cross-referencing of patient identifiers across Patient Identification Domains.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,28, '2008-04-17 12:09:39.211601', '0', 'TIME_CLIENT', 'Time Client', 'Establishes time synchronization with one or more Time Servers using the NTP protocol and either the NTP or SNTP algorithms.  Maintains the local computer system clock synchronization with UTC based on synchronization with the Time Servers.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,29, '2008-04-17 12:09:39.212498', '0', 'USER_CONTXT_PARTICIPANT', 'User Context Participant', 'Receives notification of user context changes and follows them for the application that contains it.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,151, '2009-08-05 15:22:56.907', 'smoore', 'ACS', 'Access Control Service', 'Access Control Service', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,152, '2009-08-05 15:24:32.581', 'smoore', 'SERVICE_PROVIDER', 'Service Provider', 'Service Provider', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,31, '2008-04-17 12:09:39.214412', '0', 'ORT', 'Order Result Tracker', 'A hospital or enterprise-wide system that stores observations of various types (test results, images, clinical examinations reports, radiology reports, surgical act reports) obtained for the patients, registers all state changes in the results notified by Order Fillers. This actor doesnt store standalone observations, but ordered observations. The observations are always stored within the context of the order that generated them, with all the information related to that order.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,32, '2008-04-17 12:09:39.215207', '0', 'ID', 'Image Display', 'A part of a system that can access imaging evidence objects (images, Presentation States, Key Image Notes, Evidence Documents) through network query/retrieve or reading interchange media and allow the user to view these objects.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,33, '2008-04-17 12:09:39.21611', '0', 'PC', 'Print Composer', 'A system that generates DICOM print requests to the Print Server. Print requests include presentation state information in the form of Presentation Look-Up Tables (Presentation LUTs). It may also read the DICOM information contained on interchange media.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,34, '2008-04-17 12:09:39.216887', '0', 'PMC', 'Portable Media Creator', 'This actor assembles the content of the media and writes it to the physical medium.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,35, '2008-04-17 12:09:39.217876', '0', 'PMI', 'Portable Media Importer', 'This actor reads the DICOM information (DICOM FSR) contained on the media. This system provides the user the ability to select a set of DICOM instances and reconcile key patient and study attributes (when necessary) to facilitate inclusion of the imported data in the local information system(s).', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,36, '2008-04-17 12:09:39.218681', '0', 'PDC', 'Patient Demographics Consumer', 'This actor allows a user to associate information with a patient at the point of care.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,37, '2008-04-17 12:09:39.21943', '0', 'PDS', 'Patient Demographics Supplier', 'A repository of patient information that can be searched on demographic or visit-related fields.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,38, '2008-04-17 12:09:39.220407', '0', 'PWPC', 'Personnel White Pages Consumer', 'This actor has a use for information that can be found in the Personnel White Pages Directory.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,39, '2008-04-17 12:09:39.22139', '0', 'DNS', 'DNS Server', 'This actor has authoritative location information.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,40, '2008-04-17 12:09:39.222369', '0', 'PWPD', 'Personnel White Pages Directory', 'This actor has authoritative Personnel White Pages information on the human workforce members of the enterprise.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,41, '2008-04-17 12:09:39.223228', '0', 'DOC_SOURCE', 'Document Source', 'The Document Source Actor is the producer and publisher of documents. It is responsible for sending documents to a Document Repository Actor. It also supplies metadata to the Document Repository Actor for subsequent registration of the documents with the Document Registry Actor.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,42, '2008-04-17 12:09:39.224079', '0', 'DOC_CONSUMER', 'Document Consumer', 'The Document Consumer Actor queries a Document Registry Actor for documents meeting certain criteria, and retrieves selected documents from one or more Document Repository actors.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,43, '2008-04-17 12:09:39.224927', '0', 'DOC_REGISTRY', 'Document Registry', 'The Document Registry Actor maintains metadata about each registered document in a document entry. This includes a link to the Document in the Repository where it is stored. The Document Registry responds to queries from Document Consumer actors about documents meeting specific criteria. It also enforces some healthcare specific technical policies at the time of document registration.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,44, '2008-04-17 12:09:39.225791', '0', 'DOC_REPOSITORY', 'Document Repository', 'The Document Repository is responsible for both the persistent storage of these documents as well as for their registration with the appropriate Document Registry. It assigns a URI to documents for subsequent retrieval by a Document Consumer.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,45, '2008-04-17 12:09:39.226691', '0', 'PAT_IDENTITY_SRC', 'Patient Identity Source', 'Each Patient Identification Domain requires this Actor to assign patient identities and to notify a Patient Identity Cross-reference Manager Actor of all events related to patient identification (creation, update, merge, etc.). For example, the Registration (ADT) Actor defined by the radiology Scheduled Workflow Profile would likely be a Patient Identity Source.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,47, '2008-04-17 12:09:39.228497', '0', 'SNC', 'Secure Node Client', '', true);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,48, '2008-04-17 12:09:39.229334', '0', 'SNS', 'Secure Node Server', '', true);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,50, '2008-04-17 12:09:39.231043', '0', 'CSM', 'Code Set Master', 'A system which owns (is responsible for the maintenance of) one or several code sets. This system may also be an Order Filler or an Enterprise Common Repository. Code sets can be sent on a routine basis (e.g. every week) or every time the code set changes. A code set may contain battery, test and observation codes.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,51, '2008-04-17 12:09:39.231924', '0', 'CSC', 'Code Set Consumer', 'A system which receives code sets from Code Set Master(s) and updates its internal tables to reflect the code set as maintained by the Code Set Master. This system may  also be an Order Placer, an Order Result Tracker, an Automation Manager, or an Order Filler.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,52, '2008-04-17 12:09:39.232757', '0', 'POCRG', 'Point Of Care Result Generator', 'A system which receives code sets from Code Set Master(s) and updates its internal tables to reflect the code set as maintained by the Code Set Master. This system may 130 also be an Order Placer, an Order Result Tracker, an Automation Manager, or an Order Filler.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,53, '2008-04-17 12:09:39.23364', '0', 'POCDM', 'Point Of Care Data Manager', 'This actor used in LPOCT profile is an application managing a set of POCRG and centralizing their results. The POCDM is ready to react to any conversation from a POCRG. The POCDM receives point of care observations from POCRG actors. It controls these observations within their context, stores them and forwards them to the Order Filler.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,54, '2008-04-17 12:09:39.234491', '0', 'EMBED_REPOS', 'Integrated Document Source/Repository', 'The Integrated Document Source/Repository is an XDS combination of Document Source and Document Repository that does not expose the interface between the Source and Repository. That is, this Source only publishes documents to its own Repository. It does register documents with a Document Registry', true);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,55, '2008-04-17 12:09:39.235333', '0', 'NOTIFICATION_SENDER', 'Notification Sender', 'This actor sends notifications of availability for documents in an XDS registry, and receives acknowledgements of these notifications.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,56, '2008-04-17 12:09:39.236195', '0', 'NOTIFICATION_RECEIVER', 'Notification Receiver', 'This actor receives notifications of availability for documents in an XDS registry, and may optionally send acknowledgments of them.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,57, '2008-04-17 12:09:39.237298', '0', 'X_ID_PROVIDER', 'X-Identity Provider', 'This actor has authoritative identity information on the human user that is operating the X-Service User actor.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,60, '2008-04-17 12:09:39.240907', '0', 'PEC', 'Patient Encounter Consumer', 'A system that uses patient encounter information provided by the Patient Encounter Source about a patient. It must be grouped with the Patient Demographics Consumer.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,61, '2008-04-17 12:09:39.241849', '0', 'SMTP_AETHER', 'SMTP Aether', 'This actor is shown for completeness, but is really part of the SMTP Infrastructure of the Internet.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,157, '2009-08-21 22:16:06.352', 'fourquetl', 'HITSP_Lab_result_msg_receiver', 'Laboratory Result Message Receiver', 'An authorized entity that is receiving a laboratory result message', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,173, '2009-08-24 14:55:11.839', 'furst', 'IDCR', 'Implantable Device - Cardiac - Reporter', 'Sending actor in IDCO profile.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,62, '2008-04-17 12:09:39.242866', '0', 'IMG_DOC_SOURCE', 'Imaging Document Source', 'The Imaging Document Source actor is the producer and publisher of imaging documents. It is responsible for providing imaging documents and meta-data to the Document Repository actor, which subsequently registers the imaging documents with the Document Registry actor. It also supports the retrieval services for DICOM SOP Instances referenced in a published imaging manifest document.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,63, '2008-04-17 12:09:39.243666', '0', 'IMG_DOC_CONSUMER', 'Imaging Document Consumer', 'The Imaging Document Source actor is the producer and publisher of imaging documents. It is responsible for providing imaging documents and meta-data to the Document Repository actor, which subsequently registers the imaging documents with the Document Registry actor. It also supports the retrieval services for DICOM SOP Instances referenced in a published imaging manifest document.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,64, '2008-04-17 12:09:39.244501', '0', 'EXPORT_SELECTOR', 'Export Selector', 'A system that allows a user to select one or more instances, series or studies for export, for a specific purpose, with a specific disposition, optionally with the inclusion of additional information.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,65, '2008-04-17 12:09:39.245429', '0', 'EXPORT_MANAGER', 'Export Manager', 'A system that can de-identify and pseudonymize the attributes, and optionally the pixel data, of a selected list of instances, before exporting them.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,66, '2008-04-17 12:09:39.246245', '0', 'RECEIVER', 'Receiver', 'A system that can receive exported instances over the network, whose behavior is otherwise unspecified, unless grouped with other actors.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,67, '2008-04-17 12:09:39.247148', '0', 'PAT_IDENTITY_CONSUMER', 'Patient Identifier Cross-reference Consumer', 'This actor allows a system in a Patient Identification Domain to find out the identification of a patient in a different Patient Identification Domain by using the services of a Patient Identity Cross-Reference Manager Actor. ', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,68, '2008-04-17 12:09:39.248047', '0', 'AM', 'Automation Manager', 'A system or component that manages the automation in the laboratory or a part of it. Automation involves the integration or interfacing of automated or robotic transport systems, analytical instruments, and pre- or post-analytical process equipment such as automated centrifuges and aliquoters, decappers, recappers, sorters, and specimen storage and retrieval systems. This actor receives work orders from the Order Filler. It manages the processing of the ordered tests on the appropriate devices, and sends technically validated results back to the Order Filler. This actor must be considered even if it manages a small part of the analytical process; e.g. if it manages one single analytical instrument. Multiple Automation Managers can be related to one Order Filler. The Automation Manager can match unexpected results produced by an analyzer with the appropriate incoming Work Order, or create a new Work Order to fit the unsolicited observations and send them to the OF.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,69, '2008-04-17 12:09:39.248965', '0', 'ANALYZER', 'Analyzer', 'An actor which is an automated device which fulfills clinical tests on biologic specimen. An Analyzer performs analyzing for a specimen according to AWOS, and return the result to the AM.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,70, '2008-04-17 12:09:39.250008', '0', 'PRE_POST_PROCESSOR', 'Pre/Post-processor', 'An actor which provides some pre- and post- processes to the specimen. This actor is categorized to two sub categories, one is pre-processor and the other one is post-processor. A Pre/Post-processor processes a specimen according to SWOS, and return the result to the AM.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,71, '2008-04-17 12:09:39.250837', '0', 'IMPORTER', 'Importer', 'A system that imports evidence documents such as images, presentation states, Key Image Notes or Evidence Documents from hardcopy or digital media.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,75, '2008-04-17 12:09:39.254261', '0', 'HL7_MSG_ROUTER', 'HL7 Message Router', ' A system that receives HL7 messages, routes them to one or more configured actors, and handles transport level acknowledgements.  The HL7 Message Router may also provide modification of the messages in accordance with specific profiles.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,76, '2008-04-17 12:09:39.255104', '0', 'DOC_RECIPIENT', 'Document Recipient', ' A system that receives a set of documents sent by another actor. Typically this document set will be made available to the intended recipient who will choose to either view it or integrate it into the Electronic Healthcare Record (EHR)', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,77, '2008-04-17 12:09:39.255947', '0', 'DEV_OBS_REPORTER', 'Device Observation Reporter', 'The Device Observation Reporter (DOR) actor receives data from PCDs, including those based on proprietary formats, and maps the received data to transactions providing consistent syntax and semantics.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,78, '2008-04-17 12:09:39.2569', '0', 'DEV_OBS_FILTER', 'Device Observation Filter', 'The Device Observation Filter (DOF) actor is responsible for providing PCD data filtering services based on publish/subscribe predicates negotiated with client applications implementing the Device Observation Consumer.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,79, '2008-04-17 12:09:39.257835', '0', 'DEV_OBS_CONSUMER', 'Device Observation Consumer', 'The actor responsible for receiving PCD data from the Device Observation Reporter, the Device Observation Filter, or both.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,80, '2008-04-17 12:09:39.258655', '0', 'CONTENT_CREATOR', 'Content Creator', 'The Content Creator creates content in a content integration profile', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,81, '2008-04-17 12:09:39.259485', '0', 'CONTENT_CONSUMER', 'Content Consumer', 'The Content Consumer consumes content in a content integration profile', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,82, '2008-04-17 12:09:39.26033', '0', 'FORM_FILLER', 'Form Filler', 'The actor responsible for retrieving a form from a Form Manager, and for submitting form instance data to a Form Receiver.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,83, '2008-04-17 12:09:39.261297', '0', 'FORM_ARCHIVER', 'Form Archiver', 'The actor responsible for receiving form instance data for archival purposes.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,84, '2008-04-17 12:09:39.262141', '0', 'FORM_MANAGER', 'Form Manager', 'The actor that supplies a form based upon a request that supplies a unique form identification.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,85, '2008-04-17 12:09:39.263144', '0', 'FORM_RECEIVER', 'Form Receiver', 'The actor that receives form instance data.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,86, '2008-04-17 12:09:39.263995', '0', 'SA', 'Secure Application', 'The difference between the Secure Node and the Secure Application is the extent to which the underlying operating system and other environment are secured.  A Secure Node includes all aspects of user authentication, file system protections, and operating environment security.  The Secure Application is a product that does not include the operating environment.  The Secure Application provides security features only for the application features.  See section 9.7 for the relationships among a Secure Node, Secure Application, and other actors.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,91, '2008-04-17 12:09:39.267661', '0', 'CLIN_DATA_CONSUMER', 'Clinical Data Consumer', 'A clinical data consumer makes use of clinical patient data.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,89, '2009-07-03 10:03:15.078', 'admin', 'INIT_GATEWAY', 'Initiating Gateway', '', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,87, '2009-07-03 09:59:51.791', 'admin', 'X-SERVICE-USER', 'X-Service User', 'X-Service User', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,90, '2009-07-03 10:05:36.066', 'admin', 'RESP_GATEWAY', 'Responding Gateway', '', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,99, '2008-04-17 12:09:39.274393', '0', '--', 'None', 'Dummy actor', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,100, '2008-04-17 12:09:39.275233', '0', 'LIP', 'Label Information Provider', 'An actor that provides the actor Label broker with label information', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,101, '2008-04-17 12:09:39.276108', '0', 'LB', 'Label Broker', 'The Label Broker receives label information, and delivers these labels in appropriate operations, and may notify the status of this process. ', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,102, '2008-04-17 12:09:39.276959', '0', 'PES', 'Patient Encounter Supplier', 'A system responsible for adding, updating and maintaining encounter information about a patient. It supplies new and updated information to the Patient Encounter Consumer. It must be grouped with either the Patient Demographics Source or the Patient Demographics Consumer. ', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,103, '2008-08-04 10:34:00', '0', 'CLIN_DATA_SOURCE', 'Clinical Data Source', 'A Clinical Data Sources maintains patient information about vital  signs, problem and allergies, results from diagnostic tests (e.g., Lab, Imaging, or other test results), medications, immunizations or historical or planned visits and procedures.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,104, '2008-08-04 15:00:00', '0', 'DOSE_INFO_CONSUMER', 'Dose Information Consumer', 'Responsible for supplemental handling of irradiation events, generally on an individual basis, e.g. display, analysis, or further processing.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,105, '2008-08-04 15:00:00', '0', 'DOSE_INFO_REPORTER', 'Dose Information Reporter', 'Responsible for the aggregation, analysis, reporting and business logic related to irradiation events, which may include meeting facility obligations to de-identify and submit data to various dose registers.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,106, '2008-08-04 15:00:00', '0', 'DOSE_REGISTER', 'Dose Register', 'Collates information about irradiation events from a number of facilities, generally to perform analysis.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,107, '2008-08-05 15:35:00', '0', 'VALUE_SET_REPOSITORY', 'Value Set Repository', 'Provides Resolved Value Sets ', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,108, '2008-08-05 15:35:00', '0', 'VALUE_SET_CONSUMER', 'Value Set Consumer', 'Retrieves Resolved Value Sets based on its OID and possibly its version if the latter is available.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,111, '2008-10-25 12:00:00', '0', 'GUIDELINE_MGR', 'Guideline Manager', 'The guideline manager actor is responsible for managing the guidelines used to create care plans, and for communicating those guidelines to other systems.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,112, '2008-10-25 12:00:00', '0', 'CARE_MGR', 'Care Manager', 'The care manager actor is responsible for supporting the management of the care of patients with respect to a specific health condition. It gathers information about the care provided and current health status of the patient. A Care Manager actor may be designed for management of a single condition, such as management of Diabetes, or may be a general purpose system supporting management of multiple conditions.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,113, '2008-10-25 12:00:00', '0', 'ALRM_RPT', 'Alarm Reporter', 'The Alarm Reporter (AR) actor sources the alarm to Alarm Manager (AM).', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,114, '2008-10-25 12:00:00', '0', 'ALRM_MGR', 'Alarm Manager', 'The Alarm Manager (AM) actor receives the alarm from the Alarm Reporter (AR), potentially analyzes the alarm, and dispatches the alarm to the Alarm Communicator (AC).', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,115, '2008-10-25 12:00:00', '0', 'ALRM_COMMUNICATOR', 'Alarm Communicator', 'The Alarm Communicator  (AC) actor receives the alarm from the Alarm Manager (AM) and sends the alarm to the client application in the endpoint device.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,116, '2008-10-25 12:00:00', '0', 'ALRM_ARCHIVER', 'Alarm Archiver', 'The Alarm Archiver (AA) actor sends alarm subscription requests to the AM actor and receives report alarm responses from the AM actor.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,117, '2008-10-25 12:00:00', '0', 'IOP', 'Infusion Order Programmer', 'The Infusion Order Programmer (IOP) actor sends the information comprising an order to the Infusion Order Consumer  (IOC).  The mechanism by which the IOP obtains the order information is outside the scope of this profile.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,118, '2008-10-25 12:00:00', '0', 'IOC', 'Infusion Order Consumer', 'The Infusion Order Consumer  (IOC) actor receives the order information from the IOP actor and in turn programs the pump.  The mechanism by which the IOC programs the pump with the received information is outside the scope of this profile.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,88, '2009-07-03 09:59:17.447', 'admin', 'X-SERVICE-PROVIDER', 'X-Service Provider', 'X-Service Provider', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,98, '2009-07-03 10:02:49.691', 'admin', 'HITSP-ACTOR', 'Generic HITSP Actor', '', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,110, '2009-07-03 10:03:38.847', 'admin', 'REFERRAL_DISPATCHER', 'Referral Dispatcher', '', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,109, '2009-07-03 10:04:02.438', 'admin', 'REFERRAL_REQUESTOR', 'Referral Requestor', '', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,156, '2009-08-21 22:17:13.411', 'fourquetl', 'HITSP_Lab_result_msg_sender', 'HITSP Laboratory Result Message Sender', 'The holder of a laboratory result who is communicating a laboratory result message to another actor', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,120, '2009-07-02 14:57:24.907', 'admin', 'PMS', 'Portable Media Sender', '', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,121, '2009-07-02 15:05:02.937', 'admin', 'DM_NOTIF_BROKER', 'Document Metadata Notification Broker', '', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,18, '2008-04-17 12:09:39.202551', '0', 'EC', 'Evidence Creator', 'A system that creates additional evidence objects such as images, presentation states, Key Image Notes, and/or Evidence Documents and transmits them to an Image Archive. It also makes requests for storage commitment to the Image Manager for the data previously transmitted. It may also retrieve worklist entries for post-processing steps from the Post-Processing Manager and provide notification of completion of the step, allowing the enterprise to track the status of post-processing work.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,122, '2009-07-02 15:05:55.662', 'admin', 'DM_PUBLISHER', 'Document Metadata Publisher', '', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,123, '2009-07-02 15:07:08.214', 'admin', 'DM_SUBSCRIBER', 'Document Metadata Subscriber ', '', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,124, '2009-07-02 15:08:27.462', 'admin', 'DM_NOTIF_RECIPIENT', 'Document Metadata Notification Recipient', '', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,119, '2009-07-03 10:02:03.379', 'admin', 'LEGACY_MOD', 'Legacy Acquisition Modality Importer', 'Legacy Acquisition Modality Importer', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,126, '2009-07-08 14:07:53.538', 'admin', 'CONTOURER', 'Contourer', 'A system that consumes CT and creates RT Structure Set. If the Contourer consumes multiple series CT or has an internal requirement for resampling, it also will generate a single series CT to which the RT Structure Set maps.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,127, '2009-07-08 14:12:02.889', 'admin', 'GEOMETRIC_PLANNER', 'Geometric Planner', 'A system that consumes (single series) CT and RT Structure Set and creates a Geometric Plan', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,128, '2009-07-08 14:12:40.896', 'admin', 'DOSIMETRIC_PLANNER', 'Dosimetric Planner', 'A system that consumes (single series) CT, an RT Structure Set, a Geometric Plan, and creates a Dosimetric Plan and an RT Dose.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,129, '2009-07-08 14:13:33.507', 'admin', 'DOSE_DISPLAYER', 'Dose Displayer', 'A system that consumes a Dosimetric Plan, CT, Structure Set and an RT Dose and displays the dose', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,130, '2009-07-08 14:17:23.236', 'admin', 'ARCHIVE', 'Archive (including RT)', 'A system that stores the RT SOP Classes in addition to the CT images and is capable of transmitting them.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,131, '2009-07-08 14:38:02.216', 'admin', 'REGISTRATOR', 'Registrator', 'A system that consumes multi-modality images and generates 1 or more Spatial Registration objects.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,132, '2009-07-08 14:39:14.751', 'admin', 'REG_DISPLAY', 'Registered Display', 'A system that consumes multi-modality images, RT Structure Set objects, and Spatial Registration objects and allows the user to display the registered information', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,133, '2009-07-08 14:40:04.34', 'admin', 'REG_DOSE_DISPLAY', 'Registered Dose Display', 'A system that consumes multi-modality images, RT Structure Set objects, RT Dose objects and Spatial Registration objects and allows the user to display the registered information.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,134, '2009-07-08 14:40:31.728', 'admin', 'REG_CONTOURER', 'Registered Contourer', 'A system that consumes multi-modality images, RT Structure Set objects, and Spatial Registration objects and allows the user to contour images in a registered display.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,135, '2009-07-08 14:48:41.188', 'admin', 'TMS', 'Treatment Management System', '', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,136, '2009-07-08 14:49:26.411', 'admin', 'TDD', 'Treatment Delivery Device', 'A system that delivers therapeutic radiation to a correctly positioned patient.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,137, '2009-07-08 14:51:42.362', 'admin', 'PD_SYSTEM', 'Positioning and Delivery System', 'A system that determines and corrects patient position then delivers therapeutic radiation.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,139, '2009-07-14 11:41:14.06', 'admin', 'RPT_SENDER', 'Report Sender', 'Report Sender', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,140, '2009-07-14 11:41:31.737', 'admin', 'RPT_RECEIVER', 'Report Receiver', 'Report Receiver', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,141, '2009-07-14 14:49:43.421', 'admin', 'PROT_EXECUTOR', 'Protocol Executor', 'Protocol Executor', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,142, '2009-07-14 14:52:42.475', 'admin', 'PROT_DEF_MGR', 'Protocol Definition Manager', 'Protocol Definition Manager', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,143, '2009-07-14 14:53:11.099', 'admin', 'PROT_STATE_MGR', 'Protocol State Manager', 'Protocol State Manager', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,144, '2009-07-24 15:33:18.194', 'admin', 'REQUESTER', 'Requester', 'Requester', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,145, '2009-07-24 15:33:35.522', 'admin', 'SUBCONTRACTOR', 'Subcontractor', 'Subcontractor', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,155, '2009-08-10 16:23:35.665', 'admin', 'NEW_ACTOR', 'New Actor 1', 'description', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,147, '2009-08-02 12:51:05.371', 'admin', 'ALERT_MSG_RECEIVER', 'Alert Message Receiver', 'Alert Message Receiver', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,169, '2009-08-22 00:21:28.486', 'fourquetl', 'HITSP_Med_Ord_Flr', 'HITSP Medication Order Filler', 'The Medication Order Filler responds to the requests for medication orders/prescriptions. This includes the ability to respond to: new orders, refill orders, change orders and cancel orders. These responses are sent to the Medication Order Prescriber.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,149, '2009-08-02 22:35:23.614', 'admin', 'ALERT_MSG_TRANSMITTER', 'Alert Message Transmitter', 'Alert Message Transmitter', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,138, '2009-08-14 13:58:45.666', 'smoore', 'DECISION_SUPPORT', 'Decision Support Service', 'Decision Support Service', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,146, '2009-08-19 22:28:02.116', 'fourquetl', 'KNOWLEDGE_REQUESTOR', 'Knowledge Requestor', 'KnA system that formulates and sends a contextual request for ancillary information about a medical concept. Takes the parameters and sends to the resource available', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,148, '2009-08-19 22:29:17.204', 'fourquetl', 'KNOWLEDGE_RESOURCE', 'Knowledge Resource', 'The system that holds the information requested and responds to the request from the Knowledge Requestor', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,174, '2009-08-24 14:54:33.856', 'furst', 'IDCC', 'Implantable Device - Cardiac - Consumer', 'Receiving actor in IDCO profile.', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,158, '2009-08-21 22:32:54.59', 'fourquetl', 'HITSP_Web_Application', 'Web Application', 'The Web Application the healthcare professional uses to view a laboratory report Web', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,159, '2009-08-21 22:38:06.56', 'fourquetl', 'HITSP_Pseudoymisation_SVC', 'HITSP Pseudonymization Services', 'Module or service that can be invoked by Patient Identifier Cross-Reference (PIX) Manager (see next section) to return pseudo-identifier upon request', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,160, '2009-08-21 22:59:10.259', 'fourquetl', 'HITSP_Eligibility_info_receiver', 'Eligibility Information Receiver', 'The system that initiates an inquiry to the Eligibility Information Source about an individual’s insurance eligibility, coverage and benefits', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,161, '2009-08-21 23:00:13.989', 'fourquetl', 'HITSP_Eligibility_info_Source', 'Eligibility Information Source', 'The system which holds and maintains the information regarding the individual’s insurance eligibility, coverage and benefits, and responds to the queries initiated by the Eligibility Information Receiver', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,162, '2009-08-21 23:05:21.379', 'fourquetl', 'HITSP_Med_Status_Receiver', 'HITSP Medication Status Receiver', 'The Medication Status Receiver receives a dispensing status (RXFILL message) from a Medication Status Dispenser about a previously performed medication order / prescription', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,163, '2009-08-21 23:06:20.383', 'fourquetl', 'HITSP_Med_Status_Dispenser', 'HITSP Medication Status Dispenser', 'The Medication Status Dispenser provides a dispensing status (RXFILL message) to a Medication Status Receiver about a preciously performed medication order / prescription', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,164, '2009-08-21 23:27:17.382', 'fourquetl', 'HITSP_Info_Rcvr_Health_Plan_Auth', 'HITSP Information Receiver for Health Plan Authorization', 'The system that initiates a request to the Information Source for Health Plan Authorization about an individuals health insurance requirements to obtain an authorization approval for purposes of benefit coverage determination in order to refer a patient for healthcare services', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,165, '2009-08-21 23:28:49.527', 'fourquetl', 'HITSP_Info_Src_Health_Plan_Auth', 'HITSP Information Source for Health Plan Authorization', 'The system which holds and maintains the information regarding the individual’s health insurance requirements related to an authorization for benefit coverage', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,166, '2009-08-21 23:40:02.292', 'fourquetl', 'HITSP_Admin_Transport_Client', 'HITSP Administrative Transport Client', 'A provider sending a request to a health plan has a client role', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,167, '2009-08-21 23:41:01.854', 'fourquetl', 'HITSP_Admin_Transport_Svr', 'HITSP Administrative Transport Server', 'A health plan responding to a request from a provider has a server role', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,170, '2009-08-22 00:29:57.131', 'fourquetl', 'HITSP_Med_Form_Bene_Rcvr', 'HITSP Medication Formulary and Benefits Retriever', 'The entity that is asking about an individual’s formulary and benefits information. It initiates queries to the Medication Formulary and Benefits Source', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,171, '2009-08-22 00:31:49.02', 'fourquetl', 'HITSP_Med_Form_Bene_Src', 'HITSP Medication Formulary and Benefits Source', 'The entity that maintains individual’s formulary and benefits information. It responds to queries from the Medication Formulary and Benefits Retriever', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,172, '2009-08-22 01:53:28.733', 'fourquetl', 'HITSP_Service_User', 'HITSP Service User', 'The entity represents any individual entity (such as an EHR/PHR system) that needs to make a service request of a Service Provider. The Entity may also be known as a principal and/or entity, which represents an application, a machine, or any other type of entity that may act as a requester in a transaction. A principal is typically represented in a transaction with a digital identity and the principal may have multiple valid digital identities to use with different transactions. Any Service User may also be a Service Provider', false);
INSERT INTO tf_actor_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, combined) VALUES (1,0,168, '2009-09-14 14:53:59.46', 'smoore', 'HITSP_Med_Order_Pscr', 'HITSP Medication Order Prescriber', 'The Medication Order Prescriber initiates requests for medication orders/prescriptions. This includes the ability to: create new orders, refill orders, change orders and cancel orders. These requests are sent to the Medication Order Filler.', false);
-- 10_tf_domain_aud_data.sql
INSERT INTO tf_domain_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description) VALUES (1,0,1, NULL, NULL, 'RAD', 'Radiology', 'IHE Radiology addresses information sharing, workflow and patient care in radiology, including mammography and nuclear medicine.');
INSERT INTO tf_domain_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description) VALUES (1,0,2, NULL, NULL, 'ITI', 'IT-Infrastructure', 'The IT Infrastructure Domain supplies infrastructure for sharing healthcare information. An infrastructure interoperability component represents a common IT function that is used as a building block for a variety of use cases... a necessary ingredient, but rarely visible to the end user!! These components may be embedded in an application, but are often deployed as a shared resource within a RHIO or Health Information Exchange.');
INSERT INTO tf_domain_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description) VALUES (1,0,4, NULL, NULL, 'CARD', 'Cardiology', 'IHE Cardiology addresses information sharing, workflow and patient care in cardiology, including electrophysiology and nuclear medicine.');
INSERT INTO tf_domain_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description) VALUES (1,0,5, NULL, NULL, 'PCC', 'Patient Care Coordination', 'IHE Patient Care Coordination (PCC) domain was established in July 2005 to deal with integration issues that cross providers, patient problems or time. It deals with general clinical care aspects such as document exchange, order processing, and coordination with other specialty domains. PCC also addresses workflows that are common to multiple specialty areas and the integration needs of specialty areas that do not have a separate domain within IHE.');
INSERT INTO tf_domain_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description) VALUES (1,0,6, NULL, NULL, 'RO', 'Radiation Oncology', 'IHE Radiation Oncology addresses information sharing, workflow, and patient care in radiation oncology.');
INSERT INTO tf_domain_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description) VALUES (1,0,7, NULL, NULL, 'PCD', 'Patient Care Devices', 'The Patient Care Device Domain is concerned with use cases in which at least one actor is a regulated patient-centric point-of-care medical device that communicates with at least one other actor such as a medical device or information system.');
INSERT INTO tf_domain_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description) VALUES (1,0,8, NULL, NULL, 'EYE', 'Eye Care', 'IHE Eye Care is sponsored by the American Academy of Ophthalmology (AAO) and manages the Eye Care Profiles and the Eye Care Technical Frameworks.');
INSERT INTO tf_domain_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description) VALUES (1,0,9, NULL, NULL, 'QRPH', 'Quality Research Public Health', 'IHE Quality, Research and Public Health Domain (QRPH) addresses the infrastructure necessary to share information relevant to quality improvement in electronic patient care and health care records.');
INSERT INTO tf_domain_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description) VALUES (1,0,10, NULL, NULL, 'PATH', 'Pathology', 'IHE Anatomic Pathology addresses information sharing, workflow and patient care in Pathology, including anatomical pathology.');
INSERT INTO tf_domain_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description) VALUES (1,0,3, '2009-07-24 16:03:39.684', 'admin', 'LAB', 'Laboratory', 'IHE Laboratory addresses information sharing and workflow related to in vitro diagnostic testing in clinical laboratories as well as on the point of care.');
-- 10_tf_integration_profile_data.sql
SET escape_string_warning = off;
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (138, '2009-08-21 22:49:29.217', 'fourquetl', '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.', 'T29', 'HITSP Notification of Document Availability Transaction', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (139, '2009-08-21 22:52:52.831', 'fourquetl', '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.', 'T31', 'HITSP Reliable Document Exchange', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (145, '2009-08-21 22:56:57.896', 'fourquetl', '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.', 'T33', 'Transfer of Documents on Media', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (142, '2009-08-21 23:10:32.086', 'fourquetl', '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.', 'T64', 'HITSP Personnel White Pages', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (140, '2009-08-21 23:22:38.213', 'fourquetl', '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.', 'T67', 'HITSP Document-based Referral - DRR', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (204, '2009-08-21 23:46:42.725', 'fourquetl', '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', 'T73', 'HITSP Aggregate Device Information Communication', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (148, '2009-08-22 01:45:56.702', 'fourquetl', '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.', 'TP50', 'HITSP Retrieve Form for Data Capture', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (151, '2009-08-22 01:47:22.445', 'fourquetl', '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.', 'TP49', 'HITSP Sharing Radiology Results Transaction Package', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (152, '2009-08-22 01:56:10.89', 'fourquetl', '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.', 'TP20', 'HITSP Access Control', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (206, '2009-08-22 02:13:13.106', 'fourquetl', 'US HITSP: T147 Multi-Patient Queries', 'T147', ' HITSP Multi-Patient Queries', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (208, '2009-08-22 02:19:12.024', 'fourquetl', 'US HITSP: T146  Document Metadata Subscription', 'T146', 'HITSP Document Metadata Subscription', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (187, '2009-08-20 17:16:12.208', 'fourquetc', '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.', 'T18', 'HITSP View Laboratory Results from a Web Application Transaction', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (188, '2009-08-20 17:16:47.297', 'fourquetc', '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.', 'T24', 'HITSP Pseudonymize Transaction', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (103, '2009-08-11 17:31:20.947', 'smoore', 'Composite Triage and Nursing Note', 'CTNN', 'Composite Triage and Nursing Note', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (5, '2008-04-17 12:10:28.752691', '0', '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', 'XD-Star', 'XDM, XDR, XDS', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (104, '2009-08-11 17:31:43.489', 'smoore', 'ED Physician Note', 'EDPN', 'ED Physician Note', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (189, '2009-08-20 17:17:33.999', 'fourquetc', '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.', 'T40', 'HITSP Patient Generic Health Plan Eligibility Verification Transaction', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (190, '2009-08-20 17:18:22.35', 'fourquetc', '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.', 'T42', 'HITSP Medication Dispensing Status Transaction', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (191, '2009-08-20 17:19:00.91', 'fourquetc', '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.', 'T68', 'Patient Health Plan Authorization Request and Response Transaction', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (192, '2009-08-20 17:19:36.283', 'fourquetc', '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', 'T79', 'Pharmacy to Health Plan Authorization Request and Response Transaction', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (193, '2009-08-20 17:20:14.729', 'fourquetc', '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', 'T85', 'Administrative Transport to Health Plan', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (198, '2009-08-21 12:23:23.173', 'fourquetl', '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', 'C151', 'Clinical Research Document ', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (200, '2009-08-21 12:28:51.122', 'fourquetl', 'US HITSP: C150 Mother and Child Health', 'C150', 'HITSP Mother and Child Health', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (201, '2009-08-21 12:32:18.125', 'fourquetl', 'US HITSP: TP149 Retrieve Protocol for Execution', 'TP149', 'HITSP Retrieve Protocol for Execution', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (203, '2009-08-21 12:39:08.023', 'fourquetl', 'US HITSP: C153 HITSP Anonymize Clinical Research Data', 'C153', 'HITSP Anonymize Clinical Research Data', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (202, '2009-08-21 12:41:22.825', 'fourquetl', 'US HITSP: C152  Clinical Research Data Acquisition', 'C152', 'HITSP Clinical Research Data Acquisition', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (124, '2009-08-21 21:58:13.543', 'fourquetl', '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.', 'T17', 'HITSP Secured Communication Channel Transaction', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (150, '2009-08-21 22:07:07.259', 'fourquetl', '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.', 'T23', 'HITSP Patient Demographics Query Transaction', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (173, '2009-08-20 16:16:43.944', 'fourquetc', '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.', 'C75', 'Healthcare Associated Infection (HAI) Report Component', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (174, '2009-08-20 16:18:20.069', 'fourquetc', '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.', 'C80', 'Clinical Document and Message Terminology Component', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (175, '2009-08-20 16:19:24.578', 'fourquetc', '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.', 'C83', 'CDA Content Modules Component', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (176, '2009-08-20 16:20:56.757', 'fourquetc', '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.', 'C84', 'Consult and History & Physical Note Component', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (177, '2009-08-20 16:24:27.038', 'fourquetc', '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.', 'C87', 'Anonymize Public Health Case Reporting Data Component', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (178, '2009-08-20 16:25:32.251', 'fourquetc', '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.', 'C88', 'Anonymize Immunizations and Response Management Data Component', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (179, '2009-08-20 16:26:37.565', 'fourquetc', '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.', 'C90', 'Clinical Genomic Decision Support Component', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (180, '2009-08-20 16:27:12.05', 'fourquetc', '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.', 'C105', 'Patient Level Quality Data Document Using HL7 Quality Reporting Document Architecture (QRDA)', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (181, '2009-08-20 16:28:49.909', 'fourquetc', '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', 'C106', 'Measurement Criteria Document', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (182, '2009-08-20 17:10:16.121', 'fourquetc', '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).', 'TP14', 'HITSP Send Laboratory Result Message to Ordering Clinician and Providers of Care Transaction Package', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (183, '2009-08-20 17:11:26.093', 'fourquetc', '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.', 'TP43', 'HITSP Medication Orders Transaction Package', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (184, '2009-08-20 17:12:03.806', 'fourquetc', '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.', 'TP46', 'HITSP Medication Formulary and Benefits Information Transaction Package', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (185, '2009-08-20 17:12:57.779', 'fourquetc', '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', 'TP89', 'Sharing Imaging Results Transaction Package', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (186, '2009-08-20 17:14:39.516', 'fourquetc', '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) ', 'T14', 'HITSP Send Laboratory Result Message Transaction', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (113, '2009-07-14 11:05:41.459', 'admin', 'Drug Safety Content', 'DSC', 'Drug Safety Content', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (114, '2009-07-14 11:15:46.289', 'admin', 'Retrieve Protocol for Execution', 'RPE', 'Retrieve Protocol for Execution', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (115, '2009-07-14 11:23:05.618', 'admin', 'Anatomic Pathology Reporting to Public Health', 'ARPH', 'Anatomic Pathology Reporting to Public Health', 3);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (116, '2009-07-24 15:43:25.821', 'admin', 'Inter-Laboratory Workflow', 'ILW', 'Inter-Laboratory Workflow', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (67, '2009-07-28 14:30:12.554', 'admin', '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.', 'EYECARE', 'Eye Care Workflow', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (101, '2009-08-11 17:30:22.695', 'smoore', 'Triage Note', 'TN', 'Triage Note', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (102, '2009-08-11 17:30:53.294', 'smoore', 'Nursing Note', 'NN', 'Nursing Note', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (136, '2009-08-19 06:38:28.161', 'fourquetl', '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.', 'C48', 'HITSP Encounter Document Using IHE Medical Summary (XDS-MS)', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (36, '2009-08-19 07:28:59.603', 'fourquetl', '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.', 'TP13', 'Manage Sharing of Documents Transaction Package with Doc Integrity Check', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (194, '2009-08-21 06:24:54.126', 'fourquetl', 'birthing Summary/delivery record', 'C144', 'Labor and Delivery Report', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (195, '2009-08-21 06:28:15.914', 'fourquetl', 'HITSP Vaccine Forecast Component', 'C145', 'Vaccine Forecast', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (196, '2009-08-21 06:32:22.124', 'fourquetl', 'HITSP EMS Transfer of Care', 'C148 ', 'HITSP EMS Transfer of Care', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (105, '2009-08-21 06:33:45.634', 'fourquetl', 'US HITSP: EMS Transfer of care', 'ETC', 'EMS Transfer of Care', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (146, '2009-08-19 19:51:46.903', 'fourquetl', '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.', 'TP13a', 'Manage Sharing of Documents (XDS.A Option)', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (165, '2009-08-20 16:00:53.245', 'fourquetc', '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.', 'C34', 'HITSP Patient Level Quality Data Message Component', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (166, '2009-08-20 16:02:54.347', 'fourquetc', 'The Lab Result Terminology Component defines the vocabulary for either message-based or document-based laboratory results reporting.', 'C35', 'HITSP EHR Lab Result Terminology Component', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (167, '2009-08-20 16:05:01.155', 'fourquetc', '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.', 'C39', 'HITSP Encounter Message Component', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (168, '2009-08-20 16:07:27.634', 'fourquetc', '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.', 'C41', 'HITSP Radiology Result Message Component', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (169, '2009-08-20 16:09:27.088', 'fourquetc', 'The Secure Web Connection Component provides the capability to access documents through a secure web browser.', 'C44', 'HITSP Secure Web Connection Component', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (170, '2009-08-20 16:11:17.771', 'fourquetc', '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.', 'C47', 'HITSP Resource Utilization Message Component', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (171, '2009-08-20 16:13:03.064', 'fourquetc', '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.', 'C70', 'Immunization Query and Response', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (172, '2009-08-20 16:15:09.608', 'fourquetc', '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.', 'C74', 'Remote Monitoring Observation Document Component', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (76, '2009-07-03 09:08:17.432', 'admin', '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.', 'MAWF', 'Mammography Acquisition Workflow', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (74, '2009-07-03 09:15:46.428', 'admin', '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.', 'TCE', 'Teaching File and Clinical Trial Export', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (94, '2009-07-08 14:32:32.52', 'admin', 'involves the flow of DICOM images and treatment planning data, from CT scan through dose display, for 3D conformal, external beam radiation therapy', 'RTO', 'Radiation Therapy Objects', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (95, '2009-07-08 14:35:36.30', 'admin', '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.', 'REG', 'Image Registration', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, 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, description, keyword, name, integration_profile_status_type_id) VALUES (3, '2009-07-08 17:00:03.818', 'admin', '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.', 'NAV', 'Notification of Document Availability', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, 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, description, keyword, name, integration_profile_status_type_id) VALUES (135, '2009-08-19 06:37:33.941', 'fourquetl', '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', 'C72', 'HITSP Vaccination Message', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (161, '2009-08-19 22:36:33.463', 'fourquetl', '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.', 'C25', 'HITSP Anonymize Component', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (53, '2009-07-08 17:21:28.167', 'admin', '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.', 'CATH', 'Cardiac Catheterization Workflow', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (14, '2009-07-08 17:28:26.981', 'admin', '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.', 'ECG', 'Retrieve ECG for Display', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (98, '2009-07-13 22:20:08.772', 'admin', 'Antepartum History and Physical', 'APHP', 'Antepartum History and Physical', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (99, '2009-07-13 22:20:42.031', 'admin', 'Antepartum Education', 'APE', 'Antepartum Education', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (100, '2009-07-13 22:21:18.966', 'admin', 'Antepartum Laboratory', 'APL', 'Antepartum Laboratory', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (97, '2009-07-13 23:00:30.97', 'admin', 'Antepartum Summary', 'APS', 'Antepartum Summary', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (107, '2009-07-13 23:35:01.747', 'admin', 'Labor and Delivery Summary', 'LDS', 'Labor and Delivery Summary', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (108, '2009-07-13 23:35:28.607', 'admin', 'Maternal Discharge Summary', 'MDS', 'Maternal Discharge Summary', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (109, '2009-07-13 23:43:22.369', 'admin', 'Patient Plan of Care', 'PPOC', 'Patient Plan of Care', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (110, '2009-07-14 09:46:47.719', 'admin', 'Request for Clinical Guidance', 'RCG', 'Request for Clinical Guidance', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (111, '2009-07-14 09:47:27.337', 'admin', 'Immunization Care Plan', 'ICP', 'Immunization Care Plan', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (61, '2009-07-14 10:06:39.459', 'admin', '<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.', 'DWF', 'Departmental Workflow', 1);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (112, '2009-07-14 10:55:09.345', 'admin', 'Mother and Child Health', 'MCH', 'Mother and Child Health', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (79, '2009-07-03 09:11:58.838', 'admin', '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.', 'SVS', 'Sharing Value Sets', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (85, '2009-07-03 09:14:50.722', 'admin', '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.', 'CRD', 'Clinical Research Data Capture', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (83, '2009-07-12 21:29:10.466', 'admin', '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.', 'ACM', 'Alarm Communication Management', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (81, '2009-07-13 21:24:24.80', 'admin', '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.', 'CM', 'Care Management', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (78, '2009-07-13 22:06:20.605', 'admin', '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.', 'APR', 'Antepartum Record', 2);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (132, '2009-08-19 06:33:01.223', 'fourquetl', '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.', 'C78', 'HITSP Immunization Content', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (82, '2009-07-13 23:32:43.073', 'admin', 'Immunization Content', 'IC', 'Immunization Content', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (86, '2009-07-14 11:21:48.719', 'admin', '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', 'APW', 'Pathology Workflow', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (134, '2009-08-19 06:36:31.182', 'fourquetl', '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.', 'C76', 'HITSP Case Report Pre-populate', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, 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, description, keyword, name, 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, description, keyword, name, 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, description, keyword, name, 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, description, keyword, name, integration_profile_status_type_id) VALUES (1, '2009-07-03 08:12:55.703', 'admin', '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.', 'RFD', 'Retrieve Form for Data Capture', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (18, '2009-07-03 08:14:21.812', 'admin', '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.', 'XDS-I', 'Cross-enterprise Document Sharing for Imaging', 6);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (29, '2009-07-03 08:15:27.136', 'admin', '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.', 'XCA', 'Cross Community Access', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (38, '2009-07-03 08:59:36.715', 'admin', '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.', 'XDS.a', 'Cross-Enterprise Clinical Documents Share (XDS.a)', 6);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (51, '2009-07-03 09:01:23.948', 'admin', '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.', 'SEC', 'Basic Security', 6);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (62, '2009-07-03 09:03:36.394', 'admin', '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', 'FUS', 'Image Fusion', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (43, '2009-08-13 16:36:12.615', 'admin', '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.', 'PAM', 'Patient Administration Management', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (66, '2009-07-08 17:37:26.997', 'admin', 'The Stress Testing Workflow Profile provides the mechanism for ordering and collecting multi-modality data during diagnostic Stress testing procedures.', 'STRESS', 'Stress Testing Workflow', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (68, '2009-07-28 14:31:37.047', 'admin', '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.', 'EYE-CHG', 'Eye Care Charge Posting', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (147, '2008-08-18 21:30:00', '0', 'US HITSP: TP13b: Manage Sharing of Documents (with reference to the IHE XDS.b supplement to suport Entity Identity)', 'TP13b', 'Manage Sharing of Documents (XDS.B Option)', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (130, '2009-08-19 06:27:15.271', 'fourquetl', '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.', 'C38', 'C38 Patient Level Quality Document Using IHE Medical Summary (XDS-MS)', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (154, '2009-08-19 06:29:25.572', 'fourquetl', '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.', 'C26', 'HITSP Nonrepudiation of Origin Component', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (144, '2009-08-21 23:09:25.816', 'fourquetl', '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.', 'T63', 'HITSP Emergency Message Distribution Element', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (143, '2009-08-21 23:37:10.809', 'fourquetl', '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.', 'T81', 'HITSP T81 Retrieval of Medical Knowledge', 7);

INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (73, '2008-04-17 12:10:28.713458', '0', '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.', 'LCSD', 'Laboratory Code Set Distribution', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (75, '2008-04-17 12:10:28.716779', '0', '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.', 'LPOCT', 'Laboratory Point Of Care Testing', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (84, '2009-08-11 21:46:52.01', 'furst', '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.', 'PIV', 'Point-of-Care Infusion Verification', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, 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, description, keyword, name, 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, description, keyword, name, integration_profile_status_type_id) VALUES (77, '2009-07-03 09:09:03.825', 'admin', '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.', 'REM', 'Radiation Exposure Monitoring', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (80, '2009-07-03 09:11:35.413', 'admin', '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.', 'DRR', 'Document-based Referral Request', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (59, '2008-04-17 12:10:28.703586', '0', '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.', 'CHG', 'Charge Posting', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (54, '2009-07-08 17:22:43.023', 'admin', '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.', 'ECHO', 'Echocardiography Workflow', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (133, '2009-08-19 06:35:39.388', 'fourquetl', '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.', 'C82', 'HITSP Common Alerting Protocol', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (131, '2009-08-19 06:34:05.794', 'fourquetl', '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.', 'C62', 'HITSP XDS-SD', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (123, '2009-08-21 21:49:45.379', 'fourquetl', '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.', 'T15', 'HITSP Collect and Communicate Audit Trail', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (125, '2009-08-22 01:50:20.891', 'fourquetl', '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.', 'TP30', 'HITSP Manage Consent Directions Transaction Package', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (60, '2008-04-17 12:10:28.711804', '0', '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.', 'PWF', 'Post-Processing Workflow', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (63, '2008-04-17 12:10:28.746218', '0', '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.', 'IRWF', 'Import Reconciliation Workflow', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (64, '2008-04-17 12:10:28.74714', '0', '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.', 'MAMMO', 'Mammography Image', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (71, '2008-04-17 12:10:28.788402', '0', '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.   ', 'LTW', 'Laboratory Testing Workflow ', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (35, '2009-08-19 06:30:10.994', 'fourquetl', '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.', 'C32', 'Registration and Medication History Document Component', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (69, '2009-07-28 14:31:00.785', 'admin', '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.', 'ECED', 'Eye Care Evidence Documents', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (70, '2009-07-28 14:31:59.274', 'admin', '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.', 'ECDR', 'Eye Care Displayable Reports', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (50, '2008-04-17 12:10:28.738894', '0', '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.', 'XUA', 'Cross Enterprise User Authentication', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (46, '2009-07-03 08:59:58.328', 'admin', '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.', 'DSG', 'Digital Signature', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (45, '2009-07-03 09:00:21.251', 'admin', '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).', 'PDQV3', 'Patient Demographic Query HL7 V3', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (44, '2009-07-03 09:02:43.549', 'admin', '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.', 'PIXV3', 'Patient Identifier Cross-Reference HL7 V3', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (48, '2009-07-08 17:27:41.641', 'admin', '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. ', 'ATNA', 'Audit Trail and Node Authentication ', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (149, '2009-08-19 07:50:10.711', 'fourquetl', '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.', 'TP22', 'Patient ID Cross-Referencing using IHE PIX', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (52, '2008-04-17 12:10:28.696413', '0', '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.', 'SWF', 'Scheduled Workflow', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (55, '2008-04-17 12:10:28.699382', '0', '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.', 'PIR', 'Patient Information Reconciliation', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (56, '2008-04-17 12:10:28.700224', '0', '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.', 'PGP', 'Presentation of Grouped Procedures', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (57, '2008-04-17 12:10:28.701117', '0', '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.', 'RWF', 'Reporting Workflow', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (58, '2008-04-17 12:10:28.701923', '0', '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.', 'NMI', 'NM Image', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (31, '2009-07-14 10:00:48.065', 'admin', '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.', 'EDES', 'Emergency Department Encounter Summary', 2);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (34, '2009-08-21 12:29:44.782', 'fourquetl', '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).', 'C28', 'HITSP Emergency Encounter Summary Documents Component', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (28, '2009-07-24 16:05:03.003', 'admin', '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.', 'XD-LAB', 'Sharing Lab Report', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (32, '2009-08-13 23:05:22.049', 'smoore', '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.', 'FSA', 'Functional Status Assessment', 3);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (155, '2009-08-21 21:41:56.619', 'fourquetl', '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.', 'T66', 'HITSP Sharing Value Sets - SVS', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (121, '2009-08-19 06:17:32.09', 'fourquetl', '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.', 'C19', 'HITSP Entity Identity Assertion Component', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (137, '2009-08-21 21:57:29.648', 'fourquetl', '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.', 'T16', 'HITSP T16: Consistent Time', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (37, '2008-04-17 12:10:28.775021', '0', 'HITSP Testing using IHE Profiles', 'HITSPIHE', 'HITSP Testing using IHE Profiles', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (39, '2008-04-17 12:10:28.790411', '0', '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>', 'XDS.b', 'Cross-Enterprise Clinical Documents Share (XDS.b)', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (40, '2008-04-17 12:10:28.740801', '0', '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.', 'PIX', 'Patient Identifier Cross-referencing for MPI', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (41, '2008-04-17 12:10:28.741754', '0', '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).', 'PDQ', 'Patient Demographics Query', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (42, '2008-04-17 12:10:28.742814', '0', '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.', 'PSA', 'Patient Synchronized Application ', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (9, '2009-08-19 06:26:07.172', 'fourquetl', '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.', 'C37', 'Lab Report Document Component', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (47, '2008-04-17 12:10:28.729005', '0', '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.', 'CT', 'Consistent Time', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (49, '2008-04-17 12:10:28.736696', '0', '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', 'EUA', 'Enterprise User Authentication', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (17, '2008-04-17 12:10:28.726844', '0', '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.', 'CPI', 'Consistent Presentation of Images', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (6, '2009-07-03 08:13:09.839', 'admin', '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).', 'DRPT', 'Displayable Reports', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (126, '2009-08-19 07:35:17.622', 'fourquetl', '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.', 'TP21', 'HITSP Query for Existing Data', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (2, '2009-07-08 16:20:08.383', 'admin', '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.', 'PWP', 'Personnel White Pages', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (4, '2009-07-08 16:21:57.949', 'admin', '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. ', 'LDA', 'Laboratory Device Automation', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (8, '2009-08-19 06:25:16.051', 'fourquetl', '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.', 'C36', 'Lab Result Message Component', 7);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (106, '2009-09-08 15:10:11.804', 'smoore', 'Labor and Delivery History and Physical', 'LDHP', 'Labor and Delivery History and Physical', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (19, '2008-04-17 12:10:28.728308', '0', '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.', 'XDS-MS', 'Cross-Enterprise Sharing of Medical Summaries', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (20, '2008-04-17 12:10:28.749911', '0', '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.', 'XDM', 'Cross-Enterprise Document Media Interchange', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (22, '2008-04-17 12:10:28.751778', '0', '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.', 'XDS-SD', 'Cross-Enterprise Document Sharing of Scanned Documents', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (23, '2008-04-17 12:10:28.753647', '0', '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', 'BPPC', 'Basic Patient Privacy Consents', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (24, '2008-04-17 12:10:28.754606', '0', '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).', 'EDR', 'Emergency Department Referral', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (26, '2008-04-17 12:10:28.756328', '0', '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.', 'XPHR', 'Exchange of Personal Health Record Content', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (21, '2009-07-03 08:14:51.169', 'admin', '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.', 'XDR', 'Cross-Enterprise Document Reliable Interchange', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (33, '2009-07-03 08:59:10.444', 'admin', '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. ', 'QED', 'Query for Existing Data', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (27, '2009-07-12 22:20:45.035', 'admin', '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.', 'DEC', 'Device Enterprise Communication', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (7, '2008-04-17 12:10:28.718754', '0', '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.', 'ED-CARD', 'Cardiology Evidence Documents', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (10, '2008-04-17 12:10:28.72185', '0', '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.', 'KIN', 'Key Image Note', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (11, '2008-04-17 12:10:28.722505', '0', '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.', 'SINR', 'Simple Image and Numeric Report', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (12, '2008-04-17 12:10:28.723157', '0', '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.', 'ED', 'Evidence Documents', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (13, '2008-04-17 12:10:28.72391', '0', '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.', 'RID', 'Retrieve Information for Display', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (160, '2009-08-11 12:42:04.78', 'admin', 'IDCO specifies the creation, transmission, and processing of discrete data elements and report attachments associated with implantable cardiac device interrogations (observations) or messages.', 'IDCO', 'Implantable Device - Cardiac - Observation', 4);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (15, '2008-04-17 12:10:28.725364', '0', '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.', 'PDI', 'Portable Data for Imaging', 5);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id) VALUES (16, '2008-04-17 12:10:28.72619', '0', '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.', 'ARI', 'Access to Radiology Information', 5);
SET escape_string_warning = off;
-- 10_tf_integration_profile_option_aud_data.sql
INSERT INTO tf_integration_profile_option_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, reference) VALUES (1,0,1, '2008-04-17 12:10:01.085139', '0', 'NONE', 'None', 'None', '');
INSERT INTO tf_integration_profile_option_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, reference) VALUES (1,0,3, '2008-04-17 12:10:01.087951', '0', 'ASST_ACQ_PROT_SET', 'Assisted Acquisition Protocol Setting', 'Assisted Acquisition Protocol Setting', 'Rad TF-2:4.6');
INSERT INTO tf_integration_profile_option_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, reference) VALUES (1,0,4, '2008-04-17 12:10:01.089286', '0', 'PPS_EXC_MGT', 'PPS Exception Management', 'PPS Exception Management', 'Rad TF-2:4.7');
INSERT INTO tf_integration_profile_option_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, reference) VALUES (1,0,5, '2008-04-17 12:10:01.090053', '0', 'WRK_STAT_UPD_RCV', 'Performed Work Status Update Recieve', 'Performed Work Status Update Recieve', 'Rad TF-2:4.20-21');
INSERT INTO tf_integration_profile_option_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, reference) VALUES (1,0,6, '2008-04-17 12:10:01.090763', '0', 'PAT_QUERY', 'Patient Based Worklist Query', 'Patient Based Worklist Query', 'Rad TF-2:4.5');
INSERT INTO tf_integration_profile_option_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, reference) VALUES (1,0,8, '2008-04-17 12:10:01.09234', '0', 'MOD_GROUP_CASE', 'Modality Group Case', 'Modality Group Case', 'Rad TF-2:4.6');
INSERT INTO tf_integration_profile_option_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, reference) VALUES (1,0,9, '2008-04-17 12:10:01.093083', '0', 'BILL_AND_MAT_MGT', 'Billing and Material Management', 'Billing and Material Management', 'Rad TF-4:4.7');
INSERT INTO tf_integration_profile_option_aud (rev,revtype,id, last_changed, last_modifier_id, keyword, name, description, reference) VALUES (1,0,10, '2008-04-17 12:10:01.093872', '0', 'CRT_PPS', 'Creator Performed Procedure Step', 'Creator Performed Procedure Step', 'Rad TF-2:4.20-21');
