-
Created by Unknown User (gaelle.laurent.ext@imec.be), last modified on Mar 26, 2019
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 9
Next »
Basic Flow
Flow | Specifications |
---|
| ID | AR-UC06-BF | Name | Put Patient Consent - Patient | Description | A patient declares his own "Informed Patient Consent" by using the WS Consent. The Certificate from the eID of the patient is used to access to the WS Consent. | Actor(s) | | Requirements | - End-user is a patient
- End-user acts as author of the request through his software and manages himself throughout his usual software
- Valid eID
- Consent WS is integrated in the software of the end-user
| Trigger | The user wants to declare his Patient Consent | Precondition | - 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 | Post Condition(s) | - Request is logged
- The informed patient consent is stored in the eHealth Database
| Test Data |
| End point(s) | WS Consent |
|
Alternative Flow - Parent of patient requests consent
Alternative Flow - Mandatary of patient requests consent