Home › Robotic Medicine › Protocol library › RMP-RAD-002

Robotic Medicine · Protocol library

RMP-RAD-002 Personal dosimeter readout, exchange and logging (the crewmember keeps their own dosimeter; the robot never interprets a reading)

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 10 review: 10 required corrections, R1 to R10, of which R10 applies to RMP-CARD-004, RMP-EGR-002, RMP-EGR-003 and RMP-NEURO-005; 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 [7].
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: reading as displayed, reading not obtained, dosimeter ID does not match the record, logged, not interpreted, sent to flight surgeon. Never: normal, no problem found, all clear, negative, any diagnosis or cause, within limits, below the limit, over the limit, low dose, high dose, safe level, acceptable, expected, nothing to worry about, safe, mild, minor.

1 · Identity and scope

At the times the flight surgeon schedules (or on a crewmember's or the CMO's command), the robot prompts each crewmember that a dosimeter readout or passive-dosimeter exchange is due. The prompt and the exchange and stowage log are the core. A camera readout is optional, only when the vehicle has no dosimetry downlink, the downlink has failed, or the flight surgeon asks for it: the crewmember then holds their active dosimeter where the robot's camera can read the display and ID label without contact, and the robot logs the totals and rate as displayed, with the dosimeter ID and clock time. For a scheduled exchange, the crewmember places their own passive dosimeter in a labelled exchange pouch and closes it, and the robot carries the closed pouch to the stowage location the radiation plan lists. Missing or damaged dosimeters are flagged. The robot never interprets a reading or compares it with a limit.

Why this protocol was chosen. Each crewmember's radiation exposure must be monitored (V2 6162) and kept as low as reasonably achievable (V1 4029), within the career limit of 600 mSv effective dose (V1 4030) and with protection from solar particle events (V1 4031). Since 2020, ISS crew have carried Crew Active Dosimeters that measure continuously, time-stamp readings and send them by Bluetooth to station laptops for the Space Radiation Analysis Group, with a display that shows the crewmember their total mission dose and recent dose rate; passive dosimeters give only the cumulative dose on return (SRAG; Gaza 2023). Monitoring, dosimetry and timely reporting to alert crew to shelter are essential (OCHMO-TB-020). Interpreting doses and tracking limits belong to the flight surgeon and the program's radiation team, never the robot. The robot's role (a prompt, a camera readout as displayed, and carrying a closed pouch) is design judgment; it adds a record, never a replacement for the vehicle's own dosimetry downlink.

Autonomy: Max rung 2 for the scheduled prompt, reading each active dosimeter display and ID label by camera without contact, logging the reading as displayed, and carrying a closed passive-dosimeter exchange pouch to the stowage location the radiation plan lists. The crewmember removes and fits their own dosimeter; the robot never opens, resets or configures a dosimeter and never says what a reading means.

Covers

Scheduled or on-command readouts of personal active dosimeters, as displayed
Scheduled passive-dosimeter exchanges done by the crewmember, with the closed pouch carried to stowage
Missing, damaged or unreadable dosimeters
Radiation alarms and solar particle events: RMP-RAD-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)
Opening, resetting, configuring or removing a dosimeter, or opening an exchange pouch
Saying a reading is low, high, within or over a limit, or comparing it with a limit
Deciding on shelter, EVA changes or any crew action (the commander and flight surgeon decide)
Showing a crewmember's readings to anyone except that crewmember, the CMO, the flight surgeon and the radiation team the flight surgeon names

Related: RMP-RAD-001 · RMP-EVA-001 · RMP-PREV-001 · RMP-ENV-001

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

Radiation team (ground), named by the flight surgeon: interprets readings and tracks exposure against limits
Vehicle commander: leads any radiation alarm or shelter procedure (RMP-RAD-001)
Second trained CMO: receives every alert and takes over if the CMO is the patient

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

Robot may

Prompt the crewmember at the scheduled time
Read the dosimeter display and ID label by camera, without contact
Log readings as displayed, with ID and clock time
Carry a closed exchange pouch to the stowage location the radiation plan lists
Flag a missing, damaged or unreadable dosimeter

