Now recruiting capture teams worldwide. Get paid to record first-person video of real work.

Apply to capture

Care room tasks

Egocentric Care Room Meal and Drink Service Data

Carrying and placing a meal tray, positioning a drink with a straw and presenting a spoon are three rows in the site’s task catalog, all in its Care Room environment. This page covers egocentric care room meal and drink service data for those three rows only: first-person meal tray and drink with straw video, what an assisted feeding robot dataset can and cannot claim, how the rows are captured and listed, and what the site does not state. We run custom care task data collection fast and on demand against a written spec, as custom collection at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs. It is tray, drink and spoon handling only, never a feeding or care procedure.
Catalog rows
Three: Deliver meal tray (Easy), Serve drink + straw (Easy), Assisted feeding (Medium)
Environment
Care Room (assistive care), Healthcare & Life Sciences
Status
All three Available on request, as the catalog lists it
Catalog capture setup
Multiview rig + handheld grippers
License
Perpetual, buyer-owned

Requirements

What does care room meal and drink service data need?

01

Three named tasks, not one care label

Carrying and placing a tray, positioning a drink with a straw and presenting a spoon are three different sequences, so a spec names each one, where it starts and where it ends.

02

The capture mode stated per row

The catalog lists a multiview rig with handheld grippers for all three rows, so the spec states which streams that mode carries rather than assuming them.

03

Hands and objects on one clock

Where the spec asks for them, contact events and action segments mark when a tray, a cup or a spoon is picked up, set down or handed on, aligned to video and depth.

04

Who or what receives it settled before capture

The environment examples say participant or mannequin, and the site does not say which a given row uses. The spec settles it, under the simulated-patient-only boundary.

05

Rights you can ship on

A perpetual, buyer-owned commercial license backed by a documented consent chain.

Definition

What is egocentric care room meal and drink service data, and why does it need its own page?

It is video of three tray and table tasks in a staged care room: carrying and placing a meal tray, positioning a drink with a straw, and presenting a spoon. People reach it through several phrasings: egocentric assisted living data, first-person meal tray and drink with straw video, an assisted feeding robot dataset, or custom care task data collection. All describe the same work, recorded against a written spec with depth, contact events and frame-accurate action segments aligned on one hardware clock where the spec includes them.

The elder care and assisted living page names two of these rows in a short paragraph about an adjacent environment, and the grooming page covers a different Care Room row. This page puts the three meal and drink rows in one place so a spec can be read at once. The data is human capture by paid, consented contributors, not robot or teleoperation data, so use for a specific robot still needs your own retargeting step.

Catalog rows

Which catalog rows cover meal and drink service, and what is their status?

Three, all in the Care Room (assistive care) environment of the Healthcare & Life Sciences sector. "Deliver meal tray" is described as "Carry and place a meal tray." and rated Easy. "Serve drink + straw" is described as "Position a drink with a straw." and rated Easy. "Assisted feeding" is described as "Present a spoon to a participant/mannequin." and rated Medium.

All three are listed as Available on request, with the capture setup "Multiview rig + handheld grippers". Available on request 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 site states no delivered hours for any of the three rows, so this page claims none.

The environment

What is the Care Room, and who or what is in the scene?

The catalog describes the Care Room with the examples "Care room: bed, tray table, linens, participant or mannequin". It has twelve rows, all Available on request, and every one lists the capture setup Multiview rig + handheld grippers. Nine are outside this page: Arrange comfort items, Change bed linens, Fold + organize laundry, Grooming setup + handover, Hand over mobility aid, Make a bed, Sort medication packs, Tidy + reset room and Wipe + clean surfaces.

The site does not describe the Care Room as a facility and names no provider or site. It does not say whether a given row uses a participant or a mannequin, so this page says neither. It describes a staged room with a bed, a tray table and linens, and leaves who or what receives the tray, the drink or the spoon to the written spec.

Difference

How is this different from the elder care, tray assembly and meal plating pages?

