Skip to content

Consent Management App

The Consent Management App (CMA) is an application that gives data owners visibility and control over who accesses their data. It consists of a mobile frontend and a backend service that together form a single logical application.

The CMA is described here in conceptual terms. The current implementation is a prototype; the application will be fully redesigned in a future iteration.

Purpose

The CMA allows a data owner to:

  • View which providers hold their data.
  • Review pending data access requests from consumers.
  • Grant or revoke consent for specific studies or providers.

Architecture (conceptual)

The mobile frontend provides the user interface for the data owner. It communicates with the CMA backend, which abstracts the complexity of the dataspace from the mobile client.

The CMA backend interacts with:

  • FC-Service to retrieve the list of registered providers.
  • RUN-DSP (consumer role) to query available studies and datasets from providers.

In scenarios where data owner consent is required, the RUN-DSP contract hook can gate a transfer on the consent state held by the CMA backend. If the data owner has not granted consent, the contract negotiation does not proceed to agreement.

The current r-squared demo scenario does not use the CMA — it runs without data owner consent. Future demo scenarios will integrate the CMA to demonstrate the full consent flow.