Robot may not

Touch the crewmember or take a dosimeter from them
Open a pouch or a dosimeter
Say what a reading means or compare it with a limit
Decide on shelter or any crew action
Start a scheduled readout without a human accepting the prompt

3 · Preconditions and consent

PRE-1 The readout or exchange 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 readout schedule and to readings being logged and sent to the flight surgeon and the radiation team the flight surgeon names; readings are part of the medical record.
Emergency consent: During a radiation alarm or solar particle event this protocol does not run; RMP-RAD-001 applies.
Withdrawal: The crewmember can skip or stop a readout; the robot logs "skipped by the crewmember" and tells the CMO and flight surgeon.

4 · Required sensor inputs

ID	Input	Source	Required	If missing
IN-1	The flight surgeon's readout and exchange schedule, and the radiation plan's stowage location for returned passive dosimeters	Flight surgeon / radiation plan	Yes	The robot shows "schedule not loaded" and runs only on a human command; a pouch stays with the crewmember until the CMO names a location.
IN-2	Each active dosimeter display (totals and rate) and ID label, as displayed	Crewmember's active dosimeter, read by camera	Yes	Log "reading not obtained" (never a value) and tell the CMO.
IN-3	Dosimeter and pouch IDs on the crew record	Inventory system	Yes	Log "dosimeter ID does not match the record"; no reading is attributed to a crewmember.
IN-4	Symptoms in the crewmember's words after a radiation alarm or solar particle event (nausea, vomiting, unusual tiredness, skin redness)	Crewmember	Optional	Log "no response"; D3 applies.
IN-5	Link status and delay	Communications system	Yes	Treat as link down; readings are 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

At the scheduled time, show the crewmember an on-screen prompt that a dosimeter readout (or a passive-dosimeter exchange) is due, and tell the flight surgeon and the CMO (URGENT if a red flag is stated). The readout starts only when the crewmember or the CMO accepts the prompt; an unaccepted prompt is logged "not accepted" and the CMO is told. 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.

V2 10174V2 6162V1 3006
S2Crew

Only when a camera readout is run (S3): the crewmember holds their own active dosimeter where the robot's camera can read the display and ID label; they never hand it to the robot.

Done when: Display in view, or the crewmember reads it out.

V2 6162
S3RobotRung 2

Camera readout, only when the vehicle has no dosimetry downlink, the downlink has failed, or the flight surgeon asks for it: read the display and ID label by camera, no closer than the set camera distance, and log each value exactly as displayed with its unit, the dosimeter ID and the clock time. A value the camera cannot read is logged as "reading not obtained", never estimated; a value the crewmember reads out is logged as "as stated by the crewmember". The robot never says what a reading means. Otherwise the robot logs only that the crewmember confirmed the readout, and the vehicle downlink is the record.

Done when: Reading logged as displayed, "reading not obtained", or "downlink is the record".

Limit: <set by validation>

V2 6162V1 7001
D1DecisionRobot decides

Does the dosimeter ID read by camera match the crewmember's record?
- Yes → Log the reading against this crewmember.
- No, or the ID cannot be read → Log "dosimeter ID does not match the record"; no reading is attributed to the crewmember; flag to the CMO and flight surgeon.
S4Crew

For a scheduled passive-dosimeter exchange, the crewmember removes their own passive dosimeter, places it in the labelled exchange pouch, closes the pouch and fits the new dosimeter themselves.

Done when: Pouch closed; new dosimeter fitted, as stated.

V2 6162
S5RobotRung 2

Scan the pouch label and the new dosimeter's ID against the crew record, then carry the closed pouch, without opening it, along routes no crewmember is using, to the stowage location the radiation plan lists, and update the inventory record. A pouch that is open or damaged is not carried; it is flagged to the CMO.

Done when: Pouch stowed and recorded, or flagged.

Limit: <set by validation>

V2 7059V2 7058
S6RobotRung 2

