...
A consent may have two types. Indeed, it is called prospective when it is valuable for data posterior to the signing date (i.e. the date that should be taken into account is the ‘medical date’ of the transaction). It is referred to as retrospective in the opposite case. This does not mean that all documents with a medical date anterior to the signing date of the consent will automatically be made available
The Consent service provides four methods (it is noteworthy that in this use case only the GetPatientConsentStatus method is used):
...
Flow | Specification | ||
---|---|---|---|
Use case ID | ATH-UC-12-BF | ||
Use case name | Consult the consent of a patient using the GetPatientConsentStatus method | ||
Actors |
| ||
Short Description | In order to consult the consent management history of a patient using the SOA-based version, it is important to use the Token exchange service in order to convert a JWT message token into a SAML one (and vice versa). The aim of this use case is to consult the consent management history status. | ||
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 getPatientConsentStatus 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 management history of the patient | ||
Exceptions (exception flows) |
| ||
Frequency |
|
...