RMP-PREV-003 Flight-surgeon-ordered surveillance scans (such as kidney and bladder ultrasound): reminder, checked kit fetch, display holding and clip labelling with a crew-held probe (diagnostic only)

1 · Identity and scope

Only when the flight surgeon has loaded a scan order for this crewmember (for example a kidney and bladder surveillance scan), the robot prompts the crewmember at the ordered time; the scan starts only when the crewmember or the CMO accepts. The robot brings the ultrasound kit by a checked kit fetch, holds the display and the scan checklist where the CMO can see them, relays live images and voice to the ground imaging expert when the link allows, and labels each clip with the side, view and clock time. The CMO holds the probe. Every image is "non-diagnostic, for human review": the robot never reads an image or says what it shows. Any symptom moves to the matching care protocol.

Why this protocol was chosen. NASA screens astronauts' kidneys by ultrasound for mineralized material that can become stones; after 282 studies in 73 people there was no change from before to after flight, so routine screening was reduced to selection, the first annual exam and before and after flight (Reyes 2023, abstract). Renal ultrasound before and after flight is standard, ultrasound helps if a stone is suspected in flight, and NASA has tested guided ultrasound for non-physician astronauts (OCHMO-MTB-003); clinical ultrasound has been done on the ISS by crew with remote guidance (Sargsyan 2005). In-flight surveillance scans are not routine: the robot runs this protocol only when the flight surgeon has loaded a scan order for this crewmember, and how often is the flight surgeon's decision; the robot's role (prompt, fetch, display, label) is design judgment and follows RMP-GI-001 and RMP-RESP-004.

Autonomy: Max rung 2 for the scheduled prompt, supervised fetching of the ultrasound kit, holding the display and the scan checklist, and labelling and relaying clips, as in RMP-GI-001 and RMP-RESP-004. The CMO holds the probe: "Contact with the crewmember: not allowed".

Related: RMP-GI-001 · RMP-RESP-004 · RMP-RENAL-001 · RMP-RENAL-002 · RMP-RENAL-003 · RMP-INF-002 · RMP-PREV-002

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

• Second trained CMO: receives every alert and takes over if the CMO is the patient
• Vehicle commander: leads any cabin emergency procedure
• Other crew: help as the CMO or commander directs

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.) [15]

3 · Preconditions and consent

• PRE-1 The scan starts only when the crewmember (or the CMO) accepts the on-screen prompt; a loaded schedule alone never starts it. An unaccepted prompt is logged "not accepted" and the CMO is told. A crewmember or the CMO can also start it by command.human_start == trueV2 10174
• PRE-2 Robot self-test passed; kit stowage locations known.V2 10161V2 7059
• PRE-3 Robot and supplies restrained when not moving.V2 7046
• PRE-4 Link status known. The crew never wait for the robot before acting.link_state in [live, delayed, down]

Consent

The crewmember agrees to the scan and to clips being recorded and sent to the flight surgeon and the ground imaging expert. Clips go only to the people the flight surgeon names.

Emergency consent

If the crewmember cannot agree, this is not a scheduled scan: the robot sends an URGENT alert and a crewmember checks in person (X7).

Withdrawal

The crewmember can stop the scan at any time; the flight surgeon decides on clips already taken.

4 · Required sensor inputs

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. S1RobotRung 2

   Only when the flight surgeon has loaded a scan order for this crewmember, and at the ordered time, show the crewmember an on-screen prompt that a surveillance scan is due, and tell the flight surgeon and the CMO (URGENT if any red flag is stated). The scan starts only when the crewmember or the CMO accepts the prompt; an unaccepted prompt is logged "not accepted" and the CMO is told. Show the symptom prompt first and log answers word for word. Every URGENT alert goes to the CMO and the flight surgeon at the same time (queued for the flight surgeon if the link is down). If the CMO is the patient, is busy treating, or does not answer, the alert goes to the second trained CMO, or the crewmember named before flight [V1 3006]. An URGENT alert that is not acknowledged within <set by validation> seconds is repeated and sent to the next named crewmember.

   Done when: Prompt accepted, or "not accepted" logged and sent; answers logged.

   V2 10174V1 3003V1 3006

   D3DecisionRobot decides

   Did the crewmember answer the symptom prompt, or say they want to skip it?

   • Yes → Continue.
   • Declined explicitly (the crewmember says no to a question) → Log "declined" for that question only; the alert already sent stands.
   • No response, or the answer does not make sense → URGENT: log "no response" (never "declined"); the CMO, or the second trained CMO if the CMO is the patient, checks the crewmember in person at once.
2. S2RobotRung 2

   On the CMO's command, run a checked kit fetch of the ultrasound medical kit (unit, sealed gel and probe-cover pack): check the kit ID and seal before hand-over, and quarantine a kit whose ID or seal does not match (no hand-over; the CMO is told). Any medicine goes only through RMP-PHARM-001. If an URGENT red flag has fired or a human states an emergency, bring it instead as an emergency fetch: This is an emergency fetch on a human command (CMO): no barcode check runs before hand-over and nothing waits for one. The robot reads the kit's own label and seal status only if that adds no delay, says "EMERGENCY FETCH – NOT VERIFIED (CMO command)", and "seal not intact" if so, and hands the kit over anyway. The fetch is logged as an override: time, who asked, the reason as stated, kit ID and seal status. It never says "verified".

   Done when: Kit within reach after a matched ID and seal, or quarantined, or emergency fetch logged.

   Limit: <set by validation>

   V2 7046V2 7059

   D1DecisionRobot decides

   Which kit fetch was it, and what did the checked kit fetch show?

   • EMERGENCY FETCH (an URGENT red flag had fired, or a crewmember or the CMO stated an emergency) → Hand-over already done as an emergency fetch, logged as an override; reconciled afterwards (not a check before use).
   • KIT ID AND SEAL MATCH → Hand the kit over closed; log "KIT ID AND SEAL MATCH. Not a check of the contents." and the clock time.
   • MISMATCH, seal not intact or CANNOT VERIFY → Shown with the reason. No hand-over under this protocol: the kit stays sealed in quarantine (the RMP-PHARM-001 default), and the robot never hands it over unprompted or to anyone but the CMO. The robot does not offer or suggest an override. Only if the CMO explicitly makes the two-step override request inside RMP-PHARM-001 can the kit go to the CMO, logged there as an override with the reason, and flagged to the flight surgeon. If the need becomes an emergency, a crewmember or the CMO states it and the emergency fetch applies.No hand-over
3. S3Crew

   The crewmember and the CMO are restrained for scanning; the crewmember empties or does not empty the bladder as the scan list states. The probe and gel are never placed on an open wound or broken skin unless the flight surgeon directs it with a sterile cover.

   Done when: Ready to scan.

   V2 7046

4. S4RobotRung 2

   Hold the ultrasound display and the scan checklist where the CMO can see them, no closer than the set display distance, and relay live images and voice to the ground imaging expert when the link allows. When the link is down, show the onboard scan checklist and store the clips for forwarding.

   Done when: Display held; relay running or clips stored.

   Limit: <set by validation>

   V1 6003

5. S5Crew

   The CMO holds the probe and scans the sides and views on the scan list or as the ground expert guides; the crewmember can stop at any time.

   Done when: Scan done or stopped.

   V1 3003

6. S6RobotRung 2

   Label and store each clip with the side and view the CMO names and the clock time, and mark every clip "non-diagnostic, for human review". A device image-quality prompt is passed on to the CMO as displayed; the robot never judges an image.

   Done when: Clips labelled, or "image not obtained".

   V1 7001

   D2DecisionRobot decides

   Checked after every answer and at any point in the run (even mid-question or mid-step): does any answer, reading or observation meet a red flag?

   • Yes → Stop the current question or step at once and apply the action listed for each matching red flag (URGENT alert, flag, or stop), with the answer or reading itself, never a cause. Every URGENT alert goes to the CMO and the flight surgeon at the same time (queued for the flight surgeon if the link is down). If the CMO is the patient, is busy treating, or does not answer, the alert goes to the second trained CMO, or the crewmember named before flight [V1 3006]. An URGENT alert that is not acknowledged within <set by validation> seconds is repeated and sent to the next named crewmember.
   • No → Continue.
