| Situation / Action | Information |
|---|
| 1 | There is no local medication info. Vitalink holds a medication scheme Vx OPTIONAL: Support staff starts preparation of the ambulant visit (eg. for staff meeting of oncology visit with patiënt)
Vitalink medication scheme is imported. |
| 2 | In the hospital people start the preparation of an ambulant visit. Vitalink medication scheme Vx is downloaded. | The EPD requests the latest version of the Vitalink medication scheme. This action can be done manually by a user action,
but is preferably done automatically. Vitalink responds with the same version that is already present in the EPD. The local medication scheme and Vitalink medication scheme | 3 | Local EMR and Vitalink are in sync. |
| 3 - 4 | OPTIONAL: Local medication can be updated in the combined overview during the preparation for Local EMR makes changes to the medication schema (Vx') in preparation of the ambulant visit Vx'. |
| 4 | Preparation OPTIONAL: Preparing of the ambulant visit stops. The local medication scheme is now version 1'. |
| 5 | Start ambulant visit. |
| 6 | In between the preparation phase and the ambulant visit, a newer version Vx+1 is the meantime, a new medication scheme was uploaded to Vitalink (this update is not caused by the hospital!). |
| 6 | Ambulant visit starts. |
| 6 - 7 | During the visit, changes are made to medication in the local EMR until a final local medication scheme (Vx") is produced. |
by another Caregiver. The Vitalink medication scheme is now Version 2. |
| 7 | End ambulant visit. The caregiver made changed to the local medication scheme. The local medication scheme is now Version 1". |
| 8 | The local medication scheme is exported to Vitalink. The export failed because the version of the medication scheme in Vitalink is more recent than the local medication scheme. |
| 9 | 7 - 8 | The medication scheme is uploaded to Vitalink Vx+2.
When uploading, you have a version Vx+1 on VL meanwhile local EMR holds an accent version Vx''. | The local EMR holds the master medication scheme. The local EMR has to provide an interface (= combined overview) in order to show medication changes between | VX en VX+1 Version 1 and Version 2 of the Vitalink medication scheme and the local | version existing. medication scheme Version 1". The caregiver can validate/reject changes. We recommend to show a notification that there is newer version of the medication scheme on Vitalink. |
| 10 | The local medication scheme is now version 2'. |
| 11 | The local medication scheme is exported to Vitalink. | The user has the possibility to continue editing vX" (step 6) with the new updates of Vx+1 or to upload the local medication schema Vx" to Vitalink.The Vitalink medication scheme now becomes Version 3. |
| 12 | Vitalink sends the updated identification code for each medication (URI's) back to the EPD. There are two options: - The EPD adds the URI's in the local medication scheme and updates the version number to Version 3.
- The EPD requests Version 2 of the medication scheme from Vitalink to update the version and URI's in the local medicationscheme.
|
| 13 | The local medication scheme is now Version 3. The local medication scheme and Vitalink medication scheme |
8 | Local EMR medication data and Vitalink are in sync. |
