...
The API eHealth Therapeutic Exclusion provides five methods. It is noteworthy that in this use case only the Get therapeutic exclusion method is used.
Basic flow
Flow | Specification | ||
---|---|---|---|
Use case ID | ATH-UC-19-BF | ||
Use case name | Consult the therapeutic exclusions of a patient using the GET /therapeuticExclusions/{patientSsin} operation | ||
Actors |
| ||
Short Description | This use case enables to consult the therapeutic exclusion of a given patient using the GET /therapeuticExclusions/{patientSsin} operation of the REST version of the Therapeutic Exclusion WS. | ||
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 GET /therapeuticExclusions/{patientSsin} 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 JWT response to the IAM | ||
5 | The IAM connect receives the response and sends it to the client | ||
6 | The client receives information about the therapeutic exclusion(s) of the patient | ||
Exceptions (exception flows) | |||
|
...