RMP-CARD-005 Scheduled heart rate and blood pressure checks: reminder, preparation checklist and record (the crewmember places the cuff)

1 · Identity and scope

At the times the flight surgeon schedules, the robot reminds the crewmember that a heart rate and blood pressure check is due, brings the vital-signs kit by a checked kit fetch, shows the preparation checklist (rest, position, cuff size, arm support, no talking), records each reading as displayed with the clock time and position, and sends the log to the flight surgeon. A displayed value past the alert values set by the clinical lead, or any symptom, raises an alert; the robot never says a reading is high, low or fine.

Why this protocol was chosen. Accurate blood pressure needs a standard technique: the American Heart Association lists an empty bladder, at least 5 minutes of quiet rest, no talking, a supported back and arm at heart level, feet flat, a bare arm and a correctly sized cuff, with repeat readings 1-2 minutes apart, no caffeine, exercise or smoking in the 30 minutes before, an arm that is supported rather than held up, and the middle of the cuff at heart level; a cuff that is too small reads falsely high and one too large falsely low (Muntner 2019). Those positions are for Earth: in weightlessness the crewmember is restrained in the position the flight surgeon's checklist sets, and the same position is used every time so readings can be compared (design judgment). Heart rate and blood pressure change with spaceflight and on return to gravity (OCHMO-TB-019). The schedule, the number of readings and the alert values are set by the flight surgeon and clinical lead; the robot's role (reminder, checklist, record only) is design judgment. The shared value SPO2_ALERT_PCT only raises an alert; it never gates a crew action (the crew act without waiting for a reading), and the clinical lead sets it per mission with the flight surgeon, because the cabin atmosphere can differ by mission.

Autonomy: Max rung 2 for the scheduled reminder, a checked fetch of the vital-signs kit, showing the preparation checklist and recording readings as displayed. The crewmember or CMO places the cuff; the robot never touches anyone and never judges a reading.

Related: RMP-CARD-002 · RMP-CARD-003 · RMP-CARD-004 · RMP-CARD-001 · RMP-RESP-001 · RMP-EGR-003 · RMP-PHARM-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

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

Commercial flights

On commercial flights, 'flight surgeon' and 'CMO' mean the operator's designated medical authority and trained onboard responder. If no trained responder is aboard, this protocol is not used. (NASA-STD-3001 requires two CMOs per vehicle for NASA programs [V1 3006]; FAA rules set no medical standards for spaceflight participants.) [12]

3 · Preconditions and consent

• PRE-1 A scheduled check 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 a check 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 schedule and to the readings being recorded and sent to the flight surgeon; they place the cuff themselves or the CMO does.

Emergency consent

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

Withdrawal

The crewmember can skip or stop any check; the robot logs "skipped by the crewmember" and tells the CMO.

4 · Required sensor inputs

5–6 · Steps and decision points

Each step names who acts. Decision points sit after the step they follow and say who decides: Robot Crew Ground. Any stop rule in section 7 can interrupt any step.

1. S1RobotRung 2

   At the scheduled time, show the crewmember an on-screen prompt that a heart rate and blood pressure check is due, and tell the flight surgeon and the CMO (URGENT if any red flag is stated). The check starts only when the crewmember or the CMO accepts the prompt; an unaccepted prompt is logged "not accepted" and the CMO is told. If the crewmember says not now, ask again once at the time the CMO sets, then log "check not done" and tell the CMO and flight surgeon. 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: Reminder acknowledged, or "check not done" logged and sent.

   V1 3006V1 6003

2. S2RobotRung 2

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

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

   Limit: <set by validation>

   V2 7046V2 7059

   D1DecisionRobot decides

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

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

   Show the preparation checklist on screen: the position the flight surgeon's checklist sets, the same each time; an empty bladder; quiet rest for the time the checklist states, with no talking; no exercise, caffeine or nicotine in the last 30 minutes (if there was, the robot logs "within 30 minutes of exercise, caffeine or nicotine" as stated and the reading is taken anyway); a bare arm, held at heart level by a strap or restraint, not by the crewmember's own effort; the middle of the cuff at mid-chest (breastbone) level; the cuff size the kit chart gives for the arm. The robot does not time the rest: On request only, the robot shows the time elapsed since the start the CMO called, as a clock-time entry; it never announces a time, and never says "time reached", "done", "passed" or "failed".

   Done when: Checklist shown; the crewmember says when they are ready.

   V1 6003

4. S4Crew

   The crewmember (or the CMO) places the cuff and starts each reading, and repeats it as many times as the schedule states, about 1-2 minutes apart.

   Done when: Readings taken, or "not obtained".

   V1 6003

5. S5RobotRung 2

   Record each reading as displayed, with the clock time, the arm and position stated, and the cuff size; a missing reading is logged as "reading not obtained", never a value. Show an on-screen symptom prompt the crewmember can accept and log the answers word for word.

   Done when: Readings and answers logged, or "no response".

   V1 6003V1 7001

   D2DecisionRobot decides

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

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

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

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

7. S7Ground

   The flight surgeon (or the CMO under the onboard checklist when there is no link) reviews the readings and decides on any change to the schedule, repeat checks or care.

   Done when: Decision logged.

   V1 3004

   D4DecisionGround decides

   What schedule, repeat checks or care apply?

   • 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.
8. S8RobotRung 2

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

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

   V2 7059

   D5DecisionRobot decides

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

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

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

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

   V2 7059

10. S10RobotRung 2

    Send the flight surgeon one package: readings as displayed with times, arm, position and cuff size; answers; alerts and decisions; checks not done.

    Done when: Package delivered or queued.

    V1 6003V1 7003

