Transparency in exporting of local data
In the process of data sharing in the framework from Vitalink, it is important that the user has a clear view about what data is on the Vitalink platform and what data he/she will share via Vitalink with other caregivers and the patient. Not only it is a matter of patient safety, it also has to do with legal responsibility. It is therefore mandatory that the application visualizes to the user which locally edited data will be shared and asks for explicit validation of data sharing. This includes explicitly visualising any removal of central data.
Transparency in importing of central data
When the application imports central data from Vitalink, it needs to visualize to the user which displayed data comes from the shared central source.
This includes explicitly visualising any removal of local data. This is important because users often want to keep control about the data they 'administer' and data that came from other sources. In that sense it is a good practice to clearly show what changes will be made in the local file.
Exhaustive data mapping
Verify that all the data from the central source is visible for the user. This means that no data from the central source should be lost. Even if you show all data that will be exported and all data that will be imported that the mapping of all data is complete.