Authorized Organization to access the Consent WS. |
Actor(s) | - A doctor working in the authorized organization
|
Requirements | - End-user is a doctor working in the authorized organisation that acts in behalf of a HIO
- The informed patient consent is managed by a recognized authorized organization through its usual software
- Valid eHealth Certificate of the authorized organization
- Consent WS is integrated in the software of the end-user
|
Trigger | The user wants to declare a Patient Consent in the behalf of a HIO |
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 Authorized Organization
- 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 Conditions | - Request is logged
- Informed Patient Consent is stored in the eHealth Database
|
Test Data |
|
Endpoint(s) | - WS Consent
- eHealth Database
|
Remarks | The identification of the Authorized organization is not mandatory in the Author of the request as the Trusted Third Party rule is applied |