Process Documentation- LabCorp

Table of Content
1. Point of Contacts
2. Test Records Information
3. Engine Requirements
4. Workflow
5. Mapping for Data Transfer
6. Testing
7. Post-Go Live
 Teams Point of Contact
Lab Team Simibhat@gmail.com
Bridges Team HeatherBhat@gmail.com
Lab Operations LisBhat@gmail.com
Engine Team Pratik@gmail.com
LabCorp Website www.LabCorp.com, Adairhelen@gmail.com
POINT OF CONTACT
This section provides information about the key individuals responsible for the LabCorp
implementation project. It includes their names, roles, contact details, and responsibilities. The
designated points of contact will facilitate communication, coordination, and issue resolution
throughout the implementation process.

TEST RECORD INFORMATION

Here, we outline the necessary details related to test records. This includes the types of test records
required, their formats, and any specific information or documentation needed for the LabCorp
implementation. The document will guide you on how to prepare and organize test records
effectively. This can be downloaded from the website or can be requested by sending an email to
LabCorpTeams@gmail.com.

Format of Request

Subject: Request for Compendium

Send order codes of the test records you need compendium for.

ENGINE REQUIREMENTS
In this section, we present the hardware, software, and infrastructure requirements for the LabCorp
engine. These requirements ensure optimal performance and compatibility with your existing
systems. The document provides a comprehensive list of specifications and configurations necessary
for successful implementation.

LabCorp is using Rapsody engine, Team Name: Engine Team

Data is exchanged between system using HL7 interoperability standards which goes from electronic
health record to third-party labs through engines. Below is the flow of data in hospital scenarios:

EMR> EMR Interface > EMR Engine> LabCorp Engine> LabCorp Interface> LabCorp
WORKFLOWS
This section includes the workflows where we need to send patient draws and specimen to LabCorp
for testing. We need to define steps in inpatient as well as outpatient context of the LabCorp lab has
a role to play. The workflow section describes the step-by-step process involved in the LabCorp
implementation. This would include the timeline, process, and requirements for any orders LabCorp
testing.
Two scenarios where any lab would need LabCorp assistance
Inpatient: Where specimen is collected within the facility and send it out to LabCorp for testing.
LabCorp then sends back the result through available channels like interfaces, fax.

Outpatient: Where order is placed within the facility but the specimen is collected at the LabCorp
Lab and once the testing is performed successfully, results are sent back to the facility through
available channels like interfaces, fax.

MAPPING FOR DATA TRANSFER

Here, we discuss the mapping process for transferring data from your current system to the LabCorp
platform. This includes identifying data fields, defining data mappings, and ensuring data integrity
during the transfer. The document provides guidelines and best practices to ensure accurate and
seamless data migration.

For any lab order to go through the right LabCorp process/channel, it needs a specific mapping which
is provided my LabCorp team and needs to be mapped at the required fields for the procedure
records and result observations.

TESTING
The testing phase is crucial for ensuring the functionality, performance, and reliability of the LabCorp
implementation. This section explains the testing approach, test scenarios, and test cases that will be
executed to validate the system. It also outlines the roles and responsibilities of the testing team and
provides guidelines for reporting and resolving issues.

POST-GO LIVE
After the successful implementation of LabCorp, this section addresses the post-go-live activities. It
covers topics such as user training, ongoing support, system maintenance, and monitoring. The
document provides guidance on how to effectively manage the system post-implementation to
ensure smooth operations and user satisfaction.