7. S7Crew

   After the scan, the crew clean the probe and any shared surface under RMP-INF-002; a probe on intact skin is noncritical equipment, and a probe cover never allows a lower level of cleaning. A probe that touched broken skin is semicritical equipment: the crew tag it "not for use" under RMP-INF-002 until it has had high-level disinfection.

   Done when: Cleaning recorded as stated under RMP-INF-002.

   V2 7046

8. S8RobotRung 2

   After any URGENT alert: After an URGENT alert the robot does not leave on its own: it stays at its rest position in the module, with its screen and voice link available, until a human has taken over or tells it to go. It never follows, blocks or touches anyone. It keeps time-stamping what humans say they did, and repeats the alert if it is not acknowledged.

   Done when: Robot at rest in the module until a human releases it; alert acknowledged or escalated.

   V2 10173V1 3006

9. S9Ground

   The flight surgeon with the ground imaging expert (or the CMO under the onboard checklist when there is no link) reviews the clips and decides on any follow-up, care or the next scan.

   Done when: Decision logged.

   V1 3003

   D4DecisionGround decides

   What follow-up, care or next scan applies?

   • Link live → Flight surgeon decides; robot logs.
   • Link down or delay too long → The CMO decides under the pre-approved onboard checklist; the flight surgeon reviews the log at the next contact.
10. S10RobotRung 2

    Only after the CMO or flight surgeon has placed an order, run RMP-PHARM-001 for the ordered item (fetch, barcode match to every order field, recipient check). This protocol adds nothing to that check, never suggests an order, and never hands anything over outside RMP-PHARM-001.

    Done when: RMP-PHARM-001 run logged with its result, or none ordered.

    V2 7059

    D5DecisionRobot decides

    What did RMP-PHARM-001 show for the ordered item?

    • MATCH TO ORDER → RMP-PHARM-001 completes its own recipient check and hand-over; this protocol only logs "MATCH TO ORDER. Not a dose, interaction or allergy review." and the clock time.
    • MISMATCH or CANNOT VERIFY on any field, or a failed scan or recipient check → MISMATCH or CANNOT VERIFY shown with the fields named. No hand-over under this protocol: the item stays sealed in the NOT VERIFIED bag in quarantine (the RMP-PHARM-001 default), and the robot never hands it over unprompted or to anyone but the CMO. The robot does not offer or suggest an override. Only if the CMO explicitly makes the two-step override request inside RMP-PHARM-001 can the item go to the CMO, logged there as an override with the reason and the mismatched fields, and flagged to the flight surgeon.No hand-over
11. S11RobotRung 2

    When the CMO says the event is over, run RMP-PHARM-001 reconciliation on each kit fetched: record the items the CMO or crew state were used, the remaining contents against the kit list, seal status and expiry, labelled "inventory reconciliation after emergency use – not a check before use". Flag the override to the flight surgeon and the pharmacy lead, and show each kit as "opened – not restocked" until a human restocks and reseals it.

    Done when: Kit reconciled or shown as "opened – not restocked".

    V2 7059

12. S12RobotRung 2

    Send the flight surgeon one package: answers as stated, labelled clips, times, alerts and decisions; clips go only to the people the flight surgeon names.

    Done when: Package delivered or queued.

    V1 6003V1 7003

7 · Stop and escalate rules, red flags

Red flags

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

8 · Safety limits

9 · Logs and audit

• LOG-1 Every input, robot action, decision (with who made it) and hand-off, time-stamped to the second.V2 10163V2 10164
• LOG-2 Mode changes and safety-limit events are announced to the operator as they happen and logged.V2 10162V2 10172
• LOG-3 Records are stored and sent as private medical data, encrypted, with access limited to the medical team.V1 6003V1 7003
• LOG-4 Results are kept in a permanent, retrievable format so the flight surgeon can see trends.V1 7001
• LOG-5 Prompt and acceptance; answers as stated; each clip with side, view and time; images not obtained; who viewed the clips.
• LOG-6 Each URGENT alert, who received it, the time it was acknowledged (or the escalation to the next named crewmember), and the time a human released the robot.V2 10163
• LOG-7 Each emergency fetch as an override (time, who asked, reason as stated, kit ID, seal status) and the later inventory reconciliation, labelled "not a check before use".V2 7059
• LOG-8 Each RMP-PHARM-001 run started from this protocol: order ID, result (MATCH TO ORDER, MISMATCH or CANNOT VERIFY with the fields), quarantine, and any CMO override logged by RMP-PHARM-001 (reason and mismatched fields), at clock time. No running counter of doses.V2 7059
• LOG-9 Each checked kit fetch: time, who asked, kit ID, seal status and result (KIT ID AND SEAL MATCH, MISMATCH, seal not intact or CANNOT VERIFY), and any quarantine.V2 7059

