Skip to content

Commit c59361c

Browse files
[DOCS] [health] tiny rn fixes main (#1984)
1 parent 803b559 commit c59361c

File tree

2 files changed

+24
-13
lines changed

2 files changed

+24
-13
lines changed

health-and-life-sciences-ai-suite/multi_modal_patient_monitoring/docs/user-guide/get-started/system-requirements.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ This section lists the hardware, software, and network requirements for running
2323

2424
- **Graphics / Accelerators:**
2525
- Required: Intel CPU.
26-
- Optional (recommended for full experience,):
26+
- Optional (recommended for full experience):
2727
- Intel integrated GPU supported by Intel® Graphics Compute Runtime.
2828
- Intel NPU supported by the linux‑npu‑driver stack (see [Release Notes](../release-notes.md) for a known issue).
2929

Lines changed: 23 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,18 @@
1-
# Release Notes
1+
# Release Notes - Multi-Modal Patient Monitoring
22

33
## Version 1.0.0 - March 25, 2026
44

55
This is the initial release of the application, therefore, it is considered a preview version.
66

7+
Multi-Modal Patient Monitoring showcases how a single Intel-powered edge system can
8+
simultaneously run computer vision, physiological signal processing, artificial intelligence
9+
inference, and real-time medical device telemetry — all within one integrated dashboard.
10+
11+
It proves that heterogeneous workloads — from 3D human pose estimation to heart-rate
12+
extraction, AI-based ECG analysis, and medical device simulation — can coexist efficiently on
13+
one platform without compromising performance or stability.
14+
15+
716
### New
817

918
The initial feature set of the application is now available:
@@ -15,15 +24,17 @@ The initial feature set of the application is now available:
1524

1625
### Known issues
1726

18-
Docker fails with the `gathering device information` error.
19-
: This may happen on systems without NPU. NPU is optional for use but is still defined as a
20-
possible accellerator in the image setup.
21-
: To work around the issue, in `docker-compose.yaml`, remove the device by commenting out
22-
the following lines, like so:
23-
24-
```
25-
# devices:
26-
# - /dev/dri
27-
# - /dev/accel
28-
# - /dev/accel/accel0
27+
- Docker fails with the `gathering device information` error.
28+
29+
This may happen on systems without NPU. NPU is optional for use but is still defined as a
30+
possible accelerator in the image setup.
31+
32+
To work around the issue, in `docker-compose.yaml`, remove the device by commenting out
33+
the following lines, like so:
34+
35+
```
36+
# devices:
37+
# - /dev/dri
38+
# - /dev/accel
39+
# - /dev/accel/accel0
2940
```

0 commit comments

Comments
 (0)