-- Name: tf_document_sections_pkey; Type: CONSTRAINT; Schema: public; Owner: gazelle; Tablespace: 
--

ALTER TABLE ONLY tf_document_sections
    ADD CONSTRAINT tf_document_sections_pkey PRIMARY KEY (id);


--
-- Name: tf_document_sections_section_key; Type: CONSTRAINT; Schema: public; Owner: gazelle; Tablespace: 
--

ALTER TABLE ONLY tf_document_sections
    ADD CONSTRAINT tf_document_sections_section_key UNIQUE (section, document_id);


--
-- Name: uk_gqqt5kk1xa5npiaptbwwdu9bt; Type: CONSTRAINT; Schema: public; Owner: gazelle; Tablespace: 
--

ALTER TABLE ONLY tf_document_sections
    ADD CONSTRAINT uk_gqqt5kk1xa5npiaptbwwdu9bt UNIQUE (section, document_id);


--
-- Name: fka47dcc45a9b2d794; Type: FK CONSTRAINT; Schema: public; Owner: gazelle
--

ALTER TABLE ONLY tf_document_sections
    ADD CONSTRAINT fka47dcc45a9b2d794 FOREIGN KEY (document_id) REFERENCES tf_document(id);


--
--

--
--





--
-- Name: tf_actor; Type: TABLE; Schema: public; Owner: gazelle; Tablespace: 
--

CREATE TABLE tf_actor (
    id integer NOT NULL,
    last_changed timestamp without time zone,
    last_modifier_id character varying(255),
    combined boolean,
    description character varying(2048),
    keyword character varying(128) NOT NULL,
    name character varying(128)
);


ALTER TABLE public.tf_actor OWNER TO gazelle;

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

INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1191, '2011-05-13 18:14:38.141', 'lynn', NULL, 'The Initiating Imaging Gateway Actor proxies Imaging  Document Set Retrieve requests from an Image Document Consumer to a Responding Imaging Gateway with a Cross Gateway Retrieve Imaging Document Set transaction. ', 'INIT_IMG_GATEWAY', 'Initiating Imaging Gateway');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1192, '2011-05-13 18:15:24.254', 'lynn', NULL, 'The responding Imaging Gateway proxies Cross Gateway Retrieve Imaging Document Set requests from an Initiating Imaging Gateway to an Imaging Document Source with an Image Document Set Retrieve request.', 'RESP_IMG_GATEWAY', 'Responding Imaging Gateway');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1194, '2011-07-20 17:20:15.476', 'lynn', NULL, 'The Metadata-Limited Document Source sends documents and metadata similar to a Document Source but is limited in the quantity of metadata it is able to provide.', 'METADATA_LTD_DOC_SOURCE', 'Metadata-Limited Document Source');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1195, '2011-08-09 21:03:30.768', 'jungers', NULL, 'The Reconciliation Agent actor accesses clinical information in structured form. It automatically identifies potentially duplicated, overlapping, conflicting, or superseded information based upon application knowledge and provides that information for presentation to a clinician to complete the reconciliation process. It presents the demographics used identify the patient provided by each separate source of clinical information to the end user. 
It highlights inconsistencies found during the automated reconciliation process and provides the clinician with mechanisms to adjust or correct the input. 
It provides a mechanism for a clinician to add new information to the reconciled results. It authenticates the clinician prior to storage of the reconciled data (this step may be combined with other authentication steps used to finalize the record). It stores the data for future use by other actors.', 'RECON_AGENT', 'Reconciliation Agent');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (187, '2010-07-28 16:57:24.518', 'lynn', false, 'The On-Demand Document Source is the producer and publisher of On-Demand Documents.  This actor registers On-Demand Document Entries with the Document Registry and responds to Retrieve Document Set transactions with a document reflecting current information for the entry requested.', 'ON_DEMAND_DOC_SOURCE', 'On-Demand Document Source');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1196, '2011-08-10 21:31:04.508', 'jungers', NULL, '', 'CONTENT_AGENT', 'Content Agent');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (16, '2011-08-30 16:06:11.078', 'moores', false, '- 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 (192, '2010-08-09 14:38:21.887', 'lnelson', false, 'The ProcessActivityExecutor performs activities as prescribed by a running process being managed by a ProcessStateManager. The ProcessActivityExecutor retrieves current activity or task lists, works its list, updating the ProcessStateManager on activity state until completion. This cycle is repeated until all process activities have been worked and the process itself completes.', 'PROC_ACT_EXECUTOR', 'Process Activity Executor');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (12, '2011-08-30 17:45:34.526', 'moores', false, 'is 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 (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 (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 (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 (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 (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 (1230, '2013-07-19 18:22:23.956918', 'lynn', NULL, 'The Form Processor is an integrated Form Manager and From Receiver, supporting all of the transactions and options of those actors.

The Form Processor constructs form such that form data is submitted back to itself.', 'FORM_PROCESSOR', 'Form Processor');
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 (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 (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 (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 (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 (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 (1297, '2015-04-01 22:27:31.048967', 'lynn', NULL, 'A creator of DICOM composite instances', 'IMG_CAPTURER', 'Image Capturer');
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 (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 (1193, '2011-05-13 18:50:01.664', 'lynn', NULL, 'A system that communicates changes to an Image Manager / Archive, indicating that certain imaging instances should be deleted. In addition, it may also send new versions of these imaging instances containing corrected information', 'CHANGE_REQUESTER', 'Change Requester');
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 (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 (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 (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 (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 (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 (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 (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 (186, '2010-07-22 18:28:45.36', 'lnelson', false, 'The Extraction Specification Manager manages a set of extraction specifications.  An extraction specification explicitly indicates which information to extract from a source document. Extraction Specification Managers are queried using an identifier for a particular Extraction Specification and they return the associated specification file.', 'EXTR_SPEC_MGR', 'Extraction Specification Manager');
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 (177, '2010-03-05 00:00:59.597', 'jgilbert', NULL, 'Secure Message Delivery Sender Intermediary', 'SMD_SI', 'SMD Sender Intermediary');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (193, '2010-08-09 14:40:19.255', 'lnelson', false, 'The ProcessStateManager manages the initiation and state of runtime process instances. The ProcessStateManager typically also supports the initiation and lifecycle management of task activities associated with a process while providing the abilty for task performers to retrieve and update activities. ', 'PROC_STATE_MGR', 'Process State Manager');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (194, '2010-08-09 14:44:24.673', 'lnelson', false, 'The ProcessDefinitionManager manages access to a repository of process definitions allowing for search and retrieval. ', 'PROC_DEF_MGR', 'Process Definition Manager');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (195, '2010-08-18 13:44:04.244', 'jungers', false, 'The Personal Health Record actor represents the information system storing a s personal health data.   This actor is responsible for supplying personal health data to the Care Manager actors through the PCC-0 Exchange Content transaction using the PHR Extract content specified in the Exchange of Personal Health Record Content profile.', 'Personal_Health_Record', 'Personal Health Record');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (198, '2010-08-23 13:57:17.117', 'lnelson', false, 'The Distribution Message Receiver  is responsible for receiving and processing the communications from the Distribution Message Transmitter.', 'DIST_MSG_RECEIVER', 'Distribution Message Receiver');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1182, '2010-07-27 09:50:14.941', 'epoiseau', NULL, 'This is the country of care', 'NCP-B', 'National Contact Point Country B');
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 (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 (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 (146, '2010-08-23 14:04:31.703', 'lnelson', false, 'The 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 (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 (175, '2010-03-04 23:58:55.176', 'jgilbert', NULL, 'Secure Message Delivery Sender', 'SMD_S', 'SMD Sender');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1198, '2011-12-17 10:50:33.727', 'epoiseau', NULL, '', 'CONTENT_UPDATER', 'Content Updater');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (135, '2014-10-06 17:16:09.127386', 'wbosch', false, 'Treatment Management System accepts RT Plan instances (one of 14 beam types).', 'TMS', 'Treatment Management System');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1299, '2015-09-08 17:25:56.527725', 'moores', NULL, 'An actor that requests evaluation of a proposed action to determine whether it may or should be initiated. 

First defined: PCC Guideline Appropriate Ordering (GAO) Supplement, May 2015', 'ORDER_EVAL_REQUESTER', 'Order Evaluation Requester');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1325, '2015-12-09 00:08:15.799749', 'lynn', NULL, 'Submits new tasks to a Task Manager', 'TASK_REQUESTER', 'Task Requester');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (201, '2010-09-23 16:37:24.446', 'jungers', false, 'The Imaging Order Filler Actor represents the information system that receives and processes orders for imaging services.  The Imaging Order Filler is a minor variation of Order Filler in the Structured Workflow (SWF) profile of the IHE Radiology Technical Framework.  It supports the same ordering transactions as found in the SWF profile, but has one required and two optional transactions.  From the perspective of the care providers in this profile, an Imaging Order Filler is a single information system that manages orders and results for a given type of study.', 'IMG_ORD_FILLER', 'Imaging Order Filler');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (203, '2010-09-23 17:18:43.083', 'jungers', false, 'The Device Gateway Actor coordinates communication between the recording/viewing equipment and specialized monitoring (e.g., electronic fetal monitoring) or treatment (e.g., Infusion Pump) devices.', 'DEV_GATEWAY', 'Device Gateway');
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 (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 (180, '2010-06-10 11:39:35.651', 'lynn', false, 'A system that handles requests for appointments and requests for appointment information. The system is responsible for providing schedule information including both appointments requested by the Appointment Requester Actor and those that were not.', 'APPT_SCHEDULER', 'Appointment Scheduler');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (184, '2010-07-21 14:33:53.163', 'lynn', false, 'The Document Administrator actor supports metadata update by issuing the Update Document Set transaction [ITI-57] and Delete Document Set [ITI-61 ] transaction to the Document Registry actor.', 'DOC_ADMINISTRATOR', 'Document Administrator');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (185, '2010-07-22 18:20:29.015', 'lnelson', false, 'The Redactor applies an extraction specification to select only specific information from an input document.  The Redactor creates a new document containing only the information included in the extraction specification. The Redactor''s output, called a redacted document, is returned to the sender of the original document.', 'REDACTOR', 'Redactor');
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 (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 (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 (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 (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 (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 (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 (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 (1199, '2012-06-28 17:33:53.304', 'lynn', NULL, 'receives DICOM SOP Instances and image reports.', 'IMG_DOC_RECIPIENT', 'Imaging Document Recipient');
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 (183, '2010-07-19 15:31:17.986', 'lynn', false, '', 'PROV_INFO_DIR', 'Provider Information Directory');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (62, '2012-06-28 17:34:22.277', 'lynn', false, 'sends DICOM SOP Instances and image reports.', 'IMG_DOC_SOURCE', 'Imaging Document Source');
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 (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 (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 (1302, '2015-05-28 16:13:40.692661', 'moores', NULL, 'This actor receives sensor data from Personal Healthcare Devices (PHDs)', 'SENSOR_DATA_CONSUMER', 'Sensor Data Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (199, '2010-08-23 14:01:10.542', 'lnelson', false, 'The Distribution Message Transmitter is responsible for transmitting the source data that is communicated to the Distribution Message Receiver.', 'DIST_MSG_TRANSMITTER', 'Distribution Message Transmitter');
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 (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 (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 (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 (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 (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, '2010-07-21 09:47:07.346', 'lynn', false, 'Provides Expanded Value Sets ', 'VALUE_SET_REPOSITORY', 'Value Set Repository');
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 (1181, '2010-07-27 09:48:13.247', 'epoiseau', NULL, 'This is the country of affiliation of the patient', 'NCP-A', 'National Contact Point Country A ');
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 (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 (200, '2010-09-22 23:59:13.92', 'jungers', false, 'The Patient Registration Actor is responsible for communicating patient demographics and administrative data (e.g., insurance) to other actors in this profile.  These other actors may choose to accept this information from the Patient Registration Actor, or may provide another mechanism to support registration.  The actors that support the Patient Registration Option will accept this communication from the Patient Registration Actor', 'PAT_REGISTRATION', 'Patient Registration');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (120, '2010-02-16 14:29:59.774', 'aberge', false, 'The Portable Media Sender actor will never appear in an Integration Statement, since it only exists in the context of the Sending Software Option of the Portable Media Creator', 'PMS', 'Portable Media Sender');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1274, '2013-08-23 17:39:17.414523', 'moores', NULL, 'TBD', 'RESEARCH_INFO_SOURCE', 'Research Information Source');
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 (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 (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 (1221, '2012-11-13 17:52:40.223', 'epoiseau', NULL, 'Participant responsible for the scheduling of the Tumor Board Review, by providing one of the timeslots for the requested TBR', 'TBR_SCHEDULER', 'TBR Scheduler');
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 (1201, '2012-07-27 20:00:03.168', 'moores', NULL, 'requests that new workitems be created by systems that will either manage or perform the workitems.', 'WORKITEM_CREATOR', 'Workitem Creator');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (43, '2014-11-25 10:39:20.604194', 'jlabbe', NULL, '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 (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 (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 (196, '2010-08-18 13:45:41.602', 'jungers', false, 'The Laboratory Order Filler actor represents the information system that receives and processes orders for laboratory testing.  The Laboratory Order Filler actor is a simplification of the Order Filler in the Laboratory Testing Workflow (LTW) profile of the IHE Laboratory Technical Framework.  It supports the same ordering transactions as found in the LTW profile, but has one optional transaction.  The Laboratory Order Filler implementing the Content Exchange option also supports the direct exchange of laboratory reports via the PCC-0 Exchange Content transaction using the content specified in XD-LAB profile.', 'LAB_ORDER_FILLER', 'Laboratory Order Filler');
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 (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 (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 (179, '2010-06-10 11:38:25.343', 'lynn', false, 'A system that sends requests for appointments and/or schedules and displays the results of those requests.', 'APPT_REQUESTER', 'Appointment Requester');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (176, '2010-03-04 23:59:48.094', 'jgilbert', NULL, 'Secure Message Delivery Receiver', 'SMD_R', 'SMD Receiver');
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');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (76, '2012-07-20 16:48:15.711', 'lynn', false, ' A system that receives documents and metadata sent by another actor. ', 'DOC_RECIPIENT', 'Document Recipient');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1190, '2011-01-08 10:14:08.228', 'epoiseau', NULL, 'The main role of this actor consists in providing the business logic for status management and other purposes. As a second role it acts as a “relaying role” where certain standard XDS communication is routed through for providing the possibility of applying project-specific business logic on it.
It provides special query-transactions which consuming actors (prescription placer, pharmaceutical adviser or medication dispenser) used for reducing the amount of data flowing to them. They return just “relevant” information for specific purposes (e.g., returning just all “active” prescriptions ready for being validated or dispensed together with all related documents). This actor is usually a system actor without human participation.', 'CPM', 'Community Pharmacy Manager');
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 (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 (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 (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 (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 (1200, '2012-07-20 16:46:05.99', 'lynn', NULL, 'The receiver of and responder to requests for document entries and documents. ', 'DOC_RESPONDER', 'Document Responder');
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 (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 (1208, '2012-07-27 20:46:55.03', 'moores', NULL, 'a system or a module in a NANI framework, the purpose of which is to process subscription/un-subscription requests, to keep track of existing subscriptions, to receive information, and based on the set of filters for each subscription to send a notification about the received information to the appropriate Newborn Admission Notification Recipients. ', 'NEWBORN_ADMIT_NOTIF_MGR', 'Newborn Admission Notification Manager');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1209, '2012-07-27 20:47:58.382', 'moores', NULL, 'a system or a module in a NANI framework, the purpose of which is to receive and process notifications from the Newborn Admission Notification Manager.', 'NEWBORN_ADMIT_NOTIF_SUBSCRIBER', 'Newborn Admission Notification Subscriber');
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 (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 (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 (41, '2012-07-20 16:47:10.686', 'lynn', false, 'The Document Source is the producer and publisher of documents and metadata.', 'DOC_SOURCE', 'Document Source');
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 (1210, '2012-07-28 00:05:31.781', 'moores', NULL, 'A Clinical Knowledge Directory receives requests for clinical knowledge and returns a list of relevant clinical knowledge resources based on the content of the knowledge request.', 'CLIN_KNOWLEDGE_DIRECTORY', 'Clinical Knowledge Directory');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1211, '2012-07-28 00:06:22.905', 'moores', NULL, 'A Clinical Knowledge Requester collects appropriate clinical context and uses it to request clinical knowledge, and presents the resulting knowledge to the user.', 'CLIN_KNOWLEDGE_REQUESTER', 'Clinical Knowledge Requester');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1213, '2012-07-29 04:17:10.979', 'Manny', NULL, 'The Retrospective Data Consumer (RDC) initiates the query for retrospective data, initiating such query with the PCD-12 transaction.', 'RDC', 'Retrospective Data Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1225, '2013-05-17 22:22:05.325279', 'lynn', NULL, 'A system that provides storage and management of report templates. ', 'RPT_TEMPLATE_MGR', 'Report Template Manager');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1214, '2012-07-29 04:14:06.423', 'Manny', NULL, 'The Retrospective Data Responder (RDR) responds to the Retrospective Data Query for retrospective data with an Retrospective Data Query Response containing (at most) the requested data or (at minimum) a NULL indicating no such data exist.', 'RDR', 'Retrospective Data Responder');
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 (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 (1187, '2011-01-08 10:05:58.518', 'epoiseau', NULL, 'This repository contains the medication prescribed to the patient from the prescription placer and may receive updates to the current treatment (cancellations, changes, etc.). It also provides the current treatment to other actors such as the prescription consumer.', 'PRES_REPO', 'Prescription 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 (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 (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 (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 (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 (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 (108, '2010-07-21 09:46:36.853', 'lynn', false, 'Retrieves Expanded 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 (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 (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 (109, '2012-08-02 15:11:06.484', 'lynn', false, '', 'REFERRAL_REQUESTER', 'Referral Requester');
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 (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 (151, '2011-02-24 11:10:06.839', 'epoiseau', false, 'Access Control Service ', 'ACS', 'Access Control Service');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1183, '2011-01-08 10:07:02.8', 'epoiseau', NULL, 'The main role of this actor consists in placing the prescription (initial or modified in case of a substitution of invalidation, for example). It sends the cancellation of the prescription or its discontinuation, as well. In order to fulfill this task, the prescription placer retrieves the current treatment of the patient and medication already dispensed recently.
The prescription placer receives the pharmaceutical validation and status tracking information such as substitution, availability, administration plan and reports and cancellation. The corresponding human actor is a prescriber.', 'PRES_PLACER', 'Prescription Placer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1215, '2012-08-02 15:12:17.862', 'lynn', NULL, '', 'REFERRAL_SCHEDULER', 'Referral Scheduler');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1264, '2013-08-05 17:50:34.625048', 'moores', NULL, '', 'BASIC_STATIC_MLC_BEAM_PRODUCER', 'Basic Static MLC Beam Producer');
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 (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 (190, '2010-08-03 08:53:18.339', 'lnelson', false, 'A system that manages the status of reporting, and additionally maintains an internal report repository.', 'INTEG_RM_RRP', 'Integrated Report Manager/Repository');
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 (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 (181, '2010-07-19 15:26:15.589', 'lynn', false, '', 'PROV_INFO_SRC', 'Provider Information Source');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (182, '2010-07-19 15:30:00.097', 'lynn', false, '', 'PROV_INFO_CONS', 'Provider Information Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1197, '2011-12-15 12:23:25.332', 'epoiseau', NULL, 'An Automation Manager that manage the analytical part of the laboratory. This actor is involved in the LAW profiles.', 'ANALYZER_MGR', 'Analyzer Manager');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1216, '2012-08-02 15:12:46.526', 'lynn', NULL, '', 'REFERRAL_PERFORMER', 'Referral Performer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1217, '2012-08-02 15:13:12.344', 'lynn', NULL, '', 'WORKFLOW_MONITOR', 'Workflow Monitor');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1218, '2012-08-02 15:42:21.77', 'lynn', NULL, '', 'GENL_CLINICIAN_MGR', 'General Clinician Manager');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1219, '2012-08-02 15:42:48.543', 'lynn', NULL, '', 'CONSULT_MGR', 'Consult Manager');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1220, '2012-11-13 17:50:58.602', 'epoiseau', NULL, 'Participant (Healthcare Professional, e.g., gastroenterologist) who initiates the XTB-WD workflow. Produces the Request and the related supporting documents', 'TBR_REQUESTOR', 'TBR Requestor');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1222, '2012-11-13 17:53:41.627', 'epoiseau', NULL, 'Any Participant that is part of the Tumor Board, and involved in the review process', 'TBR_PREPARATOR', 'TBR Preparator');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1226, '2013-05-17 22:22:45.960961', 'lynn', NULL, 'A system that enables a user to create and edit report templates.', 'RPT_TEMPLATE_CREATOR', 'Report Template Creator');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1202, '2012-07-27 20:00:49.839', 'moores', NULL, 'provides management, query access and notifications for workitems in a worklist.', 'WORKITEM_MANAGER', 'Workitem Manager');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1203, '2012-07-27 20:01:29.962', 'moores', NULL, 'provides management, query access and notifications for workitems in a worklist.', 'WORKITEM_PERFORMER', 'Workitem Performer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1204, '2012-07-27 20:02:10.305', 'moores', NULL, 'subscribes and receives notifications of events associated with a workitem (such as modification, cancelation or completion).', 'WATCHER', 'Watcher');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1205, '2012-07-27 20:02:55.009', 'moores', NULL, 'a system that hosts applications, including providing an execution environment and mediating interactions with resources.', 'HOSTING_SYSTEM', 'Hosting System');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1206, '2012-07-27 20:03:47.782', 'moores', NULL, 'an application (program) runs in an environment provided by a host.', 'HOSTED_APPLICATION', 'Hosted Application');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1228, '2013-06-11 21:12:19.329449', 'Casertano', NULL, 'sends DICOM SOP Instances and image reports and associated documents.', 'DENTAL_DOC_SOURCE', 'Dental Document Source');
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 (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 (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 (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 (202, '2010-09-23 17:04:52.008', 'jungers', false, 'The Device Observation Consumer / Alarm Manager  Actor accepts monitoring and alarm data from the Device Gateway and makes it available to healthcare providers.', 'DEV_OBS_CONSUMER_ALRM_MGR', 'Device Observation Consumer / Alarm Manager');
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 (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 (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 (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 (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 (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 (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 (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 (178, '2010-03-05 00:05:24.386', 'jgilbert', NULL, 'Secure Message Delivery Receiver Intermediary', 'SMD_RI', 'SMD Receiver Intermediary');
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 (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 (99, '2010-10-24 09:28:36.45', '0', false, '', '', '');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (189, '2010-07-29 16:03:05.128', 'lnelson', false, 'Electronic Health Record System (EHR-S) is an actor supporting the functions of patient administration, scheduling, clinical records management, decision support, and external orders and referrals.  ', 'EHRS', 'Electronic Health Record System');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (191, '2010-08-04 14:49:41.997', 'lnelson', false, 'A system that manages the acquisition workflow of resting ECGs.', 'INTEG_ECG_MGR', 'Integrated ECG Manager');
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 (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 (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 (188, '2010-07-29 13:34:06.818', 'lnelson', false, 'The Integrated Electronic Health Record System combines the functionality of the EHR-S, DSS/OS, and PPS Manager actors in an integrated implementation. In such an integrated implementation, the transactions between the EHR-S and the DSS/OF are not externalized; i.e., patient and order management are solely the internal responsibility of the Integrated EHR-S implementation.', 'INTEG_EHRS', 'Integrated Electronic Health Record System');
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 (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 (1207, '2012-07-27 20:46:02.833', 'moores', NULL, 'a system or a module in a NANI framework, the purpose of which is to publish information to the Newborn Admission Notification Manager.', 'ADMISSION_INFO_SRC', 'Admission Information Source');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1212, '2012-07-28 00:07:24.208', 'moores', NULL, 'A Clinical Knowledge Resource Repository stores documents providing clinical knowledge and returns them to Requesters on demand.', 'CLIN_KNOWLEDGE_RESOURCE_REPOS', 'Clinical Knowledge Resource Repository');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1236, '2013-08-05 16:00:36.344335', 'moores', NULL, 'A Treatment Planning System (TPS) capable of producing a radiation therapy treatment plan with static, non-MLC, treatment beams.', 'BASIC_STATIC_BEAM_PRODUCER', 'Basic Static Beam Producer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1223, '2012-11-13 17:55:00.826', 'epoiseau', NULL, 'A Participant (usually a Healthcare Professional) who writes down the conclusions of the Tumor Board Review', 'TBR_REPORT_WRITER', 'TBR Report Writer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1224, '2012-11-13 17:56:12.166', 'epoiseau', NULL, 'A Participant who validates the preliminary Tumor Board Review report', 'TBR_FINALIZER', 'TBR Finalizer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (7, '2013-05-17 22:23:22.76067', 'lynn', false, 'A system that generates and transmits draft (and optionally, final) diagnostic reports. It may also retrieve work list entries for reporting steps from the Report Manager and provide notification of completion of the step, allowing the enterprise to track the status of an awaited report', 'RC', 'Report Creator');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1227, '2013-05-17 23:02:47.707341', 'lynn', NULL, 'This profile specifies only the interoperability requirements of the Image Display Invoker immediately associated with requesting the display of images.', 'IMG_DISPLAY_INVOKER', 'Image Display Invoker');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1229, '2013-06-11 21:12:52.029797', 'Casertano', NULL, 'receives DICOM SOP Instances and image reports and associated documents.', 'DENTAL_DOC_RECIPIENT', 'Dental Document Recipient');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (19, '2013-07-02 22:02:30.371839', 'lynn', false, 'Provide local management of user authentication.', 'CAA', 'Client Authentication Agent');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (23, '2013-07-02 22:03:18.001351', 'lynn', false, 'Provides central authentication of enterprise users.', 'KER_AUTH_SVR', 'Kerberos Authentication Server');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (115, '2015-08-10 22:33:48.809997', 'psherman', false, 'The Alert Communicator  (AC) actor receives the alert from the Alert Manager (AM) and sends the alert to the client application in the endpoint device and reports the dissemination status back to the Alert Manager (AM).', 'ALRT_COMMUNICATOR', 'Alert Communicator');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1231, '2013-07-24 23:41:38.092956', 'lynn', NULL, 'The Notification Puller is the actor that can create a pull point resource for the storing of notifications. It pulls notifications stored in a Notification Pull point actor when requested.', 'NOTIFICATION_PULLER', 'Notification Puller');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1323, '2015-12-01 16:41:42.889545', 'epoiseau', NULL, 'eCR client actor is a grouping of the actors IHE Document Consumer, IHE Document Source, and IHE X-Service User.
', 'eCR Client', 'eCR Client');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1232, '2013-07-24 23:42:51.92147', 'lynn', NULL, 'The Notification Pull Point is the actor that stores notifications targeted to a specific Document Metadata Notification Recipient that cannot be directly notified. This actor delivers notifications to the Notification Puller when requested.', 'NOTIFICATION_PULL_POINT', 'Notification Pull Point');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (121, '2013-07-25 00:17:27.649316', 'lynn', false, 'The Document Metadata Notification Broker is the receiver of the Document Metadata Subscribe transaction containing a subscription request, or a subscription cancellation. It keeps track of all subscriptions in the Metadata Notification domain, including the time limits of subscriptions. Based on the metadata associated with document registrations, this actor sends notifications to interested subscribers. ', 'DM_NOTIF_BROKER', 'Document Metadata Notification Broker');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (124, '2013-07-25 00:17:49.496814', 'lynn', false, 'The Document Metadata Notification Recipient actor receives the notification about an event, when the subscription filters specified for this Document Metadata Notification Recipient are satisfied. ', 'DM_NOTIF_RECIPIENT', 'Document Metadata Notification Recipient');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1185, '2012-10-26 11:36:51.362', 'aboufahj', NULL, 'This actor is responsible for the process of dispensing medication to the patient, fulfilling the prescription. Therefore it produces the information on the medication dispensed to the patient. In order to achieve this, it receives prescriptions already validated. It also confirms drug availability for administration and it receives the administration plan and administration reports.
This actor may be implemented as the point of sale software of a community pharmacy or the hospital pharmacy module of a hospital information system. The human actor behind this system actor is usually a pharmacist or a pharmacist assistant.
In addition to the dispense, in this version this actor is considered to take care of all the dependencies to ensure a proper dispensing.', 'MED_DIS', 'Medication Dispenser');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1189, '2012-10-26 11:38:46.482', 'aboufahj', NULL, 'This repository contains the medication actually dispensed to the patient; this information is received from the medication dispenser. The dispensed medication repository provides the medication record of the patient to other actors such as the dispensed medication consumer.', 'DISP_MED_REPO', 'Dispensed Medication Repository');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1186, '2012-10-26 11:39:00.685', 'aboufahj', NULL, 'The medication administration informer’s main responsibility consists in creating and placing the medication administration plan and the corresponding administration reports. In order to achieve this, it receives the initial prescription, the pharmaceutical validation or a “simple” substitution. It also receives the confirmation of drug availability for administration.
Through administration reports, the Medication Administration Manager actor reports, among others:
	The replacements (e.g., the 1g tablet by two 500 mg single dose packets) 
	The follow-up (e.g., injectable follow-up)', 'MED_ADM_INFO', 'Medication Administration Informer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1184, '2012-10-26 11:39:14.127', 'aboufahj', NULL, 'This actor is responsible for the validation of prescriptions from a pharmacist’s perspective. Therefore, it receives the initial prescription, validates it and sends it back (accepted, cancelled, modified, substitution of pharmaceutical product); therefore it provides the pharmaceutical advice. To perform this task it checks the current treatment.
The pharmaceutical advice can be due to clinical, legal, or supply aspects.
This actor may be implemented in the hospital pharmacy module of a hospital information system or the point of sale software of the pharmacy. The corresponding human actor is typically a pharmacist (or pharmacist assistant).', 'PHA_ADV', 'Pharmaceutical Adviser');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1188, '2012-10-26 11:39:28.394', 'aboufahj', NULL, 'This repository contains the pharmaceutical advice issued by the pharmaceutical adviser (typically a pharmacist). It provides this information to the prescription & pharmaceutical advice consumer.', 'PHA_ADV_REPO', 'Pharmaceutical Advice Repository');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (122, '2013-07-25 00:18:06.062163', 'lynn', false, 'The Document Metadata Publisher actor sends a Document Metadata Publish transaction to the Document Metadata Notification Broker for any event for which a subscription exists. ', 'DM_PUBLISHER', 'Document Metadata Publisher');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (123, '2013-07-25 00:18:22.34281', 'lynn', false, 'The Document Metadata Subscriber actor initiates and terminates subscriptions on behalf of a Document Metadata Notification Recipient. ', 'DM_SUBSCRIBER', 'Document Metadata Subscriber ');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1233, '2013-07-26 15:47:37.288869', 'lynn', NULL, 'A client that presents authorization tokens as part of transactions.', 'AUTH_CLIENT', 'Authorization Client');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1234, '2013-07-26 15:48:17.403864', 'lynn', NULL, 'A server that provides authorization tokens to requesting clients', 'AUTH_SERVER', 'Authorization Server');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1235, '2013-07-26 15:48:44.128596', 'lynn', NULL, 'A server that provides services that need authorization', 'RESOURCE_SERVER', 'Resource Server');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1237, '2013-08-05 16:01:21.04389', 'moores', NULL, 'A Treatment Planning System (TPS) capable of consuming a radiation therapy treatment plan with static, non-MLC, treatment beams.', 'BASIC_STATIC_BEAM_CONSUMER', 'Basic Static Beam Consumer ');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1238, '2013-08-05 16:13:39.916415', 'moores', NULL, 'A Treatment Planning System (TPS) capable of producing a radiation therapy treatment plan with non-MLC arc treatment beams.', 'ARC BEAM PRODUCER', 'Arc Beam Producer ');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1239, '2013-08-05 16:14:57.102076', 'moores', NULL, 'A Treatment Planning System (TPS) capable of consuming a radiation therapy treatment plan with non-MLC arc treatment beams.', 'ARC_BEAM_CONSUMER', 'Arc Beam Consumer ');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1240, '2013-08-05 16:15:42.165084', 'moores', NULL, 'A Treatment Planning System (TPS) capable of producing a radiation therapy treatment plan with MLC arc treatment beams.', 'MLC_ARC_BEAM_PRODUCER', 'MLC Arc Beam Producer ');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1265, '2013-08-05 17:50:58.405366', 'moores', NULL, '', 'BASIC_STATIC_MLC_BEAM_CONSUMER', 'Basic Static MLC Beam Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1241, '2013-08-05 16:18:29.859298', 'moores', NULL, 'A Treatment Planning System (TPS) capable of consuming a radiation therapy treatment plan with MLC arc treatment beams.', 'MLC_ARC_BEAM_CONSUMER', 'MLC Arc Beam Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1242, '2013-08-05 16:19:10.838125', 'moores', NULL, 'A Treatment Planning System (TPS) capable of producing a radiation therapy treatment plan with conformal arc treatment beams.', 'CONFORMAL_ARC_BEAM_PRODUCER', 'Conformal Arc Beam Producer ');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1244, '2013-08-05 16:22:45.541513', 'moores', NULL, 'A Treatment Planning System (TPS) capable of producing a radiation therapy treatment plan with static treatment beams using physical wedges.', 'HARD_WEDGE_BEAM_PRODUCER', 'Hard Wedge Beam Producer ');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1246, '2013-08-05 16:24:51.503899', 'moores', NULL, 'A Treatment Planning System (TPS) capable of producing a radiation therapy treatment plan with static treatment beams using virtual wedges.', 'VIRTUAL_WEDGE_BEAM_PRODUCER', 'Virtual Wedge Beam Producer ');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1266, '2013-08-30 23:22:00.898367', 'lynn', NULL, 'The Service Finder actor submits queries to the Care Services InfoManager, who returns the result(s) in a response document. Queries may be expressed by invoking “stored” queries or (optionally) by submitting well-formed ad hoc XQuery queries. Service Finder actors who support the FreeBusy option may submit a FreeBusy query to a Service Availability actor who will reply with a vFREEBUSY response.', 'SERVICE_FINDER', 'Service Finder');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1250, '2013-08-05 16:35:45.710414', 'moores', NULL, 'A Treatment Planning System (TPS) capable of consuming a radiation therapy treatment plan with static treatment beams using motorized wedges.', 'MOTORIZED_WEDGE_BEAM_CONSUMER', 'Motorized Wedge Beam Consumer ');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1251, '2013-08-05 16:36:43.775855', 'moores', NULL, 'A Treatment Planning System (TPS) capable of producing a radiation therapy treatment plan with static electron treatment beams.', 'STATIC_ELECTRON_BEAM_PRODUCER', 'Static Electron Beam Producer ');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1252, '2013-08-05 16:37:19.198871', 'moores', NULL, 'A Treatment Planning System (TPS) capable of consuming a radiation therapy treatment plan with static electron treatment beams.', 'STATIC_ELECTRON_BEAM_CONSUMER', 'Static Electron Beam Consumer ');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1253, '2013-08-05 16:37:57.830033', 'moores', NULL, 'A Treatment Planning System (TPS) capable of producing a radiation therapy treatment plan with step & shoot IMRT treatment beams.', 'STEP_SHOOT_BEAM_PRODUCER', 'Step & Shoot Beam Producer ');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1256, '2013-08-05 16:47:25.626228', 'moores', NULL, 'A Treatment Planning System (TPS) capable of consuming a radiation therapy treatment plan with sliding window IMRT treatment beams.', 'SLIDING_WINDOW_BEAM_CONSUMER', 'Sliding Window Beam Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1258, '2013-08-05 16:48:38.37335', 'moores', NULL, 'A Treatment Planning System (TPS) capable of consuming a radiation therapy treatment plan with VMAT/IMAT IMRT treatment beams.', 'IMAT_VMAT_BEAM_CONSUMER', 'IMAT/VMAT Beam Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1260, '2013-08-05 16:49:57.886694', 'moores', NULL, 'A Treatment Planning System (TPS) capable of consuming a radiation therapy treatment plan with static, stereotactic treatment beams.', 'STEROTACTIC_BEAM_CONSUMER', 'Stereotactic Beam Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1262, '2013-08-05 16:51:19.3063', 'moores', NULL, 'A Treatment Planning System (TPS) capable of consuming a radiation therapy treatment plan with stereotactic arc treatment beams.', 'STEREOTACTIC_ARC_BEAM_CONSUMER', 'Stereotactic Arc Beam Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1243, '2013-08-05 16:19:46.161989', 'moores', NULL, 'A Treatment Planning System (TPS) capable of consuming a radiation therapy treatment plan with conformal arc treatment beams.', 'CONFORMAL_ARC_BEAM_CONSUMER', 'Conformal Arc Beam Consumer ');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1245, '2013-08-05 16:23:51.397756', 'moores', NULL, 'A Treatment Planning System (TPS) capable of consuming a radiation therapy treatment plan with static treatment beams using physical wedges.', 'HARD_WEDGE_BEAM_CONSUMER', 'Hard Wedge Beam Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1248, '2013-08-05 16:33:20.385433', 'moores', NULL, 'A Treatment Planning System (TPS) capable of consuming a radiation therapy treatment plan with static treatment beams using virtual wedges.', 'VIRTUAL_WEDGE_BEAM_CONSUMER', 'Virtual Wedge Beam Consumer ');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1249, '2013-08-05 16:34:27.048316', 'moores', NULL, 'A Treatment Planning System (TPS) capable of producing a radiation therapy treatment plan with static treatment beams using motorized wedges.', 'MOTORIZED_WEDGE_BEAM_PRODUCER', 'Motorized Wedge Beam Producer ');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1255, '2013-08-05 16:46:29.122359', 'moores', NULL, 'A Treatment Planning System (TPS) capable of producing a radiation therapy treatment plan with sliding window IMRT treatment beams.', 'SLIDING_WINDOW_BEAM_PRODUCER', 'Sliding Window Beam Producer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1257, '2013-08-05 16:48:02.430691', 'moores', NULL, 'A Treatment Planning System (TPS) capable of producing a radiation therapy treatment plan with VMAT/IMAT IMRT treatment beams.', 'IMAT_VMAT_BEAM_PRODUCER', 'IMAT/VMAT Beam Producer ');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1259, '2013-08-05 16:49:16.333449', 'moores', NULL, 'A Treatment Planning System (TPS) capable of producing a radiation therapy treatment plan with static, stereotactic treatment beams.', 'STEROTACTIC_BEAM_PRODUCER', 'Stereotactic Beam Producer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1261, '2013-08-05 16:50:38.09361', 'moores', NULL, 'A Treatment Planning System (TPS) capable of producing a radiation therapy treatment plan with stereotactic arc treatment beams.', 'STEROTACTIC_ARC_BEAM_PRODUCER', 'Stereotactic Arc Beam Producer ');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1263, '2013-08-05 16:52:01.780927', 'moores', NULL, 'An application providing radiation oncology management services and capable of consuming treatment plans with any of the above treatment techniques.', 'TREATMENT_MANAGEMENT_SYSTEM', 'Treatment Management System (TMS)');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1254, '2013-08-05 17:54:23.47401', 'moores', NULL, 'A Treatment Planning System (TPS) capable of consuming a radiation therapy treatment plan with step & shoot IMRT treatment beams.', 'STEP_SHOOT_BEAM_CONSUMER', 'Step & Shoot Beam Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1268, '2013-08-19 20:23:04.999147', 'swillis', NULL, 'TBD', 'PLAN_OF_CARE_MGR', 'Plan of Care Manager');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1269, '2013-08-19 20:24:22.410863', 'swillis', NULL, 'TBD', 'SCREENING_RQSTR', 'Screening Requester');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1270, '2013-08-19 20:25:35.029168', 'swillis', NULL, 'TBD', 'CARE_SUMMARY_GENTR', 'Care Summary Generator');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1271, '2013-08-23 15:47:13.047919', 'moores', NULL, 'The Metadata Consumer is responsible for the importation of metadata created by the Metadata Source. The Metadata Consumer can optionally query the Metadata Source for a list of Data Elements matching a selection criteria.
', 'METADATA_CONSUMER', 'Metadata Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1272, '2013-08-23 15:47:47.291941', 'moores', NULL, 'The Metadata Source is responsible for creation of the Data Element list matching a selection criteria and the creation of metadata for a selected Data Element per request from the Metadata Consumer.  The Metadata Source is associated with a metadata registry.', 'METADATA_SOURCE', 'Metadata Source');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1273, '2013-08-23 17:34:56.786375', 'moores', NULL, 'The Research Information Consumer is responsible for the retrieval of a list of potential research studies or of eligibility criteria.', 'RESEARCH_INFO_CONS', 'Research Information Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1275, '2013-08-23 20:44:46.195127', 'moores', NULL, 'This Form Receiver CDA Exporter receives data submitted through the Submit Form Transaction (ITI-35), transforms that data to create a CDA  document,  and shares that newly created CDA document with a Content Consumer. ', 'FORM_RCVR_CDA_EXPORTER', 'Form Receiver CDA Exporter');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1276, '2013-08-23 20:45:18.416733', 'moores', NULL, 'This Form Receiver Message Exporter receives data submitted through the Submit Form Transaction (ITI-35), transforms that data to an HL7 message and sends that message to an Information Recipient. ', 'FORM_RCVR_MSG_EXPORTER', 'Form Receiver Message Exporter');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1280, '2013-09-18 20:09:32.458729', 'moores', NULL, 'The Information Source Actor is responsible for creating and transmitting an HL7 V2.5.1 message to an Information Recipient.', 'INFO_SRC_HL7', 'Information Source (HL7)');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1281, '2013-09-18 20:10:20.814542', 'moores', NULL, 'The Information Recipient Actor is responsible for receiving the HL7 V2.5.1 message from an Information Source or from a Form Receiver Message Exporter.', 'INFO_RECIPIENT_HL7', 'Information Recipient (HL7)');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1267, '2013-08-30 23:22:36.014326', 'lynn', NULL, 'The InfoManager actor has two roles. The InfoManager maintains a local content cache that represents cross-referenced data from one or more Care Services Directory actors. The InfoManager periodically refreshes this cache by querying Directory actors for updated content. The InfoManager’s other role is to process inbound queries from Service Finder actors. These queries are executed against the cached content. Results from an inbound query are returned to the Service Finder actor in a response document.', 'CARE_SERV_INFOMGR', 'Care Services InfoManager');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1278, '2013-08-30 23:23:33.832004', 'lynn', NULL, 'The Directory actor is responsible for returning an XML document in response to a refresh request from a Care Services InfoManager. The response document contains content which has been inserted or updated in the Directory since the last refresh and is expressed in the XML format defined by the CSD profile’s XML schema.', 'CARE_SERVICES_DIR', 'Care Services Directory');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1303, '2015-05-28 16:28:29.500714', 'moores', NULL, 'Referenced in PCC Remote Monitoring Supplement. Have not yet found the formal definition.', 'DEV_OBS_SOURCE', 'Device Observation Source');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1279, '2013-08-30 23:23:59.930843', 'lynn', NULL, 'the Service Availability actor responds to vFREEBUSY requests for busy time for a provider or service at a specified facility. The format of the request and response is defined by the IETF CalDAV specification (RFC 4791).', 'SERVICE_AVAIL', 'Service Availability');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1283, '2014-07-31 16:18:36.694695', 'lynn', NULL, 'Actor that can perform Access Control decision, evaluating requests for authorization. The result of this evaluation is the creation of an Authorization Decision that certifies the decision made.', 'AUTH_DECISIONS_MGR', 'Authorization Decisions Manager');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1284, '2014-07-31 16:19:21.830899', 'lynn', NULL, 'This actor queries for Authorizations Decision related to the Requester Entity before disclosing specific documents. An Authorization Decision is stored and managed by the Authorization Decisions Manager actor and certifies that a decision was made by a trustable actor. ', 'AUTH_DECISIONS_VERIF', 'Authorization Decisions Verifier');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1285, '2014-07-31 18:10:32.364182', 'lynn', NULL, 'Searches for current patient locations.', 'PAT_LOC_TRACKING_CONS', 'Patient Location Tracking Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1286, '2014-07-31 18:11:11.731578', 'lynn', NULL, 'Provides updated patient locations.', 'PAT_LOC_TRACKING_SUPP', 'Patient Location Tracking Supplier');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1287, '2014-07-31 18:11:40.608279', 'lynn', NULL, 'Manages patient locations within an enterprise.', 'PAT_LOC_TRACKING_MGR', 'Patient Location Tracking Manager');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1288, '2014-08-06 21:47:42.355778', 'lynn', NULL, 'A system responsible for the generation of patient demographic and visit information. It registers new patients and provides updates.', 'PAT_REGISTRATION_SRC', 'Patient Registration Source');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1289, '2014-08-06 21:48:06.685415', 'lynn', NULL, 'An information system responsible for consuming patient appointment information. It updates its system with the appointment information and statuses.', 'PAT_REGISTRATION_CONS', 'Patient Registration Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1290, '2014-08-06 21:48:37.097323', 'lynn', NULL, 'A system responsible for receiving DICOM SOP Instances, storing those SOP Instances, and the ability to present them for viewing to the user. ', 'IMG_STORAGE-DISPLAY', 'Image Storage/Display');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1291, '2014-08-06 21:49:32.897032', 'lynn', NULL, 'An information system responsible for consuming patient appointment information. It updates its system with the appointment information and statuses.', 'APPT_CONSUMER', 'Appointment Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1292, '2014-08-12 17:57:46.685941', 'psherman', NULL, 'The Alert Consumer (ACON) actor receives the alert from the Alert Reporter (AR) and uses the alert information strictly as a consumer of the alert being raised.  There is no implementation requirement for how the ACON ultimately uses the alert information.', 'ACON', 'Alert Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1293, '2014-08-14 16:28:22.101649', 'psherman', NULL, 'The Device Management Information Reporter (DMIR) produces observations.  The Device Management Information Reporter (DMIR) may also be an observation transaction sending actor in other IHE PCD profiles, such as a DEC DOR, an ACM AR, or an IPEC DOR.  If that is the case then the observations defined in this document may be included in existing observation content for those profiles without adoption of this profile, unless the destination to which the observations are being sent is a CMMS and not an EMR/EHR system.  If that the case then this profile should be implemented.', 'DMIR', 'Device Management Information Reporter');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1294, '2014-08-14 16:32:18.032394', 'psherman', NULL, 'The DMIC is a new and distinct destination actor and is likely to be a Computerized Maintenance Management System (CMMS), or more specifically a Clinical Equipment Management System (CEMS), but may also be an actor in a different profile (DEC DOC, ACM AM, IPEC DOC).  ', 'DMIC', 'Device Management Information Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1295, '2014-08-14 18:29:58.159011', 'psherman', NULL, 'The LOR is likely to be a Location Services system (LS) also recognized by the underlying technology used for equipment and people tracking, such as Radio Frequency Identification (RFID) or Real Time Location Services (RTLS), but may also be an actor in a different profile (DEC DOR, ACM AR, IPEC DOR), assuming the location tracking and reporting capability is embedded into the medical device or the location observation is merged with the medical device data in a gateway system prior to it being sent to the observation consumer', 'LOR', 'Location Observation Reporter');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1296, '2014-08-14 18:32:36.256063', 'psherman', NULL, 'The LOC may also be an actor in a different profile (DEC DOC, ACM AM, IPEC DOC).  It is highly likely that the Location Observation Consumer (LOC) may also be an observation transaction receiving actor in other IHE PCD profiles.  If the observation is simply to be recorded it is likely to be a DEC DOC or IPEC DOC actor.  If the observation is to be acted upon it is likely to be an ACM AM actor.  If the location observation is to be used for equipment management the LOC actor is likely to be a MEMDMC DMIC actor (a CMMS). ', 'LOC', 'Location Observation Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (71, '2014-11-25 10:39:20.823679', 'jlabbe', NULL, '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 (37, '2014-11-25 10:39:21.857', 'jlabbe', NULL, '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 (45, '2014-11-25 10:39:20.596181', 'jlabbe', NULL, '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 (36, '2014-11-25 10:39:21.760754', 'jlabbe', NULL, '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 (67, '2014-11-25 10:39:21.653246', 'jlabbe', NULL, '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 (27, '2014-11-25 10:39:21.508045', 'jlabbe', NULL, '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 (1298, '2015-04-14 09:54:44.010341', 'lynn', NULL, 'Stores DICOM objects without guarantee of long-term storage.', 'IMG_MANAGER', 'Image Manager');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1312, '2015-06-19 20:20:08.605334', 'lynn', NULL, 'Acquisition Modality Importer in U-EYECARE - Model II', 'AMI_Model_II', 'Acquisition Modality Importer in U-EYECARE - Model II');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1307, '2015-06-19 23:53:23.725346', 'lynn', NULL, 'DSS Order Filler in U-EYECARE - Model III', 'OF_Model_III', 'DSS Order Filler in U-EYECARE - Model III');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1311, '2015-06-19 20:19:23.634164', 'lynn', NULL, 'Acquisition Modality in U-EYECARE Model II', 'MOD_Model_II', 'Acquisition Modality in U-EYECARE Model II');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1301, '2015-09-08 16:17:08.441175', 'moores', NULL, 'The Clinical Mapper selects appropriate mappings for terms that it has been requested to map.

First seen: PCC Clinical Mapping Supplement, May 2015
', 'CLINICAL_MAPPER', 'Clinical Mapper');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (119, '2015-06-19 20:20:27.815823', 'lynn', false, 'A system that interfaces to a non-DICOM ready modality in order to integrate that modality into the Eye Care workflow.', 'AMI', 'Acquisition Modality Importer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1305, '2015-06-19 23:21:13.263925', 'lynn', NULL, 'DSS Order Filler Actor in U-EYECARE - Model I', 'OF_Model_I', 'DSS Order Filler Actor in U-EYECARE - Model I');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1308, '2015-06-19 23:24:29.800063', 'lynn', NULL, 'Image Manager-Image Archive in U-EYECARE - Model I', 'IM_Model_I', 'Image Manager-Image Archive in U-EYECARE - Model I');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1310, '2015-06-19 23:24:52.841226', 'lynn', NULL, 'Image Manager-Image Archive in U-EYECARE Model III', 'IM_Model_III', 'Image Manager-Image Archive in U-EYECARE Model III');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1306, '2015-06-19 23:26:06.577426', 'lynn', NULL, 'DSS Order Filler in U-EYECARE - Model II', 'OF_Model_II', 'DSS Order Filler in U-EYECARE - Model II');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1326, '2015-12-09 00:08:36.822611', 'lynn', NULL, 'Manages task instances in a worklist and provides associated query access and notifications', 'TASK_MANAGER', 'Task Manager');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1313, '2015-07-29 00:40:51.311841', 'lynn', NULL, 'Search for syslog and ATNA audit messages based upon queries using Syslog metadata and ATNA audit message content. Subsequent processing is not defined.', 'AUDIT_CONSUMER', 'Audit Consumer');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1315, '2015-07-29 01:00:45.392434', 'lynn', NULL, 'This actor receives alerts from the Alert Reporter and collects status events related to the dissemination of the alert.', 'ALERT_AGGREGATOR', 'Alert Aggregator');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (114, '2015-08-10 22:32:22.021351', 'psherman', false, 'The Alert Manager (AM) actor receives the alerts from the Alert Reporter (AR), potentially analyzes the alert, and dispatches the alert to the Alert Communicator (AC), and optionally, provides the alert to the Alert Archiver (AA) or Alert Consumer (ACON) upon subscription.', 'ALRT_MGR', 'Alert Manager');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (113, '2015-08-10 23:05:58.052932', 'lynn', false, 'The Alert Reporter originates the alert (an alarm, either physiological or technical, or an advisory). ', 'ALERT_RPT', 'Alert Reporter');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1317, '2015-08-11 23:31:14.255897', 'lynn', NULL, 'This actor consumes standard CDA summary of care documents and creates standard patient level quality reports. Additionally, this actor may consume patient-level quality reports and produce the corresponding aggregate-level quality report for an electronic clinical quality measure.', 'REPORT_ASSEMBLER', 'Report Assembler');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1318, '2015-08-12 00:09:05.318571', 'lynn', NULL, 'The Content Data Structure Creator creates a message structure definition that may be employed by a Content Creator to develop profile-conformant messages for exchange with a Content Consumer. ', 'CONTENT_DATA_STRUCTURE_CREATOR', 'Content Data Structure Creator');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1300, '2015-09-08 16:12:41.814127', 'moores', NULL, 'The Clinical Mapping Requestor identifies terms that need to be mapped and requests mappings for them.

First seen: PCC TF Clinical Mapping Supplement, May 2015', 'CLINICAL_MAPPING_REQUESTOR', 'Clinical Mapping Requestor');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1319, '2015-09-08 17:48:19.688948', 'moores', NULL, 'This actor is the Personal Healthcare Devices (PHD) generating sensor data', 'SENSOR_DATA_SRC', 'Sensor Data Source');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1320, '2015-09-10 17:07:29.07925', 'lynn', NULL, 'DAF Query Requestor - responsible for Sending the query and receiving the response from the Responding application.

First defined:  DAF Implementation Guide, Sep 2015, PCC US National Extension', 'QUERY_REQUESTOR', 'Query Requestor');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1321, '2015-09-10 17:08:00.336805', 'lynn', NULL, 'DAF Query Responder - responsible for Receiving the query request, processing the query request, creating the query response and sending the query response.

First defined:  DAF Implementation Guide, Sep 2015, PCC US National Extension', 'QUERY_RESPONDER', 'Query Responder');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1322, '2015-09-25 20:39:00.278873', 'lynn', NULL, 'This actor filters audit records that have been received and forwards selected audit records to an Audit Record Repository.

Added to the ATNA profile in Sept 2015 in CP-ITI-872', 'AUDIT_RECORD_FORWARDER', 'Audit Record Forwarder');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1324, '2015-12-01 16:42:20.717848', 'epoiseau', NULL, 'eCR provider is a grouping of the actors IHE Document Registry, IHE Document Repository, and IHE X-Service Provider. eCR Provider actor shall be deployed as a secure node.', 'eCR Provider', 'eCR Provider');
INSERT INTO tf_actor (id, last_changed, last_modifier_id, combined, description, keyword, name) VALUES (1327, '2015-12-09 00:08:59.089981', 'lynn', NULL, 'Claims, performs and updates tasks managed by a Task Manager', 'TASK_PERFORMER', 'Task Performer');


--
-- Name: tf_actor_keyword_key; Type: CONSTRAINT; Schema: public; Owner: gazelle; Tablespace: 
--

ALTER TABLE ONLY tf_actor
    ADD CONSTRAINT tf_actor_keyword_key UNIQUE (keyword);


--
-- Name: tf_actor_pkey; Type: CONSTRAINT; Schema: public; Owner: gazelle; Tablespace: 
--

ALTER TABLE ONLY tf_actor
    ADD CONSTRAINT tf_actor_pkey PRIMARY KEY (id);


--
-- Name: uk_fpb6vpa9bnw6cjsb1pucuuivw; Type: CONSTRAINT; Schema: public; Owner: gazelle; Tablespace: 
--

ALTER TABLE ONLY tf_actor
    ADD CONSTRAINT uk_fpb6vpa9bnw6cjsb1pucuuivw UNIQUE (keyword);


--
--

--
--





--
-- Name: tf_affinity_domain; Type: TABLE; Schema: public; Owner: gazelle; Tablespace: 
--

CREATE TABLE tf_affinity_domain (
    id integer NOT NULL,
    description character varying(255),
    keyword character varying(255),
    label_to_display character varying(255)
);


ALTER TABLE public.tf_affinity_domain OWNER TO gazelle;

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

INSERT INTO tf_affinity_domain (id, description, keyword, label_to_display) VALUES (1, 'IHE', 'IHE', 'IHE');
INSERT INTO tf_affinity_domain (id, description, keyword, label_to_display) VALUES (2, 'French Extension for PAM', 'PAM_FR', 'PAM FR');
INSERT INTO tf_affinity_domain (id, description, keyword, label_to_display) VALUES (3, 'German extension', 'IHE_DE', 'IHE Germany');


--
-- Name: tf_affinity_domain_keyword_key; Type: CONSTRAINT; Schema: public; Owner: gazelle; Tablespace: 
--

ALTER TABLE ONLY tf_affinity_domain
    ADD CONSTRAINT tf_affinity_domain_keyword_key UNIQUE (keyword);


--
-- Name: tf_affinity_domain_pkey; Type: CONSTRAINT; Schema: public; Owner: gazelle; Tablespace: 
--

ALTER TABLE ONLY tf_affinity_domain
    ADD CONSTRAINT tf_affinity_domain_pkey PRIMARY KEY (id);


--
-- Name: uk_9lriehprhbeo91cxqn7rqwjsy; Type: CONSTRAINT; Schema: public; Owner: gazelle; Tablespace: 
--

ALTER TABLE ONLY tf_affinity_domain
    ADD CONSTRAINT uk_9lriehprhbeo91cxqn7rqwjsy UNIQUE (keyword);


--
--

--
--





--
-- Name: tf_domain; Type: TABLE; Schema: public; Owner: gazelle; Tablespace: 
--

CREATE TABLE tf_domain (
    id integer NOT NULL,
    last_changed timestamp without time zone,
    last_modifier_id character varying(255),
    description character varying(2048),
    keyword character varying(128) NOT NULL,
    name character varying(128)
);


ALTER TABLE public.tf_domain OWNER TO gazelle;

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

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 (16, '2012-11-20 13:45:21.602', 'epoiseau', 'Dental Domain', 'DENT', 'Dental');
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');
INSERT INTO tf_domain (id, last_changed, last_modifier_id, description, keyword, name) VALUES (12, '2010-03-04 23:50:50.065', 'jgilbert', 'Domain that holds all the Australian defined profiles', 'AUS', 'Australia');
INSERT INTO tf_domain (id, last_changed, last_modifier_id, description, keyword, name) VALUES (13, '2010-10-10 11:21:26.362', 'epoiseau', 'Domain specific to the epSOS european project. Please see http://www.epsos.eu for more information on the epSOS project. ', 'epSOS', 'epSOS');
INSERT INTO tf_domain (id, last_changed, last_modifier_id, description, keyword, name) VALUES (15, '2012-08-16 00:30:13.222', 'lynn', 'Health Story Project - Consolidated CDA', 'HSP', 'Health Story Project - Consolidated CDA');
INSERT INTO tf_domain (id, last_changed, last_modifier_id, description, keyword, name) VALUES (18, '2014-01-10 17:36:30.401479', 'lynn', 'Entered as a holding place for IHE USA New Directions.', 'NewD', 'New Directions');
INSERT INTO tf_domain (id, last_changed, last_modifier_id, description, keyword, name) VALUES (14, '2011-03-17 10:03:09.551', 'epoiseau', 'Domain for Pharmacy', 'PHARM', 'Pharmacy');
INSERT INTO tf_domain (id, last_changed, last_modifier_id, description, keyword, name) VALUES (9, '2011-08-03 16:51:19.955', 'lynn', '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 and Public Health');
INSERT INTO tf_domain (id, last_changed, last_modifier_id, description, keyword, name) VALUES (19, '2015-10-05 22:20:07.168225', 'lynn', 'A domain designed to hold initiatives found in the US.', 'US_Initiatives', 'US Initiatives');
INSERT INTO tf_domain (id, last_changed, last_modifier_id, description, keyword, name) VALUES (20, '2015-11-30 15:58:07.770594', 'epoiseau', '', 'cdaefa', ' CDA für die elektronische Fallakte.');


--
-- Name: tf_domain_keyword_key; Type: CONSTRAINT; Schema: public; Owner: gazelle; Tablespace: 
--

ALTER TABLE ONLY tf_domain
    ADD CONSTRAINT tf_domain_keyword_key UNIQUE (keyword);


--
-- Name: tf_domain_pkey; Type: CONSTRAINT; Schema: public; Owner: gazelle; Tablespace: 
--

ALTER TABLE ONLY tf_domain
    ADD CONSTRAINT tf_domain_pkey PRIMARY KEY (id);


--
-- Name: uk_436tct1jl8811q2xgd8bjth9q; Type: CONSTRAINT; Schema: public; Owner: gazelle; Tablespace: 
--

ALTER TABLE ONLY tf_domain
    ADD CONSTRAINT uk_436tct1jl8811q2xgd8bjth9q UNIQUE (keyword);


--
--

--
--





--
-- Name: tf_integration_profile; Type: TABLE; Schema: public; Owner: gazelle; Tablespace: 
--

CREATE TABLE tf_integration_profile (
    id integer NOT NULL,
    last_changed timestamp without time zone,
    last_modifier_id character varying(255),
    description character varying(4096),
    keyword character varying(32) NOT NULL,
    name character varying(128) NOT NULL,
    integration_profile_status_type_id integer,
    documentsection integer
);


ALTER TABLE public.tf_integration_profile OWNER TO gazelle;

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

INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (38, '2013-05-17 21:50:56.519944', 'lynn', '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.', 'DEPRECATED:XDS.a', 'DEPRECATED: Cross-Enterprise Clinical Documents Share (XDS.a)', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (253, '2013-07-11 22:48:44.415324', 'lynn', 'The Cross-Community Access for Imaging (XCA-I) Integration Profile specifies actors and transactions to query and retrieve patient-relevant medical imaging data being held by other communities. ', 'XCA-I', 'Cross-Community Access for Imaging', 5, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (80, '2013-05-17 21:49:29.16193', 'lynn', '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.', 'DEPRECATED:DRR', 'DEPRECATED:Document-based Referral Request', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (1, '2012-11-28 08:54:35.73753', 'epoiseau', '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', 5, 889);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (115, '2010-07-27 17:09:55.971', 'lynn', 'Anatomic Pathology Reporting to Public Health', 'ARPH', 'Anatomic Pathology Reporting to Public Health', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (293, '2012-07-27 23:35:12.324', 'moores', 'The existing IHE profile Retrieve Process for Execution acts as a general framework which provides messaging interactions, which could be used to convey the necessary information.  The proposed Research Content profiles utilize RPE as a framework and solve the issues of exchanging detailed content specific to the research domain.', 'CRPC', 'Clinical Research Process Content', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (300, '2012-08-20 19:55:28.98', 'moores', 'Health Story: History and Physical CDA', 'HSP-HP', 'HSP History and Physical', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (299, '2012-08-20 19:54:30.937', 'moores', 'Health Story Project Consultation CDA:  Consultation Note', 'HSP-CN', 'HSP Consultation Note', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (240, '2010-07-27 10:19:31.616', 'epoiseau', 'The epSOS consent service provides operations for the remote management of consents (e. g. giving and revoking consent from abroad). ', 'epSOS Consent Service', 'epSOS Consent Service', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (88, '2009-07-02 13:19:57.751', 'admin', '', 'PERF', 'CT/MR Perfusion with Imaging Contrast', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (242, '2010-10-22 09:49:58.597', 'epoiseau', 'This is the content profile describing the content of the CDA document for Consent.', 'epSOS-eConsent Document', 'epSOS Consent Document', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (243, '2010-11-19 14:08:37.649', 'epoiseau', 'This profile is for handling the security aspects of epSOS', 'epSOS Security', 'epSOS Security', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (311, '2013-06-26 12:43:03.277442', 'epoiseau', 'Stereotactic Mammography Image (SMI) is designed to provide faithful and complete storage from Acquisition Modalities to Image Managers/Image Archives and retrieval by Image Displays of DICOM stereotactic breast projection x-ray image data, with sufficient display capability to allow optimal visualization of images for the purpose of consultation or second opinion.', 'SMI', 'Stereotactic Mammography Image', 4, 9077);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (48, '2012-11-20 14:12:09.222', 'epoiseau', '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, 1074);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (112, '2013-05-17 23:14:32.000986', 'lynn', 'This profile describes the content to be used in automating the data captured for vital records purposes such as for the U.S. Standard Certificate of Live Birth and the U.S. Standard Report of Fetal Death. Health at Birth Summary (HBS) content contains a summary of all the information impacting on the newborn''s health status evaluation as presented in the birth certificate.  Child Growth Summary. (CGS) content represents information about the child''s development (medical and social conditions) that can be submitted to health authorities for possible intervention or general epidemiological studies.', 'DEPRECATED:MCH2010', 'DEPRECATED: Mother and Child Health', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (92, '2012-11-27 13:47:40.235155', 'epoiseau', '', 'MPQ', 'Multi-Patient Queries', 5, 988);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (6, '2013-05-17 21:55:19.773488', 'lynn', 'The Displayable Reports Profile describes mechanisms for the transmission of PDF formatted 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).', 'DEPRECATED:DRPT2009', 'DEPRECATED: Displayable Reports', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (114, '2013-05-17 23:15:59.733188', 'lynn', 'Retrieve Protocol for Execution was in Trial implementation in 2009-2010 cycle, but was replaced by a more generic profile called Retrieve Process for Execution (RPE) in the 2010-2011 cycle.', 'DEPRECATED:RPE2010', 'DEPRECATED: Retrieve Protocol for Execution', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (219, '2010-07-28 08:09:33.514', 'lnelson', 'The Image-Enabled Office (IEO) Profile specifies the integration of an imaging suite (modalities, storage server, and workstations) with an electronic health record system in an ambulatory office setting.  This is a fully bi-directional integration, including ordering/scheduling of an imaging exam, status reporting for that exam, report creation, and web-based imaging exam review integration.  ', 'IEO', 'Image-Enabled Office', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (221, '2010-08-02 10:04:00.11', 'jungers', '', 'PPVS', 'Postpartum Visit Summary', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (222, '2010-08-02 10:41:09.708', 'jungers', '', 'NDS', 'Newborn Discharge Summary', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (213, '2010-08-02 12:54:52.985', 'lynn', 'Allows the creation of a scheduling information exchange between a master appointment schedule and a working provider, recognizing that often the master schedule and the personnel who operate it may not be readily available at the provider''s location.', 'ECAS', 'Eye Care Appointment Scheduling', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (388, '2015-11-23 09:39:32.208187', 'aboufahj', 'Profile SMP for testing the CP epSOS-SMP-v0.5 from EXPAND project', 'SMP', 'SMP', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (389, '2015-12-01 16:40:43.297035', 'epoiseau', '', 'eCR', 'eCR', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (218, '2010-08-04 14:47:05.823', 'lnelson', 'A resting ECG is the most widely prescribed diagnostic cardiac test.  Electrocardiographs, unlike other cardiology modality devices, have traditionally used proprietary communication protocols making device interoperability and clinical workflow very difficult. The Resting ECG Workflow (REWF) integration profile specifies actors and transactions that allow users to register a patient, order the test, perform the test (acquiring the waveforms), and interpret the test results (reporting) in an interoperable way. The Resting ECG Workflow profile will also handle unordered tests, urgent cases, and ECGs acquired in both hospital and office settings.', 'REWF', 'Resting Electrocardiography Workflow', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (225, '2010-08-16 17:26:06.012', 'lynn', 'The Chest X-Ray CAD Display Profile specifies how DICOM Chest CAD evidence objects are applied for display. It describes how Image Displays make use of the content in the Chest CAD SR SOP instance to render the CAD marks on projection radiographs of the chest encoded as 75 CR, DX or Secondary Capture images.', 'CXCAD', 'Chest X-Ray CAD Display', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (331, '2013-09-30 13:29:15.597882', 'aboufahj', 'This is the content profile that describes the content of the CDA HCER document', 'epSOS HCER Document', 'epSOS HCER Document', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (229, '2011-08-12 21:32:58.533', 'lynn', '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', 5, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (27, '2011-08-17 21:17:18.441', 'lynn', 'This entry represents the DEC profile as it was documented in the PCD TF in 2009.  In 2010, the PDC actor was removed from DEC and brought in through grouping.  The new profile actor/option structure is entered under the DEC profile entry in gazelle.', 'DEC2009', 'DEPRECATED: 2009 Device Enterprise Communication', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (292, '2013-05-28 22:00:12.28908', 'lynn', 'The NANI Profile describes the content needed to communicate a timely notification of birth to public health to be used by Early Hearing Detection and Intervention (EHDI) screening programs. ', 'NANI', 'Newborn Admission Notification Information Summary', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (55, '2013-01-09 12:38:08.707198', 'epoiseau', '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, 7159);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (217, '2010-08-20 14:56:04.025', 'lnelson', 'The Physician Reporting to a Public Health Repository provides a means through which physician office EMR systems can report information on patients with a specific condition to the associated public health registry. This profile includes a mechanism for identifying the patient for which reporting is required and defines the data elements to be retrieved from the EMR and transmitted to the registry. The Trial Implementation is demonstrated for the Cancer Registry.', 'PRPH-Ca', 'Physician Reporting to Public Health - Cancer Registry', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (224, '2010-09-16 18:51:29.032', 'lynn', 'Retrieve Process for Execution (RPE) is a proposed IHE standard for collaborative workflow or collaborative process management involving three main actors: 1/ the manager of process definitions, 2/ the manager of runtime processes and 3/ the performer of process activities.  RPE started as Retrieve Protocol for Execution Profile a proposed automated mechanism for an Electronic Health Record (EHR) to retrieve a complex set of clinical research instructions (a study protocol) from a research sponsor''s Electronic Data Capture (EDC) system and to execute these instructions within the EHR. ', 'RPE', 'Retrieve Process for Execution', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (56, '2013-01-09 12:37:34.028883', 'epoiseau', '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, 7167);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (12, '2013-01-09 12:32:55.147201', 'epoiseau', '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, 6991);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (313, '2013-06-26 12:42:19.711285', 'epoiseau', 'The Invoke Image Display Profile allows the user of an Image Display Invoker, typically a non-image-aware system like an EHR, PHR or RIS, to request the display of studies for a patient, and have the display performed by an image-aware system like an Image Display (PACS).', 'IID', 'Invoke Image Display', 4, 8883);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (78, '2013-05-17 23:09:18.194804', 'lynn', '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.', 'DEPRECATED:APR', 'DEPRECATED: Antepartum Record', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (230, '2011-08-17 21:17:01.674', 'lynn', 'This entry represents how the DEC profile was documented in 2010.  In 2011, the DOF actor was removed, the PCD-02 transaction was removed, and all options were removed', 'DEC2010', 'DEPRECATED: 2010 Device Enterprise Communication', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (357, '2015-04-19 19:22:33.25716', 'aboufahj', 'Profile for testing trillium bridge', 'TrilliumBridge', 'Trillium Bridge', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (23, '2013-05-17 21:55:52.557541', 'lynn', 'This entry represents the actor/option structure of the BPPC profile prior to the publication of the ITI TF in August 2010.   In gazelle, the "BPPC" profile entry contains the updated structure for the profile with only 2 actors - Content Creator and Content Consumer.', 'DEPRECATED:BPPC2009', 'DEPRECATED: Basic Patient Privacy Consents', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (216, '2013-05-17 23:17:10.174995', 'lynn', 'The Redaction Services Profile provides a method for extracting specified data from a document to create a new redacted version of the document which is needed by an external system.', 'DEPRECATED:RSP', 'DEPRECATED: Redaction Services', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (316, '2013-07-26 16:00:03.852389', 'lynn', 'The IUA profile adds authorization information to RESTful transactions.  The IUA actors and behavior will be added to other profiles and transactions that need authorization.', 'IUA', 'Internet User Authorization', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (104, '2013-09-19 21:55:06.649846', 'moores', 'The ED Physician Note is a CDA document that may be submitted to an ED Folder in order to record the care delivered to a patient in the emergency department. The ED physician note is designed to support documentation sufficient to support transfer of care. It is recognized that the specification is not sufficient to document all medicolegal facets of care, and conversely that providers may not capture the entire list of sections, owing to patient presentation, acuity or time constraints. ', 'EDPN', 'ED Physician Note', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (231, '2010-09-23 19:51:29.532', 'jungers', 'Perinatal Workflow', 'PW', 'Perinatal Workflow', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (256, '2011-07-20 16:42:03.713', 'lynn', 'The Document Encryption profile provides a means to encrypt health documents independent of particular transports means, healthcare applications and document types thereby supporting end-to-end confidentiality in heterogeneous workflows and unanticipated workflows. It enables access to documents to be targeted to specific recipients. It addresses the need to protect documents from certain intermediaries in the document exchange path and provides confidentiality to transports that do not have a confidentiality mechanism. 
The Document Encryption profile allows for multiple alternatives for identity and key management which makes it suitable for a rich set of healthcare environments (many of which have a pre-existing key management infrastructure in place). Examples include symmetric keys, certificates, passwords, single and multiple recipients, and out-of-band key acquisition. To cater to these different situations the profile contains hooks to different technical key management methods.
', 'DEN', 'Document Encryption', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (257, '2011-07-20 17:10:52.022', 'lynn', 'The Cross-Community Fetch (XCF) profile defines a single transaction for exchanging medical data between gateways that facilitate multiple dimensions of communication (trust, semantics, encoding, legislation, authority, etc.). The profile is highly inspired by the Cross Gateway Query/Cross Gateway Retrieve transactions and integrates these originally distinct transactions in order to allow for keeping Responding Gateways to remain stateless, controllable, and simple.', 'XCF', 'Cross-Community Fetch', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (271, '2011-08-11 17:13:41.751', 'lynn', 'The Cardiac Imaging Report Content (CIRC) Profile specifies the content structure for a clinical 
report of a cardiology imaging exam, recorded in a DICOM Study.

The CIRC Profile specifies the use of an HL7 Clinical Document Architecture (CDA) format for 
the report. This format supports both the human readable narrative historically used for clinical 
reports, as well as a substantial set of discrete data ', 'CIRC', 'Cardiac Imaging Report Content', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (261, '2011-08-07 20:13:15.66', 'Manny', 'The Infusion Pump Event Communication (IPEC) Profile specifies methods for communicating significant clinical and technical events from a Patient Care Device such as infusion pump to an information system which may present it to a clinical user, acts on it in some way or records it. The information is communicated in a data format similar to that of Device Enterprise Communications (DEC) Profile, but differs in that DEC is mainly used for sampled physiological and technical data at timed, equal intervals, while IPEC is used to communicate significant occurrences which happen at unscheduled times. Infusion Pump Event Communications is also related to Alarm Communications Management (ACM) Profile, except that ACM is designed for physiological alarms and technical alerts to a human actor via portable devices, where IPEC is designed for system-to-system communication for automated recording or tracking occurrences which do not necessarily require urgent attention from a person.', 'IPEC', 'Infusion Pump Event Communication', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (267, '2011-08-09 21:13:25.493', 'jungers', 'The Interfacility Transport Summary contains a record of the “referral summary” usually received during transport.  This document content module is a Transport Record Summary and inherits all header constaints from Transport Record Summary. (1.3.6.1.4.1.19376.1.5.3.1).', 'ITS', 'Interfacility Transport Summary', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (268, '2011-08-12 20:02:36.638', 'lynn', 'This profile details how information is shared during all aspects of patient transport.  Whenever a patient is moved between facilities and care services their information about this specific event needs to travel with them.  The ability to share this information with the transporters, regardless of transport time, is essential to complete patient care.', 'ETS', 'EMS Transport Summary', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (94, '2012-09-04 12:05:55.97', 'epoiseau', 'involves the flow of DICOM images and treatment planning data, from CT scan through dose display, for 3D conformal, external beam radiation therapy', 'BRTO', 'Basic Radiation Therapy Objects', 5, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (74, '2013-01-09 12:42:31.998669', 'epoiseau', '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, 7023);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (356, '2015-04-01 22:25:46.802384', 'lynn', 'The Web-based Image Capture (WIC) Profile provides a simple, lightweight, mobile-friendly mechanism to encode and send captured images, videos and evidence documents from the mobile device to the Image Manager so that these objects can be easily integrated into the rest of the imaging workflow.', 'WIC', 'Web-based Image Capture', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (59, '2013-01-09 12:31:51.143328', 'epoiseau', '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, 6957);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (72, '2008-04-17 12:10:28.789529', '0', 'The Laboratory Barcode Labeling Integration Profile supports this workflow: A robotic system delivers specimen containers pre-identified with a bar coded label, for the specimen collection related to a laboratory test order. This robotic system receives patient, test order and specimen data from another system (HIS, CIS, LIS), and issues a label for each (specimen, container) needed, with the specimen identifier bar coded on the label, and possibly other information printed on this label.  This workflow is supported by two new actors, Label Information Provider (LIP) and Label Broker (LB).  The Label Broker receives label information, and delivers these labels in appropriate operations, and may notify the status of this process. The Label Information Provider is usually grouped with the Order Filler or the Order Placer from the Laboratory TestingWorkflow Integration Profile.  The Label Broker may be notified passively with the labeling instructions or may query the Label Information Provider to get these instructions. This profile addresses only specimen container labeling within the scope of the Laboratory Domain. It does not address labeling workflows in other domains. ', 'LBL', 'Laboratory Specimen Barcode Labeling', 5, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (110, '2009-07-14 09:46:47.719', 'admin', 'Request for Clinical Guidance', 'RCG', 'Request for Clinical Guidance', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (111, '2009-07-14 09:47:27.337', 'admin', 'Immunization Care Plan', 'ICP', 'Immunization Care Plan', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (301, '2012-08-20 19:56:27.648', 'moores', 'Health Story: Progress Note CDA', 'HSP-PN', 'HSP Progress Note', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (302, '2012-08-20 19:57:22.021', 'moores', 'Health Story: Operative Note CDA', 'HSP-ON', 'HSP Operative Note', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (303, '2012-08-20 19:58:20.018', 'moores', 'Health Story: Diagnostics Imaging Report CDA', 'HSP-DIR', 'HSP Diagnostic Imaging Report', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (304, '2012-08-20 19:59:16.15', 'moores', 'Health Story: Discharge Summary CDA', 'HSP-DS', 'HSP Discharge Summary', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (306, '2012-08-20 20:00:51.731', 'moores', 'Health Story: Procedure Note CDA', 'HSP-ProcNote', 'HSP Procedure Note', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (21, '2012-11-28 08:58:32.231252', 'epoiseau', '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', 5, 837);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (29, '2012-11-28 09:06:05.194499', 'epoiseau', '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', 5, 905);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (209, '2010-03-05 02:16:17.062', 'jgilbert', 'ATS 5822:2010 E-health secure message delivery', 'SMD', 'Secure Message Delivery', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (31, '2013-05-17 23:09:51.146736', 'lynn', '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.', 'DEPRECATED:EDES', 'DEPRECATED: Emergency Department Encounter Summary', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (44, '2012-11-28 08:52:54.725448', 'epoiseau', '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', 5, 965);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (358, '2015-04-23 13:52:56.564014', 'epoiseau', 'e-SENS Build Block', 'e-SENS-NREE', 'Non Repudiation Evidence Emitter', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (277, '2011-08-24 17:44:35.832', 'lynn', 'The Displayable Reports Profile specifies transactions supporting the creation, revision, intra/ 
inter-department transmission, and reading of display-ready clinical reports. In the imaging 
procedure context, it provides linkage between the report, the imaging and other evidence of the procedure. The report is provided to actors outside the department for broad distribution (e.g., using other profiles).  
', 'DRPT', 'Displayable Reports', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (84, '2011-08-17 21:25:00.402', 'lynn', 'This profile entry represents the structure of actors and options in the PIV profile as published in 2009 and tested at NA2010.  The documentation was updated in 2010, and the new profile entry, PIV, represents the updated structure.', 'PIV2009', 'DEPRECATED: 2009 Point-of-Care Infusion Verification', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (18, '2013-05-17 21:53:09.317873', 'lynn', '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.', 'DEPRECATED:XDS-I', 'DEPRECATED: Cross-enterprise Document Sharing for Imaging', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (228, '2012-11-20 16:11:12.824', 'epoiseau', 'The document sharing infrastructure provided by XD* allow for the publication and use of clinical documents associated with a patient. This profile allows for a Patient Privacy Policy Domain (e.g., an XDS Affinity Domain to have a number of Patient Privacy Policies that can be acknowledged (aka consent). This allows for more flexibility to support some patient concerns, while providing an important and useful dataset to the healthcare provider. Without BPPC, the XDS profile requires that the administrators of an XDS Affinity Domain creates and agrees to a single document publication and use policy (See ITI TF-1: Appendix L). Such a single XDS Affinity Domain Policy is enforced in a distributed way through the inherent access controls of the systems involved in the XDS Affinity Domain.', 'BPPC', 'Basic Patient Privacy Consents', 5, 931);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (245, '2011-01-08 09:43:04.583', 'epoiseau', 'This integration profile instantiates the interoperability model to the Hospital - basic inpatient scenario', 'HMW', 'Hospital Medication Workflow', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (49, '2012-11-27 13:46:31.707484', 'epoiseau', '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, 1029);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (3, '2013-05-17 21:48:45.144638', 'lynn', '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.b 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.', 'DEPRECATED:NAV', 'DEPRECATED: Notification of Document Availability', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (248, '2013-02-13 17:16:24.698797', 'epoiseau', 'The Pharmacy Prescription Document Profile (PRE) describes the content and format of a prescription document generated during the process in which a health care professional (in most cases, but not necessarily always, a medical specialist or a general practitioner) decides that the patient needs medication. A prescription is an entity that can be seen as an order to anyone entitled to dispense (prepare and hand out) medication to the patient.
Documents created according to this profile are intended to be used in the context of the “Community Prescription and Dispense” Integration Profile (CMPD).', 'PRE', 'Pharmacy Prescription', 4, 5841);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (278, '2011-12-15 12:08:27.742', 'epoiseau', 'The Laboratory Analytical Workflow (LAW) integration profile supports the analytical workflow of IVD test work order steps and their results between IVD analyzers and the systems driving their work (LIS or LAS).', 'LAW', 'Laboratory Analytical Workflow', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (330, '2013-09-30 12:03:22.411302', 'aboufahj', 'This is the content profile that describes the content of the CDA MRO document', 'epSOS MRO Document', 'epSOS MRO Document', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (295, '2012-08-08 23:33:59.012', 'lynn', 'Retrospective Data Query (RDQ) consists of patient specific, user-initiated queries of retrospective data stores of clinical data (i.e., retrospective data) for the purpose of aligning those data under a common time frame with the appropriate resolution to support clinical decision making based on said retrospective data.', 'RDQ', 'Retrospective Data Query', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (307, '2012-08-20 20:01:42.408', 'moores', 'Health Story: Unstructured Document CDA', 'HSP-UnstructuredDoc', 'HSP Unstructured Document', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (113, '2012-09-19 16:30:16.849', 'lynn', 'The Drug Safety Content Profile (DSC) specifies a standard way to generate an adverse event document from EHR data provided in the CDA standard. 

', 'DSC', 'Drug Safety Content', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (212, '2010-03-16 12:01:11.967', 'epoiseau', 'Laboratory Scheduled Workflow'', ''The Laboratory Scheduled Workflow Integration Profile establishes the continuity and integrity of clinical laboratory testing and observation data throughout the healthcare enterprise. It involves a set of transactions, to maintain the consistency of ordering and patient information, to control the conformity of specimens, and to deliver the results at various steps of validation. Some of these transactions are already defined in the IHE Radiology Technical Framework. This profile also enables automation of preanalytical, analytical and post-analytical processes within the laboratory.', 'LSWF', 'Laboratory Scheduled Workflow', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (42, '2012-11-28 08:53:42.738776', 'epoiseau', '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, 1046);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (15, '2013-01-09 12:36:50.388192', 'epoiseau', '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, 7002);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (77, '2013-01-09 12:39:01.506618', 'epoiseau', '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', 5, 7098);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (32, '2013-05-17 23:11:00.138476', 'lynn', '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.', 'DEPRECATED:FSA', 'DEPRECATED: Functional Status Assessment', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (64, '2013-01-09 12:34:43.927424', 'epoiseau', '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, 7048);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (50, '2012-11-28 08:56:17.501572', 'epoiseau', '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 Assertion', 5, 804);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (325, '2015-01-07 21:38:58.456206', 'epoiseau', 'The CSD profile supports queries across related directories containing data about: organizations, facilities, services and providers. Queries against an optional “FreeBusy” service are also supported; this FreeBusy information would support the development of a list of schedulable time slots for providers or services at specific facilities.', 'CSD', 'Care Services Discovery', 4, 9239);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (22, '2012-11-28 08:57:02.505637', 'epoiseau', '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, 955);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (17, '2013-01-09 12:32:20.321741', 'epoiseau', '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, 7163);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (58, '2013-01-09 12:35:31.157331', 'epoiseau', '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, 7006);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (281, '2012-06-28 17:29:00.77', 'lynn', 'Cross-Enterprise Document Reliable Interchange of Images (XDR-I) is a content profile for interchange of images, image reports and other DICOM instances using the ITI Cross-Enterprise Document Reliable Interchange (XDR) Integration Profile. This permits direct image interchange between healthcare systems exchanging DICOM instances and image reports.', 'XDR-I', 'Cross-Enterprise Document Reliable Interchange of Images', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (200, '2009-08-21 12:28:51.122', 'fourquetl', 'US HITSP: C150 Mother and Child Health', 'C150', 'HITSP Mother and Child Health', 7, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (45, '2012-11-27 13:51:10.689668', 'epoiseau', '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', 5, 975);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (332, '2013-09-30 14:54:06.343662', 'aboufahj', 'epSOS Fetch Service', 'epSOS Fetch Service', 'epSOS Fetch Service', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (333, '2013-09-30 15:49:08.753291', 'aboufahj', 'epSOS Provide Service', 'epSOS Provide Service', 'epSOS Provide Service', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (57, '2013-01-09 12:39:35.151668', 'epoiseau', '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, 6987);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (85, '2013-05-17 23:12:10.988397', 'lynn', '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.', 'DEPRECATED:CRD2011', 'DEPRECATED: Clinical Research Document', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (52, '2013-01-09 12:40:51.674218', 'epoiseau', '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, 7146);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (308, '2012-08-20 20:02:33.53', 'moores', 'Health Story: Continuity of Care Document', 'HSP-CCD', 'HSP: Continuity of Care Document', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (309, '2012-08-20 20:09:36.189', 'moores', 'HSP Content Consumers', 'HSP-Consumers', 'HSP Content Consumers', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (215, '2013-01-09 14:00:14.250171', 'epoiseau', '', 'HPD', 'Healthcare Provider Directory', 4, 371);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (36, '2010-03-04 19:20:39.797', 'lynn', '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', 7, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (16, '2013-01-09 12:30:50.534893', 'epoiseau', '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, 7172);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (90, '2013-01-09 12:44:45.84859', 'epoiseau', '', 'XDS-I.b', 'Cross-Enterprise Document Sharing for Imaging', 5, 7044);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (116, '2009-07-24 15:43:25.821', 'admin', 'Inter-Laboratory Workflow', 'ILW', 'Inter-Laboratory Workflow', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (232, '2010-05-25 12:24:04.224', 'epoiseau', 'Test for epSOS demo of gazelle', 'EPSOS-IS', 'EPSOS-IS', 2, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (246, '2013-02-13 17:13:35.615915', 'epoiseau', 'The Pharmacy Dispense Document Profile (DIS) describes the content and format of a dispense document generated during the process in which a health care professional (in most cases, but not necessarily always, a pharmacist) hands out a medication to a patient.
Documents created according to this profile are intended to be used in the context of the “Community Prescription and Dispense” Integration Profile (CMPD).', 'DIS', 'Pharmacy Dispense', 4, 5341);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (237, '2010-07-27 10:00:17.359', 'epoiseau', 'The epSOS Patient Service provides a single operation for retrieving an identified patient’s patient summary from that patient’s country of affiliation. ', 'epSOS Patient Service', 'epSOS Patient Service', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (87, '2009-07-02 13:18:56.457', 'admin', '', 'BIR', 'Basic Image Review', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (41, '2015-01-07 21:44:13.311342', 'epoiseau', '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, 1057);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (67, '2011-08-22 19:48:48.964', 'lynn', '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.', 'A-EYECARE', 'Advanced Eye Care Workflow', 5, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (89, '2009-07-02 13:20:37.184', 'admin', '', 'DIFF', 'MR Diffusion Imaging', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (241, '2010-07-27 17:20:45.979', 'epoiseau', '', 'epSOS-Authentication', 'epSOS-Authentication', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (234, '2010-10-22 09:50:55.628', 'epoiseau', 'Content profile describing the content of the CDA Prescription document', 'epSOS ePresc Document', 'epSOS ePrescription Document', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (51, '2013-05-17 21:50:18.495881', 'lynn', '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.', 'DEPRECATED:SEC', 'DEPRECATED: Basic Security', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (83, '2011-08-17 21:25:16.586', 'lynn', '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.', 'ACM2010', 'DEPRECATED: 2010 Alarm Communication Management', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (11, '2013-01-09 12:40:12.8717', 'epoiseau', '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, 7184);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (236, '2010-07-27 10:25:08.726', 'epoiseau', 'The epSOS Identification Service defines means for the agreement on a shared identifier and for increasing the degree of accuracy of the patient identification that is performed at the point of care. 


', 'epSOS Identification Service', 'epSOS Identification Service ', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (239, '2010-07-27 10:13:01.013', 'epoiseau', 'The epSOS Dispensation Service provides an operation for notifying the patient’s country of affili-ation on the dispensation of a previously retrieved ePrescription.', 'epSOS Dispensation Service', 'epSOS Dispensation Service', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (202, '2009-08-21 12:41:22.825', 'fourquetl', 'US HITSP: C152  Clinical Research Data Acquisition', 'C152', 'HITSP Clinical Research Data Acquisition', 7, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (235, '2010-10-22 09:51:27.097', 'epoiseau', 'This is the content profile that describes the content of the CDA document for patient summary', 'epSOS ePS Document', 'epSOS Patient Summary Document', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (160, '2011-08-12 21:33:47.807', 'lynn', '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', 5, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (81, '2009-07-13 21:24:24.8', '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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (244, '2012-11-19 12:08:41.454', 'epoiseau', 'The Community Medication Prescription and Dispense Integration Profile (CMPD) describes the process of prescription, validation and dispense of medication in the community domain.', 'CMPD', 'Community Medication Prescription and Dispense', 4, 5239);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (315, '2013-08-07 18:57:54.716307', 'Casertano', 'The Secure Exchange of Dental Images (SEDI) Content Profile provides DICOM SOP Instances and image related documents using a reliable web based messaging service. It also allows for the option to support email transport of these imaging documents. SEDI permits direct imaging document interchange between an Imaging Document Source and other healthcare IT imaging document-capable systems.', 'SEDI', 'Secure Exchange of Dental Information', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (37, '2008-04-17 12:10:28.775021', '0', 'HITSP Testing using IHE Profiles', 'HITSPIHE', 'HITSP Testing using IHE Profiles', 5, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (194, '2009-08-21 06:24:54.126', 'fourquetl', 'birthing Summary/delivery record', 'C144', 'Labor and Delivery Report', 7, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (95, '2009-07-08 14:35:36.3', '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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (10, '2013-01-09 12:33:58.396873', 'epoiseau', '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, 7176);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (100, '2009-07-13 22:21:18.966', 'admin', 'Antepartum Laboratory', 'APL', 'Antepartum Laboratory', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (75, '2011-01-11 09:35:18.34', 'epoiseau', 'Laboratory Point Of Care Testing (LPOCT) covers the workflow related to clinical laboratory tests performed on the point of care or on patient''s bedside, by ward staff.', 'LPOCT', 'Laboratory Point Of Care Testing', 5, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (238, '2010-07-27 10:06:58.417', 'epoiseau', 'The epSOS Order Service provides a single operation for retrieving an identified patient’s available ePrescriptions  from that patient’s country of affiliation. ', 'epSOS Order Service', 'epSOS Order Service', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (107, '2009-07-13 23:35:01.747', 'admin', 'Labor and Delivery Summary', 'LDS', 'Labor and Delivery Summary', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (2, '2012-11-28 08:54:05.512096', 'epoiseau', '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, 791);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (201, '2009-08-21 12:32:18.125', 'fourquetl', 'US HITSP: TP149 Retrieve Protocol for Execution', 'TP149', 'HITSP Retrieve Protocol for Execution', 7, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (195, '2009-08-21 06:28:15.914', 'fourquetl', 'HITSP Vaccine Forecast Component', 'C145', 'Vaccine Forecast', 7, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (196, '2009-08-21 06:32:22.124', 'fourquetl', 'HITSP EMS Transfer of Care', 'C148 ', 'HITSP EMS Transfer of Care', 7, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (98, '2009-07-13 22:20:08.772', 'admin', 'Antepartum History and Physical', 'APHP', 'Antepartum History and Physical', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (97, '2009-07-13 23:00:30.97', 'admin', 'Antepartum Summary', 'APS', 'Antepartum Summary', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) 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, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (208, '2009-08-22 02:19:12.024', 'fourquetl', 'US HITSP: T146  Document Metadata Subscription', 'T146', 'HITSP Document Metadata Subscription', 5, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (39, '2012-11-28 08:55:45.756149', 'epoiseau', 'The Cross-Enterprise Document Sharing (XDS.b) IHE Integration Profile facilitates the registration, distribution and access across health enterprises of patient electronic health records.  Cross-Enterprise Document Sharing 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.b', 'Cross-Enterprise Document Sharing', 5, 787);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (233, '2010-10-22 09:50:23.104', 'epoiseau', 'Content profile describing the content of a CDA dispensation document', 'epSOS eDisp Document', 'epSOS eDispensation Document', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (96, '2009-07-08 15:25:25.686', 'admin', '', 'MDW', 'Managed Delivery Workflow', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (99, '2009-07-13 22:20:42.031', 'admin', 'Antepartum Education', 'APE', 'Antepartum Education', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (206, '2009-08-22 02:13:13.106', 'fourquetl', 'US HITSP: T147 Multi-Patient Queries', 'T147', ' HITSP Multi-Patient Queries', 7, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (105, '2013-05-17 23:10:14.960355', 'lynn', 'US HITSP: EMS Transfer of care', 'DEPRECATED:ETC', 'DEPRECATED: EMS Transfer of Care', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (5, '2013-05-17 23:18:13.007721', 'lynn', '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', 'DEPRECATED:XD-Star', 'DEPRECATED:XDM, XDR, XDS', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (13, '2012-11-28 09:04:21.781067', 'epoiseau', '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, 1022);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (103, '2013-09-19 21:53:04.952856', 'moores', 'The composite triage and nursing note is a CDA document that may be submitted to an ED Folder in order to record the act of both triage and nursing care delivered to a patient in the emergency department. The ED nursing note is designed to support documentation sufficient to support transfer of care. It is recognized that the specification is not sufficient to document all medicolegal facets of care, and conversely that providers may not capture the entire list of sections, owing to patient presentation, acuity or time constraints. ', 'CTNN', 'Composite Triage and Nursing Note', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (226, '2013-05-17 23:13:03.703374', 'lynn', 'This Profile will assist detection, documentation of and intervention for hearing loss advocated by professional organizations through an Early Hearing Care Plan (EHCP) made available to all authorized providers of care as jurisdictionally directed by the Public Health EHDI program. This Profile will also enable reporting on quality measures to assure more effective care for all children, especially those with special needs.  Lastly, this Profile will enable public health and population health surveillance to assure access to care and appropriate resources. ', 'DEPRECATED:EHDI', 'DEPRECATED: Early Hearing Loss Detection and Intervention', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (20, '2012-11-28 09:05:11.903085', 'epoiseau', '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, 850);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (297, '2012-08-03 09:02:51.207', 'epoiseau', 'This content profile describes an anatomic pathology structured report (APSR) as a CDA r2 document to be published towards a document sharing resource such as a shared electronic health record used by a community of care providers, relying on one of the infrastructure 
document sharing/exchanging profiles defined in IHE ITI TF.', 'APSR', 'Anatomic Pathology Structured Reports', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (283, '2012-07-11 21:36:26.721', 'lynn', 'General Eye Evaluation (GEE) is a content profile that defines the structure of the data that is often collected during a patient’s routine eye care examination. An eye examination consists of an evaluation of the physiological function and the anatomical status of the eye, visual system, and its related structures. Also included is related patient information such as history, allergies, review of systems, social history, etc.', 'GEE', 'General Eye Evaluation', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (79, '2013-05-15 18:53:58.95594', 'lynn', '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', 5, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (285, '2012-09-19 16:32:41.375', 'lynn', '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 Document', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (43, '2012-11-27 13:48:28.106343', 'epoiseau', '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, 829);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (310, '2012-11-13 17:48:05.924', 'epoiseau', 'The Cross-enterprise Tumor Board Workflow Definition (XTB-WD) describes the different Tasks of a Tumor Board Review process, and the accompanying information in the form of input- and output documents that are linked to the different Tasks in the process. The XTB-WD describes a relatively small part of a larger workflow definition, in this case an oncological care pathway. Other parts of the oncological pathway can be defined in a later stage, in other Workflow Definitions. The different Workflow Definitions can be seen as ‘building blocks’ that describe the actual care pathway of an individual patient. ', 'XTB-WD', 'Cross-enterprise Tumor Board Workflow Definition Profile', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (288, '2012-07-27 19:44:11.046', 'moores', 'The Post-Acquisition Workflow Profile addresses the need to schedule, coordinate and monitor the status of typical post-acquisition steps, such as performing QA, additional reconstructions, Computer Aided Detection, clinical analysis applications, image processing or visualizations such as preparing 3D surface views. Worklists containing workitems for such 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 and notifications provided to other interested systems.', 'PAWF', 'Post-Acquisition Workflow', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (91, '2013-07-25 00:16:10.822081', 'lynn', 'This profile describes the use of subscription and notification mechanism for use within an XDS Affinity Domain and across communities. The subscription allows for the matching of metadata during the publication of a new document for a given patient, and results in the delivery of a notification. ', 'DSUB', 'Document Metadata Subscription', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (312, '2013-06-26 12:41:36.929733', 'epoiseau', 'This profile describes an enhanced feature set for report authoring templates, delineates how such templates from a vendor-agnostic template library could be used immediately by a reporting system, and provides a format for migration of templates between reporting systems.', 'MRRT', 'Management of Radiology Report Templates', 4, 8950);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (320, '2013-08-15 17:28:00.392041', 'swillis', 'Patient Care Plan is a content profile that defines a centralized patient care plan that will meet the needs of many stakeholders (providers and patients) and provide a method to reconcile and consolidate the many disparate care plans that can be attached to a patient. It provides the beginning of a framework for a centralized patient care plan. ', 'PtCP', 'Patient Care Plan', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (336, '2014-05-08 18:53:04.09369', 'lynn', 'The IT Infrastructure Technical Framework defines a profile to access XDS content using RESTful services, called Mobile access to Health Documents (MHD), but this does not provide a solution for images. MHD-I addresses that gap by leveraging the MHD transactions within an imaging context and provides access to DICOM instances via the WADO-URI and WADO-RS Retrieve methods. ', 'MHD-I', 'Mobile access to Health Documents for Imaging', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (294, '2012-07-28 00:08:48.122', 'moores', 'This profile describes how Health IT systems, Person Health Records, and HIEs can retrieve clinical knowledge on a topic suitable for presentation to a clinician or patient.
There are a great number of web resources available that support access of Clinical Knowledge on a specific disease, medical condition, set of symptoms or complaints, medications, et cetera for both clinicians and patients.  However, these resources have inconsistent representations of content, search APIs, and responses, making them difficult to integrate into Healthcare IT solutions. This profile provides a consistent set of rules for issuing knowledge requests for information that is either patient-, clinician- or payer-oriented, and on how to return results so that EHRs and PHRs can process the results and display them in a uniform way.
This profile combines information presently found in standards and implementation guides from Health Level 7 International (HL7), the Internet Engineering Task Force (IETF), the World Wide Web Consortium (W3C) and IHE to describe a single interface that can be used by any system needing access to clinical content.
', 'RCK', 'Retrieve Clinical Knowledge', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (259, '2013-05-17 23:15:18.325185', 'lynn', 'The BFDR Profile is based on the ITI RFD profile. The reader is referred to ITI TF 1:X for a description of the ITI RFD profile. This BFDR Profile defines the content that is used to pre-populate the form retrieved from the Form Manager, and the specification of the pre-population rules to be executed by the Form Manager. This profile does not further constrain the Form Receiver or Form Archiver actors. The pre-pop data is defined by the IHE PCC LDS Profile. See QRPH 1: Appendix X for the specification of the desired pre-pop data constraints to PCC LDS that optimize the Birth and Fetal Death Report data pre-population. ', 'DEPRECATED:MCH-BFDrpt2011', 'DEPRECATED: MCH-BFDrpt2011 use BFDR', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (314, '2013-05-17 23:53:30.285071', 'lynn', 'Scheduled Workflow.b', 'SWF.b', 'Scheduled Workflow.b', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (359, '2015-05-11 23:44:54.522044', 'lynn', 'The Cross-Community Document Reliable Interchange (XCDR) Profile provides the capability
to send a set of documents in a Cross-Community environment. The XCDR Profile specifies the transaction to push documents from an Initiating Gateway of a source Community to the
Responding Gateway of a target Community. ', 'XCDR', 'Cross-Community Document Reliable Interchange', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (258, '2014-08-01 18:27:50.674691', 'lynn', 'The XAD-PID Change Management  (XPID) profile provides a means by which a XDS Document Registry can be notified of external changes to XDS Affinity Domain Patient IDs (XAD-PIDs) links so that it can affect these changes, as appropriate, in its database.', 'XPID', 'XAD-PID Change Management', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (247, '2013-02-13 17:15:54.570495', 'epoiseau', 'The Pharmacy Pharmaceutical Advice Document Profile (PADV) describes the content and format of a pharmaceutical advice generated during the process in which a health care professional (in most cases, but not necessarily always, a pharmacist) validates a prescription item of a prescription against pharmaceutical knowledge and regulations. The validation can be with regard to conflicts with other prescription items or current medication of the patient or other reasons which affect the further processing of the prescription item (may be dispensed, dispensed with change, etc.).
Documents created according to this profile are intended to be used in the context of the “Community Prescription and Dispense” Integration Profile (CMPD).', 'PADV', 'Pharmacy Pharmaceutical Advice', 4, 5770);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (298, '2012-08-10 18:04:59.213', 'lynn', 'The Import Reconciliation Workflow Integration Profile (IRWF.b) specifies how data Importers obtain local demographics, coerce patient and procedure attribute values in the imported data and report progress/status of the importation process. This Profile complements the Scheduled Workflow Profile by using the existing workflow mechanisms for notification and storage of imported Evidence Objects.
', 'IRWF.b', 'Import Reconciliation Workflow', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (276, '2012-08-15 22:46:13.925', 'lynn', 'The Device Enterprise Communication Profile supports communication of vendor 
independent, multi-modality Patient Care Devices data to Enterprise Applications using 
consistent semantics. It accomplishes this by mapping 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. Options are 
provided to allow applications to filter particular PCD data of interest', 'DEC', 'Device Enterprise Communication ', 5, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (47, '2012-11-20 16:23:15.994', 'epoiseau', '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, 1050);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (274, '2013-10-18 05:14:08.855632', 'Manny', 'This profile defines the communication of alerts from alert source systems to alert manager systems and from alert manager systems to alert communicator systems. 

This profile provides for alert dissemination between alert source devices and systems, from the connector to and within the communication services to the required abstract semantics, in a manner that, if complied with, enables multi-vendor multi-modality interoperation. ', 'ACM', 'Alert Communication Management', 5, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (63, '2013-05-17 21:52:49.256817', 'lynn', '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.', 'DEPRECATED:IRWF', 'DEPRECATED: Import Reconciliation Workflow', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (60, '2013-05-17 21:53:56.934133', 'lynn', '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.', 'DEPRECATED:PWF', 'DEPRECATED: Post-Processing Workflow', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (318, '2013-08-05 20:18:40.721848', 'moores', 'This Integration Profile specifies how images, RT Structure Sets, RT Doses, and associated spatial registration information can be exchanged, stored, processed and displayed. For a display workstation, it is essential that a workstation correctly identifies the corresponding image sets, matches data from single-slice and multi-slice datasets, matches coordinate systems, and performs spatial translations.  The use of relevant DICOM objects (Spatial Registration) is clarified and constrained in order to avoid misinterpretation.', 'MMRO-II', 'Multimodality Image Registration for Radiation Oncology 2012 ', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (321, '2013-08-15 17:51:04.336009', 'swillis', 'This profile describes what is necessary to communicate and link the referral and/or order number in documentation and metadata associated with services requested by an order placer. It does not describe where orders are placed when the referral and/or order is communicated using CDA documents. It can be used within the context of profiles using the Cross Enterprise Document Workflow, or it can be used outside of those contexts.

This profile is intended to support care coordination. There are a number of situations where outstanding requests for referrals, consultations, studies, lab tests or other services may need to be tracked or followed. These requests can be tracked using identifiers, often referred to as referral numbers or order numbers depending upon the type of service requested. The distinction between an order and a referral is based on jurisdictional policy. From a technical perspective, referral numbers and order numbers are tracked and communicated in the same way, so to save space, we will refer to them simply as orders (and order numbers) in the remainder of this document, but where we have used the term order, it could also be understood as referral.
', 'ROL', 'Referral/Order Linking', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (322, '2013-08-19 20:28:25.784582', 'swillis', 'This IHE EHDI-WD profile specifies a standard workflow to orchestrate the collection and exchange of newborn hearing screening information between clinical and EHDI program public health information systems. ', 'EHDI-WD', 'Early Hearing Detection and Intervention-Workflow Definition', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (362, '2015-05-20 21:40:12.138463', 'lynn', 'The Clinical Decision Support - Order Appropriateness Tracking Profile (CDS-OAT) propagates the Clinical Decision Support (CDS) and Appropriate Use Criteria (AUC) information to existing actors in the Radiology Scheduled Workflow, Reporting Workflow, and Charge Posting Profiles.', 'CDS-OAT', 'Clinical Decision Support - Order Appropriateness Tracking', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (324, '2013-08-23 17:36:19.69967', 'moores', 'Clinical research studies do not do a good job of recruiting appropriate subjects. A better system is needed. EHRs and registries contain much of the information that is needed to identify appropriate subjects. An automated method allowing research sponsors to search EHRs will lead to better results and be more efficient and cost effective. An automated method allowing providers or patients to identify studies of interest to them would have similar benefits. Finally, if a research system is enabled to push a research protocol to an EHR, the result is an EHR-enabled approach to research matching.
Government, advocacy groups, health care providers and the pharmaceutical industry all agree that the current clinical research recruitment system needs improvement and that more minorities need to be recruited into studies. Individuals and groups from all these constituencies have been in discussions about development of a National Clinical Trial Network (NCTN) linking, among others, physicians, provider networks, academic research centers, hospitals and the pharmaceutical industry; most of them will be available to provide support,  financial or otherwise, to implement the profile. The tools developed as a result of this profile will be key components of the NCTN. 
This profile combines workflow and content.
', 'RM', 'Research Matching', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (317, '2013-09-09 21:46:10.463539', 'bbennett', 'This integration profile involves the exchange of RT Plan information between treatment planning systems and between treatment planning systems and treatment management systems.  The emphasis for this profile is on reducing ambiguity involved in re-planning and incorporation of the planning information in to the treatment management system in anticipation of transfer to a treatment delivery system.  The transactions revolve around content rather than workflow.', 'ARTI', 'Advanced Radiation Therapy Integration', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (102, '2013-09-19 21:51:43.087263', 'moores', 'The nursing note is a CDA document that may be submitted to an ED Folder in order to record the act of nursing care delivered to a patient in the emergency department. The ED nursing note is designed to support documentation sufficient to support transfer of care. It is recognized that the ED Nursing Note specification is not sufficient to document all medicolegal facets of care, and conversely that providers may not capture the entire list of sections, owing to patient presentation, acuity or time constraints. ', 'NN', 'Nursing Note', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (327, '2013-09-18 22:20:56.269761', 'moores', 'The Vital Records Death Reporting (VRDR) Profile provides a means to capture and communicate information needed for to report a death.

The Vital Records Death Reporting (VRDR) is a content profile that defines the content of Vital Records Death Reporting information that is transmitted by clinical systems to public health systems for vital registration purposes. This profile uses several different mechanisms for capturing and communicating that information:
+ Defined content in CDA documents,
+ Defined content in HL7 V2.5.1 messaging,

Electronic data capture and form submission using the ITI Retrieve Form for Data Capture profile with transformation capabilities provided by two new actors:
1. Form Receiver/CDA Exporter which transforms the form data to a VRDR CDA Document defined in this profile in Volume 3
2. Form Receiver/Message Exporter which transforms the form data to a VRDRFeed (QRPH-38) HL7 message defined in this profile in Volume 2', 'VRDR', 'Vital Records Death Reporting', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (291, '2013-09-18 23:24:59.67513', 'moores', 'This profile focuses on the definition of a standardized and shared document structure for the proper management of the clinical process involving chronic patients followed by telemonitoring services. Although this profile has the word “home” in its title, the telemonitoring process considered in this profile allows the patient to be monitored not only from his home but from the place in which he is resident.

The main goal is to allow every participant involved in the process (e.g., specialist, general practitioner, telemonitoring centre’s staff) to manage and share the complete clinical history of the patient, from the monitored data to the events occurring during the process (e.g., visits, changes of therapy). To achieve this, this profile is based on the ITI Cross-enterprise Document Workflow (XDW) Profile that provides a structure to build cross-enterprise workflows, where each event and the related status and documents are tracked and shared between all individuals involved. The XTHM-WD Profile follows the technical specifications contained in the XDW Profile to define the rules needed to create and manage a cross-enterprise workflow related to a telemonitoring process.
', 'XTHM-WD', 'Cross-Enterprise TeleHomeMonitoring Workflow Definition', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (284, '2015-02-27 17:19:38.515116', 'lynn', 'The Mobile access to Health Documents (MHD) profile defines a simple HTTP interface to an XDS like environment. It defines transactions to a) submit a new document and metadata from the mobile device to a document receiver, b) get the metadata for an identified document, c) find document entries containing metadata based on query parameters, and d) retrieve a copy of a specific document.', 'DEPRECATED:MHD-2014', 'DEPRECATED:Mobile access to Health Documents-2014', 6, 439);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (323, '2015-07-30 21:55:33.90339', 'lynn', 'This profile leverages the power of an ISO/IEC 11179 Metadata Registry (here after called “metadata registry”) to add mapping metadata to an annotated data capture form at the point of form design.  ISO/IEC 11179 is a “standard for metadata-driven exchange of data in a heterogeneous environment” (http://en.wikipedia.org/wiki/ISO_11179).  The core object of ISO/IEC 11179 is the data element, which includes a data concept and data representation.  The term “data element” in ISO/IEC 11179 refers to the structure of the data, and is distinct from a data instance. This profile describes the exchange of metadata, rather than the exchange of data instances. (footnote 1)
', 'DEX', 'Data Element Exchange', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (326, '2015-07-30 22:44:15.484076', 'lynn', 'This profile was deprecated in fall 2015 and replaced with an updated Trial Implementation of HW in 2015. ', 'DEPRECATED:HW2014', 'DEPRECATED:Healthy Weight 2014', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (290, '2013-09-18 23:36:19.600008', 'moores', 'The Cross Enterprise Basic eReferral Workflow Definition profile builds upon the ITI Cross Enterprise Document Workflow (XDW) profile to manage the workflow related to an eReferral. 

The management of the workflow related to clinical processes is a critical complement to the use by different sectors of document sharing related IHE profiles with their different types of document and information. IHE ITI has approved in Trial Implementation the Cross-Enterprise Document Workflow profile but the work done by ITI has been on the definition of the technical infrastructure to manage a clinical workflow and not on the definition of the clinical processes, work left to the different IHE Domains.

The Cross Enterprise Basic eReferral Workflow Definition Profile defines the workflow related to the eReferral. This workflow is involved in many clinical and organizational processes for its important role in the process of digitalization. The definition of a workflow with fixed rules and tasks is needed in a cross enterprise scenario in which many participants are involved to support a referral process
', 'XBeR-WD', 'Cross-Enterprise eReferral Workflow Definition', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (109, '2013-09-19 21:29:01.231679', 'moores', 'This PPOC content profile scope contains five of the six components of the nursing process to document human response. The assessment information, as described in the use case, is added to support a depiction of change in health status leading to patient admission, discharge and transfer to another level of care. Assessment documentation profiles will be proposed in future years and as such will not be in scope for the current work.

The PPOC Profile provides a mechanism for capture and electronic exchange of data related to creating and managing individualized patient care between and among HIT systems. This profile enables the exchange of this information based on concepts for diagnoses, interventions, and outcomes in a standardized framework using the American Nurses Association (ANA) nursing process to evolve its information model.  It is for example informed by models of care used in the Clinical Care Classification (CCC) System , and can convey the concepts found in that and other controlled vocabularies.

These models extend the description of the content structures for the plan of care in the current technical framework. The PPOC focuses on the following six components in a clinical document: 
  1.	Assessment
  2.	Nursing Diagnosis
  3.	Outcomes Identification
  4.	Planning
  5.	Implementation (Interventions)
  6.	Evaluation
', 'PPOC', 'Patient Plan of Care', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (106, '2013-09-19 21:30:39.44057', 'moores', 'Labor and Delivery Summary is a content profile that defines the structure of the data that is often collected during the labor and delivery period at the birthing facility.  It includes, but is not limited to demographics, histories, allergies, physical examinations, vital signs, and newborn delivery information.', 'LDHP', 'Labor and Delivery History and Physical', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (108, '2013-09-19 21:32:15.727686', 'moores', 'Maternal Discharge Summary is a content profile that defines the structure of the data that is often collected t-delivery until discharge from the birthing facility.  It includes, but is not limited to demographics, medications, laboratory results, newborn delivery information, patient education, and outcomes.', 'MDS', 'Maternal Discharge Summary', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (220, '2013-09-19 21:36:01.879103', 'moores', 'To ensure consistent information, accurate and concise communication must be present during patient care transitions or hand off. Care transitions, or “hand-offs”, occur multiple times each day in a hospital and at every change of care location. This does not include off unit reports for lunch breaks, special procedures lab, physical or occupational therapy, or general radiology reports on the patient given by the unit nurse.

Standardization work has been initiated by the HL7 Clinical Document Architecture group, nursing process and ISO Reference Terminology Model. European eHealth has called for a summary which crosses borders and provides a timely transfer. IHE could solve the issue by creating an interoperable nursing eHealth summary which is possible to use nationally and internationally

The purpose of  the eNursing Summary Profile is to create an interoperable summary of nursing related data that communicates the ongoing patient care needs to another care provider. The data elements were determined by an international survey of 589 nurses. Data element information for the selected Use Cases are documented in a summary table for ease of comparison. 
', 'ENS', 'E-Nursing Summary', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (101, '2013-09-19 21:50:38.438896', 'moores', 'The triage note is a CDA document that may be submitted to an ED Folder in order to record the act of triaging a patient upon presentation to the emergency department. The triage note is designed to support a comprehensive triage assessment, although it is recognized that providers may not capture the entire list of sections, owing to patient presentation, acuity or time constraints. ', 'TN', 'Triage Note', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (280, '2013-10-24 15:05:01.489184', 'epoiseau', 'The Cath Report Content (CRC) Profile specifies the content structure for a clinical report of a cardiology procedure recorded in a Cardiac Cath Lab. Such procedures include (1) Diagnostic Cath, (2) Angiography, (3) IVUS/IVOCT, (4) PCI.', 'CRC', 'Cath Report Content', 4, 26);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (335, '2014-05-08 18:26:05.907162', 'lynn', 'The Digital Breast Tomosynthesis (DBT) Profile specifies the creation, exchange and use of DBT images. It defines basic display capabilities that Image Displays are expected to provide, especially simultaneous review of DBT and conventional 2D mammography images (FFDM). 

The Digital Breast Tomosynthesis Profile is designed to provide faithful storage and retrieval of DBT images. Furthermore, sufficient display functionality to allow adequate review of current and prior studies consisting of DBT and/or conventional 2D mammography images is defined.', 'DBT', 'Digital Breast Tomosynthesis', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (93, '2014-06-09 21:57:41.458333', 'lynn', 'The Cross-Community Patient Discovery (XCPD) profile supports the means to locate 275 communities that hold patient relevant health data and the translation of patient identifiers across communities holding the same patient‟s data. A community is defined as a group of facilities/enterprises that have agreed to work together using a common set of policies for the purpose of sharing health information within the community 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.', 'XCPD', 'Cross Community Patient Discovery', 5, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (337, '2014-07-31 16:28:44.416153', 'lynn', 'This profile defines a framework able to enforce a centralized Access Control system, conveying between actors involved in a XDS sharing environment the evidence of the reliable decisions already made by an Access Decision Manager. 

The main objective of this profile is to create a system of trust between the actor that performs access decisions (Authorization Decisions Manager), and actors that store clinical data (XDS Document Repositories). This split of responsibilities is needed in many environments where systems that expose clinical data are not able to replicate and repeat access decisions. 
', 'SeR', 'Secure Retrieve', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (338, '2014-07-31 18:40:53.517684', 'lynn', 'The Patient Location Tracking (PLT) integration profile supports collecting the patient location information in a facility, and providing his/her recently recognized location to other systems. PLT covers patient location tracking inside single facilities, not between two or more facilities.', 'PLT', 'Patient Location Tracking', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (254, '2014-07-31 18:58:38.818685', 'lynn', 'The Imaging Object Change Management Integration Profile (IOCM) specifies how one actor communicates local changes applied on existing imaging objects to other actors that manage copies of the modified imaging objects in their own local systems. The supported changes include (1) object rejection due to quality or patient safety reasons, (2) correction of incorrect modality worklist entry selection, and (3) expiration of objects due to data retention requirements. It defines how changes are captured and how to communicate these changes.', 'IOCM', 'Imaging Object Change Management', 5, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (340, '2014-08-04 23:08:11.501176', 'moores', 'This profile provides guidance on how text in CDA documents may be tagged to achieve different rendering behaviors. This allows one document to serve different needs based upon the requirements of the person viewing the document. The viewing requirements of a patient differ from the requirements of a healthcare provider. The profile identifies many of the requirements expressed by patients, classifies these requirements, identifies the rendering behavior associated with each, and provides guidance on how to tag CDA content in order to bind it to an identified behavior. Use of this profile allows one CDA document to serve the needs of different Document Consumers. This profile is strictly about the rendering of the narrative, and the view has no relationship to content that may be imported by other actors.
', 'MCV', 'Multiple Content Views', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (339, '2015-10-16 19:13:44.339626', 'moores', 'The Patient Demographics for Mobile (PDQm) profile provides a transaction for mobile and lightweight browser based applications to query a patient demographics supplier for a list of patients based on user-defined search criteria and retrieve a patient’s demographic information into the application.', 'PDQm', 'Patient Demographics Query for Mobile', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (82, '2014-08-08 22:57:03.324478', 'moores', 'The Immunization Content Profile (IC) provides a standard document to exchange immunization data. It is intended to facilitate the exchange of immunization data among multiple systems belonging to a single or to multiple organizations. Data exchange with and among the installed
base of U.S. Immunization Information System (IIS) base was a critical consideration in formulating this profile. However, its intention is to go beyond data exchange among IISs, and facilitate immunization data exchange on a healthcare information network that includes electronic medical record (EMR) systems, Health Information Exchanges, other public health systems, Personal Health Record (PHR) systems, and other stakeholder systems. Thus, the profile specifies common data formats for exchanging immunization data only, or for exchanging immunization data along with medical summary data needed for the overall care of a patient related to immunizations.

To accomplish this, IC includes a history of administered vaccines with such details as lot number, who administered the shot, and so forth, and handles immunization as well as other information related to the patient''s care. For example, it includes medical history, medications, allergies, vital signs, and so forth.
', 'IC', 'Immunization Content', 5, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (341, '2014-08-04 23:35:44.069399', 'moores', 'The Birth and Fetal Death Reporting-Enhanced (BFDR-E) Profile provides a means to capture and communicate information needed to report births and fetal deaths for vital registration purposes. BFDR-E builds upon the earlier Birth and Fetal Death Reporting (BFDR) Profile that utilizes actors and transactions defined in the ITI Retrieve Form for Data Capture (RFD) Profile to capture structured data using digital forms. 

BFDR-E defines a specialized Labor and Delivery Summary (LDS-VR) CDA document. The LDS-VR document is used to prepopulate an electronic form (worksheet) that collects the information needed for submission to vital records. BFDR-E supports pre-population of the worksheet form using either the specialized LDS-VR document or a more general Labor and Delivery Summary (LDS) document that does not conform to all the further constraints of an LDS-VR document. Use of the LDS-VR pre-population option optimizes the initial Birth and Fetal Death Report form data population. 

BFDR-E further defines a mechanism to transform form submission data and record it in a CDA document designed to exchange the information in a standard format. BFDR-E defines a Form Receiver CDA Exporter Actor to perform the transform on the form submission data  and share that document with a Content Consumer. BFDR-E defines the IHE BFDR Document Template which adapts the HL7 BFDR CDA document template to support standard interchange of the information gathered from the form.

BFDR-E also defines a mechanism to transform form submission data and transmit it as a standard HL7 v2 message. The IHE BFDR Message adapts the HL7 V2.5.1 BFDR Message for this purpose. BFDR-E defines the BFDRfeed transaction to transmit this message. The BFDRfeed transaction is just like the VRDRfeed [QRPH-38] transaction defined in the QRPH Vital Records Profile, but is carries a different message payload. 
', 'BFDR-E', 'Birth and Fetal Death Reporting-Enhanced', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (342, '2014-08-06 21:58:33.441362', 'lynn', 'This Core Eye Care Workflow (C-Workflow) profile addresses a scenario where organizations have a Practice Management System (PMS), Electronic Health Record System (EHR) and eye care diagnostic imaging and testing equipment (fundus cameras, slit lamps, refractive measurement devices, visual fields etc.).

This profile enables the consistent handling of patient identifiers and demographic data among the above types of systems. It includes support for features such as patient registration, appointment scheduling, eye care orders and equipment modality worklist. It reduces the implementation requirements of the other eye care workflows by not integrating an Image Archive (i.e. PACS system).  Therefore, users of this profile must understand that acquisition devices and users are responsible for the safe keeping of the images and/or measurements created upon their system.  It is important for users to understand how this is accomplished so that patient data is protected.  How this is accomplished is outside the scope of IHE. 
', 'C-EYECARE', 'Core Eye Care Workflow', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (255, '2014-08-06 22:33:22.91362', 'lynn', 'Basic 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 is a subset of the features defined in the Advanced Eye Care Workflow Integration profile. ', 'B-EYECARE', 'Basic Eye Care Workflow', 5, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (343, '2014-08-07 22:55:15.512557', 'moores', 'The Family Planning (FP) Profile provides a means to capture information needed for mandated reporting, monitoring and evaluation, and quality improvement initiatives related to family planning service delivery. The FP Profile is a content profile that defines the content of Family Planning information to be exchanged between systems. This profile uses several different mechanisms for capturing and communicating that information:
•	Electronic data capture and form submission using the ITI Retrieve Form for Data Capture (RFD),
•	Defined content in CDA documents.
', 'FP', 'Family Planning', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (344, '2014-08-07 23:19:33.379193', 'moores', 'The Structured Data Capture (SDC) Content Profile provides specifications to enable an Electronic Health Record (EHR) system or other application to retrieve a data capture form and submit data from the completed form. The SDC Profile utilizes the IHE Retrieve Form for Data Capture (RFD) Profile and an ISO/IEC 19763-13 Meta-model for Framework Interoperability (MFI) form registration. This profile also supports optional use IHE Data Element Exchange (DEX) Profile for retrieving and submitting forms in a standardized and structured format.

This supplement is based on the work of the Office of the National Coordinator (ONC) Standards & Interoperability (S&I) Framework SDC Initiative. The SDC initiative has developed use cases, identified national standards for the structure of Common Data Elements and form model definition, developed guidance to assist in implementation, and conducted pilots for evaluation of SDC.', 'SDC', 'Structured Data Capture', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (345, '2014-08-08 21:00:25.658757', 'moores', 'The EHDI Profile describes the content needed to create a hearing plan of care for a newborn. The HPoC document supports communication and care planning with providers who are a part of the newborn’s care team. It helps to standardize care coordination for infants with suspected hearing loss. It also provides interoperability between clinical EMR systems and EHDI systems for increased efficiency and better data quality.

The EHDI Profile also specifies the message content needed to constrain a message for transmitting device observations from hearing screening devices. The message is used to automate population of hearing screening results in the HPoC document.

The EHDI Profile also specifies the data element mapping needed to populate a form designed to capture structured data for hearing screening results and risk indicators. The form is used to manually capture hearing screening results and risk indicators when that data in not available for automated population.', 'EHDI', 'Early Hearing Detection and Intervention', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (269, '2014-08-08 22:05:17.612781', 'moores', 'Reconciliation of electronic clinical information from multiple data sources is a difficult task.  It involves managing lists of clinical information that are often larger than most people can keep in working memory.  This profile enables information contained in Health Information Systems and Exchanges to be used to support automation of these reconciliation tasks and clinical workflows.  This profile explains what information can help reconciliation, and how it can be used to assist healthcare providers to automate this complex task.', 'RECON-DEPRECATED', 'Reconciliation of Diagnoses, Allergies and Medications', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (347, '2014-08-08 22:05:57.368295', 'moores', 'As data is exchanged, the ability to maintain the support of care provision is needed. As an attempt to support the management of care provision, Reconciliation of Clinical Content and Care Providers Profile (RECON) will identify and examine heuristics that can be used to facilitate identification of duplicated, overlapping, conflicting or superseded entries that may be introduced as a result of semantic interoperability. This will be accomplished by classifying clinical information into the following categories for the purpose of determining the heuristics that will be used for the purpose of reconciliation. ', 'RECON', 'Reconciliation of Clinical Content and Care Providers', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (334, '2014-08-13 21:20:39.091128', 'lynn', 'The Federated HPD profile is a proposed USA specific profile being created by the joint effort of IHE USA, Office of the National Coordinator for the US (ONC) and EHR|HIE IWG. 

The initial proposed artifacts developed by ONC can be accessed at 

http://modularspecs.siframework.org/Provider+Directories+Artifacts
', 'F_HPD', 'Federated HPD', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (348, '2014-08-14 17:10:57.506721', 'psherman', 'MEMDMC is focused with sending equipment identification observations whether or not there is a patient associated with the device to equipment management systems, such as CMMS.  Equipment identification, configuration, and status information needs to be recorded for effective management of the equipment, whether or not there is a patient currently associated with the equipment.', 'MEMDMC', 'Medical Equipment Management  Device Management Communication', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (349, '2014-08-14 18:58:13.0061', 'psherman', 'This profile provides detailed device and people location identification which can be sourced by embedded location sensing components or through location sensing tags external to equipment and these tags can also provide additional information such as button presses and environmental information such as temperature and humidity  It is a combination of profile types as it defines workflow through use case specification and transport through its described use of the HL7 and IEEE 11073 standards for information communication.', 'MEMLS', 'Medical Equipment Management Location Services', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (350, '2014-08-19 23:09:55.879031', 'epoiseau', 'The Registry Content Submission-CathPCI V4.4 (RCS-C) Profile specifies the content structure 
and value sets for reporting the data elements collected during a cardiac catheterization and/or 
PCI to the NCDR®. The scope of the RCS-C content is stipulated by the NCDR specifications
for providing data and required value sets to the NCDR CathPCI Registry V4.4.', 'RCS-C', 'Registry Content Submission – CathPCI V4.4', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (351, '2014-08-20 14:19:37.745465', 'lynn', 'The Electrophysiology Implant/Explant Report Content (EPRC-IE) Profile specifies the content structure for a clinical report of an electrophysiology procedure recorded in an EP Lab.', 'EPRC-IE', 'Electrophysiology Implant/Explant Report Content', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (40, '2015-01-08 23:04:48.582637', 'epoiseau', '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, 1041);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (354, '2015-02-27 17:20:07.948257', 'lynn', 'The Mobile access to Health Documents (MHD) Profile defines one standardized interface to health documents (a.k.a. an Application Programming Interface (API)) for use by mobile devices so that deployment of mobile applications is more consistent and reusable. In this context, mobile devices include tablets, smartphones, and embedded devices including home-health devices. ', 'MHD', 'Mobile access to Health Documents', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (46, '2015-02-27 18:20:59.359614', 'lynn', '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.', 'DEPRECATED:DSG-2014', 'DEPRECATED:Digital Signature-2014', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (352, '2015-02-25 10:05:13.568975', 'epoiseau', 'The Pharmacy Medication List Profile (PML) describes the content and format of a Medication List document generated during a process in which a health care professional (physician, pharmacist, nurse, etc.) requests this information (e.g., to support its prescribing). Documents created according to this profile are intended to be used in the context of the “Community Prescription and Dispense” Integration Profile (CMPD). The Community Pharmacy Prescription and Dispense workflow includes the stage of requesting the Medication List of a patient by a health care professional (physician, pharmacist, nurse, etc.). A Medication List document is the documentation of the performed determination of the Medication list. It contains a set of Prescription- and/or Dispense Items (and their related Pharmaceutical Advice Items) representing the Medication information of the patient at a certain point of time and according to business rules specified out of scope of this profile. For a detailed overview on the whole Pharmacy domain business processes, please refer to the “Common parts” document, which is accompanying this profile.', 'PML', 'Pharmacy Medication List', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (355, '2015-02-27 18:22:06.48538', 'lynn', 'The Document Digital Signature (DSG) Profile is a Document Content Profile that provides general purpose methods of digitally signing of documents for communication and persistence. This method can be used within a Document Sharing infrastructure (e.g., XDS, XCA, XDM, XDR, and MHD). There are three methods of digital signature provided: Enveloping, Detached, and SubmissionSet. ', 'DSG', 'Document Digital Signature', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (365, '2015-06-15 16:24:56.826801', 'aboufahj', 'The Registry Content Submission – Electrophysiology (RCS-EP) Profile specifies the data
structure and vocabulary for a submission to an electrophysiology registry, such as the NCDR®
EP RegistryTM Suite, which includes ICD RegistryTM v2.2, and AFib Ablation RegistryTM. The
specification is written for use within the US Realm, but can be localized to other realms via the
IHE specification localization process.', 'RCS-EP', 'Registry Content Submission  - Electrophysiology', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (366, '2015-06-18 21:49:28.564965', 'lynn', 'The Unified Eye Care Workflow (U-EYECARE) integration profile establishes the continuity and integrity of basic patient and procedure data in the context of an eye clinic workflow scenario. This profile deals specifically with consistent handling of patient identifiers and demographic data. It specifies the scheduling and coordination of procedure data to a wide variety of diagnostic imaging and testing equipment and the ability to post eye care charges.', 'U-EYECARE', 'Unified Eye Care Workflow', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (367, '2015-07-14 23:24:54.405777', 'lynn', 'This profile defines the structure of data that is collected for a patient’s eye care summary medical record, generally for the purpose of transfer or referral of care to another provider. ', 'EC-Summary', 'Eye Care Summary Record', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (368, '2015-07-29 00:59:13.103401', 'lynn', 'The mACM Profile provides the infrastructural components needed to send short, unstructured text alerts to human recipients and records the outcomes of any human interactions upon receipt of the alert. The mACM Profile additionally allows for a feedback mechanism to determine the status of an alert through the use of alert statuses', 'mACM', 'Mobile Alert Communication Management', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (279, '2015-07-29 01:07:09.994709', 'lynn', 'The Cross-Enterprise Document Workflow (XDW) profile enables participants in a multi- organizational environment to manage and track the tasks related to patient-centric workflows as the systems hosting workflow management applications coordinate their activities for the health professionals and patients they support. XDW builds upon the sharing of health documents provided by other IHE profiles such as XDS, adding the means to associate documents conveying clinical facts to a patient-specific workflow. XDW provides a common interoperability infrastructure upon which a wide range of specific workflow definitions may be supported. It is designed to support the complexity of health services delivery with flexibility to adapt as workflows evolve.', 'XDW', 'Cross-Enterprise Document Workflow', 5, 671);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (369, '2015-07-29 01:42:10.755928', 'lynn', 'The Patient Identifier Cross-reference Mobile (PIXm) Integration Profile provides a transaction for mobile and lightweight browser based applications to query a Patient Identifier Cross-reference Manager for a list of patient identifiers based on the patient Identifier in a different domain and retrieve a patient’s cross-domain identifiers information into the application.', 'PIXm', 'Patient Identifier Cross-reference for Mobile', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (286, '2015-07-30 21:51:30.71833', 'lynn', 'This profile was deprecated in fall 2015 and replaced with an updated Trial Implementation of QME-EH in 2015. ', 'DEPRECATED:QME-EH-2014', 'DEPRECATED: Quality Measure Execution–Early Hearing 2014', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (370, '2015-08-11 23:30:30.526555', 'lynn', 'This is a content module profile which defines the patient-level quality report needed for the Newborn Hearing Screening (CMS31v4, NQF1354) electronic clinical quality measure (eCQM) defined by the Centers for Disease Control and Prevention’s Early Hearing Detection and Intervention program. The measure is used to assess the quality of the process of hearing screening for newborns. To support all realms, the profile uses generalized content modules (documents) which are then bound to specific content documents in the realm specific sections of Volume 4. ', 'QME-EH', 'Quality Measure Execution - Early Hearing', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (371, '2015-08-12 00:07:59.836164', 'lynn', 'The Aggregate Data Exchange (ADX) profile defines the structure of ADX/XML messages to be exchanged between a Content Creator and a Content Consumer.  . ADX introduces a new actor: the Content Data Structure Creator.  The Content Data Structure Creator defines the structural metadata (eg code lists for dataelements) to be used in the message exchange.  The message structure definition files created by the Content Data Structure Creator may be employed by a Content Creator to construct and exchange interoperable, ADX-conformant messages with a Content Consumer. ', 'ADX', 'Aggregate Data Exchange', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (372, '2015-08-12 00:14:23.207275', 'lynn', 'The Healthy Weight (HW) Profile provides a means to capture and communicate among clinical systems and public health information systems, the information needed for managing and monitoring healthy weight. The HW Profile is a content profile that defines the content of Healthy Weight information that is transmitted. ', 'HW', 'Healthy Weight', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (287, '2015-08-12 15:48:53.805715', 'lynn', 'The BFDR Profile is based on the ITI RFD profile. The reader is referred to ITI TF 1:X for a description of the ITI RFD profile. This BFDR Profile defines the content that is used to pre-populate the form retrieved from the Form Manager, and the specification of the pre-population rules to be executed by the Form Manager. This profile does not further constrain the Form Receiver or Form Archiver actors. The pre-pop data is defined by the IHE PCC LDS Profile. See QRPH 1: Appendix X for the specification of the desired pre-pop data constraints to PCC LDS that optimize the Birth and Fetal Death Report data pre-population. ', 'DEPRECATED:BFDR2014', 'DEPRECATED:Birth and Fetal Death Reporting', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (260, '2015-08-12 15:49:23.26326', 'lynn', 'The Early Hearing Care Plan (EHCP) profile describes the content needed to communicate care plan instructions to properly manage the detection and intervention of hearing loss in newborns and young children.', 'DEPRECATED:EHCP', 'DEPRECATED - Early Hearing Care Plan', 6, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (364, '2015-09-08 22:48:26.118053', 'moores', 'The Remote Patient Monitoring Profile describes a standardized means to transmit measurements taken by personal healthcare devices in a remote setting to a health care provider, including remote home monitoring, sub-acute therapy devices and wearable technologies. Remote in this case means outside of a care provider facility and is typically in the patient’s home.

This profile is, for all practical purposes, an expression of the already existing set of standards and interfaces defined by PCHA for the delivery of remote patient data taken by Personal Healthcare Devices to the care provider in terms of IHE actors and transactions. No new standards or transactions are proposed.', 'RPM', 'Remote Patient Monitoring', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (361, '2015-09-08 17:37:41.259984', 'moores', 'The Guideline Appropriate Ordering profile supplies a mechanism by which EHR and departmental systems can evaluate orders to determine whether these orders conform to guidelines.  The profile enables the results of the evaluation (essentially an authorization) to be stored and transmitted, and the receiver of those results to verify that an order was evaluated with regard to appropriateness.

Supplement published for Public Trial Implementation: August 2015', 'GAO', 'Guideline Appropriate Ordering', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (363, '2015-09-08 17:38:17.892361', 'moores', 'Mapping to and from clinical terminologies is important to handle situations in which:
•	Device generated observations need to be converted to clinical terminologies for use in clinical decision making and record keeping
•	Clinical terminologies need to be converted to charge capture / billing compatible terminologies for  communicating diagnoses and procedures:
o	ICD-10 for international purposes
o	Others as needed for national extensions
•	Clinical terminologies need to be converted to other clinical terminologies (future)
Benefits include:
•	Significant time savings
•	Data entry error reduction
•	Consistency in practice to permit comparison and aggregation of data post-conversion

Supplement published for Trial Implementation: August 2015', 'CMAP', 'Clinical Mapping', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (374, '2015-09-10 19:43:30.235189', 'moores', 'A Care Plan (including Home Health Plan of Care (HHPoC)) is a consensus-driven dynamic plan that represents a patient’s and Care Team Members’ prioritized concerns, goals, and planned interventions. It serves as a blueprint shared by all Care Team Members (including the patient, their caregivers and providers), to guide the patient’s care. A Care Plan integrates multiple interventions proposed by multiple providers and disciplines for multiple conditions.

A Care Plan represents one or more Plan(s) of Care and serves to reconcile and resolve conflicts between the various Plans of Care developed for a specific patient by different providers. While both a plan of care and a care plan include the patient’s life goals and require Care Team Members (including patients) to prioritize goals and interventions, the reconciliation process becomes more complex as the number of plans of care increases. The Care Plan also serves to enable longitudinal coordination of care.

The CDA Care Plan represents an instance of this dynamic Care Plan at a point in time. The CDA document itself is NOT dynamic.', 'C-CDA2.1_CARE-PLAN', 'C-CDA 2.1 Care Plan (V2)', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (375, '2015-09-10 19:46:48.600535', 'moores', 'The Consultation Note is generated by a request from a clinician for an opinion or advice from another clinician. Consultations may involve face-to-face time with the patient or may fall under the auspices of telemedicine visits. Consultations may occur while the patient is inpatient or ambulatory. The Consultation Note should also be used to summarize an Emergency Room or Urgent Care encounter.

A Consultation Note includes the reason for the referral, history of present illness, physical examination, and decision-making components (Assessment and Plan).
', 'C-CDA2.1_CONSULT', 'C-CDA 2.1 Consultation Note (V3)', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (376, '2015-09-10 19:52:21.477068', 'moores', 'This document type was originally based on the Continuity of Care Document (CCD) Release 1.1 which itself was derived from HITSP C32 and CCD Release 1.0.

The Continuity of Care Document (CCD) represents a core data set of the most relevant administrative, demographic, and clinical information facts about a patient''s healthcare, covering one or more healthcare encounters. It provides a means for one healthcare practitioner, system, or setting to aggregate all of the pertinent data about a patient and forward it to another to support the continuity of care.

The primary use case for the CCD is to provide a snapshot in time containing the germane clinical, demographic, and administrative data for a specific patient. The key characteristic of a CCD is that the ServiceEvent is constrained to "PCPR". This means it does not function to report new ServiceEvents associated with performing care. It reports on care that has already been provided. The CCD provides a historical tally of the care over a range of time and is not a record of new services delivered.
', 'C-CDA2.1_CCD', 'C-CDA 2.1 Continuity of Care Document (CCD) (V3)', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (377, '2015-09-10 19:54:19.940895', 'moores', 'A Diagnostic Imaging Report (DIR) is a document that contains a consulting specialist’s interpretation of image data. It conveys the interpretation to the referring (ordering) physician and becomes part of the patient’s medical record. It is for use in Radiology, Endoscopy, Cardiology, and other imaging specialties.', 'C-CDA2.1_DIAG-IMAGING', 'C-CDA 2.1 Diagnostic Imaging Report (V3)', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (378, '2015-09-10 19:56:32.184009', 'moores', 'The Discharge Summary is a document which synopsizes a patient''s admission to a hospital, LTPAC provider, or other setting. It provides information for the continuation of care following discharge. The Joint Commission requires the following information to be included in the Discharge Summary (http://www.jointcommission.org/):
• The reason for hospitalization (the admission)
• The procedures performed, as applicable
• The care, treatment, and services provided
• The patient’s condition and disposition at discharge
• Information provided to the patient and family
• Provisions for follow-up care', 'C-CDA2.1_DISCHARGE', 'C-CDA 2.1 Discharge Summary (V3)', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (379, '2015-09-10 19:58:26.92666', 'moores', 'A History and Physical (H&P) note is a medical report that documents the current and past conditions of the patient. It contains essential information that helps determine an individual''s health status.
The first portion of the report is a current collection of organized information unique to an individual. This is typically supplied by the patient or the caregiver, concerning the current medical problem or the reason for the patient encounter. This information is followed by a description of any past or ongoing medical issues, including current medications and allergies. Information is also obtained about the patient''s lifestyle, habits, and diseases among family members.
The next portion of the report contains information obtained by physically examining the patient and gathering diagnostic information in the form of laboratory tests, imaging, or other diagnostic procedures.
The report ends with the clinician''s assessment of the patient''s situation and the intended plan to address those issues.
A History and Physical Examination is required upon hospital admission as well as before operative procedures. An initial evaluation in an ambulatory setting is often documented in the form of an H&P note.', 'C-CDA2.1_HandP', 'C-CDA 2.1 History and Physical (V3)', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (380, '2015-09-10 20:00:49.933759', 'moores', 'The Operative Note is a frequently used type of procedure note with specific requirements set forth by regulatory agencies.

The Operative Note is created immediately following a surgical or other high-risk procedure. It records the pre- and post-surgical diagnosis, pertinent events of the procedure, as well as the condition of the patient following the procedure. The report should be sufficiently detailed to support the diagnoses, justify the treatment, document the course of the procedure, and provide continuity of care.
', 'C-CDA2.1_OPERATIVE', 'C-CDA 2.1 Operative Note (V3)', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (381, '2015-09-10 20:02:37.959793', 'moores', 'A Procedure Note encompasses many types of non-operative procedures including interventional cardiology, gastrointestinal endoscopy, osteopathic manipulation, and many other specialty fields. Procedure Notes are differentiated from Operative Notes because they do not involve incision or excision as the primary act.

The Procedure Note is created immediately following a non-operative procedure. It records the indications for the procedure and, when applicable, postprocedure diagnosis, pertinent events of the procedure, and the patient’s tolerance for the procedure. It should be detailed enough to justify the procedure, describe the course of the procedure, and provide continuity of care.
', 'C-CDA2.1_PROCEDURE', 'C-CDA 2.1 Procedure Note (V3)', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (382, '2015-09-10 20:04:18.647189', 'moores', 'This template represents a patient’s clinical status during a hospitalization, outpatient visit, treatment with a LTPAC provider, or other healthcare encounter.

Taber’s medical dictionary defines a Progress Note as “An ongoing record of a patient''s illness and treatment. Physicians, nurses, consultants, and therapists record their notes concerning the progress or lack of progress made by the patient between the time of the previous note and the most recent note.”

Mosby’s medical dictionary defines a Progress Note as “Notes made by a nurse, physician, social worker, physical therapist, and other health care professionals that describe the patient''s condition and the treatment given or planned.”

A Progress Note is not a re-evaluation note. A Progress Note is not intended to be a Progress Report for Medicare. Medicare B Section 1833(e) defines the requirements of a Medicare Progress Report.
', 'C-CDA2.1_PROGRESS', 'C-CDA 2.1 Progress Note', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (383, '2015-09-10 20:10:58.731816', 'moores', 'A Referral Note communicates pertinent information from a provider who is requesting services of another provider of clinical or non-clinical services. The information in this document includes the reason for the referral and additional information that would augment decision making and care delivery.

Examples of referral situations are when a patient is referred from a family physician to a cardiologist for cardiac evaluation or when patient is sent by a cardiologist to an emergency department for angina or when a patient is referred by a nurse practitioner to an audiologist for hearing screening or when a patient is referred by a hospitalist to social services.
', 'C-CDA2.1_REFERRAL', 'C-CDA2.1 Referral Note (V2)', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (390, '2015-12-09 00:06:22.659601', 'lynn', 'The profile is intended to address a variety of use cases involving imaging studies that are distributed to other locations for interpretation of the study and return of a diagnostic report.

The profile specifies transactions for workflow management that are based on the RESTful worklist service defined by DICOM UPS-RS. The profile also specifies (as Named Options) transactions for accessing the inputs to the reading task and storing the outputs from the reading task. The Named Options permit the use of XDS-I, RESTful DICOM, or Conventional DIMSE DICOM
', 'RRR-WF', 'Radiology Remote Reading Workflow', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (385, '2015-09-10 20:19:29.513899', 'moores', 'An Unstructured Document (UD) document type can (1) include unstructured content, such as a graphic, directly in a text element with a mediaType attribute, or (2) reference a single document file, such as a word-processing document using a text/reference element.

For guidance on how to handle multiple files, on the selection of media types for this IG, and on the identification of external files, see the examples that follow the constraints below.

IHE’s XDS-SD (Cross-Transaction Specifications and Content Specifications, Scanned Documents Module) profile addresses a similar, more restricted use case, specifically for scanned documents or documents electronically created from existing text sources, and limits content to PDF-A or text. This Unstructured Documents template is applicable not only for scanned documents in non-PDF formats, but also for clinical documents produced through word processing applications, etc.

For conformance with both specifications, implementers need to ensure that their documents at a minimum conform with the SHALL constraints from either specification
', 'C-CDA2.1_UNSTRUCTURED', 'C-CDA 2.1 Unstructured Document (V3)', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (384, '2015-09-10 20:12:31.387394', 'moores', 'This document describes constraints on the Clinical Document Architecture (CDA) header and body elements for a Transfer Summary. The Transfer Summary standardizes critical information for exchange of information between providers of care when a patient moves between health care settings.

Standardization of information used in this form will promote interoperability; create information suitable for reuse in quality measurement, public health, research, and for reimbursement.
', 'C-CDA2.1_TRANSFER', 'C-CDA2.1 Transfer Summary (V2)', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (386, '2015-09-10 20:21:39.437908', 'moores', 'This profile is not defined directly by the C-CDA 2.1 documentation. We create this profile as a collector for Content Consumers who will consume various Consolidated CDA 2.1 documents.', 'C-CDA2.1_CONSUMERS', 'C-CDA 2.1 Document Consumers', 4, NULL);
INSERT INTO tf_integration_profile (id, last_changed, last_modifier_id, description, keyword, name, integration_profile_status_type_id, documentsection) VALUES (373, '2015-09-13 20:53:07.615103', 'lynn', 'The DAF Implementation Guide is not a profile, but rather a US National Extension describing use of several profiles in the ITI domain. -- The Data Access Framework (DAF) Document Metadata Based Access Implementation Guide, describes United States implementation guidelines for specific transactions and content modules defined in the IHE IT Infrastructure (ITI) Technical Framework to meet United States ONC S&I Frameworks requirements for the Data Access Framework. This Implementation Guide was developed as a joint collaboration of ONC S&I Frameworks and IHE USA.

First defined:  DAF Implementation Guide, Sep 2015, PCC US National Extension', 'DAF', 'Data Access Framework Implementation Guide', 4, NULL);


--
