-
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 33
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. Only the hospital is checked in the rules of access. | Actor(s) | - A health care professional of AR 78 in a hospital
| Requirements | - End-user is a professional of AR 78 working in a hospital
- 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 | - If support card number is provided then it must be compliant e.g. correct format, check-digit and combination
- Support card number is not mandatory if the concerned patient is a new born (0 < patient < 3 months)
| 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 | - If support card number is provided then it must be compliant e.g. correct format, check-digit and combination
- Support card number is not mandatory if the concerned patient is a new born (0 < patient < 3 months)
| 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 |
|