10 · Links to NASA-STD-3001

IDs as published in Volume 1 Revision C [10] and Volume 2 Revision F [11]. 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. Scripted scans with an unaccepted prompt, a kit seal mismatch, flank pain stated mid-scan, CMO as patient, lost link. Pass: Zero contact; zero image interpretation; every red flag raised.
2. Training model. Scan drill on an ultrasound training model with remote guidance. Pass: Every clip labelled with side, view and time.
3. Parabolic or station demonstration. Display holding and kit fetch in weightlessness. Pass: Display distance and keep-out held.
4. Flight use under flight surgeon supervision. First scheduled scan. Pass: No safety or privacy events.

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

Scheduled by the flight surgeon and accepted by the crewmember or CMO, or started by command. The CMO holds the probe; the flight surgeon and the imaging expert read every image.

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.2.

13 · Change control for learning

• Every change gets a new version number and a written reason; earlier versions are kept.
• Any change to steps, thresholds, limits or software that touches the patient repeats validation from the simulation stage before use.
• Software and learned-skill updates follow a pre-agreed change plan (what may change, how it is tested, how to roll back), modeled on the FDA predetermined change control plan approach.
• If a new version misbehaves, the robot rolls back to the last validated version and the event is reviewed by the flight surgeon and safety board.
• The robot never changes its own protocol, thresholds or limits.

Change-plan model: FDA guidance [14].

Loss of signal and Mars delay

Live link

Low Earth orbit: the ground imaging expert guides live when the link allows.

Loss of signal

• Only the robot pauses non-essential motion, at a position clear of hatch routes and crew routes, and tells the CMO; it resumes offline only on the CMO's confirmation.
• Crew scanning already under way and all other care continue under the onboard checklist and never wait for the link or the robot.
• The scan follows the onboard checklist; clips are stored and forwarded.

Mars-class delay

• Mars: no live guidance; the CMO follows the onboard checklist and clips are reviewed with delay.

[13]

Sources

