Medical Imaging Assistant Basic Priorities Patient List

Budget: 30$ Our project deals with the use of a recently proposed technique in literature: Artificial Intelligence (AI) models. These models will incorporate information from several different modes by a User Interface (UI) with AI-Assisted techniques behind. Therefore, we aim to improve our already implemented Medical Imaging (MI) Assistant that will assist physicians across diagnosis. Related with our last projects [1, 2], with the presented project we aim at exploring the acquired sets of data among system functionalities and features. The purpose is to develop a list of priorities (i.e., the results that are more important for the final BIRADS on a top-down order) for our decision model. Each priority has the percentage of the achieved value, resulted from computing our AI models. Users can manage the provided priorities so that, it is possible to re-configure them (see uploaded images). For instance, if the system considers wrongly the Shape as more important in comparison to Margin, the user can change and put the Margin on the top of the list. As stated, we need to develop a list of priorities for each Patient ID. For the purpose, we will use the JSON format as usual. Each Patient ID will be available on a foo/ folder, to be designated. For instance, inside the foo/ folder, we will have [login to view URL] file (see uploaded example), where 12345 is the Patient ID. Inside this file, the structure is simple (see next source code). For now, we will have an attr variable that represents the priority. Each attr priority will have the respective value associated. Both model_order and user_order are representing the priority order on the list. The lower the value, the higher the priority. This means that a "model_order": 0 will have top priority. The difference between model_order and user_order is that the model_order represents the attributed value that came from the one considered by the AI model. On the other hand, the user_order starts by default with the same value as model_order. However, when the user changes the order on the UI, it will change this user_order value. Note: The Shape and Margin values are patient-wise, instead of being lesion-wise. The following structure shows a data representation of our idea: [1] https://www.freelancer.com/projects/html/Medical-Imaging-Assistant-Basic-Features [2] https://www.freelancer.com/projects/html/Assistant-Interactive-Preliminary