-
Created by Unknown User (gaelle.laurent.ext@imec.be), last modified on Mar 25, 2019
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 19
Next »
Basic Flow
Flow | Specifications |
---|
| ID | AR-UC04-BF | Name | Put Patient Consent - Pharmacy | Description | A pharmacist who is holder of the pharmacy declares an "Informed Patient Consent" on behalf of the patient by using the WS Consent. The personal eHealth Certificate of the pharmacy is used to access the WS Consent. | Actor(s) | - A pharmacist who is the pharmacy holder
| Requirements | - End-user is a pharmacist who is the pharmacy holder
- End-user is not known in a hub
- Valid eHeatlh Certificate of the pharmacy
- Consent WS is integrated in the software of the end-user
| Trigger | The user wants to declare a Patient Consent on behalf of the patient | Precondition(s) | - 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 the eHealth Certificate of the pharmacy
- 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
- Informed Patient Consent is stored in the eHealth Database
| Test Data |
| Endpoint(s) |
|
|
Alternative flow
Flow | Specifications |
---|
| ID | AR-UC04-AF01 | Name | Put Patient Consent - Pharmacy end-user is not the pharmacy holder | Description | A pharmacist who is holder of the pharmacy declares an "Informed Patient Consent" on behalf of the patient by using the WS Consent. The personal eHealth Certificate of the pharmacy is used to access the Consent WS. | Actor(s) | - A pharmacist who isn't the holder of the pharmacy
| Requirements | - End-user is a pharmacist who isn't the pharmacy holder
- End-user is not known in a hub
- Valid eHeatlh Certificate of the pharmacy
- Consent WS is integrated in the software of the end-user
| Trigger | The user wants to declare a Patient Consent on behalf of the patient | Precondition(s) | - 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 the eHealth Certificate of the pharmacy
- 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 | Put Patient Consent Request - Request : Identification of the end-user: SSIN number, NIHII number if available, professional category | Post conditions | - Request is logged
- Informed Patient Consent is stored in the eHealth Database
| Test Data |
| Endpoint(s) |
|
|