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

Patients' Preferences for Artificial Intelligence Applications Versus Clinicians in Disease Diagnosis During the SARS-CoV-2 Pandemic in China: Discrete Choice Experiment. | LitMetric

AI Article Synopsis

Article Abstract

Background: Misdiagnosis, arbitrary charges, annoying queues, and clinic waiting times among others are long-standing phenomena in the medical industry across the world. These factors can contribute to patient anxiety about misdiagnosis by clinicians. However, with the increasing growth in use of big data in biomedical and health care communities, the performance of artificial intelligence (Al) techniques of diagnosis is improving and can help avoid medical practice errors, including under the current circumstance of COVID-19.

Objective: This study aims to visualize and measure patients' heterogeneous preferences from various angles of AI diagnosis versus clinicians in the context of the COVID-19 epidemic in China. We also aim to illustrate the different decision-making factors of the latent class of a discrete choice experiment (DCE) and prospects for the application of AI techniques in judgment and management during the pandemic of SARS-CoV-2 and in the future.

Methods: A DCE approach was the main analysis method applied in this paper. Attributes from different dimensions were hypothesized: diagnostic method, outpatient waiting time, diagnosis time, accuracy, follow-up after diagnosis, and diagnostic expense. After that, a questionnaire is formed. With collected data from the DCE questionnaire, we apply Sawtooth software to construct a generalized multinomial logit (GMNL) model, mixed logit model, and latent class model with the data sets. Moreover, we calculate the variables' coefficients, standard error, P value, and odds ratio (OR) and form a utility report to present the importance and weighted percentage of attributes.

Results: A total of 55.8% of the respondents (428 out of 767) opted for AI diagnosis regardless of the description of the clinicians. In the GMNL model, we found that people prefer the 100% accuracy level the most (OR 4.548, 95% CI 4.048-5.110, P<.001). For the latent class model, the most acceptable model consists of 3 latent classes of respondents. The attributes with the most substantial effects and highest percentage weights are the accuracy (39.29% in general) and expense of diagnosis (21.69% in general), especially the preferences for the diagnosis "accuracy" attribute, which is constant across classes. For class 1 and class 3, people prefer the AI + clinicians method (class 1: OR 1.247, 95% CI 1.036-1.463, P<.001; class 3: OR 1.958, 95% CI 1.769-2.167, P<.001). For class 2, people prefer the AI method (OR 1.546, 95% CI 0.883-2.707, P=.37). The OR of levels of attributes increases with the increase of accuracy across all classes.

Conclusions: Latent class analysis was prominent and useful in quantifying preferences for attributes of diagnosis choice. People's preferences for the "accuracy" and "diagnostic expenses" attributes are palpable. AI will have a potential market. However, accuracy and diagnosis expenses need to be taken into consideration.

Download full-text PDF

Source
http://www.ncbi.nlm.nih.gov/pmc/articles/PMC7903977PMC
http://dx.doi.org/10.2196/22841DOI Listing

Publication Analysis

Top Keywords

artificial intelligence
8
versus clinicians
8
discrete choice
8
choice experiment
8
latent class
8
gmnl model
8
diagnosis
6
patients' preferences
4
preferences artificial
4
intelligence applications
4

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!

A PHP Error was encountered

Severity: Notice

Message: fwrite(): Write of 34 bytes failed with errno=28 No space left on device

Filename: drivers/Session_files_driver.php

Line Number: 272

Backtrace:

A PHP Error was encountered

Severity: Warning

Message: session_write_close(): Failed to write session data using user defined save handler. (session.save_path: /var/lib/php/sessions)

Filename: Unknown

Line Number: 0

Backtrace: