Store secrets
Keep FHIR keys, webhook secrets, signing keys, and partner credentials on the server or in an approved vault.
API authentication methods
Supported patterns include scoped FHIR integration keys and verified SMART/system-context JWTs when the target deployment enables them.
Authorization flows
Authorization joins publisher release proof, independent certification, hospital activation, current user access, and exact FHIR scope.
Server-side logic
Validate users and purpose on the partner server, call FHIR with server-held credentials, and verify events before side effects.
Listen to events
Receive HMAC-signed FHIR Bundles through the webhook endpoint and authenticate the complete v1 envelope.
Development, test, and production modes
Separate synthetic loopback development, TEST certification fixtures, hospital UAT, and production configuration.
Sandbox support
The kit provides a loopback-only bridge simulator and synthetic patient context for local development.
Local network access
Local development is restricted to explicit loopback; on-prem integrations require hospital network review and exact origins.
App settings page
An app may serve its own settings UI, but medOS has no general hosted partner settings-page contract yet.
Build an embedded UI
Serve a responsive HTTPS page that communicates through `medos-bridge/1` inside the constrained remote-app frame.
Onboard a hospital
Onboarding is a clinical-purpose and operations review, not only a sign-in screen.