Five catalog rows, rated Easy and Medium
The catalog lists instrument handling, patient preparation, post-procedure cleaning, suction and irrigation assistance and tray setup under this environment. The spec names the steps you need.
Dental clinic
Requirements
The catalog lists instrument handling, patient preparation, post-procedure cleaning, suction and irrigation assistance and tray setup under this environment. The spec names the steps you need.
Tray setup is laid out in procedure order, and instrument handling passes items to a clinician. The spec records the order and who is in frame.
A head-mounted view keeps both hands and the work in frame. Hand pose, contact events and per-frame instance masks are recorded on one clock, with a visibility flag on each joint.
Consent, anonymization and the license are stated below. No clinical, sterilization, infection-control or regulatory claim is made, because the site states none for this environment.
Definition
Egocentric dental clinic video data is first-person video of a person doing clinic tasks, recorded from their own point of view with synchronized sensor streams alongside. The camera sits on the head, close to what a robot’s onboard camera would see at the chair and tray, so the frames show what the hands are doing rather than a distant view of a room. Teams searching for a dental operatory video dataset or dental clinic robot training data are usually looking for this: footage of the hands doing the work, tied to labels they can train on.
On this site the data is human capture: a paid, consented contributor wears the rig and performs a task from a written skill spec. It is not robot or teleoperation data. This page covers the Dental Clinic environment. It is different from the dental lab page, whose bench work is fabricating prostheses and handling instrument sets, and from the broader healthcare page.
Tasks
The task catalog lists a Dental Clinic environment under Healthcare & Life Sciences. Its examples are a dental clinic, an orthodontic practice and an oral surgery center. It has five task rows. Instrument handling passes, handles and returns dental instruments to the clinician during a procedure, and it is rated Medium. Patient preparation seats the patient, fits the bib and eyewear, adjusts the chair and light and lays out supplies, and it is rated Easy.
Post-procedure cleaning clears the tray, disposes of sharps and waste and wipes and disinfects the chair and surfaces, and it is rated Easy. Suction and irrigation assistance holds the suction and irrigation tools to keep the field clear during treatment, and it is rated Medium. Tray setup lays out sterile instruments and materials on the tray in procedure order, and it is rated Easy. Instrument tray setup data is therefore a named row, not an extrapolation.
All five rows are recorded with a head-mounted phone and a multiview rig, and all five are Available on request. That means the work is scoped and recruited to spec when a buyer asks for it, rather than running as an open capture stream today. The catalog does not split the rows into sub-steps, and it names no procedure types, instrument lists, room layouts or cycle times, so this page does not either.
Episodes
Each attempt is delivered as one episode. On this site the standard episode carries action segments, 3D hand pose for both hands with a per-joint visibility flag, contact events that mark when a hand meets an item, an objects list, and per-frame instance masks stored at the depth resolution of 848×480. The capture setup table below lists the streams and sync figures the site states for the instrumented tier: ten streams hardware-triggered onto one PTP clock domain and aligned under 2 ms, 6-DoF IMU data at 200 Hz, and calibration twice per session.
The catalog lists a head-mounted phone with a multiview rig for these five rows, while the ten-stream stack is the instrumented tier. Which applies to a dental clinic program is not stated and is confirmed in the skill spec. Force and tactile readings are not among the listed streams.
Labels and delivery
Action segments divide an episode into start- and end-timestamped spans, each carrying start_ns, end_ns, verb and noun. For clinic work, a segment might be one tray layout, one pass of an item to the clinician or one wipe of the chair, as written in the skill spec.
Validation runs against signed accept criteria written into the spec before capture, and a reject log ships with each batch. Episodes are machine-checked against stated reject criteria, including a sync breach, calibration drift, the manipulated object out of frame for more than 15 percent of the episode, an undocumented bystander, and a mismatch against the named skill spec, and a human reviewer then checks each episode. Only footage that clears the criteria is billed as a validated hour, and rejected items are recaptured at our cost.
Delivery is in the format your stack already reads: RLDS, LeRobot, WebDataset, HDF5, zarr or Rerun .rrd, or raw streams with metadata, with readable converter source alongside. The license is perpetual, irrevocable and worldwide, buyer-owned and non-exclusive by default, with exclusivity available as a separate term. The executed agreement controls.
Why it is hard
Several of the catalog tasks depend on order and on other people. A tray is laid out in procedure order, so a model has to learn sequence as well as placement. Instrument handling is a pass to a clinician, so the hand-to-hand moment sits at the edge of the frame. Suction and irrigation assistance keeps tools close to the work for long stretches, which is why hand pose carries a per-joint visibility flag and contact events mark when the hand meets the item. The second table below maps each challenge to the stream or label this site states, and says so where nothing is stated.
A robot foundation model paper on arXiv organizes its training data as a pyramid, with large quantities of web data and human videos at the base, synthetic data in the middle and real robot data at the top. The same paper says human videos have no explicit action labels, so it learns latent actions to label them. That is robot-model research, not Firsthand data, and Firsthand has no relationship with its authors.
Capture and privacy
The catalog describes the head-mounted phone as recording the first-person view of real work on site. The site also states that Firsthand does not capture at a customer’s own facility. Whether a given program uses a working clinic or a staged set is not stated, and neither is the venue type. Both are agreed in the skill spec before capture begins.
Two task rows mention a patient: seating the patient, and passing instruments during a procedure. The site does not say whether a live patient, a volunteer or a stand-in is involved, and this page does not describe capturing patients. That is agreed in the spec, and an undocumented bystander is a reject criterion.
Every contributor signs a written release, and each delivered episode links to it through consent artefact IDs in the batch data card. The consent chain has six checkpoints, and a break at any one discards the footage. At ingest, automated detection finds faces, plates and screens and blurs them irreversibly. Speech is scrubbed of names, addresses and card numbers, while ambient audio is kept. A human reviewer confirms that no un-consented person is identifiable in any frame, footage that cannot be de-identified is discarded, and the anonymization record ships with the data.
The catalog notes HIPAA compliance for its Hospital & Clinical Care environment, but states nothing like it for the dental clinic. This page therefore makes no clinical, sterilization, infection-control or regulatory claim. Blurring of charts, labels or screens beyond the listed categories is not stated.
Speed
From signed spec to first validated batch, the published timeline is a median of 48 hours where coverage is deep and three to four weeks where it is thin and contributors need to be recruited first. All five dental clinic rows are Available on request, so the range that applies is confirmed when the spec is quoted rather than assumed.
At program level, a pilot runs two to three weeks to first delivery and a standing program reaches full rate in four to six weeks. These are program milestones, separate from the per-batch figures above.
Getting started
Describe the clinic tasks and their order, what counts as a finished step, who may be in frame, and the variation cases your pipeline is missing. That becomes a written skill spec, quoted for reach, timeline and price before any capture begins. Our skill spec guide walks through how to write one.
Most programs begin with a Spec Pilot, a small, fast first batch that proves the spec and the accept criteria on real footage before volume scales. Collections are billed per validated hour. Counts of sites, contributors, episodes and hours are set in the skill spec, since the site does not state them for this environment.
What is not stated
Where the site is silent, this page says so. No procedure type, instrument list, room layout, venue type, region, cycle time, number of sites or number of episodes is stated for dental clinic work. There is no quality or success label, no force or tactile stream, no clinical or regulatory status and no robot result. The delivered-versus-not-stated table below separates what is stated from what is not. Nothing here claims a training outcome.
Capture setup
| Part | As stated on this site |
|---|---|
| Catalog capture mode | Head-mounted phone for the first-person view of real work; a multiview rig adds synchronized third-person angles when the spec asks for them |
| Instrumented tier | Head-mounted stereo rig worn by the contributor; first-person RGB with metric depth recovered from the calibrated stereo rig |
| Streams | Ten: 4K head camera, two wrist cameras, depth, IMU, 3D hand and body pose, instance segmentation, action labels |
| Sync | Hardware-triggered onto one PTP clock domain; aligned under 2 ms |
| Hand pose | 21 joints per hand, 3D, in metres in the head-camera frame; per-joint visibility flag |
| Calibration | Twice per session; accepted only under the 0.28 px RMS reprojection gate |
| Masks | Per-frame instance masks, stored at 848×480 |
| Which mode applies to dental clinic work | Not stated; confirmed in the skill spec |
Every collection runs through the same seven-stage end-to-end custom collection pipeline.
Task rows
| Task | What the catalog states | Skill | Status |
|---|---|---|---|
| Tray setup | Lay out sterile instruments and materials on the tray in procedure order | Easy | Available on request |
| Instrument handling | Pass, handle and return dental instruments to the clinician during a procedure | Medium | Available on request |
| Patient preparation | Seat the patient, fit the bib and eyewear, adjust the chair and light and lay out supplies | Easy | Available on request |
| Suction and irrigation assistance | Hold the suction and irrigation tools to keep the field clear during treatment | Medium | Available on request |
| Post-procedure cleaning | Clear the tray, dispose of sharps and waste, wipe and disinfect the chair and surfaces | Easy | Available on request |
| Supply restocking | Not stated as a separate row | Not stated | Not stated |
Capture challenges
| Clinic challenge | What goes wrong | Stated stream or label |
|---|---|---|
| Ordered tray layout | Items placed in the wrong sequence | Action segments with verb and noun; order is defined in the skill spec |
| Hand-to-hand passes | The clinician and contributor overlap at the frame edge | Contact events mark when a hand meets an item; who is in frame is agreed in the spec |
| Tools close to the work | Fingers hide the item being held | 3D hand pose with per-joint visibility flags; per-frame instance masks; reject if the object is out of frame for more than 15% of an episode |
| Other people in view | An undocumented bystander appears | An undocumented bystander is a reject criterion; faces are blurred at ingest |
| Completion of a step | Whether a result is acceptable | Not stated: completion is defined in the spec and episode boundaries |
| Force and contact pressure | How hard an item is gripped or pressed | Not stated: no force or tactile stream is listed |
Delivered vs not stated
| Item | Status | Detail |
|---|---|---|
| Action segments | Delivered | start_ns, end_ns, verb, noun, one per step |
| 3D hand pose | Delivered | 21 joints per hand; per-joint visibility flag for occluded fingers |
| Contact events | Delivered | The moment a hand meets an item |
| Per-frame instance masks | Delivered | Stored at 848×480 |
| Consent and anonymization records | Delivered | Consent artefact IDs per episode; anonymization record shipped with the data |
| Procedure types, instrument lists and room layouts | Not stated | Agreed in the skill spec |
| Venue type and whether a patient is involved | Not stated | Agreed in the skill spec |
| Cycle times and throughput | Not stated | No such figure is listed |
| Number of sites, episodes and hours | Not stated | Set per program in the skill spec |
| Quality or success labels | Not stated | No such label is listed |
| Force, tactile or thermal readings | Not stated | Not among the listed streams |
| Clinical, infection-control and regulatory status | Not stated | No such statement exists for this environment |
FAQ
Sources
Tell us the clinic tasks, their order, who may be in frame and the steps your model needs to see. We will quote reach, timeline and price against a written spec, with a first validated batch in a median of 48 hours where coverage is deep.