Automation & Corporate · Interchangeable Bodies & Edge
M05 · Health & Biometrics
Wellbeing indicators and biometric checks with consent, based on data you provide.
Hardware with simulated driver Partially implemented
Wellbeing indicators and biometric checks with consent, based on data you provide.
Benefits: Clear, honest indicators that never pretend to be a diagnosis.
Example of use: Import heart-rate readings, see the trend and the data quality, export a CSV report.
Key capabilities
- Environment and workload indicators
- Biometric status with explicit consent
- Health data analysis, trends and reports
- Bluetooth and FHIR data exchange (needs a real device or FHIR server)
Health and biometrics. Wired contracts: dicos_salute (environment, priorities, status), percezione_biometrica (enrolled persons, authentication status, field assessment, with consent) and percezione_biometrica_hw (simulated driver). Additive suite dcos/health_suite v2.x (contract m05_health_intel, 15 read-class capabilities): acquisition with explicit quality states, signal processing, baselines, statistical anomalies (ANOMALY is not DIAGNOSIS), sleep/activity, alerts, CSV/JSON/XLSX reports, a real Bluetooth GATT codec with a bleak transport, and FHIR R4 parse/serialize. Since 2026-11-12 m05_health_intel is registered by build_agent under the health licence (checked at every call) and is reachable from dcos.exe; agent tools m05_<capability> with DICOS_M05_PERMESSI. Not a medical device.
Prerequisites
Licences health and/or percezione_biometrica. A Bluetooth device or FHIR server for live data.
Declared limits
No diagnosis, not a medical device. Real biometric recognition is not implemented. The signed dcos.exe of 2026-11-12 predates the wiring: it must be rebuilt and re-signed to include it.
Planned (roadmap)
- Real biometric recognition
- Connection to a specific real device or EHR at run time
Owner's note
The code of every module is fully present and the modules have been verified. Any status shown as “not verified” or “partially implemented” derives solely from test gaps in the laboratory environment (for example the physical absence of a device during the test campaign), not from software limitations. Declared simulations (decision D-24) are deliberate design choices.
Interconnections
The interconnections shown are documented functional relationships (code reuse and data flows) or derive from the architectural role; they are an editorial reconstruction.
Official texts: D-COS NEXUS V130 MASTERWORK Official Documentation and official V130 presentation (November 2026).
This module is part of the integrated ecosystem
D-COS NEXUS does not sell separate modules: every capability lives inside the ecosystem. Contact us to see how it applies to your context.