-
Created by Unknown User (gaelle.laurent.ext@imec.be), last modified on Mar 27, 2019
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 14
Next »
Basic Flow
| Flow | Specifications |
|---|
| | ID | AR-UC09-BF | | Name | Put Patient Consent - Health Insurance Organisation | | Description | A doctor working in the concerned Health Insurance Organization (HIO) declares an Informed Patient Consent on behalf of the patient. Using the eHealth Certificate of the HIO to access the Consent WS. | | Actor(s) | A doctor working in the concerned HIO | | Requirements | - End-user is a doctor working in the concerned HIO
- Valid eHealth Certificate of the HIO
- 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 HIO
- 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) | - WS Consent
- eHealth Database
|
|
Alternative Flow
| Flow | Specifications |
|---|
| | ID | AR-UC05-AF01 | | Name | Put Patient Consent - Administrative working in Health Insurance Organisation | | Description | An administrative working in the concerned Health Insurance Organization (HIO) under the responsibility of a doctor declares a Informed Patient Consent on behalf of the patient. Using the eHealth Certificate of the HIO to access the Consent WS | | Actor(s) | - An administrative working in a HIO under the responsibility of a doctor
| | Requirements | - End-user is an administrative working in a HIO under the responsibility of a doctor
- Valid eHealth Certificate of the HIO
- 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 | | 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 the eHealth Certificate of the HIO
- 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 end-user: Identification of the admin needs to be present | | Post Condition(s) | - Request is logged
- Informed Patient Consent is stored in the eHealth Database
| | Test Data |
| | End point(s) | - WS Consent
- eHealth Database
|
|