FHIR Lake Pipeline
Operational view of partner data flowing from CMS/Nexus APIs into the HAPI FHIR Lake. Partner self-service activity is on Activity Log; this page documents ops surfaces.
Partner Activity (developers portal)
Row-level pushes, API calls, and webhook deliveries for authenticated partners.
Pipeline summary
Daily push count, sync rate, and latency aggregates for your GPID.
Lake analytics app
External Next.js dashboard for lake operators (OIDC via Plexus).
Lake FHIR API
HAPI FHIR R4 endpoint for synced partner resources.
Plexus ingest explorer
Internal ops: retry/quarantine, all partners, cross-filter.
CMS pipeline health API
JSON health summary (Bearer + admin): GET /cms/pipeline/health
Data path
Partner API → durable outbox (cms_fhir_sync_events) → HAPI FHIR Lake → Nexus EHR / Pulse.
Telemetry: usage events (API calls), pipeline metrics (pushes/pulls/syncs), webhook alerts (pipeline.stale_data).