System Analysis
This is a very high level system analysis and requirements gathering for the prototype.
A Consent Form contains a title, a textual description, the purpose of the consent, who requested it and its state, i.e. accepted, denied, requested and withdrawn. The consent form is stored in the consent file related to the user. A consent form is generated when the company want to use the information gathered for a specific service for another purpose than initially stated. A consent form can be used for the initial purpose also, but is usually seen as an agreement that is done when initially signing up for the service. This solution support both use cases and is a decision the company has to make.
A Consent File is a container for the consents that have been requested from the user. A consent file is created by the system when a user signs up for a service at the company.
A Consent Template contains the generic textual representation of a consent and is used when creating a consent form. Every template has a purpose, title, textual description, version and locale.
An IT-service is any kind of service a company, internal or external to the consortium, wants to provide to the user. The registration by the user for this service is the starting point for the consent handling. By signing up for the IT-service a user is seen to agree to the information gathering and use specific for the IT-service itself. If the company wants to perform other types of information handling that is in addition to or for another purpose than the initial IT-service the company has to ask for consent.
The Consent Service is the service provided by the consortium for the user to view, accept or deny the consents and for the companies, external or internal to the consortium, to administrate, request or check consents.
This list contains a set of use cases supported in the prototype. They are by no means complete or final.