How do we leverage data through replication and warehousing to meet blood collection and transfusion service needs.
Аннотация
BACKGROUND
With the widespread adoption of Blood Establishment Computer Systems and other Blood Collection and Transfusion Service (BCTS) clinical information systems (CIS), electronic blood donor, product, and patient data are now routinely required for clinical, regulatory, operational, and quality needs. That data are often not readily accessible for such secondary use within CIS databases, particularly for applications with significant data availability requirements such as machine learning and artificial intelligence. Data replication provides one avenue by which CIS data can be made more readily available.
STUDY DESIGN AND
METHODS
Members of the AABB's Information Systems Committee along with institutional information technology colleagues provided a multi-institutional viewpoint on data replication through the lens of BCTS specific use cases. Case studies of informatics offerings leveraging such technologies were also elicited.
RESULTS
Six distinct use cases describe the potential role of data replication including the creation of data warehouses for frontline laboratory staff. Specific BCTS examples for each use case are presented to highlight the value of data replication, including visualization of critical inventory (O red blood cells, HLA-compatible platelets) and utilization analytics for patient blood management. Two case studies describe the approach to implement such technologies to (1) optimize staffing via laboratory workload reporting and (2) improve access to blood via antigen-negative blood product location services.
DISCUSSION: Data replication and warehousing can empower BCTS analytic offerings not otherwise natively available through one's CIS to improve patient care and laboratory operations.
Предметные рубрики MeSH
Подготовка и перевод публикации
Обработка статьи · этапы, ошибки и управление
Ошибки и ограничения
История · было → стало
Состояние обновляется каждые 5 секунд, пока блок открыт. Процент показывается только там, где известен объём работы. Пауза останавливает продолжение этапа; текущий запрос к источнику может завершиться.
Тип публикации указан по данным источника. Уровень доказательности автоматически не присваивается.