The elder care and assisted living page is built on five rows in the Nursing Home & Assisted Living environment, and its capture mode is a head-mounted phone or multiview rig. It lists the Care Room rows only as an adjacent environment. The tray assembly and delivery page covers one row in a hospitality service set, and the meal plating and serving page covers plating, portioning and serving on the kitchen and service side.

The patient mobility page covers five mobility rows, including Hand over mobility aid, and the grooming page covers one Care Room row. A row called Feeding sits in Childcare & Early Education and a row called Feeding assistance sits in Nursing Home & Assisted Living; neither is part of this page. None of the pages has the three Care Room meal and drink rows as its main topic, which is why this page exists. The comparison table below sets them side by side.

Meal tray

How is the meal tray row described?

One row, "Deliver meal tray", and one sentence: "Carry and place a meal tray." It holds two moves, a carry and a place, and it is rated Easy, which is all the site says about its difficulty. The environment examples list a tray table, but the row does not say that the tray is placed on it, so where it is placed is set in the spec.

What is on the tray, how heavy it is, how far it is carried, the route and what counts as placed are Not stated. A spec can decide whether an episode covers the carry, the placement or both, and the accept criteria say what counts as a finished step.

Drink and straw

How is the drink and straw row described?

One row, "Serve drink + straw", described as "Position a drink with a straw." and rated Easy. It names one move, positioning. The row is the one the site also lists among its drink rows on the beverage and coffee prep pages; this page treats it in its Care Room setting.

The drink, the container, the straw, the fill level, where the drink ends up and who or what it is positioned for are Not stated, and this page names none of them. A spec has to say what the object is, because the contact events and the out-of-frame rule both depend on it.

Spoon

How is the assisted feeding row described?

One row, "Assisted feeding", described as "Present a spoon to a participant/mannequin." and rated Medium. It is the only one of the three that names a recipient, and the only one rated Medium.

The site does not state what is on the spoon, how close it is brought, how long a presentation takes or what happens after it. It makes no clinical, care or outcome claim for the row, and nothing on this page is guidance on how to assist anyone to eat. It describes what is collected for robot training.

Why demanding

Why are meal and drink handling rows worth capturing for robot learning?

The catalog describes steps that end in an object reaching a place or a person: a tray carried and placed, a drink positioned with a straw, a spoon presented. The rows are rated Easy, Easy and Medium, and this page says no more about difficulty than that. Lighting, room layout and reach are Not stated.

What the site does state is what egocentric video puts into the training distribution: hands entering the frame from below, occlusion during grasp and motion blur during reach. RGB alone leaves a model to infer 3D hand structure it cannot see reliably through occlusion, which is why the site delivers hand pose with a visibility flag per joint where a spec includes it. Whether that stream is populated for the staged gripper capture mode is Not stated.

Capture setup

How is care room work captured, and is it head-mounted or stereo?

The catalog describes the mode as "a staged working set recorded by a multiview rig while the operator performs the task with handheld grippers, so demonstrations map onto a robot end effector." It does not list a head-mounted phone or a stereo pair for any of the three rows, and this page does not claim either is running on them. The site states no camera count, resolution or frame rate for these rows, so the capture tier is agreed in the spec.

Stereo applies only through the site’s general stereo offer: a stereo pair is a capture choice agreed in the skill spec and confirmed on a Spec Pilot. Whether the first-person head-mounted mode listed for other rows is offered for these three is Not stated. The site states no gripper model or jaw type, and care settings are among its thinner-coverage environments, so access and schedule are agreed in the spec.

Streams and labels

What does each meal and drink episode contain?

Each episode follows the Firsthand episode schema: ten streams synced under 2 ms, with RGB, depth, 3D hand pose with per-joint visibility, contact and grasp events, and frame-accurate action segments. For these rows, contact events mark when a tray, a cup or a spoon is taken up or released, and action segments mark each step as the skill spec defines it.