7 · Stop and escalate rules, red flags

Red flags

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

8 · Safety limits

9 · Logs and audit

• LOG-1 Every input, robot action, decision (with who made it) and hand-off, time-stamped to the second.V2 10163V2 10164
• LOG-2 Mode changes and safety-limit events are announced to the operator as they happen and logged.V2 10162V2 10172
• LOG-3 Records are stored and sent as private medical data, encrypted, with access limited to the medical team.V1 6003V1 7003
• LOG-4 Results are kept in a permanent, retrievable format so the flight surgeon can see trends.V1 7001
• LOG-5 Each reading as displayed with time, arm, position and cuff size; readings not obtained; checks not done; answers as stated.
• 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

IDs as published in Volume 1 Revision C [7] and Volume 2 Revision F [8]. 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 schedules with a missed check, a reading past the alert value, chest pain, a failed oximeter reading, CMO as patient, lost link. Pass: Zero contact; zero interpretation; every red flag raised.
2. Training model. Scheduled check drill with an automatic cuff. Pass: Every reading logged as displayed with time and position.
3. Parabolic or station demonstration. Checklist display and logging in weightlessness. Pass: Keep-out held.
4. Flight use under flight surgeon supervision. First use for scheduled checks. Pass: 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, or started by a crewmember or the CMO. The crewmember or CMO places the cuff.

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

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 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.
• Readings already under way and all crew care continue under the onboard checklist and never wait for the link or the robot.
• The schedule continues offline; readings are queued and alerts go to the CMO.

Mars-class delay

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

[10]

Sources

1. Muntner P, Shimbo D, Carey RM, et al. Measurement of blood pressure in humans: a scientific statement from the American Heart Association. Hypertension. 2019;73(5):e35-e66. PMID 30827125. doi:10.1161/HYP.0000000000000087 Supports: Table 5 (best practices): an empty bladder; rest quietly for at least 5 minutes; no talking or texting; back supported, feet flat, legs not crossed; cuff on a bare arm, sized to the arm; arm supported at heart level; avoid caffeine, exercise and smoking for at least 30 minutes before; the patient should not hold up their own arm, because that muscle effort affects the reading; the middle of the cuff at the level of the right atrium (mid-sternum); separate repeated readings by 1-2 minutes. A cuff that is too small gives an artificially high reading, and one that is too large an artificially low reading. Earth seated-position context; the in-flight position is set by the flight surgeon's checklist. Full text read Oct 21, 2026.
2. NASA OCHMO. Orthostatic Intolerance. Technical Brief OCHMO-TB-019 Rev B. www.nasa.gov/wp-content/uploads/2023/12/ochmo-tb-019-orthost… Supports: Spaceflight reduces intravascular fluid volume by around 15%; fluid loading before reentry is an important countermeasure to decrease orthostatic intolerance, and current protocols include 24-48 oz of salt-water solution before deorbit, depending on body weight.
3. 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: On Earth, a 12-lead ECG should be acquired and interpreted within 10 minutes of arrival; an initial normal ECG does not exclude acute coronary syndrome, so ECGs are repeated while symptoms continue; chest pain includes pressure, tightness or discomfort in the chest, shoulders, arms, neck, back, upper abdomen or jaw; sudden ripping pain radiating to the back is suspicious of an acute aortic syndrome.
4. Kleinman ME, Buick JE, Huber N, et al. Part 7: Adult Basic Life Support: 2025 American Heart Association Guidelines for Cardiopulmonary Resuscitation and Emergency Cardiovascular Care. Circulation. 2025;152(16_suppl_2):S448-S478. PMID 41122888. doi:10.1161/CIR.0000000000001369 Supports: Adult basic life support: initial recognition of cardiac arrest, activation of the emergency response, high-quality CPR and use of an automated external defibrillator; also respiratory arrest and foreign-body airway obstruction. Earth guidance; the onboard checklist leads. Abstract read via PubMed Oct 21, 2026; full text not read.
5. National Institute for Health and Care Excellence. Suspected sepsis in people aged 16 or over: recognition, assessment and early management. NICE guideline NG253 (2025, last updated Sept 23, 2026). www.nice.org.uk/guidance/ng253/chapter/Face-to-face-assessme… Supports: People with sepsis may feel very unwell and may not have a high temperature; do not rely on fever alone; a rise in temperature can be a physiological response; assess temperature, heart rate, breathing rate, blood pressure, level of consciousness and oxygen saturation; look for mottled or ashen skin, blue skin, lips or tongue, a non-blanching rash, and breaks in the skin; ask how often the person passed urine in the past 18 hours and about fever or shaking chills (rigors); pay attention to new changes in behavior and to concerns raised by others.
6. British Thoracic Society. Guideline for oxygen use in healthcare and emergency settings (emergency oxygen guideline page). Fetched Oct 21, 2026. www.brit-thoracic.org.uk/quality-improvement/guidelines/emer… Supports: Recommended target saturation range for acutely ill patients not at risk of hypercapnic respiratory failure is 94-98%; for known COPD or other risk factors for hypercapnic respiratory failure, 88-92% pending blood gas results. Context for the CMO and flight surgeon only; the robot never starts, stops or adjusts oxygen.
7. NASA. NASA-STD-3001, Space Flight Human-System Standard, Volume 1: Crew Health, Revision C (2023). www.nasa.gov/wp-content/uploads/2023/11/nasa-std-3001-vol-1-… Supports: NASA-STD-3001 Vol 1 Rev C: V1 3004, V1 3006, V1 6003 (medical monitoring), V1 7001, V1 7003.
8. 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.
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. 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.
11. 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.
12. 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.