How It's Done
LigoLab - Laboratory Information System can only benefit your organization if it gets deployed. We frequently hear about difficulties that arise to disrupt, delay or even cancel the LIS implementation. Listening to these stories we decided to share the risk of implementation with our partner laboratories. To assure the implementation is 100% sucessful and delivered on time, license fees are not billed until the system is up and running in production environment. Below is a summary of our implementation process that we have refined over the past years of successfully implementing our solution at laboratories accross the nation.
Following agreement execution LigoLab implements a test (or sandbox) LIS environment that will be used for training, configuration and validation of the LIS. Following the deployment of the test environment, LigoLab staff (comprised of domain experts, technical personnel and trainers) come on site to conduct a domain analysis (information gathering) and conduct user workshops, where current and future workflows are identified. With the assistance of an LIS manager these findings are configured as settings in the LigoLab LIS.
System configuration by the LIS manager (and our assistance) may take two to six months depending on the complexity, personnel availability and overall organization readiness. During the configuration period we identify one to three clients (to cover all the varieties of specimens and tests) and begin parallel processing of these cases through the system; these cases are used for testing, training and validation of the system.
Constant communication is key to a successful implementation. LigoLab personnel come on site and hold many remote sessions to assist and train during the implementation period. During configuration and training our interfacing and data import teams analyze all current interfaces and their conversion process as well as prepare scripts to import previous patient history into the new system.
Once a go-live date is identified and scheduled LigoLab reserves 100% of implementation support staff to the project; we only perform one implementation at a time, assuring a successful implementation. LigoLab staff will be on-site two weeks before go-live for final personnel training sessions per department and role. Two days before go-live, we enter in parallel all cases through both systems and switch over during a weekend; during the weekend the historical data is imported, all previous parallel and test patient data is deleted, the test environment is cloned to production and the system is ready to go live. LigoLab staff will be on-site for another week to assist. Since we are local we can easily extend these time periods.
Data Importing and Exporting
LigoLab LIS is using standardized XML format (LigoXML) to support data export and import needs. LigoXML provides comprehensive coverage for all LIS data elements and supports the following import-export scenarios:
- CRM Import (ability to accept Client and Provider information maintained in external CRM system)
- ADT Import (ability to accept Patient information from external systems)
- Order Import (ability to accept orders from external systems)
- Report Export (ability to export reports/results to external system)
- Result Import (ability to accept results from external systems)
- Generic LIS export (ability to perform customized export of all LIS data elements (demographics, results, orders, diagnosis, CPT codes, etc ...) to external systems (e.g. billing)
We use and contribute source code to an open-source interface engine (Mirth) to facilitate conversion between LigoXML and industry-standard formats (HL7, ASTM, X12) as well as to support a variety of transport protocols (MLLP, Web Service, S/FTP).