The site does not state which of those streams the staged gripper mode populates for each row. Object labels use the terms your spec sets. Force or tactile data, and success or quality labels for a placed tray, a positioned drink or a presented spoon, are Not stated. The streams table below sets each against what the site states.

Gloves

Can tactile gloves be used for these rows?

The site offers a tactile glove tier as a pilot-ready option. The glove signal is time-synced to a head-mounted stereo camera by hardware timestamps and an IMU, and each glove is calibrated every session.

The site does not state that the glove tier has been used on any Care Room row, and all three rows list handheld grippers as their capture mode. Treat force and tactile data as Not stated for these rows unless a spec adds the glove tier and agrees the fit with you.

People and privacy

Are real patients recorded, and how are faces and screens handled?

No. The healthcare data page states that capture in healthcare settings happens only in training environments with simulated patients, and that real patient footage is never captured, under any circumstance, regardless of what a spec requests. The Care Room rows sit in the same sector, and the site does not separately say how that boundary names a participant, so who or what stands in for the recipient, and how that person is consented, is settled in the spec.

Every episode links to a signed contributor release through a documented consent chain. Faces, plates and screens are detected and irreversibly blurred at ingest, a reviewer confirms the result before anything ships, and the anonymization record is delivered with the data. An undocumented bystander is a stated reject criterion. How name tags, wristbands or room labels are handled is Not stated, so name them in the spec.

Quality gates

How are meal and drink episodes checked for lost views?

Episodes are machine-checked at ingest against the stated reject criteria, listed in the failure-mode table below, and a human reviewer then checks the result. Two stated rules bite on this work: an episode is rejected when the manipulated object is out of frame for more than 15 percent of it, and when more than 35 percent of depth pixels in the manipulation region are invalid.

What counts as the object, a tray, a cup with a straw or a spoon, is set in the spec. How often an object leaves the view, how depth behaves on a glossy tray or a clear cup, and any blur or sharpness rule are Not stated. A rejected item goes to the reject log and is recaptured at our cost.

Delivery

How is meal and drink service data labeled and delivered?

Delivery formats are RLDS, LeRobot and WebDataset, plus HDF5, zarr and Rerun .rrd. Firsthand also offers MCAP delivery; the MCAP hub page covers the container as its own documentation describes it, and which streams would be channels in a file, and what they are named, is Not stated and is agreed in the skill spec.

Every batch is validated against signed accept criteria before it ships, with a reject log, and delivery is rolling, per validated batch. The formats table below sets each format against what its official documentation states.

Scale and speed

How do custom, fast and on-demand collection apply to these three rows?

None of the site’s off-the-shelf dataset descriptions names a Care Room meal, drink or feeding row, so for this task it is custom collection, not an off-the-shelf purchase. It is custom collection at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs.

From signed spec to first validated batch, the timeline is a median of 48 hours where coverage is deep and three to four weeks where it is thin and operators need to be recruited and vetted first. All three rows are Available on request, so which range applies is confirmed when the spec is quoted rather than assumed. On-demand top-ups run against the same spec and accept criteria after each training run. Collections are billed per validated hour, and the site publishes no price list, minimum order or batch size for these rows.

Ordering

How do you order a care room meal and drink service dataset?

Describe which of the three rows are in scope, where each task starts and ends, whether an episode covers one move or a run of them, and what counts as finished. Add the setting, who or what receives the item, the privacy rule for the room, and the variation your pipeline is missing. Then name the streams you want, the capture mode and the delivery format.

Most programs begin with a Spec Pilot, a small, fast first batch that proves the spec and accept criteria on real footage before you scale. The last table below shows what each spec element decides.

At a glance

What you get.

