Submission rights on all three evaluation queues are granted to members of the EchoRisk-MICCAI Submitters team. Membership is added automatically for the team member whose Synapse User Profile URL was supplied on the official EchoRisk-MICCAI 2026 Team Registration form. You do not need to request access if you are that person.

If you cannot see a Submit button on the evaluation queues described in Step 2, it is almost always one of the following:

• You are not the team member who filled in the registration form, so you were never added to the Submitters team
• The registration form was submitted with a missing or incorrect Synapse Profile URL
• Your team wants additional members beyond the original registrant to be able to submit

In any of these cases, email echorisk.miccai@gmail.com with your team name and the Synapse username(s) to be added to Team 3603440. Requests are turned around within one business day, but should be sent well ahead of the deadline rather than on the day it closes.

Locate the evaluation queue for your task. All three evaluation queues are accessed from the Challenge tab on the EchoRisk-MICCAI Synapse project, not the project's default landing page. Each task has its own dedicated queue; submit only to the queue(s) matching the task(s) you are entering.

• Task 1 — Cardiac Function Estimation: Evaluation Queue 9620025
• Task 2 — Assessment of LV Dysfunction: Evaluation Queue 9620026
• Task 3 — Early Prediction of Therapy-Induced Cardiotoxicity: Evaluation Queue 9620027

These are the final test-set queues only. There is no validation leaderboard or interim feedback associated with them; submitted containers are run against the hidden test set by the organisers after the deadline closes.

Prepare your predictions and container. This step has two parts. The prediction format is final and documented now; the container harness contract is not yet published.

Prediction format (confirmed). The scoring code in the evaluation repository defines the exact CSV your model must produce per task, keyed by (patient_id, timepoint), covering every exam in the ground-truth set:

github.com/EchoRisk-MICCAI/echorisk-benchmark/tree/master/evaluation

• Task 1: lvef_pred, float in [0, 100]
• Task 2: dysfunction_pred, calibrated probability in [0, 1], not a hard label
• Task 3: cardiotoxicity_pred, calibrated probability in [0, 1], baseline (T1) only

Run the official scorer locally on the validation set before packaging, so your offline numbers match what the leaderboard will compute:

The scorer enforces schema strictly: missing exams, out-of-range values, duplicate (patient_id, timepoint) keys, and missing columns are all rejected. A clean local run is a genuine correctness signal, not just a formality.

Container harness contract — coming soon. The entrypoint invocation, input mount path, output file path, and base image/GPU requirements for the containerised evaluation harness are not yet published here. This section will be completed before the new submission deadline above. Do not finalise your Dockerfile against assumed paths; check back here first.

Test offline before submitting. Per Challenge Rule 6, containers must run fully automatically with no manual intervention, no internet access, and no external API calls at inference time. Validate this locally before submission:

--network none reproduces the offline evaluation environment. If your container depends on a runtime download (model weights, tokeniser files, API calls), it will fail evaluation. The mount paths shown above are illustrative only; the exact paths the harness uses will be confirmed in Step 3 once the harness specification is published.

Submit via the evaluation queue. Open the queue for your task on Synapse and use the Submit button to push your image. You may resubmit at any point before the deadline to update your container; only your last submission is evaluated, consistent with Challenge Rule 2.

Submit as an individual, not as part of a team. When Synapse asks whether you are submitting "as an individual" or "as part of a team," you must select "as an individual."

Each registered team must submit using the Synapse account matching the Synapse Profile URL provided on the Team Registration Form. This is the only submitter identity the organisers will recognise for scoring and leaderboard purposes.

"As part of a team" uses a Synapse-native team object that is separate from your Team Registration Form entry. If you submit this way, the organisers will attempt to match the Synapse team name against the team name you provided on your registration form:

• If the Synapse team name exactly matches a team name on record from your Team Registration Form, the organisers will make a best-effort attempt to score the submission.
• If the Synapse team name does not match any registered team (including typos, unrelated pre-existing Synapse teams, or unrecognisable names), the submission will be excluded. No further identity investigation will be carried out and no correction window will be offered.

Recommendation: to avoid any risk of exclusion, always submit as an individual using the account listed on your Team Registration Form.

Recommended naming convention (optional). Organisers recommend naming Docker repositories and submissions using the format TeamName_TaskX_vN (e.g. CardioVisionLab_Task1_v3). This is a recommendation for clarity only and is not enforced.

Deadline and what happens after. The submission window closes on 20 August 2026, extended from the original 1 August 2026 date to allow the container harness specification (Step 3) to be published in time for teams to act on it. After the deadline, organisers run all final containers against the hidden test set. No test-set metrics are visible to participants before or during this process. Results are still released on 27 September 2026 during the MICCAI Annual Meeting; the extension does not affect this date.