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

MediCopia Specimen Collection
MediCopia Specimen Collection 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: MediCopia Specimen Collection is a software application that is used for positive patient identification (PPID) during specimen collecting. This software is used in conjunction with a scanner hardware device and a printer hardware device. This application requires users to scan patient identification bracelets with the scanner to prevent collecting specimens from the wrong patients. The printer is used to print the appropriate barcode label at bedside after collection in order to eliminate incorrect specimen labeling.

This technology is compatible with the following scanner hardware devices: Zebra TC51HC handheld, MC55A handheld, and DS6708 handheld.

MediCopia Specimen Collection is compatible with the following printer hardware devices: QLnHC printer, QLn220 printer, and ZD410 printer. This technology uses Bluetooth technology to connect to the QLn220 printer device.

MediCopia Specimen Collection utilizes the Microsoft Structured Query Language (SQL) server for data storage.

This technology has the option to utilize the cloud for data storage and for its communication messaging system between users.

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 v24.6
Decision Date: 06/07/2024 at 18:33:11 UTC
Introduced By: TRM Request
Vendor Name: Lattice Solutions
- The information contained on this page is accurate as of the Decision Date (06/07/2024 at 18:33:11 UTC).