Catalog row 1
"Deliver meal tray": "Carry and place a meal tray." Care Room (assistive care), Healthcare & Life Sciences; Easy; Available on request
Catalog row 2
"Serve drink + straw": "Position a drink with a straw." Care Room (assistive care), Healthcare & Life Sciences; Easy; Available on request
Catalog row 3
"Assisted feeding": "Present a spoon to a participant/mannequin." Care Room (assistive care), Healthcare & Life Sciences; Medium; Available on request
Environment examples
"Care room: bed, tray table, linens, participant or mannequin"
Catalog capture setup
Multiview rig + handheld grippers, a staged working set where the operator performs the task with handheld grippers
Episode schema
Ten streams synced under 2 ms; which streams the gripper mode populates is Not stated
Setting boundary
Training environments with simulated patients only; real patient footage is never captured, regardless of what a spec requests
Delivery
RLDS, LeRobot, WebDataset, HDF5, zarr, Rerun .rrd, MCAP or raw streams with metadata
Tray contents, drink, container, straw, spoon, food, distances, pace
Not stated; agreed in the skill spec
License
Perpetual, irrevocable, buyer-owned, non-exclusive by default

Every collection runs through the same seven-stage end-to-end custom collection pipeline. End-to-end custom data collection is a managed service that takes an AI data need from problem to owned dataset in a single accountable pipeline.

Catalog rows

Which catalog rows cover care room meal and drink service?

The three rows relied on by this page, reproduced as the catalog states them, plus items the catalog does not list.
Task (as listed)Description (as listed)EnvironmentSkillCapture setupStatus
Deliver meal trayCarry and place a meal tray.Care Room (assistive care)EasyMultiview rig + handheld grippersAvailable on request
Serve drink + strawPosition a drink with a straw.Care Room (assistive care)EasyMultiview rig + handheld grippersAvailable on request
Assisted feedingPresent a spoon to a participant/mannequin.Care Room (assistive care)MediumMultiview rig + handheld grippersAvailable on request
Any other meal, drink or feeding step in the Care RoomNot stated as catalog rowsNot statedNot statedNot statedNot stated

Compared pages

How does this page differ from the neighbouring pages?

Each page, its main topic and how it treats the three rows. “Not covered” means the page leaves them out of scope.
PageMain topicCapture framingTreatment of the three rows
This page: egocentric care room meal and drink service dataDeliver meal tray, Serve drink + straw, Assisted feedingMultiview rig + handheld grippers, as the catalog lists itThe whole page: scope, limits, streams and ordering
Egocentric elder care and assisted living dataFive Nursing Home & Assisted Living rowsPhone (head-mounted) / multiview rigNames the Care Room rows only as an adjacent environment
Egocentric tray assembly and delivery dataOne Hospitality Service Set rowMultiview rig + handheld grippersNot covered; a different environment
Egocentric meal plating and serving dataPlating, portioning and serving rowsAs the catalog lists themNot covered; kitchen and service side
Egocentric patient mobility assistance dataFive mobility rows across three environmentsAs each row lists itNot covered; mobility rows only
Egocentric grooming setup and handover dataOne Care Room row, Grooming setup + handoverMultiview rig + handheld grippersNot covered; a different row in the same environment

Stated vs not stated

What does the site state about capturing these three rows?

Left to right: the item, what the site states, and what that means for an order. “Not stated” means the site does not say.
ItemWhat the site statesFor a meal and drink order
Catalog capture setupA staged working set recorded by a multiview rig while the operator performs the task with handheld grippersStated for all three rows; no head-mounted phone or stereo pair is listed for them
StereoA stereo pair is a capture choice agreed in the skill spec through the general stereo offerNot running on these rows as far as the site states; agreed in the spec
Participant or mannequinBoth appear in the environment examples; which a row uses is Not statedSettled in the spec under the simulated-patient-only boundary
Camera count, resolution, frame rate for these rowsNot statedCapture tier agreed in the spec
Gripper model and jaw typeNot statedAgreed in the spec
Hand pose in gripper modeNot statedAgreed in the spec and confirmed on a Spec Pilot
Tray contents, drink, container, straw, spoonNot statedNot claimed; set in the spec
Faces and screensDetected and irreversibly blurred at ingest; reviewer confirms; footage that cannot be de-identified is discardedStated; record ships with the data
Row statusAvailable on requestNo volume, hours or delivered footage is claimed on this page

