| ID | AR-UC06-AF02 |
| Name | Put Patient Consent - Mandatary of Patient |
| Description | Mandatary of the patient declares an "Informed Patient Consent" in behalf of the patient by using the WS Consent. The Certificate from the eID of the mandatary is used to access to the WS Consent |
| Actor(s) | Mandatary of the concerned patient |
| Requirements | - End-user is a mandatary of the concerned patient
- End-user acts as author of the request through his software and manages himself throughout his usual software
- Valid eID of the mandatary
- Consent WS is integrated in the software of the end-user
|
| Trigger | The user wants to declare his Patient Consent |
| Preconditions | - The user has an account for the application
- The user is logged out
|
| Flow | - The user attempts to access the eHealth Consent WS
- The user needs to request a SAML Token by using his eID
- A request for a SAML Token is sent to the Secure Token Service (STS)
- The STS responds with a SAML Token
- The user has access to the eHealth WS Consent
- The user does a request for Put Patient Consent
- The Put Patient Consent Request is sent to the WS Consent
- ° The WS Consent responds with a Put Patient Consent Response
° The request is logged ° The Informed Patient Consent is stored in eHealth Database |
| Difference in flow | Identification of the Mandatary |
| Post Conditions | - Request is logged
- The informed patient consent is stored in the eHealth Database
|
| Test Data |
|
| End point(s) | - WS Consent
- eHealth Database
|
| Remarks | If support card number is provided then it must be compliant e.g. correct format, check-digit and combination |
| Additional Information | Additional information about mandatary e.g. first name and family name may be added for the audit purpose |