◢ SPACE MEDICINE FOUNDATION
⌕ Search
Space weather
Geomagnetic storm level: Loading…
Solar radiation level: Loading…
Updated --:-- -- ET · educational only
EDUCATIONAL RESOURCE · Educational use only — not medical advice and not operational guidance. Disclaimer

Home › Robotic Medicine › Protocol library › RMP-RENAL-001

CONCEPTUAL · DRAFT v0.7 · NOT FOR CLINICAL USE. An educational thought experiment about how a care robot could follow an auditable protocol. It is not a medical procedure, has not been validated, and must not be used to care for anyone. Thresholds marked <set by …> are deliberately left for clinical leads and validation to set. Disclaimer
Robotic Medicine · Protocol library

RMP-RENAL-001 Assisted diagnostic ultrasound for a suspected kidney stone

AI-assisted Reviewed (AI-assisted) AI-assisted clinical and source review by the Medical Research Assistant, Oct 20, 2026; no named human clinician. The clinical content (from the Part 1 example) was first reviewed on Oct 18, 2026; the full-format structure was reviewed on Oct 20, 2026, and all corrections are applied in this version (see Corrections).

Fixed rules (same in every protocol)

1 · Identity and scope

The robot positions and holds an ultrasound probe, captures and labels standard kidney and bladder views, and sends them to the flight surgeon, while the CMO leads and can take over at any moment. Diagnostic imaging only.

Why this protocol was chosen. Kidney stone risk is higher in flight, and ultrasound is the imaging available on board. This is the worked example from Part 1 of the Robotic Medicine series, and the scenario the ground console simulates.

Former ID: ASSIST-US-RENAL-001. First published as the worked example in Part 1.

Covers

  • Suspected kidney stone in a crewmember: right and left kidney views, bladder views including ureteral jets, optional color Doppler "twinkle" views

Locked out (never done by the robot under this protocol)

  • Ultrasonic stone propulsion, burst-wave lithotripsy, and needle or nephrostomy guidance (investigational; out of scope)
  • Any treatment, fluid or medication advice
  • Interpreting images

Related: RMP-RENAL-002 · RMP-PREV-003

2 · Roles

Medical authority
Flight surgeon (ground). Holds medical authority for every run.
Onboard lead
Crew medical officer (CMO), acting under delegated care; uses the pre-approved onboard checklist when there is no link.
Others
  • Treatment is decided by humans only: pain relief (anti-inflammatory first), anti-nausea medicine and tamsulosin are decided by the CMO and flight surgeon; no forced or high-volume fluids for acute colic
Commercial flights
On commercial flights, 'flight surgeon' and 'CMO' mean the operator's designated medical authority and trained onboard responder. If no trained responder is aboard, this protocol is not used. (NASA-STD-3001 requires two CMOs per vehicle for NASA programs [V1 3006]; FAA rules set no medical standards for spaceflight participants.) [9]

Robot may

  • Position and hold the probe
  • Capture and label images
  • Send images live or store-and-forward

Robot may not

  • Diagnose
  • Give treatment, fluid or medication advice
  • Use therapeutic ultrasound modes

3 · Preconditions and consent

Consent
Patient consent recorded by voice or touch confirmation and logged.
Emergency consent
If the patient cannot consent: proceed only on a CMO and flight surgeon emergency decision, logged.
Withdrawal
Patient says stop: stop, retract probe, alert CMO.

4 · Required sensor inputs

IDInputSourceRequiredIf missing
IN-1Ultrasound image stream with quality scoreUltrasound deviceYesHand probe control to the CMO or ground.
IN-2Probe position and contact forceRobot sensorsYesProtective stop.
IN-3Patient vital signs (heart rate, blood pressure, temperature)MonitorYesCMO measures and enters them.
IN-4Urine output and urine dipstick resultEntered by the CMO (robot records only)YesLog as missing; flag for the flight surgeon.
IN-5Communications status and current delayCommunications systemYesTreat as link down.

5–6 · Steps and decision points

