“If a SMART on FHIR server supports a custom behavior like allowing users to choose their own profile photos through a custom non-FHIR API, it can designate a custom scope using a full URL (e.g., https://ehr.example.org/scopes/profilePhoto.manage) or by using a "" prefix (e.g., profilePhoto.manage)”
example - if we wanted to assign a specific scope to permit access to the NHIPatient custom operation set-preferred-name
we could define a scope called Patient.__set-preferred-name
Summary
Use a "__" prefix before the custom operation name when it is necessary to assign a specific scope to a custom operation
From SMART
“If a SMART on FHIR server supports a custom behavior like allowing users to choose their own profile photos through a custom non-FHIR API, it can designate a custom scope using a full URL (e.g., https://ehr.example.org/scopes/profilePhoto.manage) or by using a "" prefix (e.g., profilePhoto.manage)”
example - if we wanted to assign a specific scope to permit access to the NHIPatient custom operation
set-preferred-name
we could define a scope called
Patient.__set-preferred-name
Drawbacks
none identified
Which area of the standards does this apply to?