Recip-e is the Belgian electronic prescription format. As the usecase use case for elderly care institutions is different as from the one for ambulatory patients, a specific flow has been defined as on . See the scheme below.diagram below for more explanation.
The presentation from 17/08/2017 can be downloaded here: Recip-e flow resthomes.pdf
- The elderly care institution sends the prescriptionrequests via eHealthbox to the medical doctor
- If the doctor validates the prescription, he sends the request to Recip-e
- Recip-e sends a RID (Recip-e ID) to the doctor
- If the prescription has been validated, the doctor sends a prescriptionvalidation prescription validation to the elderly care institution. If it is refuseddenied, the doctor sends a prescriptiondenial prescription denial (with a reason why).
- The elderly care institution sends the Orderlink to the pharmacy via eHealthBox. Here for For this reason the Orderlink has been modified. The RID has been added, among other things (see modification in version 1.6)
- The pharmacy checks if the RID exists on Recip-e
- The RID is marked as delivered
- The medication is delivered (or added the to the robot)
PS. The red arrows are send represent data sent via eHealthbox
Remarques Remarks and special usecases:
- The description for the prescriptionrequest can be found here.
- The description for the prescriptionacceptation can be found here.
- The description for the prescriptiondenial can be found here.
- The description for the prescriptionerror can be found here.
- In this flow now no paper is needed anymore, not even the "prove proof of electronic prescription". All parties just need the RID, which will be shared in the different files form described this flow.
- Officially the paper prescription isn't allowed anymore from as of 1/1/2018. But in the case of elderly care institutions the paper flow will still be accepted for a short period in 2018, so all software vendors have enough time to integrate this digital flow. This period has not been defined yet. This means that when starting this project a mixed situation where some doctors will already be able to prescribe electronic and some not has won't to be foreseen.
- When starting a new medication, the elderly care institution will have to add it in his its software and send the prescription request to the doctor. It is not allowed to start the flow from the medical software. This is done so because the formulary from the elderly care institution and the pharmacy are aligned, which is not the case for the doctor.
- The doctor can only accept or refuse the prescription. Modification is not allowed. If this is needed, he wil have to refuse is it and mention that he wants a modification. A new request has then to be send sent to the doctor, after the modification was treated in the elderly care institution.
- When it a prescription is refused the reason why is mandatory.
- If there is an structural error with the request, a prescription error file has to be sendsent, where the reason why is also mandatory.
- On a normal base an order without RID should not be allowed, only when if urgent. In that case the RID has to be send sent in the next Orderlink. See description Orderlink 1.6
- If the medicationschemes medication schedules are managed in the pharmacy, the same flow has to be implemented starting from the pharmacysoftware pharmacy software and sending prescription requests directly to the doctors.
- Preferential Preferably every prescription is for only one medication, however more is are allowed.
- Every prescription and their validation/refusal is send sent as 1 attachment in 1 eHealthBox message. (ex. 5 prescriptions = 5 messages)
- In order to provide a full view of the medicationscheme medication schedule for the doctor, a scheme schedule in pdf has to be added to the prescriptionrequestprescription request.
- Medical software is vendors are asked to provide a mobile functionality to validate the prescription. But this will take some time to be the case for all softwaressoftware packages.