Page History
...
Together with the calling health service, the consent verification service follows the following decision graph to determine a citizens’ / health professionals access to data:
Figure 1 (In Danish) State diagram for initial decision on granting access to health care information about at citizen.
...
For health professionals, the following decision graph is used to verify consents:
Figure 2 State diagram for consent verification steps when granting access for a health care professional to health care information about a citizen. References in parenthesis refer to [Sundhedsloven].
...
Import of SOR data to the master database is handled by an external importer component, not as part of this service.
Figure 3 Deployment of Consent Services.
...
The general service structure is that the service is implemented as a stateless session bean that implements a Web interface that is a Java Web service.
This bean then handles the service logic, DAOs and other business logic.
Security validation, logging and error handling is handled by a number of Java EE interceptors.
...
Every interceptor is annotated with @AroundInvoke, which means that they are called before the service methods are invoked.
SLA logging
SLA log-interceptor is responsible for SLA logging of all service calls.
...
Lookups are performed in the SOR database to sort organization-specific consents correctly.
If user or data verification is performed, then the general consent verification logic will subsequently be performed in the abstract class ServiceLogicHandler that has been implemented by two concrete classes: a class for user verification and a class for data verification. Filtration of consents, order of consent verification, and handling of positive/negative/data specific consents, are identical for both the concrete classes.
General service verification
...