fhir-api-client-security

To secure OAuth tokens in Canvas FHIR API clients, retrieve tokens from secrets and ensure they are never logged. Apply the token storage and scope minimization checklist to enforce safe credential handling during security reviews.

Patient-scoped authorization restricts FHIR API access to a specific patient's data context. Canvas plugins acting as FHIR API clients must enforce patient-scoped token requirements to ensure access is properly limited during Http() endpoint calls.

Audit Canvas plugin FHIR API security by applying a token and scope checklist during development. Verify OAuth patterns, token handling, scope minimization, and secure logging for plugins using Http() or Canvas SDK data models.

Yes, this security review guidance applies to Canvas plugins using Canvas SDK data models and Http() calls to FHIR endpoints. It enforces token storage, scope minimization, and patient-scoped authorization checklists for these integrations.

Common FHIR API client token handling limitations include unsafe credential storage and insecure logging. Mitigate these risks by following fhir_client_context.txt guidelines to ensure tokens are retrieved securely from secrets and never exposed in logs.

Perform a FHIR API client security review during plugin development and before deployment when your plugin calls FHIR endpoints via Http() or uses Canvas SDK data models, ensuring OAuth authentication and patient-scoped tokens meet security guidelines.