| Flow | Specification |
|---|
| Use case ID | ATH-UC-12-BF |
Use case name | Consult an active consent of a patient |
Actors | |
Short Description | In order to consult the consent of a patient, |
| Priority | 1 (High) Must have: The system must implement this goal/ assumption to be accepted. |
Pre-Conditions | - The user is already logged in
- The user needs to request a SAML Token by using his eID
- A request for a SAML Token is sent to the Secure Token Service (STS)
- The STS responds with a SAML Token
- Information about the request (request identifier, end-user identifier, date and time of the request)
- SSIN of the concerned patient
- Type of the consent (optional)
|
Post-Conditions | Information about the response (response identifier, end-user identifier, data and time of the response, initial request) - An acknowledgement (status of the completion, errors if exist)
- Information about the consent (SSIN of the patient, consent type, data of declaration, author of the declaration)Information about the
|
Steps (basic flow) | 0 |
|
| 1 |
|
| 2 |
|
| 3 |
|
| 4 |
|
| 5 |
|
| 6 |
|
| 7 |
|
| 8 |
|
| 9 |
|
| 10 |
|
| 11 |
|
Exceptions (exception flows) | - Invalid or incorrect data:
- Invalid transaction identifier.
- Invalid request sender.
- Invalid healthcare party identifier.
- Invalid patient identifier (invalid SSIN, eID, SIS numbers).
- Invalid consent type.
|
Frequency | - Every time the user wants to consult the consent of a given patient
|