-
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 29
Next »
Basic Flow
| Flow | Specifications |
|---|
| | ID | AR-UC10-BF | | Name | Put Patient Consent - Authorized organization in behalf of HIO - Doctor | | Description | A doctor working in the authorized organization that acts in behalf of a Health Insurance Organization (HIO) declares an Informed Patient Consent on behalf of the patient. Using the eHealth Certificate of the 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 |
|
Alternative Flow
| Flow | Specifications |
|---|
| | ID | AR-UC10-AF01 | | Name | Put Patient Consent - Authorized organization in behalf of HIO - Administrative | | Description | An administrative working under the responsibility of a doctor in the authorized organization that acts in behalf of a Health Insurance Organization (HIO) declares an Informed Patient Consent. Using the eHealth Certificate of the Authorized Organization to access the Consent WS. | | Actor(s) | - An administrative working in the Authorized Organization under the responsibility of a doctor
| | Requirements | - End-user is an administrative working in the Authorized Organization under the responsibility of a doctor
- 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 | | 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 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 | | Difference in flow | Identification of the end-user --> Identification of the admin: SSIN Number, professional category needs to be added to the request | | 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 |
|
Alternative Flow
| Flow | Specifications |
|---|
| | ID | AR-UC10-AF02 | | Name | Put Patient Consent - Authorized organization in behalf of HIO - Patient | | Description | A patient declares his Informed Patient Consent via an Authorized organization in behalf a HIO. Using the eHealth Certificate of the Authorized Organization to access the Consent WS. | | Actor(s) | | | Requirements | - End-user is a patient
- 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 | | Difference in flow | Identification of the end-user → Identification of HIO → Identification of patient | | Post Conditions | - Request is logged
- Informed Patient Consent is stored in the eHealth Database
| | Test Data |
| | End point(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 |
|