Home › Robotic Medicine › Protocol library › RMP-RESP-003
RMP-RESP-003 Severe allergic reaction (possible anaphylaxis): urgent alert, bring the sealed emergency kit and oxygen kit on command, record vital signs (no drug advice)
AI-assisted Reviewed (AI-assisted) AI-assisted clinical and source review by the Medical Research Assistant, Oct 20, 2026 (batch 3 review, 54 corrections); all corrections are applied in this version. No named human clinician has reviewed it.
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:
logged, not interpreted
,sent to flight surgeon
,reading as shown on the device
,dose time as stated by the CMO
,EMERGENCY FETCH – NOT VERIFIED (CMO command)
. Never:normal
,no problem found
,all clear
,negative
,any diagnosis or cause
,anaphylaxis
,not anaphylaxis
,just a rash
,mild
,resolved
,safe
,verified
,time for the next dose
,minor
.
1 · Identity and scope
If a crewmember or the CMO says a crewmember may be having an allergic reaction, the robot sends an URGENT alert at once, brings the sealed emergency (anaphylaxis) kit and the closed oxygen kit to the CMO on command, shows the allergy list from the medical record, records the vital signs and oxygen saturation the CMO measures and the medicines and times the CMO states on a clock-time timeline, and after the event reconciles the kits through RMP-PHARM-001 as an inventory record only. Afterwards it offers prompt-only check-ins for the watch period the flight surgeon sets. The CMO assesses, decides and gives every treatment.
Why this protocol was chosen. Anaphylaxis is a sudden, rapidly progressing reaction with airway, breathing or circulation problems, usually with skin or mucosal changes; skin changes can be absent in up to 20% of reactions, and in up to 30% there is no obvious trigger (Resuscitation Council UK, 2021). NASA records list 11 mild-to-moderate allergic reactions among US astronauts through 2006. The guideline stresses calling for help early, and notes biphasic reactions in about 5% of patients, also after milder reactions, with a median time of around 12 hours. Intramuscular adrenaline (epinephrine) is the first-line treatment for anaphylaxis (RCUK 2021; WAO 2020), given by the CMO under the onboard checklist; epinephrine is in the ISS flight formulary (HRP report, 2017). The robot never names, suggests or times a medicine; this is stated only so the kit contents and the checklist can be checked. Severe gastrointestinal symptoms (severe crampy belly pain, repeated vomiting) together with skin or mucosal changes also make anaphylaxis highly likely (WAO 2020). A helper that raises the alarm at once, brings the sealed kit and keeps an exact clock-time record lets the CMO keep both hands on the patient.
Autonomy: Max rung raised from 1 to 2 for supervised fetching and recording, as in batch 1. The robot never opens the kit, chooses, prepares or gives a medicine, or starts oxygen.
Covers
- Possible allergic reaction in flight: new swelling of the lips, tongue or throat, hoarse voice, wheeze or breathlessness, faintness, or hives, flushing or itching, especially after a new food, medicine, product or exposure
- Prompt-only check-ins during the watch period after a reaction
Locked out (never done by the robot under this protocol)
- Opening the emergency kit, or choosing, preparing, dosing or giving any medicine (including adrenaline); the CMO decides and gives every medicine
- Prompting or suggesting a repeat dose (the CMO and onboard checklist decide)
- Dose-interval cues: no running counter, tone, colour change or spoken cue tied to any interval after a dose; elapsed time is given only when the CMO asks
- Recording a check made after the kit was used as a check before use
- Starting, stopping or adjusting oxygen (the oxygen kit is fetched closed)
- Positioning the patient, or any airway procedure
- Deciding whether it is anaphylaxis, or that it is mild
- Touching, holding or restraining the crewmember
Related: RMP-PHARM-001 · RMP-PHARM-003 · RMP-RESP-001 · RMP-RESP-002 · RMP-CARD-001 · RMP-SKIN-004 · RMP-NEURO-004 · RMP-GI-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
- Crewmember with the reaction: answers if able; never asked to wait for the robot
- Second trained CMO: receives alerts if the CMO is the patient, and helps the CMO
- Pharmacy lead and flight surgeon: set the contents of the sealed emergency kit before flight
- 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.) [12]
Robot may
- Send an URGENT alert at once on a crewmember's word
- Bring the sealed emergency kit and the closed oxygen kit to the CMO on command, and restrain them within reach
- Show the crewmember's allergy list from the medical record to the CMO
- Record the vital signs, oxygen saturation and observations the CMO enters, and the medicines and times the CMO states
- Show a clock-time timeline of the reaction start, each stated medicine and dose time, and each CMO entry; give elapsed time only when the CMO asks, in the same words each time
- Reconcile the kits after the event through RMP-PHARM-001 as an inventory record (not a check before use) and show them as opened – not restocked until resealed
- Offer prompt-only check-ins during the watch period
Robot may not
- Open the kit, or choose, prepare, dose or give any medicine
- Suggest a dose, a repeat dose or a timing
- Start or adjust oxygen
- Position or touch the patient
- Say it is or is not anaphylaxis, or that it is mild or over
- Fetch the suspected trigger medicine again for that crewmember without a new logged order through RMP-PHARM-001
- Ask the crewmember to move toward the robot, to another module, or to the kit (the robot goes to the patient)
- Give any dose-interval cue, or say the kit was verified
- Start without a human command
3 · Preconditions and consent
- PRE-1 A crewmember or the CMO started the protocol by command. Nothing starts it automatically.
human_start == trueV2 10174 - PRE-2 Robot self-test passed; it knows the stowage location of the sealed emergency kit and the oxygen kit, and the kit seals were checked at the last inventory.V2 10161V2 7059
- PRE-3 Robot and supplies restrained when not moving.V2 7046
- PRE-4 Link status and current delay known. The CMO never waits for the robot or the link before treating.
link_state in [live, delayed, down]
- Consent
- Recording and questions by voice, with the crewmember's agreement when they can give it; any question can be declined, and an explicit "no" is logged as declined for that question only.
- Emergency consent
- If the crewmember cannot answer, the URGENT alert stands, the robot asks nothing more, and the CMO leads; recording of the CMO's entries continues as part of the medical record.
- Withdrawal
- The crewmember can stop video at any time; the URGENT alert and the record of what was given are kept.
4 · Required sensor inputs
| ID | Input | Source | Required | If missing |
|---|---|---|---|---|
| IN-1 | Reported symptoms and when they started | Crewmember or CMO, by voice | Yes | Log "no response" and keep the URGENT alert (D2). Never logged as declined. |
| IN-2 | Possible trigger (new food, medicine, product or exposure), as reported | Crewmember or CMO, by voice | Optional | Log "not known". A missing trigger never lowers the alert (up to 30% have none). |
| IN-3 | Allergy list and medicines from the medical record (shown to the CMO; the robot does not advise) | Medical record and dose log (RMP-PHARM-003) | Optional | Note "record not available". |
| IN-4 | Heart rate, blood pressure, breathing rate and oxygen saturation, measured by the CMO (recorded, not interpreted) | Entered by the CMO or read from a device the CMO placed | Optional | Log "not measured". A missing value is never treated as reassuring; an oximeter with no reading is logged as "no reading" and flagged (RF3). |
| IN-5 | Medicines given, with times, as stated by the CMO | Stated by the CMO; logged as stated | Optional | Log "not stated"; the robot never asks whether to give one. |
| IN-6 | Link status and delay | Communications system | Yes | Treat 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.
- S1RobotRung 2
On a crewmember's or the CMO's word, send an URGENT "possible severe allergic reaction" alert to the flight surgeon and the CMO at once. 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: Alert acknowledged, or escalated to the next named crewmember.
V2 10174V1 6003V1 3006
- S2RobotRung 2
On the CMO's command, bring the sealed emergency kit and the closed oxygen kit to the CMO at once and restrain them within reach. The robot never opens them. 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 CMO never waits for the robot: if the CMO or a crewmember already has the kit, the robot skips this step.
Done when: Kits within reach, or step skipped; override logged.
Limit: <set by validation>
V2 7046
- S3Crew
The CMO removes or stops the possible trigger if possible (for example an infusion), assesses airway, breathing and circulation, and decides and gives every treatment under the onboard checklist, with the flight surgeon when the link allows. The second trained CMO helps or takes over if the CMO is the patient.
Done when: Treatment decisions made by humans; the robot logs what is stated.
V1 3004
- S4RobotRung 2
Show the allergy list from the medical record to the CMO, then ask the red-flag questions by voice if the crewmember can answer (swallowing, throat, breathing, faintness). D1 is checked after every answer.
Done when: Answers logged, or "no response" logged.
D1DecisionRobot decidesChecked 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. The alert from S1 stands; skin changes alone never cancel it.
D2DecisionRobot decidesDid the crewmember answer the 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.
- S5RobotRung 2
Record the vital signs, oxygen saturation and observations the CMO enters, and each medicine and time the CMO states. Show them as a timeline of clock times: reaction start, each stated medicine and dose time, and each CMO entry. Give elapsed time only when the CMO asks ("time since the last dose?"), answering in the same words each time. No running counter, tone, colour change or spoken cue is tied to any interval after a dose.
Done when: Entries time-stamped on the timeline.
V1 3004
- 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) decides further treatment, the watch period, work limits and any evacuation [V1 3007]. If the trigger may be a medicine, the flight surgeon records it in the medical record. The robot logs the decisions.
Done when: Decision logged.
V1 3007
D3DecisionGround decidesWhat is the plan (treatment, watch period, work limits)?
- 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
During the watch period of <set by flight surgeon> hours after the reaction, offer a check-in every <set by flight surgeon> hours. 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. Any return of symptoms is URGENT (RF5).
Done when: Each prompt accepted, postponed or answered; log closed by a human.
V2 10174
- 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. Nothing in this step is recorded as a check before the kit was used.
Done when: Reconciliation recorded and labelled; override flagged; kit shown as opened – not restocked until resealed.
V2 7059
- S10RobotRung 2
Send the flight surgeon one package: symptom times, possible trigger, CMO entries, medicines and times as stated, alerts and acknowledgements.
Done when: Package delivered or queued.
V1 6003V1 7001V1 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 | Robot pauses its own movement in its stopped position and tells the CMO and the commander. This pauses robot movement only: the CMO's emergency-kit treatment, crew oxygen and CPR 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; the robot resumes only on the CMO's confirmation. Everything is logged and sent to the flight surgeon at the next contact.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 CMO or a crewmember needs the robot's space to reach the patient | Robot moves to its rest position at once and holds; it still does not leave the module on its own.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 | Airway: swelling of the tongue, lips or throat, a feeling that the throat is closing, trouble swallowing, hoarse voice, or noisy breathing in [1] | any | URGENT alert to the CMO and flight surgeon |
| RF2 | Breathing: wheeze, persistent cough, breathlessness, tiring with the effort of breathing, or oxygen saturation below the alert level [1] | any symptom; saturation below <set by clinical lead> (for context, the guideline gives below 94% as hypoxaemia) | URGENT alert |
| RF3 | Circulation: pale or clammy skin, fast heart rate, low blood pressure, dizziness, fainting, reduced alertness, or an oximeter that cannot get a reading [1] | any; heart rate or blood pressure beyond <set by clinical lead> | URGENT alert; the CMO checks in person at once |
| RF4 | Skin or mucosal changes only (hives, flushing, itching, or swelling of the skin away from the lips, tongue and throat, which are RF1) after a possible trigger [1] | any | Flag: the CMO assesses in person now. The flag stays open and the CMO sets a re-check time (a prompt only, after <set by flight surgeon> minutes); the red-flag questions stay live, and any airway, breathing, circulation or severe gastrointestinal symptom is URGENT at once (RF1-RF3, RF6) |
| RF5 | Symptoms come back after improvement [1] | any, during the watch period of <set by flight surgeon> hours (for context, biphasic reactions occur in around 5% of patients, with a median time of around 12 hours, and 6-12 hours of observation may miss over half) | URGENT alert |
| RF6 | Severe crampy belly pain or repeated vomiting, together with skin or mucosal changes, or after an allergen known to affect this crewmember [2] | any | URGENT alert; the CMO checks in person at once |
| RF7 | The possible trigger is a medicine the crewmember was given [1] | any | Flag to the flight surgeon and CMO (information only; stopping a medicine is a crew action under the checklist); the robot fetches that medicine for that crewmember again only on a new logged order (RMP-PHARM-001) |
| RF8 | Nausea or mild belly discomfort alone, with no airway, breathing or circulation problem and no skin or mucosal change [1] | any | Flag: the CMO assesses in person; the red-flag questions stay live; see RMP-GI-002 |
8 · Safety limits
| ID | Limit | Value | How enforced |
|---|---|---|---|
| L1 | Contact with the crewmember | not allowed | Keep-out zone in the robot controllerV2 10172 |
| L2 | Opening the emergency kit or handling any medicine outside its sealed kit | not allowed | No grasp mode for kit contents; kit handled closed only |
| L3 | Robot speed near crew | <set by validation> | Hard limit in the controllerV2 10172 |
| L4 | Closest approach to the patient and CMO | <set by validation> | Distance sensing; the robot stays outside it |
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 Symptom onset, each CMO entry and each stated medicine and time on a clock-time timeline, so the flight surgeon can follow the course of the reaction.
- 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
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 medical kits (b), recording vital signs (h) and recording treatment (l); administering and managing medicines (m) is a human capability. |
| [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 3007] | Medical evacuation | Medical evacuation when illness is beyond onboard capability; the flight surgeon decides. |
| [V1 5003] | Crew medical officer training (including toxicology and medical equipment) | CMO training includes medical procedures and equipment; the CMO treats. |
| [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 [8] and Volume 2 Revision F [9]. 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 reactions of every red-flag type, reactions without skin changes or without a known trigger, symptoms that return, a CMO who is the patient, no response and lost link. Pass: Every red flag acts at once; zero medicine, dose or timing suggestions; zero dose-interval cues; zero kit openings; every emergency fetch logged as an override and never as verified; unacknowledged alerts escalate.
- Training model. CMO training sessions on a manikin with the robot fetching the sealed kits and recording. Pass: Kits delivered within <set by validation> seconds of the command; the CMO is never delayed or obstructed.
- Parabolic or station demonstration. Fetching and restraining the sealed emergency kit and closed oxygen kit in weightlessness, without a patient. Pass: Kits delivered closed and restrained; seals intact.
- Flight use under flight surgeon supervision. First use as a recording aid in drills, then in real events alongside the onboard checklist. Pass: No safety events; the record is complete and accurate.
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. Every alert goes to the CMO and flight surgeon at once; the CMO treats under the onboard checklist; the flight surgeon decides when the link allows.
- 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
- 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 [11].
Loss of signal and Mars delay
- Live link
- Low Earth orbit: the flight surgeon receives the alert at once and can join by voice and video.
- Loss of signal
- The robot pauses any movement and tells the CMO; on the CMO's confirmation it keeps recording offline.
- The CMO's emergency-kit treatment, crew oxygen and CPR continue under the onboard checklist and never wait for the link or the robot.
- The CMO (or the second trained CMO) treats under the pre-approved onboard checklist; nothing waits for the link.
- At the next contact the robot sends one package: times, entries, stated medicines and alerts.
- Mars-class delay
- Replies may take up to about 21-23 minutes each way, with blackouts of about 2-3 weeks; treatment cannot wait for the ground, so the onboard checklist and two trained CMOs lead.
- The watch period and check-in schedule after a reaction are set before flight.
Corrections and updates
Oct 20, 2026, version 0.2. AI-assisted clinical and source review by the Medical Research Assistant, Oct 20, 2026 (batch 3 review); no named human clinician. Changes:
- Scope "why" names intramuscular adrenaline as first-line, given only by the CMO (RCUK 2021, WAO 2020; epinephrine in the ISS formulary per the 2017 HRP report); S3 adds removing or stopping the trigger. The robot still names no medicine (item 9).
- MANDATORY (item 10): S2 is an emergency fetch with no barcode check before hand-over, logged as an override and announced as "EMERGENCY FETCH – NOT VERIFIED (CMO command)", with "seal not intact" if so; it is never called verified.
- MANDATORY (item 11): new S9 reconciles the kits through RMP-PHARM-001 after the event, labelled "inventory reconciliation after emergency use – not a check before use", flags the override to the flight surgeon and pharmacy lead, and shows the kit as "opened – not restocked" until resealed.
- MANDATORY (item 12): the per-dose time-since counter is replaced by a clock-time timeline; elapsed time only when the CMO asks, in the same words each time; no tone, colour or spoken cue tied to a dose interval; "dose-interval cues" added to the lockouts.
- MANDATORY (item 13): RF6 is now URGENT for severe crampy belly pain or repeated vomiting with skin or mucosal changes, or after a known allergen (WAO 2020); milder gastrointestinal symptoms alone are the new RF8 Flag (RCUK).
- RF4 stays a Flag but stays open, with a CMO-set re-check prompt; swelling of the lips, tongue or throat is RF1 (item 14).
- RF7 now cites RCUK Table 1 (medication accounts for 39% of anaphylaxis-related deaths) and stays information only (item 15).
- The robot never asks the crewmember to move toward it, to another module or to the kit (item 16; RCUK, by analogy).
- Sources: WAO 2020 and the AAAAI/ACAAI 2023 practice parameter (abstract only) added; the RCUK 2021 entry notes that its printed review date (May 2026) has passed and that the RCUK page, as fetched on Oct 20, 2026, still lists May 2021 as the most recent version (item 17).
- Flight-surgeon windows and schedules that were prose only are now placeholder tokens the build can track, with context figures only where the review quoted a source (item 50).
- One emergency-fetch pattern: kits are fetched on a human command with no barcode gate, logged as an override ("EMERGENCY FETCH – NOT VERIFIED"), never called verified, reconciled afterwards through RMP-PHARM-001 as an inventory record only (never a check before use), and shown as "opened – not restocked" until resealed (item 51; ISMP).
- "Mild" and "minor" are never-words in every batch 3 protocol (item 54).
- Cross-links added for the new routes; the build checks that each target exists in the library, and planned protocols link to their library entry (item 53).
Oct 21, 2026, version 0.2. Batch 5 editorial (AI-assisted), Oct 21, 2026; batch 4 review item 49; no named human clinician. Changes:
- Inherited stop-rule and requirement wording: "holds a safe position" → "holds its stopped position"; "stays in its safe state" → "stays stopped"; "take over safely" → "take over"; "Robot stays safe if no one takes over" → "Robot stays stopped if no one takes over". Schema level name safe-state and never-word list entry "safe" unchanged.
Oct 21, 2026, version 0.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, v2). Editorial; no change to steps, thresholds or limits.
- X5 and the comms loss-of-signal branch now say only the robot pauses: crew the CMO's emergency-kit treatment under the checklist, oxygen and CPR never wait for the link or the robot (batch 6 review item 24 / suggestion 40). Editorial; robot behaviour unchanged.
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 reworded: "the CMO's emergency-kit treatment, crew oxygen and CPR continue under the onboard checklist and never wait for the link or the robot" (batch 7 review item 14). Editorial.
Earlier version: Draft v0.3, Oct 21, 2026. Download the current YAML above.
Sources
- Resuscitation Council UK. Emergency treatment of anaphylaxis: guidelines for healthcare providers (May 2021; printed review date May 2026, which has passed. The RCUK guideline page, as fetched on Oct 20, 2026, still lists May 2021 as the most recent version; a newer version was not found). www.resus.org.uk/sites/default/files/2021-05/Emergency%20Tre… Supports: Anaphylaxis is characterised by sudden onset and rapid progression of symptoms, Airway and/or Breathing and/or Circulation problems, and usually skin or mucosal changes; airway problems include throat or tongue swelling, hoarse voice and stridor; breathing problems include wheeze, persistent cough, increased work of breathing, tiredness and hypoxaemia (SpO2 below 94%); circulation problems include pale clammy skin, fast heart rate, low blood pressure, dizziness, decreased conscious level and collapse; skin or mucosal changes alone are not a sign of anaphylaxis and may be absent in up to 20% of reactions; in up to 30% of cases there may be no obvious trigger; gastrointestinal symptoms without airway, breathing or circulation problems do not usually indicate anaphylaxis; call for help early; biphasic reactions occur in around 5% of patients, also after milder reactions, with a median time of around 12 hours, and observation for 6-12 hours may miss over half of them; adrenaline is the first-line treatment, given intramuscularly, and is repeated after 5 minutes if airway, breathing or circulation problems persist; medication accounts for 39% of anaphylaxis-related deaths (Table 1), and allergens given by a parenteral route (for example an IV drug or intramuscular injection) cause a more rapid onset; patients must not walk or stand during acute reactions.
- Cardona V, Ansotegui IJ, Ebisawa M, et al. World Allergy Organization anaphylaxis guidance 2020. World Allergy Organ J. 2020;13(10):100472. PMID 33204386. doi:10.1016/j.waojou.2020.100472 Supports: Anaphylaxis is highly likely with acute skin or mucosal involvement plus respiratory or cardiovascular involvement, or severe gastrointestinal symptoms (severe crampy abdominal pain, repetitive vomiting), especially after exposure to non-food allergens; intramuscular epinephrine (adrenaline) continues to be the first-line treatment; remove exposure to the trigger if possible (for example, discontinue administration of drugs or therapeutic agents).
- Golden DBK, Wang J, Waserman S, et al. Anaphylaxis: a 2023 practice parameter update. Ann Allergy Asthma Immunol. 2024;132(2):124-176. PMID 38108678. doi:10.1016/j.anai.2023.09.015 Supports: AAAAI/ACAAI practice parameter on anaphylaxis, including epinephrine use. Only the citation and abstract were checked; the "first-line" statement in this protocol rests on RCUK 2021 and WAO 2020.
- 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: 11 mild-to-moderate allergic reactions among US astronauts (Shuttle, Mir and ISS through 2006). Epinephrine is among the compounds in the ISS operational flight formulary (2017 report; current kit contents and form not verified).
- Institute for Safe Medication Practices. Guidelines for the safe use of automated dispensing cabinets (2019). www.ismp.org/system/files/resources/2019-11/ISMP170-ADC%20Gu… Supports: Override is limited to medicines needed in emergent circumstances where waiting could harm the patient (3.3b); limit what is available on override (3.4b); require documentation of the override rationale (3.4d); routinely analyze override reports (3.6). Used for the emergency-fetch pattern by analogy (a robot fetching a sealed kit is not a dispensing cabinet).
- Institute for Safe Medication Practices. Lack of proper escalation process for BCMA scanning failures. ISMP Medication Safety Alert! Acute Care, March 21, 2024. www.ismp.org/sites/default/files/newsletter-issues/20240321.… Supports: Unsafe practices include scanning after medication administration; procedures must include an escalation process for barcode scanning failures. Used so that the reconciliation after an emergency fetch is never recorded as a check before use.
- 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. 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.
- 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. 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.