...
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 using the SOA-based version, it is important to use the Token exchange service in order to convert a JWT message into a SAML one (and vice versa). The aim of this use case is to check a consent status after its activation or revoke. | ||
Priority | 1 (High) Must have: The system must implement this goal/ assumption to be accepted. | ||
Pre-Conditions |
| ||
Post-Conditions |
| ||
Steps (basic flow) | 1 | The user tries to consult the consent and the client sends a getPatientConsent request to the IAM connect | |
2 | The IAM connect routes the request to the WS consent | ||
3 | The WS consent finds information about the consent of a patient | ||
4 | The WS consent sends a SAML-based response to the IAM | ||
5 | The IAM connect receives the response and sends it to the client using a JWT format by interacting with the token exchange service | ||
6 | The client receives information about the consent of the patient | ||
Exceptions (exception flows) |
| ||
Frequency |
|
Alternative flow 1
...
Use case ID
...
ATH-UC-12-AF-01
...
Use case name
...
Consult an inactive consent of a patient
...
Actors
...
Citizen
- HC party
...
Short Description
...
In order to consult the consent of a patient,
...
1 (High)
Must have: The system must implement this goal/ assumption to be accepted.
...
Pre-Conditions
...
- The user is logged in
...
Post-Conditions
...
Steps (basic flow)
...
0
...
2
...
4
...
6
...
7
...
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
Alternative flow 2
...
Use case ID
...
ATH-UC-12-AF-02
...
Use case name
...
Unsuccessful completion
...
Actors
...
Citizen
- HC party
...
Short Description
...
In order to consult the consent of a patient,
...
1 (High)
Must have: The system must implement this goal/ assumption to be accepted.
...
Pre-Conditions
...
- The user is logged in
...
Post-Conditions
...
Steps (basic flow)
...
0
...
2
...
4
...
6
...
7
...
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