Each step names who acts. Decision points sit after the step they follow and say who decides: Robot Crew Ground. Any stop rule in section 7 can interrupt any step.

  1. S1Crew

    Confirm patient position and expose scan areas.

    Done when: CMO confirms.

    D1DecisionCrew decides

    Is the delay Mars-class, or the link down? (Set before scanning.)

    • Yes → No real-time guidance; onboard checklist plus store-and-forward only.
    • No → Live guidance allowed.
  2. S2RobotRung 2

    Right kidney views; automatic image-quality check.

    Done when: Views meet the quality threshold.

  3. S3RobotRung 2

    Left kidney, same views as right, for side-by-side comparison.

    Done when: Views meet the quality threshold.

    D2DecisionRobot decides

    Is image quality still low after the allowed attempts?

    • Yes → Hand probe control to the CMO or ground.
    • No → Continue.
  4. S4RobotRung 2

    Bladder views, including the ureteral jet on each side.

    Done when: Views captured.

    D3DecisionGround decides

    Does the collecting system look swollen (possible blockage)? Decided by the flight surgeon when the link is live; otherwise by the CMO under the onboard checklist, with flight surgeon review at the next contact.

    • Possible swelling seen (by the human reviewer) → Flag for human review; the robot does not interpret.
    • Scan without findings → Report "non-diagnostic", never "normal" or "no stone". Ultrasound can miss ureteral stones, and swelling may not show early; CT is the reference test on Earth but is not available in flight.
  5. S5RobotRung 2

    Optional color Doppler "twinkle" views (twinkle may be harder to see at high cabin CO2; animal data only).

    Done when: Views captured or skipped.

  6. S6RobotRung 2

    Label images and attach them to the medical record; send to the flight surgeon live, or store-and-forward if no link.

    Done when: Delivery confirmed or queued.

    V1 7003

    D4DecisionRobot decides

    Did the images reach the flight surgeon?

    • Yes → Log delivery; wait for the human decision.
    • No (link down or queued) → Keep queued; show the CMO the onboard checklist page; resend at the next contact.

7 · Stop and escalate rules, red flags

IDTriggerWhat happensLevel
X1The patient (or the crewmember being examined) says stop, or withdraws consentRobot stops all motion at once, backs away to its rest position and tells the CMO. Recording stops unless the patient agrees to keep it running.V2 10165stop
X2Any crewmember presses stop or takes over controlProtective stop; robot holds its stopped position; only a human may restart it.V2 10165V2 10168V2 10174safe-state
X3Robot fault, sensor fault, or a force, speed or reach limit is reachedProtective stop and hand control to the CMO; log the fault.V2 10172V2 10168safe-state
X4CMO is asked to take over and does not respond (for example, the CMO is the patient)Robot stays stopped; the next named crewmember is called.V2 10173V2 7045safe-state
X5Loss of link, or delay longer than the limit for live guidanceOnly the robot pauses; crew care never waits for the link or the robot. Robot pauses any movement in its stopped position and tells the CMO. The CMO decides whether to continue offline under the pre-approved onboard checklist; the robot resumes only on the CMO's confirmation. Everything is logged and sent to the flight surgeon at the next contact.V2 10172V2 10173pause
X6Pain increases during scanningStop, retract probe, alert CMO.stop

Red flags

The robot reports the sign or value only, never what it means. Numeric thresholds are placeholders for the clinical lead.

IDSignThresholdAction
RF1Temperature, shaking chills or unstable vital signs [2]temperature <set by clinical lead> or higherStop; URGENT call to the flight surgeon. A suspected infected, blocked kidney needs urgent drainage plus antibiotics; from low Earth orbit this means planning evacuation. Onboard nephrostomy is not an established capability. The flight surgeon decides antibiotics and evacuation; the robot does not.
RF2No or very low urine output (general clinical red flag; no source cited)<set by clinical lead>URGENT call to the flight surgeon
RF3Known single kidney, or swelling on both sides (as judged by a human reviewer) (general clinical red flag; no source cited)anyURGENT call
RF4Pain or vomiting not controlled by onboard medicines (general clinical red flag; no source cited)anyURGENT call
RF5Dipstick positive for nitrite or leukocytes, with symptoms (general clinical red flag; no source cited)anyURGENT call
RF6Rising creatinine, where it can be measured (general clinical red flag; no source cited)<set by clinical lead>URGENT call

8 · Safety limits

IDLimitValueHow enforced
L1Probe force<set by validation>Force sensing; protective stopV2 10172
L2Probe speed<set by validation>Hard limitV2 10172
L3Session time<set by validation>Timer
L4Delay limit for live guidance<set by validation>Communications monitor

9 · Logs and audit

10 · Links to NASA-STD-3001

RequirementTopic (paraphrased)How this protocol uses it
[V1 3006]Crew medical officers: two per vehicleTwo crew medical officers per vehicle for NASA programs (see the commercial-flight note).
[V1 3007]Medical evacuationEvacuation to definitive care for a suspected infected, blocked kidney from low Earth orbit.
[V1 6003]Private medical communicationsPrivate medical communications.
[V1 7001]Medical records kept permanently and retrievable for trend analysisRecords kept in a permanent, retrievable form for trend analysis.
[V1 7003]Security of medical recordsSecure medical records.
[V2 7045]Medical equipment usable by non-physician crewUsable when the CMO is the patient; next named crewmember answers.
[V2 7046]Restraint of patient, care provider and suppliesRestraints.
[V2 10161]Automated system status shown to the operatorStatus shown.
[V2 10162]Mode changes announcedMode changes are announced to the operator.
[V2 10163]Data recording and sharingData recorded and shared.
[V2 10164]Clear allocation of responsibility (human or system)Shows who acts.
[V2 10165]Human override and shutdownHuman override.
[V2 10168]Failure recovery: safe human takeoverHuman takeover.
[V2 10172]Protective stop when limits are exceededProtective stop.
[V2 10173]Safety DefaultRobot stays stopped if no one takes over.
[V2 10174]Only a human initiates or restartsOnly a human starts or restarts the robot.

IDs as published in Volume 1 Revision C [6] and Volume 2 Revision F [7]. NASA-STD-3001 binds NASA programs; it is not a regulation for commercial flights. Its robot rules are general automation requirements, not medical-device rules.

11 · Validation

  1. Simulation. Simulated scans and the ground console scenarios at station, Moon and Mars delays. Pass: Pass criteria set in advance.
  2. Training model. Ultrasound training model (phantom). Pass: Image quality and force limits met; criteria set in advance.
  3. Earth analog. Analog crew with remote flight surgeons. Pass: Criteria set in advance.
  4. Parabolic or station demonstration. Flight demonstration. Pass: Criteria set in advance.

No stage has been run. Pass and fail criteria must be fixed in advance by the clinical lead and safety board.

12 · Human sign-off

Before any use
  • Clinical lead for the specialty (sets every clinical threshold marked <set by clinical lead>)
  • Flight surgeon, as medical authority
  • Robotics and medical-device safety board
  • Program approval for the mission
Each run
Flight surgeon agreement when the link allows; otherwise the CMO under the pre-approved onboard checklist, with flight surgeon review of images and logs at the next contact.
Restart after a stop
Human only. After any emergency or protective stop, a crewmember must restart the robot; the robot never restarts itself.

None of these sign-offs has happened. This is a Draft v0.7.

13 · Change control for learning

Loss of signal and Mars delay

Live link
Low Earth orbit: the flight surgeon can watch and guide live.
Loss of signal
  • Only the robot pauses; crew care never waits for the link or the robot.
  • The robot pauses the probe in its stopped position (or retracts it) and tells the CMO. The CMO decides whether to continue under the onboard checklist; the robot resumes only on the CMO's confirmation. Everything is logged for the flight surgeon.
Mars-class delay
  • Mars-class delay: no real-time guidance; onboard checklist plus store-and-forward only.
  • With up to about 21-23 minutes one way and blackouts of about 2-3 weeks, every threshold must be set before flight.
[8]
Delay limit for live guidance
<set by validation>
Corrections and updates

Oct 20, 2026, version 0.3. AI-assisted clinical and source review by the Medical Research Assistant, Oct 20, 2026; no named human clinician. Changes:

  • Added a precondition that a crewmember started the run ([V2 10174]).
  • D2 now says the flight surgeon decides when the link is live, otherwise the CMO under the onboard checklist.
  • The Mars-class / link-down decision now comes right after S1, before scanning.
  • X6 now covers only increasing pain; "patient says stop" stays in X1.
  • Per-run sign-off wording confirmed (flight surgeon when the link allows; otherwise the CMO, with later review).
  • Loss of link (X5) now pauses the probe and the CMO decides whether to continue.
  • Added a commercial-flight note on who the flight surgeon and CMO are, and a fixed list of robot lockouts checked by the build.

Oct 21, 2026, version 0.4. Batch 5 editorial (AI-assisted), Oct 21, 2026; no named human clinician. Changes:

  • Renal evidence report citation now includes "(approved for public release September 23, 2024)", matching RMP-RENAL-004 (batch 4 optional item 44).
  • Library-wide "safe" wording in inherited stop rules and requirement uses rewritten per batch 4 review item 49 (holds its stopped position / stays stopped / take over / Robot stays stopped). Schema level name safe-state unchanged.

