User:Shawndouglas/sandbox/sublevel43

From LIMSWiki
Jump to: navigation, search

26. Instrument data systems functions

Requirement and response
26.1 The system should be able to use an application programming interface or web services to communicate with instrument data systems.
 


RESPONSE:
 
26.2 The system should be capable of sending samples and test orders to instrument data systems.
 


RESPONSE:
 
26.3 The system should be capable of sending samples and test orders to instrument data systems.
 


RESPONSE:
 
26.4 The system should be capable of generically parsing instrument data to extract important sample details and results.
 


RESPONSE:
 

27. Systems integration

Requirement and response
27.1 The system should be capable of communicating any status changes for samples, lots, instruments, and other dynamic entities to and from external systems.
 


RESPONSE:
 
27.2 The system should accurately communicate status changes to external systems.
 


RESPONSE:
 
27.3 The system shall provide a means to choose—based on date and type of data—electronic data and metadata to archive.
 


RESPONSE:
 
27.4 The system shall provide a guaranteed means to retrieve and restore archived data and metadata that is readable and accurate.
 


RESPONSE:
 
27.5 The system should feature a reliable, effective, and supported data storage system.
 


RESPONSE:
 
27.6 The system should be able to interface directly with a third-party reporting tool.
 


RESPONSE:
 
27.7 The system should be capable of being configured to and conform to the laboratory's existing data storage platforms and standards.
 


RESPONSE:
 
27.8 The system should provide the ability to modify the data structures of the data storage mechanism as needed.
 


RESPONSE:
 
27.9 The system should allow for both development and production environments for its data storage tools and allow the movement of records from one environment to another.
 


RESPONSE:
 
27.10 The system shall provide data storage tools capable of fine-tuning the performance and security of data.
 


RESPONSE:
 
27.11 The system’s data storage tools shall provide data backup and retrieval functions that meet or exceed industry best practices, including producing exact and complete backups that are secure from manipulation and loss.
 


RESPONSE:
 
27.12 The architecture of the system should be organized such that modules are clearly and logically separated, with standard interfaces provided between the modules.
 


RESPONSE:
 
27.13 The system should be able to optimally use system and hardware resources to allow for concurrent usage and high-peak usage.
 


RESPONSE:
 
27.14 The system should come with a well-documented application programming interface in order to facilitate granular interfaces with the system's underlying modular functionality.
 


RESPONSE:
 
27.15 The system shall provide a means to integrate and exchange data electronically based on relevant methods, and in such a way so as to ensure accurate and secure data transfer and processing.
 


RESPONSE:
 
27.16 The system shall be able to accurately replicate its data storage tools to ensure a recoverable system in the event of hardware failure.
 


RESPONSE:
 
27.17 The system should be able to interface with an external enterprise resource planning system.
 


RESPONSE:
 
27.18 The system should be capable of interfacing with enterprise middleware.
 


RESPONSE:
 

28. Laboratory scheduling and capacity planning

Requirement and response
28.1 The system should be able to accurately gauge and report test-based work capacity or throughput.
 


RESPONSE:
 
28.2 The system should provide scheduling tools for allocating personnel and instruments to laboratory tasks.
 


RESPONSE:
 
28.3 The system should provide a means for tasks to be scheduled and allocated against available resources.
 


RESPONSE:
 
28.4 The system should be able to track and limit the quantity of samples or hours worked on a type of sample by personnel, e.g., number of cytology slides or hours worked on them.
 


RESPONSE:
 

29. Lean laboratory and continuous improvement

Requirement and response
29.1 The system should support a workload leveling strategy that automatically releases laboratory tasks to personnel.
 


RESPONSE:
 
29.2 The system should provide a means to quickly visualize and assess workflow processes at strategic points.
 


RESPONSE:
 
29.3 The system should provide a means for mapping everyday workflow while identifying potential failure points.
 


RESPONSE:
 

30. Artificial intelligence and smart systems

Requirement and response
30.1 The system should provide a means for integrating artificial intelligence (AI) into laboratory workflow as a smart agent or assistant.
 


RESPONSE:
 
30.2 The system should support ontology-based machine learning for assisting with the analysis of laboratory informatics datasets.
 


RESPONSE:
 
30.3 The system should support voice data capture and retrieval as smart laboratory assistance functions.
 


RESPONSE:
 
30.4 The system should be able to reschedule samples, change test assignments, and perform other laboratory activities based on voice command input.
 


RESPONSE:
 
30.5 The system should support predictive maintenance routines for laboratory instruments and equipment.
 


RESPONSE:
 
30.6 The system should judiciously allow various system parameters to be optimized and ideal models set within the system by AI.
 


RESPONSE:
 
30.7 The system should allow AI to algorithmically infer from past learning how to customize without explicit instruction system parameters such as aggregation, transformation, and reporting of data.
 


RESPONSE:
 
30.8 The system should monitor laboratory operation parameters (such as capacity utilization and data integrity risks) and send notifications when necessary with recommendations for immediate and corrective action. The system should also maintain a log of all such monitored operational parameters and their status changes.
 


RESPONSE:
 
30.9 The system should allow for other types of facility monitoring (such as alarm, light, lock, and door statuses) and send notifications when necessary with recommendations for immediate and corrective action. The system should also maintain a log of all such monitored systems and their status changes.
 


RESPONSE:
 
30.10 The system should monitor instrument health (such as critical parameters and maintenance timing) and send notifications when necessary with recommendations for immediate and corrective action. The system should also maintain a log of all such monitored instrument activities and status changes.
 


RESPONSE:
 
30.11 The system should allow for environmental control and monitoring of equipment (such as incubators and freezers) and send notifications when necessary with recommendations for immediate and corrective action. The system should also maintain a log of all such monitored equipment and their associated status changes.
 


RESPONSE: