-
Created by Unknown User (gaelle.laurent.ext@imec.be), last modified on Mar 20, 2019
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 29
Next »
| Flow | Specifications |
|---|
| | ID | AR-UC01-BF | | Name | Put Patient Consent - Physician not linked to a hospital | | Description | A physician not linked to a hospital (e.g. a general practitioner who has his own practice and isn't known in a Hub) declares an "Informed Patient Consent" on behalf of the patient by using the WS Consent. | | Actor(s) | - A physician not linked to a hospital and not known by a Hub
- A patient that gives his Informed Consent to the healthcare giver
| | Requirements | - End-user is a physician not linked to a hospital (e.g. General Practitioner)
- End-user is not known in a hub
- Valid personal eHeatlh Certificate
- 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 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
| | Postcondition(s) | - Request is logged
- The informed patient consent is stored in the eHealth Database
| | Test Data |
| | Endpoint(s) |
|
|
Alternative Flow
Author of the request is holder of the concerned patient Global Medical File → Difference in Request
| Flow | Specifications |
|---|
| | ID | AR-UC01-AF01 | Name | Put Patient Consent - Physician who is holder of the concerned patient Global Medical File and not linked to a hospital | | Description | A physician who is holder of the concerned patient Global Medical file and is not linked to a hospital declares an "Informed Patient Consent" on behalf of the patient by using the WS Consent. | | Actor(s) | Physician who is holder of the concerned patient Global Medical File | | Requirements | - End-user is a physician not linked to a hospital (e.g. General Practitioner)
- End-user is not known in a hub
- Valid personal eHeatlh Certificate
- Consent WS is integrated in the software of the end-user
- Physician is holder of the patient's Global Medical File
| | 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 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 (difference in request information → no Patient SSIN support card number needed)
- 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
| | Postconditions | - Request is logged
- The informed patient consent is stored in the eHealth Database
| | Test Data |
| | Endpoint(s) |
|
|