Streams and tasks

How do the stated streams map to the three tasks?

Streams the site states for custom collections, set against what each carries in a meal or drink episode. Whether the gripper mode populates each is Not stated.
Stream or labelStatus on this siteWhat it carries in a meal or drink episode
RGB and depthStated; ten streams synced under 2 msKeeps the tray, cup or spoon and the hands on one timeline
3D hand pose, per-joint visibilityStated; two hands of 21 joints, with a visibility flag per jointCarries how the fingers hold an object and which joints were hidden
Contact and grasp eventsStatedMarks when a tray, cup or spoon is taken up or released
Action segmentsStated; frame-accurateSeparates the carry, place, position and present steps
Per-frame instance masksStated; stored at 848×480Follows the object set in the spec
Object labelsSet by your specNames the objects and steps in the terms your policy uses
Force or tactile dataGlove tier stated; use on these rows Not statedAdded only if a spec includes the glove tier

Failure modes and QA

What goes wrong in meal and drink capture, and what does QA do about it?

Left to right: the failure mode, what the site states, and what a buyer sees. “Not stated” means the site does not say.
Failure modeWhat the site statesWhat a buyer sees
Fingers hidden behind an objectPer-joint visibility flag on hand pose where a spec includes itA hidden joint flagged as hidden, not guessed
Object out of frameEpisode rejected when the manipulated object is out of frame for more than 15 percent of itReject log per batch; what the object is gets set in the spec
Invalid depth in the manipulation regionEpisode rejected when more than 35 percent of depth pixels are invalid; behaviour on glossy or clear objects Not statedReject log per batch
Sync breachRejected beyond the ceiling for more than three consecutive framesReject log per batch
Calibration driftRejected beyond toleranceCalibration shipped with the episode
Bystander in frameUndocumented bystander rejected; faces and screens blurred and reviewer-confirmedReject log per batch; anonymization record ships with the data
Spec mismatchRejected for a mismatch against the named skill specReject log per batch
Blur or sharpnessNot statedSet in the spec if your policy needs a rule

Formats

Which formats carry meal and drink service data?

Delivery formats stated on the site, set against what each format’s official documentation states where the documentation was read.
FormatWhat the official documentation statesUsed for here
RLDSA dataset is retrieved as episodes, and each episode holds a dataset of steps (RLDS repository README)Episode-based training loaders
LeRobotLeRobotDataset v3.0 is a standardized format for robot learning data, including multi-camera video, with many episodes stored per Parquet or MP4 file (LeRobot documentation)LeRobot dataset format and tooling
WebDatasetTar files in which files that belong together share a basename, split into numbered shards (WebDataset README)Sharded streaming for large training runs
MCAPAn open source container file format for multimodal log data, supporting multiple channels of timestamped pre-serialized data (MCAP site)Multi-stream files; topics and schemas Not stated, agreed in the spec
HDF5 and zarrStated by Firsthand onlyArray storage for custom pipelines
Rerun .rrdStated by Firsthand onlyMulti-stream synchronized playback for review

Delivery and licensing

What is delivered, and under what license?

Delivery and licensing terms as stated on this site. “Set per program” means the site states no fixed value.
ItemAs stated on this siteNote
FormatsRLDS, LeRobot, WebDataset, HDF5, zarr, Rerun .rrd, MCAP, or raw streams with metadataChosen in the skill spec; converter source ships with the data
LicensePerpetual, irrevocable, worldwide, buyer-owned, non-exclusive by defaultExclusivity is available as a separate term; the executed agreement controls
BillingPer validated hourRejected items are recaptured at our cost
PrivacyFaces, plates and screens blurred irreversibly; footage that cannot be de-identified is discardedAnonymization record delivered with the data
Timelinea median of 48 hours to first validated batch where coverage is deep; three to four weeks where thinWhich applies to these rows is Not stated; quoted against your spec
Price, minimum order, batch sizeNot published for these rowsSet in your quote

Skill spec

What does the skill spec fix for a meal and drink order?

