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

Robotic Medicine · Protocol library

RMP-RENAL-003 Urinary tract infection symptoms: private symptom and dipstick result log, entered by the crewmember

Draft v0.2
Max autonomy Rung 2 · supervised
Priority Tier 2
Missions Low Earth orbit, Commercial flights, Moon, Mars
Updated Oct 21, 2026

AI-assisted Reviewed (AI-assisted) AI-assisted clinical and source review by the Medical Research Assistant, Oct 21, 2026 (batch 9 review: 16 required corrections, R1 to R17 with R10 dropped, of which R17 applies to RMP-PHARM-002; 20 optional suggestions); all required corrections that apply to this protocol are applied in this version (see Corrections). No named human clinician has reviewed it. Not for clinical use.

Download YAML Download JSON Protocol schema

Fixed rules (same in every protocol)

The flight surgeon is the medical authority. The crew medical officer (CMO) acts under delegated care [6].
A human starts the robot, can stop it at any time, and restarts it after any stop.
The robot never diagnoses and gives no drug or fluid advice.
On a fault or no human response, the robot goes to a safe state. On a lost link it pauses motion and tells the CMO, who decides whether to continue offline.
Locked out in every protocol: diagnosing; drug or fluid advice; starting, stopping or adjusting oxygen or any medicine; starting or restarting itself; changing its own protocol, thresholds or limits; handing over an item that failed a check (applies when RMP-PHARM-001 is used).
Result words the robot may use: as entered by the crewmember, logged, not interpreted, not entered, sent to flight surgeon. Never: normal, no problem found, all clear, negative, any diagnosis or cause, infection, no infection, UTI, no UTI, positive, clear, likely, unlikely, nothing to worry about, safe, mild, minor.

1 · Identity and scope

