Diagnostic assistance based on patient feedback

Marc Shawky is a pro­fes­sor of com­put­er engi­neer­ing and a mem­ber of the ‘Care, Vul­ner­a­bil­i­ty and Tech­nolo­gies’ team, for­mer­ly CRI, at the UTC Costech Lab­o­ra­to­ry. He is work­ing on the devel­op­ment of tools to aid in the diag­no­sis of Lyme dis­ease and deci­sion-mak­ing based on patient feedback.

The restruc­tur­ing of our research team more clear­ly high­lights the team’s areas of focus, empha­sis­ing the ’care” aspect of our approach­es. Cur­rent work on Lyme dis­ease is part of the Num4Lyme and Dia­ly­me projects, fund­ed respec­tive­ly by the Sor­bonne Cen­tre for Arti­fi­cial Intel­li­gence (SCAI) of the Sor­bonne Uni­ver­si­ty Alliance and the Hauts-de-France Region,” explains Marc Shawky.

The research focus­es on big data analy­sis and machine learn­ing, which pos­es chal­lenges not only in terms of data col­lec­tion but also data security.

The chal­lenge of data col­lec­tion? “Ini­tial­ly, we thought we would work with data from the Saint-Côme Poly­clin­ic in Com­piègne. How­ev­er, not only did it take a long time to set up the agree­ment, but the data avail­able was not ful­ly digi­tised. To save time, we retrieved anonymised data from 450 patients at Mater Mis­eri­cor­diae Hos­pi­tal in Dublin, which was look­ing for part­ners to eval­u­ate antibi­ot­ic treat­ments. This data­base is very spe­cif­ic in that it con­sists of Lyme dis­ease patients before and after treat­ment. Oth­er data from the Amer­i­can ILADS net­work, which spe­cialis­es in patients with vec­tor-borne dis­eases, also sup­ple­ment­ed our data,” he explains.

What about data secu­ri­ty? “As UTC does not have the option of hav­ing per­son­al data man­aged by the IT depart­ment, we opt­ed for com­plete­ly anonymised data. We also sought the opin­ion of the Sor­bonne Uni­ver­si­ty Ethics Com­mit­tee, to which we report, pro­vid­ing it with details of all the IT pro­cess­ing car­ried out on this data, as well as the audit by the UTC IT depart­ment, in order to reas­sure it about secu­ri­ty aspects. This result­ed in a favourable opin­ion,” he explains.

Marc Shawky: what is unique about your team approach? “At UTC-Costech, the analy­sis of this data is part of the syn­er­gy between the approach­es of “pro­vid­ing care”, i.e., pro­vid­ing med­ical treat­ment, and “car­ing”. The ques­tion we asked our­selves in the first case was: what can AI con­tribute and what type of AI do we want to use? From the out­set, we focused on devel­op­ing mod­els cen­tred on patients’ feel­ings. In short, we want­ed patients to be able to express their con­di­tion as they per­ceived it. We want­ed symp­toms and clin­i­cal signs to be an inte­gral part of the analy­sis. How­ev­er, these clin­i­cal signs remain sub­jec­tive and can involve near­ly 200 dif­fer­ent para­me­ters, in addi­tion to the bio­chem­i­cal para­me­ters from blood tests and oth­er sero­log­i­cal tests,” empha­sis­es Marc Shawky.

These analy­ses can include near­ly 400 spe­cif­ic para­me­ters per patient. “For exam­ple, we may have 10 clin­i­cal signs relat­ing to joint pain or headaches. They can also be cog­ni­tive in nature, such as mem­o­ry dis­or­ders, par­tic­u­lar­ly short-term mem­o­ry. Oth­er symp­toms such as car­diac arrhyth­mia or extreme fatigue are often cit­ed, to which oth­er signs may be added in the event of co-infec­tion. Indeed, when a tick bites, it can trans­mit Lyme dis­ease, but also oth­er bac­te­ria, virus­es or par­a­sites,” he explains.

Data analy­sis there­fore relies on AI and, more specif­i­cal­ly, on machine learn­ing, with approach­es capa­ble of com­bin­ing sub­jec­tive and clear­ly numer­i­cal para­me­ters. “Ini­tial­ly, the idea was to devel­op a diag­nos­tic tool, but we quick­ly realised that pro­vid­ing a pos­i­tive or neg­a­tive diag­no­sis was not effec­tive. We shift­ed our focus to devel­op­ing a deci­sion-mak­ing aid for hos­pi­tal doc­tors. A tool with a fea­ture that cal­cu­lates the prox­im­i­ty between patient pro­files. Com­put­er opti­mi­sa­tions were devel­oped to process data local­ly on the clin­i­cian’s com­put­er, trans­fer­ring only the soft­ware code from the serv­er to the com­put­er and not the patient data to the serv­er,” he adds.

How does this play out, in con­crete terms? “In a hos­pi­tal set­ting, doc­tors will use this tool to select patients from the data­base whom they have decid­ed to treat because they con­sid­er that they have suf­fi­cient evi­dence to prove that Lyme dis­ease has been con­tract­ed. But this same tool will also enable them to cal­cu­late the prox­im­i­ty of the pro­files of patients treat­ed with oth­er patients in the data­base, in order to deter­mine the most sim­i­lar pro­files and issue rec­om­men­da­tions that the prac­ti­tion­er may or may not fol­low,” con­cludes Marc Shawky.

MSD

Le magazine

linkedin facebook pinterest youtube rss twitter instagram facebook-blank rss-blank linkedin-blank pinterest youtube twitter instagram