Show an on-screen prompt the crewmember can accept for any missing or damaged dosimeter and, after any radiation alarm or solar particle event, for nausea, vomiting, unusual tiredness or skin redness; log answers word for word.

Done when: Answers logged, or "no response".

V1 6003
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 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.
S7RobotRung 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
S8Ground

The flight surgeon and the radiation team (or the CMO under the onboard checklist when there is no link) interpret the readings, track exposure against limits and decide on any action.

Done when: Decision logged.

V1 4029V1 4030V1 4031
D4DecisionGround decides

What action, if any, follows from the readings?
- 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.
S9RobotRung 2

Send the flight surgeon and the radiation team one package: readings as displayed with IDs and times, exchanges and stowage, missing or damaged dosimeters, answers, 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: dosimeter readouts 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	Any radiation alarm, solar particle event warning or shelter order	The readout ends at once; RMP-RAD-001 applies on the commander's command; the robot clears routes to the shelter and every hatch; the crew go to shelter without waiting for the robot.V2 6164	urgent
X10	Someone needs the space or route the robot is in	Robot moves clear at once without contact and holds; it never pauses in a hatch route.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	A dosimeter alarm, a vehicle radiation monitor alarm, or a solar particle event warning [1]	any	URGENT alert; start RMP-RAD-001 on the commander's command; the crew go to shelter without waiting for the robot
RF2	Nausea, vomiting, unusual tiredness or skin redness after a radiation alarm or solar particle event, as stated [2]	any	URGENT alert; see RMP-RAD-001
RF3	A displayed dose rate at or above the alert value the flight surgeon set (design judgment; a secondary flag only: the robot's reading may lag the display, and the vehicle monitor is the alert, V2 6164) (general clinical red flag; no source cited)	at or above <set by flight surgeon> (unit as the dosimeter displays it)	Flag at once to the flight surgeon and the CMO; the robot never says what it means
RF4	A dosimeter missing, damaged, or with a blank display (design judgment) (general clinical red flag; no source cited)	any	Flag to the CMO and flight surgeon; "reading not obtained" is logged, never a value

8 · Safety limits

ID	Limit	Value	How enforced
L1	Contact with the crewmember	not allowed	Keep-out zone in the robot controllerV2 10172
L2	Camera distance from the crewmember	<set by validation>	Hard limit in the controllerV2 10172
L3	Opening a pouch or a dosimeter, or resetting or configuring a dosimeter	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 Each reading as displayed with unit, dosimeter ID and time; readings not obtained; ID mismatches; exchanges with pouch ID and stowage location; answers as stated; who viewed the readings.
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

10 · Links to NASA-STD-3001

Requirement	Topic (paraphrased)	How this protocol uses 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 4029]	Radiation exposure kept as low as reasonably achievable (ALARA)	Exposure kept as low as reasonably achievable; the flight surgeon and radiation team decide.
[V1 4030]		Career limit tracked by the program and flight surgeon, never by the robot.
[V1 4031]	Protection from the design reference solar particle event	Solar particle event protection; alarms route to RMP-RAD-001.
[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 6162]	Individual crew radiation exposure monitoring	Each crewmember's radiation exposure is monitored; the robot logs personal dosimeter readings as displayed.
[V2 6164]	Radiation alerts above set thresholds	Radiation monitors alert crew and operations teams above set thresholds; the vehicle monitor stays primary.
[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 7058]	Stowage identification compatible with inventory management	Stowage identification works with inventory management.
[V2 7059]	Inventory management: track locations and quantities	Dosimeter and pouch locations are tracked in the inventory system.
[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 [5] and Volume 2 Revision F [6]. 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 readouts with an unreadable display, an ID mismatch, an open pouch, a radiation alarm mid-readout, CMO as patient, lost link. Pass: Zero contact; zero interpretation; every red flag raised; readout ends on any alarm.
Training model. Readout and exchange drill with training dosimeters. Pass: Every reading logged exactly as displayed with ID and time.
Parabolic or station demonstration. Camera readout in weightlessness. Pass: Camera distance held.
Flight use under flight surgeon supervision. First use alongside the vehicle dosimetry downlink. Pass: Agreement with the downlinked record; no safety 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 started by a crewmember or the CMO. The flight surgeon and radiation team interpret every reading.

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

Loss of signal and Mars delay

Live link

Low Earth orbit: the flight surgeon and radiation team receive readings 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.
Dosimeter readouts and all crew care continue under the onboard checklist and never wait for the link or the robot.
Readings are queued; the vehicle's own dosimetry and alarms are unaffected.

Mars-class delay

Mars: readings arrive with delay; the readout schedule and the dose-rate alert value are set before flight and the CMO decides on the onboard checklist.

[8]

Corrections and updates

Oct 21, 2026, version 0.2. Batch 10 AI-assisted clinical review (Medical Research Assistant), Oct 21, 2026; no named human clinician. Changes:

Link-loss wording (X5 and comms) fixed: the stray word "crew" before the list of what continues is removed, so the sentence reads, for example, "the exam already under way and all crew care continue under the onboard checklist" (R6).
The camera readout is optional: it runs only when the vehicle has no dosimetry downlink, the downlink has failed, or the flight surgeon asks; the prompt and the exchange and stowage log are the core (SRAG: readings are sent by Bluetooth for downlink) (S7).
RF3 stays a secondary flag and now says the robot's reading may lag the display and the vehicle monitor is the alert (V2 6164) (S8).
RF1 and the radiation-alarm stop rule add "the crew go to shelter without waiting for the robot" (S9).
Batch 10 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

NASA OCHMO. Design for Ionizing Radiation Protection. Technical Brief OCHMO-TB-020 Rev G (2025). www.nasa.gov/wp-content/uploads/2023/12/ochmo-tb-020-radiati… Supports: Shielding is effective against solar particle events (SPEs); monitoring, accurate event determination, dosimetry and timely reporting to alert crew to seek shelter are essential. A storm shelter can add about 10 cm water equivalent in crew quarters, for example by rearranging water containers and other high-hydrogen items; radiation alerting gives early warning so the crew can configure the shelter; real-time alert dosimetry protects EVA crew if the EVA is ended within 2 hours with access to shielding. Read Oct 21, 2026.
NASA Human Research Program. Evidence Report: Risk of Acute Radiation Syndromes due to Solar Particle Events (2016). humanresearchroadmap.nasa.gov/evidence/reports/Acute.pdf Supports: The acute radiation effects most likely in the prodromal phase after an SPE exposure are nausea, vomiting, anorexia and fatigue, with possible skin injury. Read Oct 21, 2026.
NASA Space Radiation Analysis Group (SRAG), Johnson Space Center. How do we protect the astronauts from space radiation? (web page, 2026). srag.jsc.nasa.gov/spaceradiation/how/how.cfm Supports: Since 2020, Crew Active Dosimeters (about the size of two AA batteries) continuously measure and log each astronaut's radiation exposure; readings are time-stamped and sent by Bluetooth to ISS laptops for downlink to SRAG, and an always-on display shows the astronaut their total mission dose and recent dose rate. Passive dosimetry gives only the cumulative mission dose on return. Read Oct 21, 2026 (saved copy in src/b10).
Gaza R, Johnson AS, Hayes B, et al. The importance of time-resolved personal dosimetry in space: the ISS Crew Active Dosimeter. Life Sci Space Res. 2023;39:95-105. PMID 37945094. doi:10.1016/j.lssr.2023.08.004 Supports: Abstract: monitoring space radiation is vital for risk reduction; the paper reports the ISS Crew Active Dosimeter, which gives time-resolved personal dosimetry for each crewmember. Abstract read Oct 21, 2026 (saved copy in src/b10).
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 3006, V1 4029, V1 4030 (career limit 600 mSv effective dose), V1 4031, 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: NASA-STD-3001 Vol 2 Rev F: V2 6162, V2 6164, V2 7058, V2 7059, and Section 10.6 automated and robotic systems.
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.