Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non-Annotated MRI Frame Warning #99

Open
FMCalisto opened this issue Feb 4, 2019 · 1 comment
Open

Non-Annotated MRI Frame Warning #99

FMCalisto opened this issue Feb 4, 2019 · 1 comment
Assignees
Labels
available Status: Available feature Type: New Feature low Priority: Low priority issue
Milestone

Comments

@FMCalisto
Copy link
Member

FMCalisto commented Feb 4, 2019

The Magnetic Resonance Imaging (MRI) technology is a type of scan that allows the visualization of several slices, framing layer-by-layer and a picture taken of each slice. This technology can help diagnose the lesions' progress across the set of slices. In our annotations dataset, we need to provide complete information regarding the existence of injuries in all frames that a lesion is presented. Therefore, we can not accept frames where there is evidence of lesion, but the clinician passed through it missing the lesion annotation.

With this issue, our goal is to surpass the problem of misannotation a frame on a set of slices. The idea is, whenever the system starts to receive at, for instance, slice s = 121 and finish at the slice s = 134 it needs to guarantee that ALL slices between those are annotated. In the following image (lucidchart.com), we can see if the slice s = 128 is not annotated, the system will trigger a warning when the clinician press the saving button.

warning_mri_missing_frames

In short, there is the (high) probability of a clinician to jump between slices. For that reason, we need to guarantee that the system warns the clinician to fix that problem. The solution to it is, each time a clinician press the saving button or closes (the behavior is the same as the last) the respective patient, we will warn the clinician.

Related Issues

@FMCalisto FMCalisto added available Status: Available high Priority: High priority issue feature Type: New Feature labels Feb 4, 2019
@FMCalisto FMCalisto added this to the 1.2.1-beta milestone Feb 4, 2019
@FMCalisto FMCalisto self-assigned this Feb 4, 2019
@FMCalisto FMCalisto modified the milestones: 1.2.1-beta, 1.3.0-beta Jul 10, 2019
@FMCalisto
Copy link
Member Author

This issue was postponed from the 1.2.1-beta milestone to the 1.3.0-beta milestone until further decision. Because of an information lack, we do not know when and where should this issue be covered during our project development.

@FMCalisto FMCalisto modified the milestones: 1.3.0-beta, 1.4, 1.5 Dec 26, 2019
@FMCalisto FMCalisto added low Priority: Low priority issue and removed high Priority: High priority issue labels Feb 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
available Status: Available feature Type: New Feature low Priority: Low priority issue
Projects
None yet
Development

No branches or pull requests

1 participant