...
- The "PutTherapeuticExlusion" method allows an end-user to declare a therapeutic exclusion.
- The "RevokeTherapeuticExlusion" method enables an end-user to revoke an active therapeutic exclusion.
- The "j'aiGetTherapeuticExclusion" method allows an end-user to consult the active therapeutic exclusions.
Basic flow
Flow | Specification | ||
---|---|---|---|
Use case ID | ATH-UC-15-BF | ||
Use case name | Consult the therapeutic exclusions of a patient | ||
Actors |
| ||
Short Description | In order to consult the therapeutic exclusions 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). | ||
Priority | 1 (High) Must have: The system must implement this goal/ assumption to be accepted. | ||
Pre-Conditions |
| ||
Post-Conditions |
| ||
Steps (basic flow) | 1 | The client sends a GetTherapeutic-Exclusion request | |
2 | The IAM connect sends the request to the Therapeutic Exclusion WS | ||
3 | The Therapeutic exclusion WS finds information about the therapeutic exclusion(s) of a patient | ||
4 | The Therapeutic link WS 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 therapeutic exclusion(s) of the patient | ||
Exceptions (exception flows) | |||
|