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. The personal eHealth Certificate of the physician is used to log inaccess the Consent WS. |
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 access 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 |
Difference in flow | Put Patient Consent - Consent : Patient SSIN support card NOT mandatory |
Post conditions | - Request is logged
- The informed patient consent is stored in the eHealth Database
|
Test Data |
|
Endpoint(s) |
|