...
Flow | Specification | ||||
---|---|---|---|---|---|
Use case ID | ATH-UC-1214-BF | ||||
Use case name | Consult an active consent the therapeutic links of a patient | ||||
Actors |
| ||||
Short Description | In order to consult the consent therapeutic links 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 | ||||
6The client receives information about the consent of the patient | |||||
Exceptions (exception flows) |
| Frequency | |||
|
...