-
Created by Unknown User (gaelle.laurent.ext@imec.be), last modified on Mar 21, 2019
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 15
Next »
Basic Flow
| Flow | Specifications |
|---|
| | ID | AR-UC04-BF | | Name |
| | Description |
| | Actor(s) |
| | Requirements |
| | Trigger |
| | Precondition(s) |
| | Flow | - The user attempts to login to the eHealth Consent WS
- The user needs to request a SAML Token by using it's personal eHealth Certificate
- 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) |
| | Test Data |
| | Endpoint(s) |
|
|
Alternative flow: End-user is not the pharmacy holder
