Used documentation
Cookbook/ materials | Version | Location |
---|---|---|
eHealthConsent WS Cookbook | 1.9 | https://www.ehealth.fgov.be/ehealthplatform/file/view/7cd655bc5f9ec7be387cfbc2d8710b5d?filename=cookbook_ehealthconsent_web_service.pdf |
Jira ticket MHEH-12 | - | MHEH-12 - Getting issue details... STATUS |
Jira ticket MHEH-13 | - | |
Jira ticket MHEH-18 | - |
MHEH-18
-
Getting issue details...
STATUS
|
Jira ticket MHEH-20 | - | MHEH-20 - Getting issue details... STATUS |
Jira ticket MHEH-26 | - | MHEH-26 - Getting issue details... STATUS |
Jira ticket MHEH-31 | - | MHEH-31 - Getting issue details... STATUS |
Jira ticket MHEH-32 | - |
MHEH-32
-
Getting issue details...
STATUS
|
General information
In the figure below, we present a logical view about the relation between the three basic services of the ehealth platform that are the WS Consent, the Therapeutic link WS, and the Therapeutic exclusion services.
The following end users can declare or revoke a patient consent via the WS Consent :
- Management by HCP professionals : Physician, Dentist, Nurse, Midwife
- Management by Patient : Patient, Mandatary or Parent
Consent information will be stored in a eHealth database.
Basic flow
Flow | Specification | ||
---|---|---|---|
Use case ID | ATH-UC-12-BF | ||
Use case name | Consult the consent of a patient | ||
Actors |
| ||
Short Description | In order to change a profile, the user should do a global logout and should authenticate him/herself a second time. | ||
Priority | 1 (High) Must have: The system must implement this goal/ assumption to be accepted. | ||
Pre-Conditions |
| ||
Post-Conditions |
| ||
Steps (basic flow) | 0 | The user has an open session in the IDP with the old profile | |
1 | The user do a global logout in order to close the session in the IDP | ||
2 | The user re-authenticates him/herself via the mobile application in order to change the profile | ||
3 | The mobile application sends an openID connect authorization request to the IAM connect | ||
4 | The IAM connects redirects the message to the eHealth IDP in a browser | ||
5 | The IDP detects that there is not an open session with the NISS and the name of the user | ||
6 | The IDP redirects the request to the CSAM in order to open a session | ||
7 | The user selects the authentication way (i.e. itsme, eID, TOTP) | ||
8 | The user is authenticated and CSAM returns a SAML assertion to the IDP regarding the user | ||
9 | The user selects a new profile and the IDP returns the selected profile to the IAM connect | ||
10 | The IAM connect creates an access token JWT with the new profile and returns it to the clent | ||
11 | The user is authenticated and accesses to the permitted services in the mobile application with respect to the new profile | ||
Exceptions (exception flows) | |||
Frequency |
|