Transforms vendor payloads into FHIR with consistent units (e.g., bpm, steps, ms). Attaches Provenance and device metadata; rejects invalid or incomplete records with actionable error reasons.
Capabilities
- Unit normalization and UCUM encoding
- Terminology mapping (LOINC/SNOMED where applicable)
- Validation rules; quarantine and replay
Provides a consistent patient experience for connecting or disconnecting devices and apps, with granular scopes (read steps, read heart rate, share sleep) and clear disclosures. Consent state is portable across channels and respected by every downstream consumer.
Benefits
- One consent UX, many devices
- Scope-based least-privilege sharing
- Revocation propagates instantly
- Full consent history for audits
Notes
- Persist both policy version and user locale shown at time of consent.
Great for:
- Security or Compliance Officers: Ensure consistent provenance and terminology mapping across wearable payloads. Enforce validation rules and reject incomplete records with clear auditability.
- Production Support and IT Operations: Gain actionable error feedback for malformed payloads. Use quarantine and replay workflows to maintain data integrity across ingestion pipelines.
- IT Managers and Platform Architects: Normalize heterogeneous data into FHIR Observations with UCUM units and mapped codes. Scale across device api layers with consistent governance.