When a crewmember reports burning or pain when passing urine, needing to pass urine often or urgently, or other urinary symptoms, the robot alerts the flight surgeon, brings the urinalysis kit by a checked kit fetch to outside the hygiene area, shows the dipstick instructions from the kit (including the manufacturer's reading time), and keeps a private log of the symptoms and dipstick results the crewmember enters themselves. Only the crewmember, the CMO and the flight surgeon see the log. The robot never reads a strip and never says what a result means.

Why this protocol was chosen. Urinary tract infections (UTIs) were uncommon on long ISS missions (2 events in 46 crewmembers; Crucian 2016), but a kidney infection far from Earth is serious. UK primary-care tools say to follow the dipstick manufacturer's guidance, including timing; in women under 65, a positive nitrite, or a positive leukocyte and blood together, makes a UTI likely; in men, dipsticks can rule infection in but not out, and urinary symptoms with fever suggest prostate or kidney involvement. Signs of kidney infection include pain in the back under the ribs, a flu-like illness, shaking chills or a temperature of 37.9 °C or above, and nausea or vomiting (UKHSA 2025); its tools for men and people over 65 also list a temperature of 36 °C or below. On Earth UKHSA uses 37.9 °C; here the alert value is the shared FEVER_ALERT_C set by the clinical lead, as in RMP-GI-003, RMP-ENT-002, RMP-SKIN-002, RMP-RENAL-004 and RMP-INF-003. The flight surgeon interprets every result and decides on care; a dipstick never rules anything out here. The crewmember entering their own results, the robot never being in the hygiene area, and the private log are design judgment, as in RMP-RENAL-004.

Autonomy: Max rung 2 for a checked fetch of the urinalysis kit to outside the hygiene area and a private symptom and result log. The crewmember does the dipstick test alone and enters the results; the robot never handles urine, strips or waste, is never in the hygiene area, and never reads or photographs a strip.

Covers

New urinary symptoms, in flight or on a planetary surface
Dipstick results entered by the crewmember, as the kit card shows them
Cannot pass urine: RMP-RENAL-002; flank pain: RMP-RENAL-001; fever or sepsis signs: RMP-INF-001

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

Diagnosis or naming a cause
Any medicine, fluid or oxygen advice; starting, stopping or adjusting oxygen
Touching the crewmember
Handing over any medicine outside RMP-PHARM-001, or after a MISMATCH or CANNOT VERIFY (the item stays quarantined; only the CMO can ask for it, through the RMP-PHARM-001 logged two-step override)
Handling urine, samples, strips, waste or waste-system parts
Being present in, or recording, the hygiene area
Reading, photographing or interpreting a dipstick
Saying whether there is an infection
Any medicine advice, including antibiotics (a human order and RMP-PHARM-001 are needed)
Showing the log to anyone except the crewmember, the CMO and the flight surgeon

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

Robot may

Alert the flight surgeon
Bring the urinalysis kit by a checked kit fetch to outside the hygiene area
Show the kit's dipstick instructions
Keep a private log of the symptoms and results the crewmember enters
Show the temperature as displayed

Robot may not

Handle urine, strips or waste
Enter or record the hygiene area
Read or photograph a strip
Say what a result means
Suggest a medicine or fluid
Start without a human command

3 · Preconditions and consent

PRE-1 A crewmember or the CMO started the protocol by command after urinary symptoms were reported.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 log and chooses voice or the private screen; only the crewmember, the CMO and the flight surgeon see it, and other crewmembers never do. Any question can be declined; an explicit "no" is logged as declined for that question only.
Emergency consent: If the crewmember cannot answer, the robot does not continue the log; it sends an URGENT alert and a crewmember checks in person (X7).
Withdrawal: The crewmember can stop or pause the log at any time; an alert already sent is not withdrawn.

4 · Required sensor inputs

ID	Input	Source	Required	If missing
IN-1	Urinary symptoms in the crewmember's words (burning or pain, frequency, urgency, blood in the urine, lower belly pain)	Crewmember (private screen or voice)	Yes	Log "no response"; D3 applies.
IN-2	Dipstick results as the crewmember reads them against the kit card (for example nitrite, leukocytes, blood), with the time read	Crewmember (private screen)	Optional	Log "not entered"; the flight surgeon decides.
IN-3	Temperature as displayed	Crew-used thermometer	Optional	Log "reading not obtained" (never a value).
IN-4	Back pain, chills, nausea or vomiting, as stated	Crewmember	Optional	Log "not stated"; never fill a blank.
IN-5	Link status and delay	Communications system	Yes	Treat as link down; the log is queued.

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.

S1RobotRung 2

Send a private "urinary symptoms" notice to the flight surgeon and the CMO (URGENT if a red flag is already stated). 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: Notice acknowledged, or escalated.

V1 3006V1 6003
S2RobotRung 2

On the CMO's command, run a checked kit fetch of the urinalysis medical kit (sealed dipstick strips and the manufacturer's colour card and instructions): 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". The robot hands the kit over outside the hygiene area and never enters it.

Done when: Kit handed over outside the hygiene area 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
S3RobotRung 2

Show the kit's dipstick instructions on the private screen, including the manufacturer's reading time, then wait outside the hygiene area, out of every route. On request only, the robot shows the time elapsed since the start the CMO called, as a clock-time entry; it never announces a time, and never says "time reached", "done", "passed" or "failed".

Done when: Instructions shown.

V1 6003
S4Crew

The crewmember collects the sample, does the dipstick test alone in the hygiene area, reads it against the kit card at the manufacturer's time, and disposes of the strip and sample in the waste system.

Done when: Test done, or not done.

V1 3004
S5RobotRung 2

Log the symptoms and dipstick results as the crewmember enters them, word for word and marked "as entered by the crewmember", with the time; the robot never speaks a result. Log the temperature as displayed. Show an on-screen prompt for back pain, chills, nausea or vomiting that the crewmember can accept.

Done when: Entries logged, or "not entered".

V1 6003V1 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.
D3DecisionRobot decides

Did the crewmember answer the last question?
- 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.
S6RobotRung 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
S7Ground

The flight surgeon (or the CMO under the onboard checklist when there is no link) interprets the symptoms and results and decides on care, a urine culture if the vehicle can do one, and any repeat test.

Done when: Decision logged.

V1 3004
D4DecisionGround decides

What is the plan (care, culture, repeat test)?
- 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.
S8RobotRung 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
S9RobotRung 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
S10RobotRung 2

Send the flight surgeon one private package: symptoms and results as entered, temperature as displayed, alerts and decisions.

Done when: Package delivered or queued.

V1 6003V1 7003

7 · Stop and escalate rules, red flags

