SAU-MIoT is a medical IoT research and engineering organization focused on connected health telemetry, secure device communication, realtime monitoring, and applied intelligence for clinical sensor data.
We build software components for collecting, processing, storing, analyzing, and visualizing patient and device telemetry in a way that keeps security, reliability, and operational clarity close to the code.
- Medical IoT telemetry ingestion
- Patient vital reading dashboards
- Device authentication and scoped access
- PostgreSQL-backed master data
- InfluxDB time-series storage
- Realtime monitoring pipelines
- Cybersecurity analysis for connected devices
- Applied intelligence over clinical telemetry
- Documentation and engineering process for healthcare-oriented systems
The organization is structured around a small set of private repositories:
| Area | Purpose |
|---|---|
| Core platform | Web API, application services, persistence, telemetry, and dashboard integration. |
| Firmware | Device-side experiments, prototypes, and embedded integration work. |
| Cybersecurity | Threat modeling, device security, and operational hardening work. |
| Intelligence | Analytics and applied intelligence experiments over telemetry. |
| Documentation | Shared research notes, architecture records, and project documentation. |
Most repositories are private while the platform is under active development.
- Keep medical and patient data private.
- Treat device telemetry and credentials as sensitive.
- Prefer explicit architecture boundaries over fast coupling.
- Keep device ingest, master data, telemetry storage, and UI concerns separated.
- Document operational assumptions before production use.
- Review changes that affect authentication, data scope, telemetry volume, or deployment behavior.
- .NET 10 and ASP.NET Core
- React, TypeScript, and Vite
- PostgreSQL
- InfluxDB
- GitHub Actions
- Device API key authentication
- Realtime-ready architecture with SignalR planned where appropriate
Do not publish real patient data, device secrets, production logs, API keys, database credentials, or telemetry exports in repositories, issues, pull requests, or discussions.
Security-sensitive findings should be reported privately to the organization maintainers.
Internal contributors should use focused pull requests, include tests for behavior changes, and update documentation when architecture, configuration, endpoints, or deployment behavior changes.
For project access or coordination, contact the organization maintainers through the approved internal channels.
