Attention A T users. To access the menus on this page please perform the following steps. 1. Please switch auto forms mode to off. 2. Hit enter to expand a main menu option (Health, Benefits, etc). 3. To enter and activate the submenu links, hit the down arrow. You will now be able to tab or arrow up or down through the submenu options to access/activate the submenu links.

VA Technical Reference Model v 24.7

LKTransfer
LKTransfer Technology

General InformationGeneral Information help

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website: Go to site
Description: LKTransfer is a laboratory workflow platform. The software manages all transactions between laboratories and Electronic Medical Record (EMR) systems through a web-based management dashboard. When a laboratory order is created in an EMR at the physician practice, LKTransfer picks up the order and delivers it to the laboratory. When the laboratory has completed the test results, LKTransfer delivers it to the EMR. This allows physician offices to request lab orders from an EMR and view the test results from the same EMR seamlessly.

LKTransfer does not store data or utilize a database; it is designed to deliver encrypted transfers of all orders and results between the laboratory and each physician practice. All connectivity for transmitting orders and results use Secure Sockets Layer (SSL) tunnel with secure RSA 2048-bit certificate.

Users can select different interface types (results or orders) and transfer types (pickup or delivery) depending on location (laboratory or physician office). For example, Pickup Configuration is used when sending data files from a machine to an outside location (for example, a laboratory). Conversely, Delivery Configuration is used to receive data from an outside location. In both cases, the data flows through a secure Data Center, so anytime a physician office sends files, the files go to the Data Center and then to the lab, and anytime a physician office receives files, the files flow from the lab to the Data Center and then to the physician office. For a results interface, results files are sent from the laboratory to the physician office`s local network to be delivered into the EMR. There are several options available to deliver data in the EMR such as Files in Folder, File Transfer Protocol (FTP) Location, Secure FTP (SFTP) Location, and Transmission Control Protocol (TCP)/Internet Protocol (IP). Additionally, the vendor utilizes Rackspace for hosting, which has data centers operating in Texas, Chicago, and Virginia, USA. The process for LKTransfer is to pass through and not store data.

The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g. VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e. SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITECSO
Technology/Standard Usage Requirements: Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information: This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision: View Decisions
Decision Source: TRM Mgmt Group
Decision Process: One-VA TRM v20.4
Decision Date: 04/13/2020 at 08:14:11 UTC
Introduced By: TRM Request
Vendor Name: ELLKAY, LLC
- The information contained on this page is accurate as of the Decision Date (04/13/2020 at 08:14:11 UTC).