conv.

All stories
ScienceQuiet 5d · day 12

Google and NASA test a robotic medical assistant for Artemis Mars missions

A proof-of-concept payload-handling robot, trained with an open-source AI model, logged an 85% success rate in early NASA lab trials.

What to know

  • The robot is a 'payload handler' first: it manages cargo, logistics and equipment, and shifts to medical tasks like preparing an ultrasound machine only when needed.
  • It builds on Google and NASA's earlier Crew Medical Officer Digital Assistant and is meant to operate under astronaut voice command, not replace human medical decision-making.
  • In early Johnson Space Center lab demonstrations it hit an 85% success rate locating and moving a medical bag, using the open-source Pi0 model fine-tuned in 2.5 hours on Google Cloud G4 instances.
  • NASA described the underlying work as developing tools using 'super intelligence (SI) technology' and said partners are still assessing potential future applications.

“For instance, the robot might be directed to assist with routine health monitoring — such as capturing basic vitals or simple ultrasounds — under the strict guidance of a human crew medical officer. This ensures astronauts receive the physical assistance they might not be able to perform by themselves, without ever replacing human decision-making.”

Jim Kelly, VP of federal sales, Google Public Sector · Nextgov ↗ · Oct 27

Jim Kelly VP of federal sales, Google Public SectorNASA Space agency partnerGoogle Public Sector Developer/partnerPhysical Intelligence AI model developer

Google and NASA test a robotic medical assistant for Artemis Mars missions
Nextgov

How it unfolded 4 developments, newest first · click a bar or a number to jump articlesposts

Peak 7 pieces in 3h at Nov 1, 8 PM; 22 pieces over 12 days (20 articles · 2 posts) Oct 27, 12 PM — 4 pieces · 4 articles — Google News 3, Newswires 1Oct 27, 3 PM — quietOct 27, 6 PM — quietOct 27, 9 PM — quietOct 28, 12 AM — quietOct 28, 3 AM — quietOct 28, 6 AM — quietOct 28, 9 AM — 1 piece · 1 article — Newswires 1Oct 28, 12 PM — quietOct 28, 3 PM — 1 piece · 1 article — Newswires 1Oct 28, 6 PM — quietOct 28, 9 PM — quietOct 29, 12 AM — quietOct 29, 3 AM — quietOct 29, 6 AM — quietOct 29, 9 AM — quietOct 29, 12 PM — quietOct 29, 3 PM — quietOct 29, 6 PM — quietOct 29, 9 PM — quietOct 30, 12 AM — quietOct 30, 3 AM — quietOct 30, 6 AM — quietOct 30, 9 AM — 5 pieces · 5 articles — Google News 5Oct 30, 12 PM — quietOct 30, 3 PM — quietOct 30, 6 PM — quietOct 30, 9 PM — quietOct 31, 12 AM — quietOct 31, 3 AM — quietOct 31, 6 AM — quietOct 31, 9 AM — quietOct 31, 12 PM — quietOct 31, 3 PM — quietOct 31, 6 PM — quietOct 31, 9 PM — quietNov 1, 12 AM — quietNov 1, 2 AM — quietNov 1, 5 AM — quietNov 1, 8 AM — quietNov 1, 11 AM — quietNov 1, 2 PM — quietNov 1, 5 PM — 1 piece · 1 post — Reddit 1Nov 1, 8 PM — 7 pieces · 7 articles — Google News 6, Newswires 1Nov 1, 11 PM — quietNov 2, 2 AM — quietNov 2, 5 AM — quietNov 2, 8 AM — 1 piece · 1 post — Mastodon 1Nov 2, 11 AM — quietNov 2, 2 PM — quietNov 2, 5 PM — quietNov 2, 8 PM — quietNov 2, 11 PM — quietNov 3, 2 AM — quietNov 3, 5 AM — quietNov 3, 8 AM — 2 pieces · 2 articles — Google News 2Nov 3, 11 AM — quietNov 3, 2 PM — quietNov 3, 5 PM — quietNov 3, 8 PM — quietNov 3, 11 PM — quietNov 4, 2 AM — quietNov 4, 5 AM — quietNov 4, 8 AM — quietNov 4, 11 AM — quietNov 4, 2 PM — quietNov 4, 5 PM — quietNov 4, 8 PM — quietNov 4, 11 PM — quietNov 5, 2 AM — quietNov 5, 5 AM — quietNov 5, 8 AM — quietNov 5, 11 AM — quietNov 5, 2 PM — quietNov 5, 5 PM — quietNov 5, 8 PM — quietNov 5, 11 PM — quietNov 6, 2 AM — quietNov 6, 5 AM — quietNov 6, 8 AM — quietNov 6, 11 AM — quietNov 6, 2 PM — quietNov 6, 5 PM — quietNov 6, 8 PM — quietNov 6, 11 PM — quietYesterday, 2 AM — quietYesterday, 5 AM — quietYesterday, 8 AM — quietYesterday, 11 AM — quietYesterday, 2 PM — quietYesterday, 5 PM — quietYesterday, 8 PM — quietYesterday, 11 PM — quietToday, 2 AM — quietToday, 5 AM — quietToday, 8 AM — quiet 1234
Oct 28Oct 29Oct 30Oct 31Nov 1Nov 2Nov 3Nov 4Nov 5Nov 6now · 11:25 AM ET
  1. 4

    Outlets tie the robot to NASA's Moon-to-Mars Artemis timeline

    Later coverage, including from the Times of India, situates the robotic assistant within NASA's broader Artemis progression from lunar to Martian missions, emphasizing its role when Earth communication is impossible.

    1. first by The Hans India, 6d ago · also TechRadar, Yahoo Tech, Digital Health News, Times of India

      5 more headlines
  2. 1 day quiet
  3. 3

    Coverage spreads across trade and wire outlets

    ExecutiveBiz, Nextgov/FCW, Yahoo Tech, Mezha.net and Investing.com syndicate and re-report the Google-NASA robotic assistant story, framing it for federal-technology and investor audiences.

    1. first by Mezha.net, 9d ago · also Nextgov/FCW, Nextgov, Google Cloud, ExecutiveBiz

      3 more headlines
  4. 1 day quiet
  5. 2

    Nextgov details robot's medical role and NASA's framing

    Nextgov reports the robot achieved an 85% baseline success rate locating and moving a medical bag in lab tests, publishes Google VP Jim Kelly's description of voice-directed operation under astronaut supervision, and quotes a NASA spokesperson calling the underlying work 'super intelligence (SI) technology.'

    “The ultimate goal is to build a robotic system that can execute a variety of tasks via simple voice instructions, under the astronauts' direct supervision and command.”
    — Jim Kelly, VP of federal sales, Google Public Sector
  6. 1

    Google and NASA reveal proof-of-concept deep-space robot

    A Google Cloud blog post describes a robotic payload-handler system, jointly developed with NASA's Human Research Program, JSC Robotics Team and JPL, tested in a proof-of-concept demonstration at Johnson Space Center's iMETRO facility.

    1. first by Investing.com Nigeria, 6d ago · also Gadget Bridge, Investing.com UK, Investing.com Canada

      1 more headline
  7. background

    Details emerge on the Pi0 model powering the robot — Reporting describes the system using Physical Intelligence's open-source Pi0 model, fine-tuned on Google Cloud G4 instances in 2.5 hours, and tested across roughly 15 edge computing devices over two years to find hardware viable for Mars missions.