Example calls

Lock/Unlock - This function will be activated in the production environment in June 2026.

The Lock function can be used to temporarily block e-prescriptions from being dispensed. The reason for the lock can be optionally specified. The system can be locked or unlocked by either the pharmacy or the prescribing physician. Please note the different prefix in the “Authorization” header.

WARNING

For data protection reasons, the blocking reason should not contain any personally identifying information.

INFO

Please note the change in the documentation: The reason for blocking is now transmitted as a JSON body instead of as a query parameter.

Lock with indication of the optional reason:

curl --location -X POST 'http://localhost:8082/ePrescription/lock/{erezept_unique_id}' \
--header 'Authorization: Bearer acs:{bearer_token}' \  --pharmacy access
--header 'Authorization: Bearer oauth:{auth_handle}' \ --physicians access
--header 'Content-Type: application/json' \
--data '{"reason":"The dosage needs to be clarified."}'

Unlock with indication of the optional unlocking reason:

curl --location -X POST 'http://localhost:8082/ePrescription/unlock/{erezept_unique_id}' \
--header 'Authorization: Bearer acs:{bearer_token}' \  --pharmacy access
--header 'Authorization: Bearer oauth:{auth_handle}' \ --physicians access
--header 'Content-Type: application/json' \
--data '{"reason":"Successful clarification with the family doctor."}'

If an e-prescription is temporarily blocked, it cannot be dispensed. However, it is still possible for the prescribing doctor to revoke the e-prescription.