| Literature DB >> 30888324 |
Tim Bezemer1, Mark Ch de Groot1, Enja Blasse1, Maarten J Ten Berg1, Teus H Kappen2, Annelien L Bredenoord3, Wouter W van Solinge1, Imo E Hoefer1, Saskia Haitjema1.
Abstract
The overwhelming amount, production speed, multidimensionality, and potential value of data currently available-often simplified and referred to as big data -exceed the limits of understanding of the human brain. At the same time, developments in data analytics and computational power provide the opportunity to obtain new insights and transfer data-provided added value to clinical practice in real time. What is the role of the health care professional in collaboration with the data scientist in the changing landscape of modern care? We discuss how health care professionals should provide expert knowledge in each of the stages of clinical decision support design: data level, algorithm level, and decision support level. Including various ethical considerations, we advocate for health care professionals to responsibly initiate and guide interprofessional teams, including patients, and embrace novel analytic technologies to translate big data into patient benefit driven by human(e) values. ©Tim Bezemer, Mark CH de Groot, Enja Blasse, Maarten J ten Berg, Teus H Kappen, Annelien L Bredenoord, Wouter W van Solinge, Imo E Hoefer, Saskia Haitjema. Originally published in the Journal of Medical Internet Research (http://www.jmir.org), 19.03.2019.Entities:
Keywords: artificial intelligence; big data; clinical decision support; data science; deep learning; expert systems; health care providers; machine learning; precision medicine
Year: 2019 PMID: 30888324 PMCID: PMC6444220 DOI: 10.2196/11732
Source DB: PubMed Journal: J Med Internet Res ISSN: 1438-8871 Impact factor: 5.428
This table shows the 3 levels in the building process of a clinical decision support system and some examples of where clinical expert knowledge of health care professionals plays a role in each of these levels.
| Level and example of issue | Example of expert knowledge | |
| Laboratory thresholds | Hemoglobin reference range to diagnose anemia | |
| Derived measurementsa | Body mass index | |
| Diagnostic codes | Grouping of related diagnoses in a study population | |
| Jargon | Same abbreviations having different meanings | |
| Temporality | Glucose values are highly dependent on the time of day (eg, pre- or postprandial) | |
| Methodological choices | How to handle missing data (eg, missing not at random) | |
| Feature engineeringa | Constructing relevant derived variables from raw data (eg, torsades de pointes, Wolff-Parkinson-White syndrome) | |
| Artifacts | For example, oxygen saturation of zero caused by a slipping pulse oximeter, switched leads in an electrocardiogram | |
| Interpretation of model output | Risk probability of 0.75 requires a warning ( | |
| Degree of autonomy | Tuning of implantable cardioverter defibrillator | |
| Knowledge on | Weighing a CDS system’s advice to treat while considering quality of life versus treatment burden in elderly cancer patients in a shared decision-making context | |
aDerived measurements may occur at the data level but also at the algorithm level; the former being undesirable because any manipulation at the data level may result in a loss of information.
bCDS: clinical decision support.
Table comparing different types of clinical data on some points important to clinical decision support systems.
| Clinical decision support issues | Electronic health record free-text/unstructured data (eg, clinical notes) | Registry/trial data (eg, case record forms case record forms and questionnaires) | Structured data/electronic health record (eg, lab values and smoking status) |
| Context completeness | Excellent: contextual information can be included. | Poor: context is essentially absent as a priori interpretation is an integral part of recording data in case record forms. | Depends on implementation. Context may be lost because of predetermined categorization. |
| Machine readability | Poor: information is mostly useful for case-specific usage by humans. May require text mining/text retrieval to convert to a machine-readable format. | Good: data are uniformly formatted and can be parsed by computers. | Excellent: data can be parsed or directly used by computers. |
| Translatability (between institutions) | Poor: free text contains jargon-specific, ambiguous abbreviations (eg, PCI: percutaneous coronary intervention/prophylactic cranial irradiation). | Excellent: trial data are usually collected using a standardized protocol, allowing for interoperability between institutions. | Good: lab values can be converted using reference values. Structured data, such as smoking and hypertensive status, can be reformatted for interoperability. |
| Noise resistance | Very poor: These type of data are very sensitive to | Excellent: data are recorded in a standardized way, designed to prevent noise. | Good: data are often machine-derived or recorded in a standardized way. However, bias because of differences in information-recording habits among health care professionals may arise. |
| Availability for reuse/general applicability | Excellent: these type of data are readily available, contain a lot of context (see Context completeness), and can thus be repurposed for a variety of applications. | Limited: trials are designed and conducted for one specific research question. | Excellent: these type of data are readily available and can thus be used for a plethora of purposes. |
| Design flexibility | Excellent: study design can be revisited if unanticipated bias effects arise. In this sense, bias could be | Poor: study design is | Excellent: study design can be revisited if unanticipated bias effects arise. In this sense, bias could be |