1. Reyes D, Sargsyan A, Everson A, Navarro C, Locke J. Update to NASA's clinical practice guideline for renal stone surveillance in U.S. astronauts (abstract; NASA Technical Reports Server 20230015727, 2023). ntrs.nasa.gov/citations/20230015727 Supports: Abstract only: for 9 years all NASA astronauts had specialized renal ultrasound screening for mineralized renal material (MRM, a precursor of stones); as of April 2023 (73 individuals, 282 studies) there was no change in MRM from before to after flight, and screening was reduced to selection, the first annual exam, and before and after flight. Read Oct 21, 2026 (saved copy in src/b11).
2. NASA OCHMO. Urinary Health. Medical Technical Brief OCHMO-MTB-003 Rev A (2025). www.nasa.gov/wp-content/uploads/2025/01/ochmo-mtb-003-urinar… Supports: Renal ultrasound before and after flight is standard; if stones are suspected in flight, ultrasound and limited laboratory work help; NASA tested guided ultrasound software for non-physician astronauts; urine left in the bladder after voiding is not retention but can lead to urinary infection and retention. Kidney stone is the second most likely reason for an emergency medical evacuation from the ISS in NASA's Integrated Medical Model. Read Oct 21, 2026 (saved copy in src/b11).
3. Sargsyan AE, Hamilton DR, Jones JA, et al. FAST at MACH 20: clinical ultrasound aboard the International Space Station. J Trauma. 2005;58(1):35-39. PMID 15674147. doi:10.1097/01.ta.0000145083.47032.78 Supports: An ISS crewmember with minimal sonography training was remotely guided from Mission Control through a FAST (focused assessment with sonography for trauma) examination of four abdominal windows in about 5.5 minutes, with a 2-second delay, private two-way audio and video downlink, and identical reference cards for crew and ground expert. Abstract read.
4. NASA Human Research Program. Evidence Report: Risk of Renal Stone Formation (2024). humanresearchroadmap.nasa.gov/evidence/other/2024%20Renal%20…
5. Stepaniak PC, Ramchandani SR, Jones JA. Acute urinary retention among astronauts. Aviat Space Environ Med. 2007;78(4 Suppl):A5-A8. PMID 17511293. pubmed.ncbi.nlm.nih.gov/17511293/ Supports: Case report: an astronaut who took promethazine and scopolamine before launch developed acute urinary retention on reaching orbit, had intermittent catheterization for the first 3 days with a single balloon-tipped catheter, which, because iodine solution was lacking on board and duties could not be interrupted, was left in place for a total of 4 days; voiding returned after day 7, retention returned on day 10 (1 day before landing), and recurred for the first 24 hours of the next mission; obstructive, medicine-related, psychogenic and nerve-related causes are discussed.
6. UK Health Security Agency. Diagnosis of urinary tract infections: quick reference tools for primary care (updated 2025). www.gov.uk/government/publications/urinary-tract-infection-d… Supports: Follow the dipstick manufacturer's guidance, including test timing. Women under 65: positive nitrite, or both positive leukocyte and blood, means a UTI (urinary tract infection) is likely. Men: use dipsticks to rule in infection, not to rule it out; urinary symptoms with fever or systemic symptoms strongly suggest prostate or kidney involvement. Check for signs of kidney infection (pyelonephritis): kidney pain or tenderness in the back under the ribs, flu-like illness, shaking chills (rigors) or a temperature of 37.9 °C or above, nausea or vomiting. Earth primary-care context for the flight surgeon. Read Oct 21, 2026 (saved copy in src/b9).
7. National Institute for Health and Care Excellence. Suspected sepsis in people aged 16 or over: recognition, assessment and early management. NICE guideline NG253 (2025, last updated Sept 23, 2026). www.nice.org.uk/guidance/ng253/chapter/Face-to-face-assessme… Supports: People with sepsis may feel very unwell and may not have a high temperature; do not rely on fever alone; a rise in temperature can be a physiological response; assess temperature, heart rate, breathing rate, blood pressure, level of consciousness and oxygen saturation; look for mottled or ashen skin, blue skin, lips or tongue, a non-blanching rash, and breaks in the skin; ask how often the person passed urine in the past 18 hours and about fever or shaking chills (rigors); pay attention to new changes in behavior and to concerns raised by others.
8. Kleinman ME, Buick JE, Huber N, et al. Part 7: Adult Basic Life Support: 2025 American Heart Association Guidelines for Cardiopulmonary Resuscitation and Emergency Cardiovascular Care. Circulation. 2025;152(16_suppl_2):S448-S478. PMID 41122888. doi:10.1161/CIR.0000000000001369 Supports: Adult basic life support: initial recognition of cardiac arrest, activation of the emergency response, high-quality CPR and use of an automated external defibrillator; also respiratory arrest and foreign-body airway obstruction. Earth guidance; the onboard checklist leads. Abstract read via PubMed Oct 21, 2026; full text not read.
9. U.S. Centers for Disease Control and Prevention. Guideline for Disinfection and Sterilization in Healthcare Facilities (2008): summary of recommendations. www.cdc.gov/infection-control/hcp/disinfection-sterilization… Supports: 3.b: at least high-level disinfection for semicritical equipment that touches mucous membranes or non-intact skin; 3.c: low-level disinfection for noncritical surfaces and equipment that touch intact skin; 4.b: follow the disinfectant label's safety precautions and use directions, including contact time; 4.c: disinfect noncritical devices when visibly soiled and on a regular basis. Content read through the web search index on Oct 21, 2026 (the CDC site returned HTTP 403 to automated fetch); copy in src/b7/cdc_summary_searchindex.txt.
10. 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: NASA-STD-3001 Vol 1 Rev C: V1 3003, V1 3006, V1 6003, V1 7001, V1 7003.
11. 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.
12. 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.
13. 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.
14. U.S. Food and Drug Administration. Marketing submission recommendations for a predetermined change control plan for artificial intelligence-enabled device software functions (guidance). www.fda.gov/regulatory-information/search-fda-guidance-docum… Supports: A model for planning, validating and rolling back software updates.
15. 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.