A PHP Error was encountered

Severity: Warning

Message: Undefined array key "choices"

Filename: controllers/Detail.php

Line Number: 249

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 249

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 249

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 249

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated

Filename: models/Detail_model.php

Line Number: 71

Backtrace:

File: /var/www/html/application/models/Detail_model.php
Line: 71
Function: strpos

File: /var/www/html/application/controllers/Detail.php
Line: 252
Function: insertAPISummary

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated

Filename: helpers/my_audit_helper.php

Line Number: 8919

Backtrace:

File: /var/www/html/application/helpers/my_audit_helper.php
Line: 8919
Function: str_replace

File: /var/www/html/application/controllers/Detail.php
Line: 255
Function: formatAIDetailSummary

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "choices"

Filename: controllers/Detail.php

Line Number: 256

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 256
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 256

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 256
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 256

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 256
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "usage"

Filename: controllers/Detail.php

Line Number: 257

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 257
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 257

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 257
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "usage"

Filename: controllers/Detail.php

Line Number: 258

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 258
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 258

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 258
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "usage"

Filename: controllers/Detail.php

Line Number: 259

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 259
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 259

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 259
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "usage"

Filename: controllers/Detail.php

Line Number: 260

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 260
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 260

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 260
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 260

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 260
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: file_get_contents(https://...@gmail.com&api_key=61f08fa0b96a73de8c900d749fcb997acc09): Failed to open stream: HTTP request failed! HTTP/1.1 429 Too Many Requests

Filename: helpers/my_audit_helper.php

Line Number: 143

Backtrace:

File: /var/www/html/application/helpers/my_audit_helper.php
Line: 143
Function: file_get_contents

File: /var/www/html/application/helpers/my_audit_helper.php
Line: 209
Function: simplexml_load_file_from_url

File: /var/www/html/application/helpers/my_audit_helper.php
Line: 3098
Function: getPubMedXML

File: /var/www/html/application/controllers/Detail.php
Line: 574
Function: pubMedSearch_Global

File: /var/www/html/application/controllers/Detail.php
Line: 488
Function: pubMedGetRelatedKeyword

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Attempt to read property "Count" on bool

Filename: helpers/my_audit_helper.php

Line Number: 3100

Backtrace:

File: /var/www/html/application/helpers/my_audit_helper.php
Line: 3100
Function: _error_handler

File: /var/www/html/application/controllers/Detail.php
Line: 574
Function: pubMedSearch_Global

File: /var/www/html/application/controllers/Detail.php
Line: 488
Function: pubMedGetRelatedKeyword

File: /var/www/html/index.php
Line: 316
Function: require_once

Integrating Patient-Based Real-Time Quality Control (PBRTQC) in a New Field: Inter-Comparison between Biochemical Instrumentations with LDL-C. | LitMetric

AI Article Synopsis

Article Abstract

Background: Patient-based real-time quality control (PBRTQC) can be a valuable tool in clinical laboratories due to its cost-effectiveness and constant monitoring. More focus is placed on discovering and improving algorithms that compliment conventional internal control techniques. The practical implementation of PBRTQC with a biochemical instrument comparison is lacking. We aim to evaluate PBRTQC's efficacy and practicality by comparing low-density lipoprotein cholesterol (LDL-C) test results to ensure consistent real-time monitoring across biochemical instrumentations in clinical laboratories.

Method: From 1 September 2021 to 30 August 2022, the First Affiliated Hospital of Xi'an Jiaotong University collected data from 158,259 both healthy and diseased patients, including 84,187 male and 74,072 female patients, and examined their LDL-C results. This dataset encompassed a group comprising 50,556 individuals undergoing health examinations, a group comprising 42,472 inpatients (IP), and a group comprising 75,490 outpatients (OP) for the PBRTQC intelligent monitoring platform to conduct daily tests, parameter configuration, program development, real-time execution, and performance validation of the patients' data. Moreover 40 patients' LDL-C levels were assessed using two biochemical analyzers, designated as the reference and comparator instruments. A total of 160 LDL-C results were obtained from 40 both healthy and diseased patients, including 14 OP, 16 IP, and 10 health examination attendees, who were selected to represent LDL-C levels broadly. Two biochemical instruments measured LDL-C measurements from the same individuals to investigate consistency and reproducibility across patient statuses and settings. We employed exponentially weighted moving average (EWMA) and moving median (MM) methods to calculate inter-instrument bias and ensure analytical accuracy. Inter-instrument bias for LDL-C measurements was determined by analyzing fresh serum samples, different concentrations of quality control (QC), and commercialized calibrators, employing both EWMA and MM within two assay systems. The assessment of inter-instrumental bias with five different methods adhered to the external quality assessment standards of the Clinical Laboratory Center of the Health Planning Commission, which mandates a bias within ±15.0%.

Result: We calculated inter-instrument comparison bias with each of the five methods based on patient big data. The comparison of fresh serum samples, different concentrations of QC, commercialized calibrators, and EWMA were all in the permissive range, except for MM. MM showed that the bias between two biochemical instruments in the concentration ranges of 1.5 mmoL/L-6.2 mmoL/L exceeded the permissible range. This was mainly due to the small number of specimens, affected by variations among individual patients, leading to increased false alarms and reduced effectiveness in monitoring the consistency of the inter-instrumental results. Moreover, the inter-comparison bias derived from EWMA was less than 3.01%, meeting the 15% range assessment criteria. The bias result for MM was lower than 24.66%, which was much higher than EWMA. Thus, EWMA is better than MM for monitoring inter-instrument comparability. PBRTQC can complement the use of inter-comparison bias between biochemical analyzers. EWMA has comparable inter-instrument comparability monitoring efficacy.

Conclusions: The utilization of AI-based PBRTQC enables the automated real-time comparison of test results across different biochemical instruments, leading to a reduction in laboratory operating costs, enhanced work efficiency, and improved QC. This advanced technology facilitates seamless data integration and analysis, ultimately contributing to a more streamlined and efficient laboratory workflow in the biomedical field.

Download full-text PDF

Source
http://www.ncbi.nlm.nih.gov/pmc/articles/PMC11083131PMC
http://dx.doi.org/10.3390/diagnostics14090872DOI Listing

Publication Analysis

Top Keywords

quality control
12
group comprising
12
biochemical instruments
12
bias
9
patient-based real-time
8
real-time quality
8
control pbrtqc
8
biochemical
8
biochemical instrumentations
8
ldl-c
8

Similar Publications

Want AI Summaries of new PubMed Abstracts delivered to your In-box?

Enter search terms and have AI summaries delivered each week - change queries or unsubscribe any time!