Spec element and where a buyer can see it in the delivery. “Set per program” means the site states no fixed value.
Spec elementWhat it decidesWhere it shows up
Rows in scopeMeal tray, drink and straw, spoon, or any mixWhat the cameras see; set per program
Steps and orderWhat one step is and how steps are namedEpisode boundaries and action segments; set per program
Episode scopeOne move, one row or a longer runSet per program; the site does not state an episode length
Object definitionWhether a tray, a cup with a straw or a spoon counts as the objectContact events and the out-of-frame reject rule; set per program
RecipientParticipant or mannequin, and how it is consentedSettled before capture; simulated-patient-only boundary applies
Capture mode and streamsMultiview rig with handheld grippers, any stereo pair, wrist views and hand poseThe channels you can read; confirm on the Spec Pilot
Accept criteriaWhat counts as a finished step and what passes QAReject log per batch
Delivery formatHow the data is packagedRLDS, LeRobot, WebDataset, HDF5, zarr or MCAP
LicenseWho owns the datasetPerpetual, irrevocable, buyer-owned, non-exclusive by default

Example footage

What does egocentric capture look like?

One real clip already published on this site, shown as a format and rig example: a head-mounted stereo capture with hands in frame. It does not show a meal tray, a drink, a straw or a spoon, and it is not a multiview-rig or handheld-gripper clip.

egocentric_stereo_sample.mp4 · head-mounted stereo · hands in frame · 1920 × 1080 web preview · format example, not a care room clip

No care room meal or drink clip is published on the site, so this is labelled as a format and rig example. Request a sample to see delivered files. See stereo sample page, request an egocentric data sample.

FAQ

Egocentric assisted living data, answered.

What is egocentric care room meal and drink service data?
Video of a paid, consented contributor carrying and placing a meal tray, positioning a drink with a straw and presenting a spoon in a staged care room, recorded against a written spec.
Which catalog rows cover it, and what is their status?
Three rows in the Care Room (assistive care) environment: "Deliver meal tray" ("Carry and place a meal tray.", Easy), "Serve drink + straw" ("Position a drink with a straw.", Easy) and "Assisted feeding" ("Present a spoon to a participant/mannequin.", Medium). All are Available on request. This page claims no delivered hours.
Is this head-mounted or stereo capture?
The catalog lists a multiview rig with handheld grippers for all three rows, a staged working set where the operator performs the task with grippers. It does not list a head-mounted phone or a stereo pair for them. A stereo pair is agreed in the skill spec through the general stereo offer.
How is this different from the elder care and assisted living page?
The elder care page is built on five Nursing Home & Assisted Living rows captured with a head-mounted phone or multiview rig, and it names the Care Room only as an adjacent environment. This page covers the three Care Room meal and drink rows.
Are real patients recorded?
No. The site states that capture in healthcare settings happens only in training environments with simulated patients, and that real patient footage is never captured. Whether a row uses a participant or a mannequin is Not stated and is settled in the spec.
Does the site state trays, drinks, spoons, distances or pace?
No. Tray contents, the drink, container, straw, spoon, food, distances and pace are Not stated and are agreed in the spec. The site makes no clinical or care claim for any of the three rows.
How fast can a custom care room dataset be collected?
From signed spec to first validated batch, a median of 48 hours where coverage is deep and three to four weeks where it is thin. All three rows are Available on request, so ask which applies when you request the quote. Collection runs at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs.
Which formats can it be delivered in?
RLDS, LeRobot, WebDataset, HDF5, zarr, Rerun .rrd or raw streams with metadata, and MCAP on request. Topic names and schemas for MCAP are Not stated and are agreed in the skill spec.

Sources

Where are the formats documented?

Request a custom care room meal and drink service dataset.

Tell us which of meal tray delivery, drink and straw service and spoon presentation are in scope, where each task starts and ends, who or what receives the item, the capture mode, the privacy rule for the room, and the streams and format you want. We will quote reach, timeline and price against a written spec.