| Date | Event | Link |
|---|---|---|
| January 13, 2020 | Train set release | Training set |
| January 13, 2020 | Development set release | Development set |
| January 13, 2020 | Additional sets release | Additional corpora |
| January 20, 2020 | Evaluation Script release | Evaluation Script |
| March 2, 2020 | Test set release (includes Background set) | Test set |
| April 28-May 1, 2020 | MIE2020 Workshop | MIE2020 Programme |
| May 10, 2020 | End of evaluation period: Participant results submissions | Submission |
| May 12, 2020 | Results notified. Test set with GS annotations release | Test set GS |
| July 17, 2020 | Participants’ working notes papers submitted | Easychair submission |
| August 14, 2020 | Notification of acceptance participant papers | TBA |
| August 28, 2020 | Camera ready paper submission | TBA |
| September 22-25, 2020 | CLEF 2020 | CLEF 2020 conference |
Submission
Submission instructions (quick guide)
- Compile the 5 prediction files of each subtask in a separate ZIP file.
- Access https://easychair.org/conferences/?conf=clefehealth2020runs
- Select enter as author
- Read the instructions.
Tips:
– Use your registration team name and the subtask name in the title.
– Do not include in the same ZIP files from different subtasks.
– Verify the files have correct format.
– Include in the ZIP file a text document explaining who you are, your registration mail and registration name. - Fill the form.
- Upload one ZIP and click submit.
Click here for a PDF with more detailed instructions.
Submission file format
Prediction files SHOULD NOT have headings (in the pictures below are added to ease interpretability). The first line of the prediction file should be a prediction.
For CodiEsp-D and CodiEsp-P, the submission file is tab-separated with two columns: clinical case and code. Codes must be ordered by rank/confidence, with more relevant codes first. For example:
For CodiEsp-X, the submission file is also tab-separated. In this case, with four columns: clinical case, reference position, code label, code. Codes do not need to be ordered by rank here. For example:
