◢ 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-MSK-004

CONCEPTUAL · DRAFT v0.4 · 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-MSK-004 Back pain in flight: symptom tracking with red-flag escalation (no drug, position or exercise advice)

AI-assisted Reviewed (AI-assisted) AI-assisted clinical and source review by the Medical Research Assistant, Oct 20, 2026 (batch 2 review, 51 corrections); all corrections are applied in this version. No named human clinician has reviewed it.

Fixed rules (same in every protocol)

1 · Identity and scope

When a crewmember reports back or neck pain in flight, the robot runs structured check-ins: red-flag questions first (bladder, saddle-area feeling, bowel, both legs, arms and hands with neck pain, sudden tearing pain, fever, injury), then pain rating, where it is, where it spreads and what changes it. It logs the answers word for word and sends them to the flight surgeon; any red-flag answer goes to the CMO and flight surgeon at once. It can show a care plan a human has already entered, word for word, but gives no drug, position or exercise advice and never touches the back.

Why this protocol was chosen. In a NASA records review, 52% of astronauts (382 of 728) had space adaptation back pain, mostly mild (86%), usually in the first days of flight; it is thought to come from the spine straightening and lengthening without gravity. Because it is so common, the rare serious causes can be missed. Disc herniation was 4.3 times more common in US astronauts than in matched controls, relatively more often in the neck, with evidence that the risk is increased immediately after flight (the study looked at diagnoses after flight, not during it). On Earth, suspected cauda equina syndrome (pressure on the nerve roots at the base of the spine) needs emergency assessment, and no single symptom rules it in or out. Neck disc problems can press on the spinal cord, and sudden tearing back pain can be an aortic emergency, so both are asked about too. Asking the same red-flag questions every time makes a missed warning sign less likely.

Covers

  • Back or neck pain that starts in flight, in a crewmember who is awake and answering
  • Repeat check-ins until the flight surgeon closes the log

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

  • Naming the cause, or saying it is "just" space adaptation back pain
  • Any drug advice, including pain relief
  • Suggesting positions, stretches, exercise or exercise-device changes (the CMO and flight surgeon decide; the robot only shows a plan a human has already entered)
  • Touching, massaging or pressing on the back
  • Testing strength, reflexes or feeling (the CMO does any examination)
  • Back pain after a fall, impact or crush (RMP-MSK-001 or RMP-MSK-002)
  • Back pain after landing (the flight surgeon and recovery team; see RMP-EGR-003)

Related: RMP-MSK-001 · RMP-MSK-002 · RMP-RENAL-001 · RMP-RENAL-002 · RMP-INF-001 · RMP-CARD-002 · RMP-EGR-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
  • Crewmember with pain: answers check-ins, can skip any question and can stop at any time
  • Flight surgeon: reviews the log and sets the care plan
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.) [14]

Robot may

  • Ask the red-flag questions first, then the pain questions, by voice or touch screen
  • Log answers word for word and send them to the flight surgeon
  • Alert the CMO and flight surgeon at once on a red-flag answer
  • Show, on request, the care plan the CMO or flight surgeon has entered, word for word
  • Remind the crewmember when a check-in is due

Robot may not

  • Diagnose, or say the pain is not serious
  • Give drug, position, stretching or exercise advice
  • Touch the crewmember
  • Show any plan that a human has not entered and signed
  • Start without a human command

3 · Preconditions and consent

Consent
The crewmember agrees by voice or touch; any question can be skipped. Questions about bladder, bowel and sexual function are asked privately, and the crewmember chooses who is present.
Emergency consent
Not applicable; the robot does not continue without the crewmember's answers. If the crewmember cannot answer, it calls the CMO.
Withdrawal
The crewmember can stop at any time; the robot logs where it stopped.

4 · Required sensor inputs

IDInputSourceRequiredIf missing
IN-1Red-flag answers: trouble starting to pass urine or reduced feeling of urine flow; numbness between the legs (saddle area); loss of the feeling of needing to open the bowels, or loss of bowel control; weakness or numbness in both legs; pain down both legs; with neck pain, new weakness, numbness or tingling in an arm or hand, clumsy hands, or new trouble with balance or walking; new pain below the knee, or numbness or weakness, in one leg; sudden severe tearing or ripping back pain, or back pain with chest or belly pain, fainting or breathlessness; fever; any fall or impactCrewmember, by voice or touch screenYesAsk the CMO to ask in person; never treated as "no".
IN-2New sexual dysfunction (asked privately; optional)CrewmemberOptionalLog "skipped".
IN-3Pain rating (0-10), where it is (back, neck, one side or flank) and where it spreadsCrewmemberYesLog "not answered".
IN-4When it started, and what makes it better or worse (as reported)CrewmemberYesLog "not answered".
IN-5Care plan entered by the CMO or flight surgeonMedical recordOptionalShow "No care plan entered; ask the CMO."
IN-6Medicines given, as logged by humans (shown to the CMO and flight surgeon; the robot does not advise)Medical record or dose logOptionalNote "no dose log available".
IN-7Time since launchMission clockYesAsk the CMO.
IN-8Link status and 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. S1RobotRung 2

    On a crewmember's command, open the log, tell the CMO, and send a "back pain log started" note to the flight surgeon (queued if the link is down).

    Done when: CMO acknowledges; note delivered or queued.

    V2 10174V1 6003

  2. S2RobotRung 2

    Ask the red-flag questions first (privately for bladder, bowel and sexual function), and log the answers word for word.

    Done when: Each red-flag question answered or marked for the CMO to ask.

    D1DecisionRobot decides

    Is any red-flag answer "yes", or not answered?

    • Yes → Stop the routine questions. Apply the action listed for each matching red flag (URGENT alert, stop, or private flag) with the answer itself; on any URGENT flag the CMO assesses in person. A normal CMO examination does not cancel a "yes" answer; the flight surgeon decides. The robot does not say what it means.
    • Not answered → Ask the CMO to ask in person before the pain questions; never treated as "no".
    • All "no" → Continue to S3.
  3. S3RobotRung 2

    Ask the pain questions: rating, place, spread, timing, and what makes it better or worse. Log answers word for word.

    Done when: Answers logged.

  4. S4RobotRung 2

    On request, show the care plan the CMO or flight surgeon has entered for this crewmember, word for word, with who entered it and when. If there is none, say "No care plan entered; ask the CMO."

    Done when: Plan shown, or "no plan" shown.

  5. S5RobotRung 2

    Send the answers to the flight surgeon, or queue them and show the CMO the onboard checklist page.

    Done when: Delivered or queued.

    V1 6003V1 7003

    D2DecisionGround decides

    What is the plan?

    • 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.
  6. S6Crew

    The CMO assesses in person when asked or on any red flag. Any medicine is ordered by a human and fetched through RMP-PHARM-001.

    Done when: CMO decision logged.

  7. S7Ground

    The flight surgeon (or the CMO under the onboard checklist when there is no link) sets the care plan and the check-in schedule; the robot logs them.

    Done when: Plan logged.

  8. S8RobotRung 2

    Offer a check-in every <set by flight surgeon> hours, red-flag questions first every time, until the flight surgeon closes the log. At each scheduled time the robot prompts the crewmember on their own screen; it approaches only when the crewmember (or the CMO) accepts, and a prompt never starts the robot.

    Done when: Each prompt accepted, postponed or answered; log closed by a human.

    V2 10174

    D3DecisionRobot decides

    Is the pain rating rising, or is pain lasting beyond the time the flight surgeon set, or new after the first flight days?

    • Yes → Flag to the flight surgeon and CMO: not assumed to be space adaptation back pain.
    • No → Continue the schedule.

7 · Stop and escalate rules, red flags

IDTriggerWhat happensLevel
X1The patient (or the crewmember being examined) says stop, or withdraws consentThe robot stops the check-in at once and moves away; declining is logged, not questioned.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. On loss of link the robot pauses any movement and tells the CMO. On the CMO's confirmation it continues check-ins and logging offline; everything is queued and sent to the flight surgeon at the next contact.V2 10172V2 10173pause
X6A red-flag answer at any check-inRobot stops the routine questions and applies the action listed for that red flag (D1); URGENT flags go to the CMO and flight surgeon at once.urgent
X7Sudden, severe, tearing or ripping back pain, or back pain with chest or belly pain, fainting or breathlessnessRobot stops the check-in and calls the CMO at once; URGENT alert to the flight surgeon; switch to RMP-CARD-002.urgent
X8The crewmember asks the robot for drug, position or exercise adviceRobot declines, shows the human-entered plan if there is one, and routes the question to the CMO or flight surgeon.stop