Oct 21, 2026, version 0.4. Batch 5 editorial (AI-assisted), Oct 21, 2026; batch 4 review item 49; no named human clinician. Changes:

  • Inherited stop-rule and requirement wording: "holds a safe position" → "holds its stopped position"; "stays in its safe state" → "stays stopped"; "take over safely" → "take over"; "Robot stays safe if no one takes over" → "Robot stays stopped if no one takes over". Schema level name safe-state and never-word list entry "safe" unchanged.

Oct 21, 2026, version 0.5. Batch 6 editorial (AI-assisted), Oct 21, 2026; no named human clinician. Changes:

  • Renal evidence report citation label changed from "(approved for public release September 23, 2024)" to "(2024)", the site's year-only citation convention.
  • Requirement use for [V2 10173] changed from "Safe default." to "Robot stays stopped if no one takes over." (batch 5 review item 25; editorial, behaviour unchanged).

Oct 21, 2026, version 0.6. Batch 7 editorial (AI-assisted), Oct 21, 2026; no named human clinician. Changes:

  • Citation labels changed to the site's year-only convention: "(approved for public release <date>)" now reads "(YYYY)", and NASA-STD-3001 Volume 2 "Revision F (approved July 14, 2026)" now reads "(Rev F, 2026)" (sources: v2). Editorial; no change to steps, thresholds or limits.

Oct 21, 2026, version 0.7. Batch 7 review and batch 8 editorial (AI-assisted), Oct 21, 2026; no named human clinician. Changes:

  • X5 and the comms loss-of-signal branch now open with "Only the robot pauses; crew care never waits for the link or the robot." (batch 7 review suggestion 29). Editorial; robot behaviour unchanged.

Earlier version: Draft v0.6, Oct 21, 2026. Download the current YAML above.

Sources

  1. NASA Human Research Program. Evidence Report: Risk of Renal Stone Formation (2024). humanresearchroadmap.nasa.gov/evidence/other/2024%20Renal%20… Supports: Imaging steps and limits of ultrasound; no CT in flight; onboard urine dipstick testing; evacuation rather than onboard nephrostomy from low Earth orbit.
  2. European Association of Urology. EAU Guidelines on Urolithiasis. uroweb.org/guidelines/urolithiasis Supports: An infected, obstructed kidney needs urgent drainage plus antibiotics.
  3. Harper JD, Cunitz BW, Dunmire B, et al. First in human clinical trial of ultrasonic propulsion of kidney stones. J Urol. 2016;195(4 Pt 1):956-964. PMID 26521719. doi:10.1016/j.juro.2015.10.131 Supports: Ultrasonic stone propulsion is still investigational.
  4. Worster AS, Bhanich Supapol W. Fluids and diuretics for acute ureteric colic. Cochrane Database Syst Rev. 2012;(2):CD004926. PMID 22336806. doi:10.1002/14651858.CD004926.pub3 Supports: No reliable evidence that forced fluids help in acute colic.
  5. NASA OCHMO. Medical Operations. Technical Brief OCHMO-TB-044 (2025). www.nasa.gov/wp-content/uploads/2025/08/ochmo-tb-044-medical… Supports: The crew surgeon keeps medical authority when care is delegated; crew medical officers train on the JSC 48522 medical checklist.
  6. NASA. NASA-STD-3001, Space Flight Human-System Standard, Volume 1: Crew Health, Revision C (2023). www.nasa.gov/wp-content/uploads/2023/11/nasa-std-3001-vol-1-… Supports: Requirement IDs beginning V1.
  7. NASA. NASA-STD-3001, Volume 2: Human Factors, Habitability, and Environmental Health (Rev F, 2026), including Section 10.6 Automated and Robotic Systems. standards.nasa.gov/standard/NASA/NASA-STD-3001_VOL_2 Supports: Requirement IDs beginning V2.
  8. NASA. Mars communications disruption and delay (fact sheet, 2023 Moon to Mars Architecture Concept Review). www.nasa.gov/wp-content/uploads/2024/01/mars-communications-… Supports: One-way Earth-Mars delay up to about 21-23 minutes, plus blackouts of about 2-3 weeks near solar conjunction.
  9. U.S. Code of Federal Regulations, Title 14, Part 460: Human space flight requirements. www.ecfr.gov/current/title-14/chapter-III/subchapter-C/part-… Supports: Federal rules for crew and spaceflight participants on licensed commercial flights; they set no medical standards for spaceflight participants.

Checked on 2026-10-20: links opened (HTTP 200 or publisher redirect), DOIs and PubMed IDs matched, NASA documents read in full text. The framework comes from Part 1.

Search and quick actions

Type to search. Use the up and down arrow keys to move through results, Enter to open, Escape to close.