Used documentation
Cookbook/ materials | Version | Location |
---|---|---|
Technical specifications Identity & Authorization Management (I.AM) - Identity Provider (IDP) | 1.0 | https://www.ehealth.fgov.be/ehealthplatform/file/view/91d9a7f7978b8a4e4d90087f83d66883?filename=ehealth_i.am_-_idp_v1.0.pdf |
Issue 22 in JIRA | - | http://jira.ivlab.ilabt.imec.be/projects/MHEH/issues/MHEH-22 |
General information
A user may have one or multiple profiles of the following types:
- Citizen: for the principal with the basic authentication if the user wants to identify himself as a natural person. This is the default profile when a user authenticates on the eHealth IDP.
- Quality: for the principals that identify the user as a professional (eg DOCTOR)
- Organization: for the principals that identify the user as a representative of an organization he belongs to.
- Mandate: for the principals that identify the user as the mandatary of another person or organization from whom he has received a mandate to act on their behalf.
The user choose a profile when he is authenticated and identified in the IDP and the AA.
Basic flow
Flow | Specification | ||
---|---|---|---|
Use case ID | ATH-UC-10-BF | ||
Use case name | |||
Actors |
| ||
Short Description | |||
Priority | 1 (High) Must have: The system must implement this goal/ assumption to be accepted. | ||
Pre-Conditions | |||
Post-Conditions | |||
Steps (basic flow) | 0 | ||
1 | |||
2 | |||
3 | |||
4 | |||
5 | |||
6 | |||
Exceptions (exception flows) | |||
Frequency |