-
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 30
Next »
| Flow | Specifications |
|---|
| | ID | AR-UC08-BF | | Name | Put Patient Consent -Health care professional of AR 78 in a hospital | | Description | A health care professional of AR 78 in a hospital declares an Informed Patient Consent on behalf of the patient by using the WS Consent. The eHealth Certificate of the hospital is used to access the WS Consent. | | Actor(s) | - A health care professional of AR 78 in a hospital (Physician - Nurse - Dentist - Midwife - Pharmacist)
| | Requirements | - End-user is a professional of AR 78 working in a hospital (Physician - Nurse - Dentist - Midwife - Pharmacist)
- Valid eHealth certificate of the hospital
- Consent WS is integrated in the software of the hospital
- The informed patient consent is managed in a recognized hospital throughout its usual software
| | 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 access the eHealth Consent WS
- The user needs to request a SAML Token by using the eHealth Certificate of the hospital
- 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) | - WS Consent
- eHealth Database
| | Remarks | The SSIN and/or NIHII of the doctor end-user are optional for the consultation method. If provided, they must be compliant with SSIN, NIHII validation (check-digit). | | Additional Information | Additional information about the hospital, doctor, software name, address, doctor name, may be added for the audit purpose |
|
Alternative Flow
| Flow | Specifications |
|---|
| | ID | AR-UC08-AF01 | | Name | Put Patient Consent -Administrative working in a hospital | | Description | An administrative working in a hospital under the responsibility of a doctor declares an Informed Patient Consent on behalf of the patient by using the WS Consent. The eHealth Certificate of the hospital is used to access the WS Consent. | | Actor(s) | - An administrative working in a hospital under the responsibility of a doctor
| | Requirements | - Administrative working a hospital under the responsibility of a doctor
- Valid eHealth certificate of the hospital
- Consent WS is integrated in the software of the hospital
- The informed patient consent is managed in a recognized hospital throughout its usual software
| | 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 hospital
- 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 Request - Request: Identification of the admin: SSIN number, the professional category is mandatory | | Post conditions | - Request is logged
- The informed patient consent is stored in the eHealth Database
| | Test Data |
| | Endpoint(s) | - WS Consent
- eHealth Database
| | Remarks | The SSIN and/or NIHII of the responsible doctor and the SSIN of the admin end-user are optional for the consultation method. If provided, they must be compliant with SSIN, NIHII validation (format and check-digit) | | Additional Information | Additional information about the hospital, doctor, administrative e.g. software name, address, doctor name, administrative name may be added for the audit purpose |
|