Medical annotation
Define modality, anatomy, input series, label IDs, review status and export checks.
sample_id / label_record / checks
QUALITY & DELIVERY · PROCUREMENT
Training-data delivery you can check, and acceptance you can cite
From the task spec and authorization through annotation QC, version records, and acceptance, research and procurement review the same materials.
Samples can be previewed here. Project files are shared under authorization and confidentiality.
Back to solutionsPROJECT STARTER TEMPLATES
Prepare a reviewable project brief
Download open planning templates for medical annotation, embodied capture and expert evaluation. These are fictional examples with untested checks, not customer files, available inventory, performance results or product certifications.
Embodied capture
Align task scope, sensor configuration, time semantics, calibration and failed-episode records.
episode_id / capture_plan / checks
Expert evaluation
Prepare authorized inputs, traceable evidence, scoring criteria and independent review.
task_id / reference_evidence / rubric
Replace example fields with your project scope; agree review methods and thresholds before production. Do not put unauthorized patient, customer or case files in an inquiry.
01
What a delivery package contains
These four items are the structure a buyer checks. The downloadable templates above help prepare your brief. Full project evidence is shared under the agreed confidentiality terms.
Project spec
02
Different tasks use different delivery specs
One delivery method for the site. Medical imaging, embodied capture, and private evaluation differ in what is delivered and how it is accepted.
| What to check | How this scene writes it | Material to compare |
|---|
Items not agreed in the project are marked “confirm in project”. There is no company-wide accuracy figure. Dice, IoU, or agreement metrics are defined only for the task that uses them.
03
How quality is checked
| Object | Method | Record | If it fails |
|---|---|---|---|
| Task scope | Compare with the confirmed spec | Spec version | Change the spec, or stop |
| Source and rights | Check source type and allowed use | Authorization status | Open items stay “confirm in project” |
| Labels or capture | Sample review as agreed | Review record | Disputes go to the revision log |
| Format and fields | Input, labels, and export checked separately | Field dictionary | Missing fields are logged |
Sample rate, pass threshold, and metric names are written in the project spec. This page does not prefill a quality score.
04
From sample alignment to acceptance
Confirm the task fits
Output: sample-scope note, including exclusions and open items.
Check the spec on a small batch
Output: pilot batch and issue list. Format and review method are fixed here.
Ship against the frozen spec
Output: data batch, labels, quality record, and version note.
Close the batch on the pass rule
Output: acceptance record. Rework and changes are written separately.
05
Six items to confirm before buying
Does the task fit?
Target task, stage, inclusions, and exclusions.
Process and review record
Which steps ran, and which records exist. Steps that did not run are not described as delivered.
Source and allowed use
What can be evaluated, what use is limited, and what is still open.
Data, labels, and files
Input, label, and export formats are listed separately. Medical imaging input defaults to DICOM. Label files and exports (nii.gz, NRRD, TXT, Excel) are separate lines. DICOM-SEG / RTSTRUCT, WSI, video, and NLP need project confirmation.
Version and change log
Data batch, guideline version, revision, and freeze rules.
Acceptance and rework
Sampling rule, pass condition, disputes, and rework scope. Metrics are set per task.
06
Confirm the task and delivery terms first
For medical work, state the anatomy, modality, and task. We confirm fit during working hours, then arrange the sample scope. The first submit does not promise a quote deadline.
Public samples do not require contact details. A project review does.