eOverdracht data flow management issue
As mentioned on the Problem definition page, healthcare organizations usually have multiple software providers for different purposes. The data flow management issue arises when trying to transfer data through the Nuts network between organizations whilst at least one of them uses multiple systems (multiple Nuts nodes).
Multiple systems on the sender's side
The following challenges rise when a customer makes use of multiple software systems that own different pieces of patient's data and wants to send data through eOverdracht:
-
The customer usually wants to send all the patient's data in one eOverdracht session instead of starting multiple eOverdrachts in all systems.
-
The customer usually wants to send different combinations of data from different systems depending on what services the patient gets from the customer (e.g. inpatients and outpatients may receive different services, or some of the care patients receive treatment and some of them don't).
Multiple systems on the receiver's side
The Nuts Network is vendor-based. Each vendor's system has its own Nuts Node connected to others within the Network. But customers are used to work in terms of organizations, subdivisions, and locations. So when a customer wants to send patient's data through eOverdracht to another care organization that use software systems of multiple vendors, they face some difficulties.
For example, for the customer it is uncertain to which of the multiple receiver's systems they should send patient's data. Because for them it is not clear what data each of the systems owns. It is also easy in this case to send the data to a wrong system.
Another example is when the customer wants to send data to a specific location or subdivision within the receiver organization. Each location/subdivision may use one or more systems that makes the sending process more complicated.