Device Data Source
Category: Healthcare Standards
Node id: device-data-source
Standards: GDPR, HIPAA-eligible
Fetch and merge patient device metrics (wearables vitals and/or IoT summaries) for a time window, ready for downstream agent analysis.
What it does
- Parallel fetch of multiple metrics across wearables + IoT sources
- Per-source/per-metric warnings instead of hard failure
- Service-to-service JWT auth to the wearables service when org_id + secret are set
Use cases
- Assemble a patient's recent vitals before an agent triage step
- Combine wearable heart-rate trends with IoT device summaries
Runtime
- Performance tier:
variable
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
patient_id | text | No | Patient ID (overrides config when the config value is empty or an unresolved {{token}}) |
input | json | No | Whole request object from an upstream input node (its output port to this input port). The executor merges it key by key, so phone, patient_id, patient_name and language arrive under their own names; the fields that are not set stay untouched. Lets a pipeline run from the input node's defaults when Studio triggers it without inputs. |
window_from | text | No | Window start (ISO-8601); used when config window.from is empty/unresolved |
window_to | text | No | Window end (ISO-8601); used when config window.to is empty/unresolved |
org_id | text | No | Organization ID; signs the wearables service JWT when a secret is configured |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
data | json | No | Merged result: {patient_id, window, sources, metrics{<metric>:{summary,raw_url,iot_summary}}, warnings, alerts, devices} |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Patient ID | patient_id | string | Yes | Patient identifier. Supports {{token}} substitution from pipeline inputs (falls back to the patient_id input port). | ||
| Time Window | window | json | Yes | {"from": "", "to": ""} | Object with ISO-8601 'from' and 'to' timestamps. Empty/unresolved values fall back to the window_from / window_to input ports. | |
| Metrics | metrics | array | No | ["heart_rate"] | Metrics to fetch (e.g. heart_rate, steps, sleep). Defaults to ["heart_rate"]. | |
| Sources | sources | array | No | ["wearables"] | Data sources to query: "wearables" and/or "iot". Defaults to ["wearables"]. |
Runtime notes
- Output is wrapped under a single 'data' port — wire it to an agent's 'data' input.
- A requested source with no configured backend URL produces a warning, not an error.
- patient_id and window may be supplied by config or by the input ports; config takes precedence unless empty or an unresolved {{token}}.
See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.
¿Algo no está claro? Envíe sus comentarios sobre la documentación por correo electrónico..