Unsupported Scopes Removal
The Appointment, Binary, and Consent resources are currently listed under the Technical Details tab of the Developer Platform screen. However:
- Appointment and Consent resources are not supported by our FHIR ecosystem.
- While we support the Binary resource, we do not support requesting a scope for it. Instead, access is governed by the resource referenced in the securityContext attribute of the Binary resource (as per FHIR Binary Documentation).
As a result, we are in the process of removing these scopes from the Developer Platform. Previously, requests for these scopes were silently rejected. Moving forward, if these scopes are included in authorization requests, you will encounter the following error:
{
"status": "BAD_REQUEST",
"error_description": "The requested scope is invalid, unknown, malformed, or exceeds that which the client is permitted to request.",
"error": "invalid_scope",
"message": "The requested scope is invalid, unknown, malformed, or exceeds that which the client is permitted to request."
}
Developers are required to update their code to exclude the Appointment, Binary, or Consent scopes in your authorization requests to avoid disruptions.
Updated 14 days ago