(2) Things to take a look at on your side:
1) Your
https://code.cerner.com/developer/smart-on-fhir/apps SMART on FHIR App page...ensure that the User/Patient/System scopes you desire for FHIR Resources are properly configured there
2) Your /token request's response payload will indicate the list of "scopes" that the "access_token" can be used for. Make sure that listing matches, otherwise there is nothing Cerner can do to help you out. To fix with a Provider app, make sure your Redirect Url has the correct list of "scopes" configured. To fix with a System app, make sure your list of "scopes" that is sent to the /token endpoint matches what you have in the
code.cerner.com/developer/smart-on-fhir/apps page for your application.
If you've done both of these, and everything on your side has been configured appropriately, then time to enter a Service Record (SR) using the
eservice.cerner.com web portal. I've had scenarios where I was using the FHIR Sandbox/CernerSandbox and changes made to the
code.cerner.com SMART on FHIR App page to my "scopes" had to be MANUALLY applied by Cerner associates (there was no automation to do this within 15 minutes like there is for production applications that do NOT use the Sandbox)
Justin