Red flags

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

IDSignThresholdAction
RF1Trouble starting to pass urine, reduced feeling of urine flow, or not knowing when the bladder is full [4]any, newURGENT alert to the CMO and flight surgeon (possible cauda equina syndrome; the flight surgeon may also start RMP-RENAL-002). Early-flight urinary retention is common and can mask, or look like, nerve compression; the robot never downgrades this flag because of time since launch.
RF2Numbness or changed feeling between the legs, around the anus or genitals (saddle area) [4]any, newURGENT alert
RF3Loss of the feeling of needing to open the bowels, or loss of bowel control [4]any, newURGENT alert
RF4Severe or worsening weakness or numbness in both legs [4]anyURGENT alert
RF5New sexual dysfunction (asked privately) [4]any, newURGENT alert
RF6Pain down both legs, or one-leg pain that spreads to both [4]anyURGENT alert (a warning sign for cauda equina syndrome)
RF7Fever, or feeling very unwell, with back pain [5]anyURGENT alert; see RMP-INF-001
RF8Back pain after a fall, impact or crush [5]anyStop; CMO trauma care (RMP-MSK-001 or RMP-MSK-002)
RF9Pain in one side or the flank, with or without blood in the urine, nausea or vomiting [7]anyURGENT alert; the flight surgeon considers the kidney stone pathway (RMP-RENAL-001; the risk of stones is raised in flight). The robot gives no fluid advice.
RF10Pain rating [1]<set by clinical lead> or higher on a 0-10 scale, or rising across check-insCMO assesses in person
RF11Pain lasting, or starting late [5]beyond <set by flight surgeon> days after launch, or new after the first flight daysFlag to the flight surgeon
RF12With neck pain: new weakness, numbness or tingling in an arm or hand, clumsy hands, or new trouble with balance or walking [2]any, newURGENT alert; the CMO assesses in person
RF13Sudden, severe, tearing or ripping back pain, or back pain with chest or belly pain, fainting or breathlessness [6]anyURGENT: CMO at once (possible aortic emergency); RMP-CARD-002
RF14New pain spreading below the knee in one leg, or new numbness or weakness in one leg [5]any, newCMO assesses in person; flag to the flight surgeon (URGENT if RF4 or RF6 also applies)

8 · Safety limits

IDLimitValueHow enforced
L1Contact with the crewmembernot allowedKeep-out zone in the robot controllerV2 10172
L2Robot speed near the crewmember<set by validation>Hard limitV2 10172
L3Showing a plan not entered and signed by the CMO or flight surgeonnot allowedOnly signed plans in the medical record can be displayed
L4Check-in length<set by validation>Timer

9 · Logs and audit

10 · Links to NASA-STD-3001

