1 / 33

1 Jožef Stefan Institute, Slovenia 2 CIMNE, Spain 3 Atos, Spain 4 Ibermática, Spain

Supporting c linical p rofessionals in the d ecision-making for p atients with c hronic d iseases. Mitja Luštrek 1 , Božidara Cvetković 1 , Maurizio Bordone 2 , Eduardo Soudah 2 , Carlos Cavero 3 , Juan Mario Rodríguez 3 , Aitor Moreno 4 , Alexander Brasaola 4 , Paolo Emilio Puddu 5.

santos
Download Presentation

1 Jožef Stefan Institute, Slovenia 2 CIMNE, Spain 3 Atos, Spain 4 Ibermática, Spain

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Supporting clinical professionals in the decision-making for patients with chronic diseases Mitja Luštrek1,Božidara Cvetković1, Maurizio Bordone2, Eduardo Soudah2, Carlos Cavero3, Juan Mario Rodríguez3, Aitor Moreno4, Alexander Brasaola4, Paolo Emilio Puddu5 • 1 Jožef Stefan Institute, Slovenia • 2 CIMNE, Spain • 3Atos, Spain • 4Ibermática, Spain • 5University of Rome “La Sapienza”, Italy

  2. Rationale • Medical labs produce a lot of data on a patient • Telemonitoring produces even more data • The amount of medical literature is huge • Overwhelming for a clinical professional

  3. Rationale • Medical labs produce a lot of data on a patient • Telemonitoring produces even more data • The amount of medical literature is huge • Overwhelming for a clinical professional • Needs tools to make sense of all these data • Decision support system (DSS)

  4. Clinical workflow • The doctor starts examining the condition of a patient, possibly because of an alert by the DSS.

  5. Clinical workflow • The doctor starts examining the condition of a patient, possibly because of an alert by the DSS. • The doctor examines the patient’s current(and historic) risk, computed by the DSS.

  6. Clinical workflow • The doctor starts examining the condition of a patient, possibly because of an alert by the DSS. • The doctor examines the patient’s current (and historic) risk, computed by the DSS. • If the risk is high, the doctor looks for reasons. The DSS computes the contribution to the risk for each of the monitored parameters.

  7. Clinical workflow • The doctor starts examining the condition of a patient, possibly because of an alert by the DSS. • The doctor examines the patient’s current (and historic) risk, computed by the DSS. • If the risk is high, the doctor looks for reasons. The DSS computes the contribution to the risk for each of the monitored parameters. • The doctor may look for further information in the medical literature with the help of the DSS.

  8. Clinical workflow • The doctor starts examining the condition of a patient, possibly because of an alert by the DSS. • The doctor examines the patient’s current (and historic) risk, computed by the DSS. • If the risk is high, the doctor looks for reasons. The DSS computes the contribution to the risk for each of the monitored parameters. • The doctor may look for further information in the medical literature with the help of the DSS. • The doctor may reconfigure the DSS.

  9. DSS architecture Alerts Configuration Sensors Risk assessment Electronichealthrecord Expertknowledge Machinelearning Anomalydetection External data Literature consultation

  10. Risk assessment – expert knowledge Alerts Configuration Sensors Risk assessment Electronichealthrecord Expertknowledge Machinelearning Anomalydetection External data Literature consultation

  11. Monitored parameters • Search of medical literature for parameters affecting the risk (for congestive heart failure) • Survey among 32 cardiologists to determine the importance of these parameters

  12. Monitored parameters • Search of medical literature for parameters affecting the risk (for congestive heart failure) • Survey among 32 cardiologists to determine the importance of these parameters • Additional information for each parameter: • Minimum, maximum value • Whether larger value means higher or lower risk • Values indicating green, yellow or red condition • Frequency of measurement (low = static, medium = measured by the doctor, high = telemonitored)

  13. Risk assessment models • Normalize parameter values: [0, 1] interval, 0 = lowest risk, 1 = highest risk

  14. Risk assessment models • Normalize parameter values: [0, 1] interval, 0 = lowest risk, 1 = highest risk • Long-term model: sum of normalized values, weighted by their importance • Medium-term model: low-frequency parameters weighted by 1/3 • Short-term model:low-frequency parameters weighted by 1/9, medium-term by 1/3

  15. Prototype

  16. Risk assessment – machine learning Alerts Configuration Sensors Risk assessment Electronichealthrecord Expertknowledge Machinelearning Anomalydetection External data Literature consultation

  17. Risk assessment – machine learning • Training data:[parameter values, cardiac event or no event] • Feature selection, decorrelation • Machine learning model selection:multilayer perceptron with input (parameters), hidden, and output (risk) layer • Training:85 % accuracy on a public heart disease dataset

  18. Risk assessment – anomaly detection Alerts Configuration Sensors Risk assessment Electronichealthrecord Expertknowledge Machinelearning Anomalydetection External data Literature consultation

  19. Risk assessment – anomaly detection Detect anomalous (= not observed before) parameter values and their relations + No knowledge or data labeled with cardiac events needed – Anomalies do not alway mean higher risk

  20. Risk assessment – anomaly detection Detect anomalous (= not observed before) parameter values and their relations + No knowledge or data labeled with cardiac events needed – Anomalies do not alway mean higher risk More on this in a separate presentation in this session by Božidara Cvetković

  21. Literature consultation Alerts Configuration Sensors Risk assessment Electronichealthrecord Expertknowledge Machinelearning Anomalydetection External data Literature consultation

  22. Literature consultation Free text (EHR) contextualization Free text / PICO question Query Ontology maping Annotate, evaluate Resources: PubMed Cochrane Library ... Semantic search Results Ranking

  23. Literature consultation Free text (EHR) contextualization Free text / PICO question Query Ontology maping Annotate, evaluate Resources: PubMed Cochrane Library ... Semantic search Results Ranking

  24. Literature consultation Free text (EHR) contextualization Free text / PICO question Query Ontology maping Annotate, evaluate Resources: PubMed Cochrane Library ... Semantic search Results Ranking

  25. Literature consultation Free text (EHR) contextualization Free text / PICO question Query Ontology maping Annotate, evaluate Resources: PubMed Cochrane Library ... Semantic search Results Ranking

  26. Literature consultation Free text (EHR) contextualization Free text / PICO question Query Ontology maping Annotate, evaluate Resources: PubMed Cochrane Library ... Semantic search Results Ranking

  27. Literature consultation Free text (EHR) contextualization Free text / PICO question Query Ontology maping Annotate, evaluate Resources: PubMed Cochrane Library ... Semantic search Results Ranking

  28. Literature consultation Free text (EHR) contextualization Free text / PICO question Query Ontology maping Annotate, evaluate Resources: PubMed Cochrane Library ... Semantic search Results Ranking

  29. Alerts and configuration Alerts Configuration Sensors Risk assessment Electronichealthrecord Expertknowledge Machinelearning Anomalydetection External data Literature consultation

  30. Alerts and configuration Alerts: • Rule engine using the Drools platform • Rules triggered on parameter or risk values • Alert modes (SMS, email) depend on the trigger

  31. Alerts and configuration Alerts: • Rule engine using the Drools platform • Rules triggered on parameter or risk values • Alert modes (SMS, email) depend on the trigger Configuration: • Parameters to be monitored for each patient • Parameter values indicating green, yellow or red condition for each patient

  32. Conclusion • DSS tailored to a (fairly generic) clinical workflow • Can be used for all diseases to which the workflow is applicable • Congestive heart failure as a case study

  33. Conclusion • DSS tailored to a (fairly generic) clinical workflow • Can be used for all diseases to which the workflow is applicable • Congestive heart failure as a case study • Observational study with 100 patients starting shortly • Tuning and testing once the data from the study is available

More Related