ID	Trigger	What happens	Level
X1	The patient (or the crewmember being examined) says stop, or withdraws consent	Robot 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 10165	stop
X2	Any crewmember presses stop or takes over control	Protective stop; robot holds its stopped position; only a human may restart it.V2 10165V2 10168V2 10174	safe-state
X3	Robot fault, sensor fault, or a force, speed or reach limit is reached	Protective stop and hand control to the CMO; log the fault.V2 10172V2 10168	safe-state
X4	CMO 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 7045	safe-state
X5	Loss of link, or delay longer than the limit for live guidance	Only the robot pauses: before it holds, it moves to a position clear of a hatch route or a crewmember's route (it never pauses in one), and tells the CMO. This pauses robot movement only: the crewmember's own test and all crew care continue under the onboard checklist and never wait for the link or the robot. The CMO decides whether the robot continues offline under the pre-approved onboard checklist; it resumes only on the CMO's confirmation.V2 10172V2 10173	pause
X6	An URGENT alert is not acknowledged within the set time	Robot repeats the alert and sends it to the next named crewmember (the second trained CMO first if the CMO is the patient), and keeps repeating at the set interval. It stays where it is: it does not leave on its own.V1 3006V2 10173	urgent
X7	The crewmember stops responding, or seems confused or drowsy, at any point	URGENT alert at once, even mid-question or mid-step; the robot stops its current task, stays at its rest position and does not continue the run; a crewmember checks in person.	urgent
X8	A crewmember asks the robot what is wrong, or for medicine, fluid or treatment advice	Robot declines, says it cannot assess or advise, and routes the question to the CMO or flight surgeon.	stop
X9	The crewmember enters or leaves the hygiene area, or asks for privacy	Robot moves away from the hygiene area entrance, out of every route, with its camera facing away, and holds.V2 10172	safe-state

Red flags

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

ID	Sign	Threshold	Action
RF1	Pain in the back under the ribs, or kidney pain, as stated [1]	any	URGENT alert; see RMP-RENAL-001
RF2	Temperature as displayed at or above the shared fever alert value, or 36 °C or below, or shaking chills (rigors) or a flu-like illness, as stated [1]	<set by clinical lead> degrees (shared parameter FEVER_ALERT_C: body temperature in degrees Celsius, the same value in RMP-GI-003, RMP-ENT-002, RMP-SKIN-002 and RMP-RENAL-004) or higher, or any shaking chills, or 36 °C or below as displayed	URGENT alert; the CMO checks the crewmember now; see RMP-INF-001
RF3	Nausea or vomiting with urinary symptoms, as stated [1]	any	URGENT alert; see RMP-GI-002
RF4	New confusion, drowsiness or fast breathing [3]	any	URGENT alert; see RMP-INF-001 (possible sepsis)
RF5	Cannot pass urine, or passing very little with lower belly pain, as stated (design judgment; see RMP-RENAL-002) (general clinical red flag; no source cited)	any	URGENT alert; see RMP-RENAL-002
RF6	Visible blood in the urine, as stated (design judgment) (general clinical red flag; no source cited)	any	Flag to the flight surgeon at once

8 · Safety limits

ID	Limit	Value	How enforced
L1	Contact with the crewmember	not allowed	Keep-out zone in the robot controllerV2 10172
L2	Robot presence in, or recording of, the hygiene area	not allowed	Keep-out zone and camera mask in the robot controller
L3	Handling urine, strips or waste	not allowed	No such task is loaded
L4	Robot speed near the crewmember	<set by validation>	Hard limit in the controllerV2 10172

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 Private log: symptoms and dipstick results as entered by the crewmember, with times; temperature as displayed; questions declined; who viewed the log.
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

10 · Links to NASA-STD-3001