RequirementTopic (paraphrased)How this protocol uses it
[V1 3003]In-mission preventive care: monitor physiological and psychosocial well-beingCapability to monitor physiological well-being in flight.
[V1 3004]In-mission medical care capabilities (including inventory, vital signs, imaging and ECG, procedures, restraints, medications, private data transmission)In-mission care includes privacy considerations (private questions); administering and managing medications is a human capability.
[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 for problems beyond onboard care; the flight surgeon decides.
[V1 6003]Private medical communicationsLogs and alerts sent to the ground are private medical communications.
[V1 7001]Medical records kept permanently and retrievable for trend analysisRecords kept so the flight surgeon can see trends.
[V1 7003]Security of medical recordsSecure handling of medical records.
[V2 7045]Medical equipment usable by non-physician crewUsable by non-physician crew, including when the CMO is the patient.
[V2 10161]Automated system status shown to the operatorRobot shows its status and health.
[V2 10162]Mode changes announcedMode changes are announced to the operator.
[V2 10163]Data recording and sharingRobot 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 shutdownHuman can override and shut down the robot.
[V2 10168]Failure recovery: safe human takeoverHuman can take over.
[V2 10172]Protective stop when limits are exceededProtective stop when a limit is exceeded.
[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 [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 check-ins with every red-flag answer, unanswered questions and rising pain, at station, Moon and Mars delays. Pass: Every red-flag answer alerts within <set by validation>; zero advice; zero plans shown that a human did not enter.
  2. Earth analog. Analog crews (for example bed-rest or isolation studies) using the check-ins, reviewed by remote clinicians. Pass: Clinicians judge the logs usable; crew rate the private questions acceptable.
  3. Flight use under flight surgeon supervision. Logging aid alongside private medical conferences in the first flight days. Pass: No safety events; no red flag missed when compared with the conference notes.

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. The flight surgeon reviews the log at each private medical conference; red flags go to the CMO and flight surgeon at once.
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.4.

13 · Change control for learning

Change-plan model: FDA guidance [13].

Loss of signal and Mars delay

Live link
Low Earth orbit: red flags reach the flight surgeon within minutes; routine logs are reviewed at the private medical conference.
Loss of signal
  • Only the robot pauses; crew care never waits for the link or the robot.
  • The robot pauses any movement and tells the CMO; on the CMO's confirmation it keeps running check-ins and logging offline.
  • Red-flag answers go to the CMO at once; the CMO decides under the pre-approved onboard checklist.
  • At the next contact the robot sends one package: answers, alerts and decisions.
Mars-class delay
  • Replies may take up to about 21-23 minutes each way, with blackouts of about 2-3 weeks, so the CMO acts on red flags onboard.
  • Red flags, the check-in schedule and the onboard plan for suspected nerve-root compression are set before flight.
[12]
Corrections and updates

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

  • Added RF12: with neck pain, new arm or hand weakness, numbness or tingling, clumsy hands, or new trouble with balance or walking (URGENT). Source: Johnston 2010 neck-disc data; no myelopathy guideline was verified (item 9).
  • Added RF13 and a stop rule: sudden severe tearing or ripping back pain, or back pain with chest or belly pain, fainting or breathlessness, as a possible aortic emergency (URGENT; RMP-CARD-002; Gulati 2021) (item 10).
  • D1: a normal CMO examination does not cancel a "yes" answer; added RF14 for new one-leg symptoms at "CMO assesses" level (item 11).
  • RF1: early-flight urinary retention can mask or look like nerve compression; never downgraded by time since launch (item 12).
  • RF9 now cites the NASA renal stone evidence report and says the risk of stones is raised in flight (not that stones are common) (item 13).
  • Johnston wording: risk increased immediately after flight; the study looked at diagnoses after flight (item 14).
  • The GIRFT cauda equina pathway is cited at its GIRFT address, with the NHS trust copy as a mirror (item 15).
  • Each red-flag decision now applies the action listed for each matching red flag (URGENT alert, stop, or private flag), not URGENT for everything (review item 47).
  • Repeat check-ins inside an open log are now on-screen prompts; the robot approaches only when the crewmember or CMO accepts, and a prompt never starts it (item 49, [V2 10174]).
  • Red flags that had no source now cite one where a source fits; the rest are shown as general clinical red flags with no source cited (item 50).
  • The "item that failed a check" lockout is kept and now notes that it applies when RMP-PHARM-001 is used (item 51).
  • NASA evidence reports are cited as "approved for public release" (item 48).

Oct 21, 2026, version 0.3. 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: ermed, renal, v2). Editorial; no change to steps, thresholds or limits.

Oct 21, 2026, version 0.4. 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.3, Oct 21, 2026. Download the current YAML above.

Sources

  1. Kerstman EL, Scheuring RA, Barnes MG, DeKorse TB, Saile LG. Space adaptation back pain: a retrospective study. Aviat Space Environ Med. 2012;83(1):2-7. PMID 22272509. doi:10.3357/asem.2876.2012 Supports: Space adaptation back pain in 52% of astronauts (382/728); mild in 86%, moderate in 11%, severe in 3% of those affected; fetal positioning (91%) and analgesic medicines and exercise (85% each) were the most effective treatments; usually mild and self-limited, but moderate or severe pain that does not respond carries a risk of functional impairment and mission impact.
  2. Johnston SL, Campbell MR, Scheuring R, Feiveson AH. Risk of herniated nucleus pulposus among U.S. astronauts. Aviat Space Environ Med. 2010;81(6):566-574. PMID 20540448. doi:10.3357/asem.2427.2010 Supports: In-flight back pain is presumably due to elongation of the spine; disc herniation was 4.3 times more common in US astronauts (321) than matched controls (983), relatively more often in the neck (18 of 44 astronaut herniations, against 3 of 35 in controls), with evidence that the risk is increased immediately after spaceflight. Used here for the neck red flag; no guideline listing spinal-cord (myelopathy) red flags was verified for this draft, so that wording is a clinical judgment.
  3. NASA OCHMO. Space Adaptation Sickness (SAS) and Space Readaptation Syndrome. Medical Technical Brief OCHMO-MTB-004 Rev A (Sept 25, 2025). www.nasa.gov/wp-content/uploads/2025/09/ochmo-mtb-004-space-… Supports: Space adaptation back pain occurs in 52% of space travelers in the first 2-5 days of flight; microgravity reduces the usual curve of the back, causing it to straighten. Urinary retention can occur in the first few days of flight.
  4. NHS England Getting It Right First Time (GIRFT). Spinal Surgery: National Suspected Cauda Equina Syndrome (CES) Pathway (February 2023). Also hosted by an NHS trust: https://www.gloshospitals.nhs.uk/media/documents/GIRFT_CES_Guidelines_2023_EJRRVj5.pdf (the copy that was read; the GIRFT-hosted copy could not be opened by automated retrieval). gettingitrightfirsttime.co.uk/wp-content/uploads/2023/02/Nat… Supports: Emergency referral for back or leg pain with recent onset of: difficulty starting to pass urine or impaired sensation of urine flow; altered perianal, perineal or genital (saddle) sensation; severe or progressive weakness of both legs; loss of the feeling of rectal fullness; or sexual dysfunction. Sudden pain down both legs, or one-leg pain that spreads to both, is a warning sign. No single symptom has good diagnostic accuracy, and negative physical tests do not rule out cauda equina syndrome if the symptoms are present; bladder scans should not be used in isolation or as a discriminator.
  5. National Institute for Health and Care Excellence. Low back pain and sciatica in over 16s: assessment and management. NICE guideline NG59 (2016, last updated July 29, 2026). www.nice.org.uk/guidance/ng59/chapter/Recommendations Supports: Think about alternative diagnoses, particularly with new or changed symptoms, and exclude specific causes of low back pain such as cancer, infection, trauma or inflammatory disease.
  6. Gulati M, Levy PD, Mukherjee D, et al. 2021 AHA/ACC/ASE/CHEST/SAEM/SCCT/SCMR guideline for the evaluation and diagnosis of chest pain. Circulation. 2021;144(22):e368-e454. PMID 34709879. doi:10.1161/CIR.0000000000001029 Supports: Sudden onset of ripping chest pain (with radiation to the upper or lower back) is suspicious of an acute aortic syndrome.
  7. NASA Human Research Program. Evidence Report: Risk of Renal Stone Formation (2024). humanresearchroadmap.nasa.gov/evidence/other/2024%20Renal%20… Supports: The increased risk of renal stone formation occurs rapidly during spaceflight and continues throughout the mission; stones can cause renal colic or severe flank pain, blood in the urine, infection or sepsis; there have been no symptomatic kidney stones in flight to date in US crewmembers on the ISS.
  8. NASA Human Research Program. Evidence Report: Risk of Adverse Health Outcomes and Decrements in Performance due to In-Flight Medical Conditions (2017). humanresearchroadmap.nasa.gov/evidence/reports/Medical.pdf Supports: Table 2: 382 space adaptation back pain events among US astronauts (Shuttle, Mir and ISS through 2006); Table 1: 1.99 back pain events per person-year on the ISS.
  9. 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.
  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: Requirement IDs beginning V1.
  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. 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.
  13. 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.
  14. 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.