Hi could some help me i try to add user/prescription.read during app registration, but i cant find this in the list of scope either using confidential or public application type.
Based on the documentation found in this link openemr/API_README.md at master · openemr/openemr · GitHub this can be found under api:oemr (user api which are the /api/ endpoints)
Thanks
Casper
Problem you are facing:
You are trying to add user/prescription.read during application registration (confidential or public app) in OpenEMR.
But you don’t see user/prescription.read available in the list of scopes.
You referred to OpenEMR’s API_README.md, which mentions scopes under api:oemr.
Explanation why you face this:
In OpenEMR, the scopes are based on what is registered in the OAuth2 Server (like the API ACL settings).
user/prescription.read is not pre-registered as a scope in the default OpenEMR installation!
Even though /api/prescriptions endpoints exist, you can’t request the user/prescription.read scope unless it is manually added to the OAuth server config.
That’s why it doesn’t show in the UI during app registration.
Solution: How to fix it properly:
You must manually add user/prescription.read to the OAuth2 Server scopes in OpenEMR.
Here’s the step-by-step to fix it:
Login to your OpenEMR admin account (or SSH into the server if needed).
In OpenEMR, scopes are handled by the database in the table:
oauth2_scopes
You can directly insert a new scope entry.
Or through GUI:
Administration → Globals → Connectors → OAuth2 Server → Scopes Management
(depending on your OpenEMR version)
If using SQL directly (for faster fixing):
INSERT INTO oauth2_scopes (scope, description)
VALUES (‘user/prescription.read’, ‘Read access to user prescriptions’);
scope = user/prescription.read
description = whatever you want (example: ‘Read access to user prescriptions’).
This registers the missing scope properly.
Usually not necessary. But if scopes are cached, restart Apache/PHP service:
sudo systemctl restart apache2
sudo systemctl restart httpd
When you create or edit your app registration in OpenEMR (OAuth2 client),
you should now see user/prescription.read available!
You can now request it in your authorization flows.
Summary:
Step
Action
1
Insert user/prescription.read into oauth2_scopes table
2
Confirm it appears in app registration scopes list
3
Use it in your API authorization requests
Use this following steps, It will help you.
Hi i already find the correct scope to display the prescription its " user/MedicationRequest.read " but i also need the write access to update the record of that prescription., when checking the available scope during api registration only the user/MedicationRequest.read is available, But when checking the api documentation user/medication.writeis supported on open emr… is this disable by default?
Thanks
Casper