The Yuan requests your support! Our content will now be available free of charge for all registered subscribers, consistent with our mission to make AI a human commons accessible to all. We are therefore requesting donations from our readers so we may continue bringing you insightful reportage of this awesome technology that is sweeping the world. Donate now
Drifting data: post-deployment considerations - clinical MLOps*
By George Mastorakos  |  Jul 19, 2022
Drifting data: post-deployment considerations - clinical MLOps*
Taihai  Sui  for  The  Yuan
What happens after a model is built and deployed and is in use by clinical stakeholders? Changes in patient data and their relationships are ineluctable, and models must be maintained, surveilled, and adapted accordingly to continue performing well. This is the world of Machine Learning Operations.

PHOENIX, ARIZONA - Change is inevitable, so it is unwise to plan for only one rainy day. Alternatively, it is always wise to have a dynamic plan in place that outlines procedures for how to best cope with and adapt to rainy days when they do arrive. Whether talking about literal precipitation, financial stability, or the anticipation of novel input data to a clinical machine learning (ML) model, the same wisdom applies. 

As mentioned in prior articles, designing and executing an end-to-end clinical ML environment is no walk in the park. One must also do the following: scope the goals of stakeholders to identify a project’s goal, identify which data match those goals, get permission to access data, curate, assess, and describe the data, pre-process the data, and build a model and validate it model, to name a few of the myriad important tasks one must consider. 

Suppose one does surmount all the difficulties that come with executing a clinical ML model. This all seems great, since performance is good, stakeholders are happy, and value is seemingly added to the clinic as a whole. Lurking in the ether, however, is an insidious, familiar mastermind that is adrift, interfering with everything that seemed great with our new model: change. The clinical input data slowly change, drift, and morph into a slightly different animal. 

Depending on the use case, such data drift and concept drift - changes of the relationships between inputs and outputs, i.e., between the data and labels - of the data can decimate the performance of models and lead to inaccurate predictions, which can also potentially lead to suboptimal care for patients. Data drift is just one of many issues relating to the post-integration phase of clinical artificial intelligence (AI). Thus, the proper maintenance and continual

The content herein is subject to copyright by The Yuan. All rights reserved. The content of the services is owned or licensed to The Yuan. Such content from The Yuan may be shared and reprinted but must clearly identify The Yuan as its original source. Content from a third-party copyright holder identified in the copyright notice contained in such third party’s content appearing in The Yuan must likewise be clearly labeled as such.
Continue reading
Sign up now to read this story for free.
- or -
Continue with Linkedin Continue with Google
Comments
Share your thoughts.
The Yuan wants to hear your voice. We welcome your on-topic commentary, critique, and expertise. All comments are moderated for civility.