DENTAL SURGERY DATASET LINE

The data

Six layers on every annotated keyframe.

What a licensed case actually contains – shown, not described: the clip with its annotation drawn on the picture, the schema behind it, and the tree that lands in your bucket.

Proof of method · sample case

Watch one minute and you understand the product.

Ninety seconds of implant placement with every layer drawn on the picture at once: the phase, the instrument list of the keyframe on screen, the action triplets, the anatomy in view, the annotator's reasoning, the clinical context, and the surgeon's own words underneath. Nothing here is a mock-up – each line is the stored value for the keyframe you are looking at.

1:29 · implant placement · 14:58–16:21 of the case · no audio track On the picture: L0L1L2L3L4L5anatomy

What you are looking at

A single case, played with its annotation rendered over the picture. The header carries the phase, the black strip the instrument list of the keyframe on screen, and the panel underneath the remaining layers – down to the surgeon's own sentence at that second. Where a layer holds nothing for a frame, the clip prints a dash instead of filler.

Procedure
All-on-4 mandibular reconstruction, five implants
Master
54:53, two synchronized angles on one clock · audio ships as separate files
Annotated keyframes
1,009 across nine surgical phases
Layers per keyframe
L0 to L5 plus anatomy, each label carrying its confidence and source
Vocabularies
39 instrument terms, 21 anatomy terms · both closed
Control arm
the same frames annotated blind, without the audio, and shipped alongside

The bar under the clip is the case's phase timeline, width proportional to annotated keyframes – hover any segment. Where a layer is empty for a frame the clip shows a dash rather than filler: coverage is reported, not padded.


Annotation schema v2

Six layers on every annotated keyframe.

From verbatim surgeon speech to clinical context – each layer answers a different question, and every label records where the knowledge came from: seen in the image, stated by the surgeon, or both. Card figures are from the released sample case; across the line so far – with the next cases always in annotation – the layers count 4,574 quotes, 14,187 instrument labels and 5,859 action triplets over 3,392 keyframes.

Plus three auxiliary fields: anatomy_visible – 21-term closed anatomy vocabulary, 1,446 labeled spans, including safety-critical structures (mental nerve, mental foramen); no_surgical_field – 60 frames flagged and reported separately, never hidden in the coverage number; uncertainty – what the annotator could not resolve, quoted verbatim instead of silently corrected.

REFERENCE RECORDING · OUR OPERATING ROOM

What you receive

Every case ships as the same package.

Recording runs year-round and cases come off the line continuously. Each one lands in the same tree – the picture, the sound, every annotated frame as a still, six layers of annotation, the blind control pass, the transcript, the reading guide and the compliance file, with a checksum for all of it. What changes between cases is length and procedure. The structure does not.

2–4 GBper case, depending on length
8folders, identical every case
L0–L5on every annotated keyframe
SHA-256published for every file
video/1 file · 1.4–3 GB

The production master

Every camera angle of the case in one H.264 file with a burnt-in timer that all timestamps in the package refer to. No audio track inside the video – the sound ships separately so picture and speech can be processed independently.

audio/2 files · FLAC + M4A

The surgeon, on the same clock

The intraoperative narration, aligned to the master's timer, lossless and compressed. This is the track every L0 quote is traceable back to, which is why it travels uncompressed as well.

keyframes/650–3,500 stills

Every annotated frame as an image

Full-resolution JPEGs in per-camera folders, plus a keyframe index and a filename map, so a frame id resolves to a file and a timestamp without guesswork. Longer cases simply carry more.

annotations/one JSON per batch + merge

Six layers, with provenance

annotations_merged.json carries L0–L5 for every keyframe, and each label records its confidence and whether it came from the image, the surgeon, or both. Batch files are kept beside the merge: a batch records what the annotator was told at the time.

baseline/blind pass + report

The control arm

The same frames annotated a second time without the audio, plus the comparison report. Every quality number we publish is computed from these files, so you can recompute them instead of taking our word for it.

transcripts/JSON + SRT

What was said, verbatim

De-identified narration on the master's clock. Clinical terms are corrected against the operating surgeon's own review, never accepted from speech recognition as-is.

index/ + docs/vocabularies, card, caveats

How to read it, and what not to claim

Closed vocabularies for instruments and anatomy, the phase timeline, the dated correction log, and the dataset card with the timebase note. Including the list of things this case cannot support – stated up front rather than discovered later.

compliance/MD · HTML · PDF

The paperwork travels with the data

The per-case compliance summary: IRB protocol, the consent basis, the de-identification method and the frame-by-frame audit behind it. It ships inside the package, not on request.

A manifest, a checksum for every file, and a list of what was deliberately left out. Each package names the material that is excluded and why, rather than quietly omitting it: camera originals, the internal speaker map used to reconcile who said what, and any track carrying conversation unrelated to the case. Knowing what is missing is part of knowing what you have.