Flow | Specification |
---|
| | ATH-UC-16-BF |
Use case name | Consult the consent of a patient using the GET /consents/{patientSsin} operation |
Actors | |
Short Description |
|
Priority | 1 (High) Must have: The system must implement this goal/ assumption to be accepted. |
Pre-Conditions | - The user is already logged in via the Token exchange service
- 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 | - The SSIN of the concerned patient
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 declarationstatus, the sign date)
|
Steps (basic flow) | 1 |
|
| 2 |
|
| 3 |
|
| 4 |
|
| 5 |
|
| 6 |
|
Exceptions (exception flows) |
|
Frequency | - Every time the user wants to consult the consent of a given patient
|