Requirement	Topic (paraphrased)	How this protocol uses it
[V1 3004]	In-mission medical care capabilities (including inventory, vital signs, imaging and ECG, procedures, restraints, medications, private data transmission)	In-mission care includes basic laboratory tests; the crewmember does the dipstick and the flight surgeon interprets it.
[V1 3006]	Crew medical officers: two per vehicle	Two trained CMOs per vehicle for NASA programs; the second trained CMO receives alerts when the CMO is the patient (see the commercial-flight note).
[V1 6003]	Private medical communications	Logs and alerts sent to the ground are private medical communications.
[V1 7001]	Medical records kept permanently and retrievable for trend analysis	Records kept so the flight surgeon can see trends.
[V1 7003]	Security of medical records	Secure handling of medical records.
[V2 7045]	Medical equipment usable by non-physician crew	Usable by non-physician crew, including when the CMO is the patient.
[V2 7046]	Restraint of patient, care provider and supplies	Patient, caregiver and supplies restrained.
[V2 7059]	Inventory management: track locations and quantities	Kit inventory and seal status are tracked; after an emergency fetch the robot reconciles the kit through RMP-PHARM-001 as an inventory record (never a check before use) and shows it as "opened – not restocked" until resealed.
[V2 10161]	Automated system status shown to the operator	Robot shows its status and health.
[V2 10162]	Mode changes announced	Mode changes are announced to the operator.
[V2 10163]	Data recording and sharing	Robot records and shares its data.
[V2 10164]	Clear allocation of responsibility (human or system)	Shows whether the human or the robot is expected to act.
[V2 10165]	Human override and shutdown	Human can override and shut down the robot.
[V2 10168]	Failure recovery: safe human takeover	Human can take over.
[V2 10172]	Protective stop when limits are exceeded	Protective stop when a limit is exceeded.
[V2 10173]	Safety Default	Robot stays stopped if no one takes over.
[V2 10174]	Only a human initiates or restarts	Only a human starts or restarts the robot.

IDs as published in Volume 1 Revision C [4] and Volume 2 Revision F [5]. 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

Simulation. Scripted symptom reports with fever, back pain, no results entered, CMO as patient, lost link. Pass: Zero entries into the hygiene area; zero interpretation; every red flag raised.
Training model. Private log drill with a training dipstick card. Pass: Results logged only as entered; only the CMO and flight surgeon can view.
Parabolic or station demonstration. Private screen and keep-out zone in weightlessness. Pass: Keep-out held.
Flight use under flight surgeon supervision. First use for a reported symptom. 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

Started by a crewmember or the CMO. The crewmember does the test and enters the results; the flight surgeon interprets them.

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 [8].

Loss of signal and Mars delay

Live link

Low Earth orbit: the flight surgeon receives the private log when the link allows and can take a private call.

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.
The crewmember's own test and all crew care continue under the onboard checklist and never wait for the link or the robot.
The log continues offline on the CMO's confirmation; entries are stored encrypted for the flight surgeon.

Mars-class delay

Mars: no real-time guidance; the onboard checklist and alert values are set before flight and the CMO decides.

[7]

Corrections and updates

Oct 21, 2026, version 0.2. AI-assisted clinical and source review by the Medical Research Assistant, Oct 21, 2026 (batch 9 review); no named human clinician. Changes:

RF2 now uses the shared fever value FEVER_ALERT_C (set by the clinical lead, as in RMP-GI-003, RMP-ENT-002, RMP-SKIN-002, RMP-RENAL-004 and RMP-INF-003), adds a temperature of 36 °C or below (UKHSA), and keeps 37.9 °C only as Earth context in the why (R11, Q4).
RF5 (cannot pass urine) is labelled design judgment and routed to RMP-RENAL-002; the urolithiasis guideline, which does not support urinary retention, is no longer cited for it (R12).
X5 now reads "the crewmember's own test and all crew care continue under the onboard checklist and never wait for the link or the robot" (R13).
Batch 9 protocols now record the review as AI-assisted (Medical Research Assistant, Oct 21, 2026); no named human clinician.

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

Sources

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 (men: over 37.9 °C), or 36 °C or below (men's and over-65 tools), nausea or vomiting. Earth primary-care context for the flight surgeon. Read Oct 21, 2026 (saved copy in src/b9).
Crucian B, Babiak-Vazquez A, Johnston S, et al. Incidence of clinical symptoms during long-duration orbital spaceflight. Int J Gen Med. 2016;9:383-391. PMID 27843335. doi:10.2147/IJGM.S114188 Supports: Among 46 long-duration ISS crewmembers, 2 urinary tract infection events were reported (0.1 per flight year); skin rashes were the most reported clinical event in the categories studied.
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.
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 3004 (in-mission care), V1 3006, V1 6003, V1 7001, V1 7003.
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.
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.
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.
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.
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.