Healthcare Robotics × Intelligent Software
AMR EVAEnhanced Virtual Aide
A healthcare robotics workflow that authenticates the operator, unlocks the payload cabinet through CAN Bus, secures it before travel, moves the autonomous robot over MQTT, and captures a patient's vitals through contactless rPPG at the destination.
PythonMQTTCAN BusrPPGFace Authentication
AMR CARE MISSION
FACE AUTHOperator verified
CABINETOpen · secure · close
AMRNAVIGATION
MQTTMovement command
rPPGPatient vitals
Face auth → cabinet open / close → MQTT travel → patient rPPG vitals
THE PROBLEM
Coordinate secure payload access, AMR navigation, and contactless patient vitals capture while keeping the mission sequence safe and understandable to operators.
HARVEY'S ROLE
Software and robotics integration across face authentication, CAN Bus cabinet and payload control, MQTT-based AMR movement, rPPG patient vitals capture, and multiple on-site deployments in Taiwan.
Claims are intentionally conservative and based only on supplied information.INTERACTIVE ARCHITECTURE SIMULATION
Secure payload delivery & patient vitals
MISSION / ROOM 304READY FOR MISSION
PATIENT MONITOR--BPM
CONTACTLESS rPPG
START
ROOM 304PATIENT VITALS ZONE
MQTT · MOVEMENT
FACE AUTH
rPPG · PATIENT VITALS
CAN BUS · CABINET
-- BPMAWAITING PATIENT
FACE AUTH
PATIENT rPPG
Face authentication Cabinet control Travel + patient rPPG
ROBOT CONTROL + CARE WORKFLOW
Authenticate, load, travel & scan
- 1Mission created
- 2Face authentication initiated
- 3Identity verified
- 4CAN Bus cabinet opened
- 5Payload secured and cabinet closed
- 6MQTT movement command published
- 7AMR navigation started
- 8Destination reached
- 9Patient rPPG vitals scan started
- 10Heart rate, SpO₂, respiration, stress, and blood pressure captured
- 11Five-second observation hold completed
- 12AMR returned to start position
AMR care mission state
HEART RATE--BPM
AWAITING PATIENT SCANSYSTEM ARCHITECTURE
A readable path from interface to system.
Conceptual architecture based only on verified technologies.
01Mission UI
02Face Authentication
03CAN Bus Unlock
04Cabinet Open / Close
05MQTT Movement
06AMR Navigation
07Patient Arrival
08rPPG Vitals
09Mission Telemetry
ENGINEERING DECISIONS
Make the system legible.
Require face authentication before granting payload access.
Open the cabinet through CAN Bus, then confirm it is closed before publishing the MQTT movement command.
Start contactless rPPG vitals capture only after the AMR reaches the patient.
TRADEOFFS & INTEGRITY
Production architecture with controlled demo data.
Simulation uses synthetic data and intentionally avoids clinical accuracy claims.
Architecture is conceptual because proprietary subsystem details are not disclosed.
PRODUCTION READINESS
Built for repeatable AMR deployment.
The AMR workflow coordinates operator authentication, cabinet control, MQTT navigation, patient rPPG capture, and mission telemetry as one deployable healthcare robotics flow.
Designed for on-site healthcare robotics integration, repeatable mission execution, and maintainable hardware-software coordination.PROJECT MEDIA
AMR EVA media archive
Project photos and videos are loaded directly from this case study's public media folder.
FROM CODE TO THE REAL WORLD
Multiple on-site deployments — Taiwan
Harvey traveled to Taiwan multiple times in connection with the Healthcare AMR project, gaining direct exposure to real-world healthcare robotics integration and deployment.
- On-site AMR integration exposure
- Real-world deployment environments
- Healthy Ageing Tech Show attendance
FIELD MEDIA
Taiwan deployment archive
Approved field photos and videos from on-site AMR deployment work.
TECHNOLOGY STACK
Healthcare robotics across software and hardware.
A cross-platform AMR system spanning React interfaces, Python robotics services, MQTT communication, CAN Bus hardware control, Android, and iOS.