Patients launch a SMART app from the portal to connect Apple Health, Google Fit, Fitbit, and others. Presents human-readable scopes and captures explicit consent with timestamps and provenance.
Bridge Types
- Patient-side: HealthKit/Google Fit app posts to the gateway under patient consent
- Portal-side: SMART app initiates OAuth with wearable APIs and manages tokens
Data Governance
- Clinical data maps to FHIR
Observation,Device,Encounter - Non-TPO wellness data remains patient-controlled without explicit consent
- Normalization ensures consistent units (steps, BPM, HRV)
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: Gain explicit, timestamped consent with policy versioning and locale tracking. Enforce scope-based access control and maintain a full audit trail for downstream data usage and revocation events.
- Production Support and IT Operations: Manage token lifecycles across devices. Troubleshoot consent and data flow issues with clear provenance. Ensure portable consent state across channels and consumers.
- IT Managers and Platform Architects: Leverage standards-based interoperability via SMART on FHIR and OAuth2. Implement modular bridge patterns for patient-side and portal-side integration. Govern clinical and wellness data normalization at scale.