Page History

OPTIONAL: Support staff starts preparation of the ambulant visit (eg. for staff meeting of oncology visit with patiënt)
Vitalink medication scheme is imported.

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 are in sync.

The local medication scheme is exported to Vitalink.

The Vitalink medication scheme now becomes Version 2.

Vitalink sends the updated identification code for each medication (URI's) back to the EPD.

Here there There are two options:

• The EPD adds the URI's in the local medication scheme and updates the version number to Version 2.
• The EPD requests Version 2 of the medication scheme from Vitalink to update the version and URI's in the local medicationscheme.

The local medication scheme is now Version 2.

The local medication scheme and Vitalink medication scheme are in sync.

OPTIONAL: Support staff starts preparation of the ambulant visit (eg. for staff meeting of oncology visit with patiënt)
Vitalink medication scheme is imported.

There is no data in the local medication scheme so 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.

The local medication scheme is now Version 1.

The local medication scheme and Vitalink medication scheme are in sync.

The local medication scheme is exported to Vitalink.

The Vitalink medication scheme now becomes Version 2.

Vitalink sends the updated identification code for each medication (URI's) back to the EPD.

Here there There are two options:

• The EPD adds the URI's in the local medication scheme and updates the version number to Version 2.
• The EPD requests Version 2 of the medication scheme from Vitalink to update the version and URI's in the local medicationscheme.

The local medication scheme is now Version 2.

The local medication scheme and Vitalink medication scheme are in sync.

OPTIONAL: Support staff starts preparation of the ambulant visit (eg. for staff meeting of oncology visit with patiënt)
Vitalink medication scheme is imported.

There is no data in the local medication scheme so the 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 send the latest version of the medication scheme to the EPD.

The Vitalink medication scheme is imported and updates, changes, etc are shown in a combined overview. The caregiver can validate/reject changes.

The If you have chosen to completely import the Vitalink medication scheme with no regard to the previous local medication scheme (Version 1), the local medication scheme is will now Version 1.The local medication scheme and Vitalink medication scheme are in syncbe Version 2 and is in sync with Vitalink.

If you have chosen to import the Vitalink medication scheme and altered it a bit with date from the previous local medication scheme (Version 1), the local medication scheme will now be Version 2' and is not in sync with Vitalink (because you have already made some changes to it).

The local medication scheme is exported to Vitalink.

The Vitalink medication scheme now becomes Version 23.

Vitalink sends the updated identification code for each medication (URI's) back to the EPD.

Here there There are two options:

• The EPD adds the URI's in the local medication scheme and updates the version number to Version 23.
• The EPD requests Version 2 of the medication scheme from Vitalink to update the version and URI's in the local medicationscheme.

The local medication scheme is now Version 23.

The local medication scheme and Vitalink medication scheme are in sync.