This document explains the network infrastructure, messaging patterns and use cases for the Data Sharing Data Model.

Network infrastructure

The HDN Platform provides network access, over which connected actors such as Cleverbase and its customers exchange messages.

For these use cases, the data users do not need a Client Registration at Cleverbase. Instead, the HDN Platform maintains the API connection with Cleverbase services.

Messaging patterns

There are two relevant messaging patterns. One is request-response, exchanged as follows:

CustomerHDN PlatformCleverbaseCustomerHDN PlatformCleverbaseRequest1Request2Response3Response4

The second relevant messaging pattern is notification, exchanged as follows:

CustomerHDN PlatformCleverbaseCustomerHDN PlatformCleverbaseNotification1Notification2

All relevant interactions on the HDN Platform happen in the context of a “dossier”. This needs to be created before the first interaction, and its identifier needs to be provided along with each message.

Use cases

In the following use cases, the technical intermediation by the HDN Platform is not visualized.

Request a connection

Any authorized customer may request a connection for data sharing. The customer needs to have user interaction with HTTP redirection support, for example through a web portal or mobile app.

CustomerCleverbaseCustomerCleverbaseUserConnection URL Request1Connection URL Response2Connection URL3HTTP GET Connection URL4Identification and Consent5Connection Notification6Redirection URL7HTTP GET Callback URL8Consent expiry9User

The customer may provide business intermediation services, requesting a connection for data sharing with multiple service providers. The user consent information represents this intent and its purpose.

Request source data

After connecting, all authorized customers can request source data as follows. They need to provide a key to the connection as part of their request.

CustomerCleverbaseCustomerCleverbaseSource Data Request1Authorization2Source Data Response3