-
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 4
Next »
Basic Flow
| Flow | Specifications |
|---|
| | ID | AR-UC11-BF | | Name | Put Patient Consent - Group of nurses | | Description | A group of nurses declares an Informed Patient Consent on behalf of the patient. Using the eHealth Certificate of the group of nurses to access the Consent WS. | | Actor(s) | - A nurse who is part of the group of nurses
| | Requirements | - End-user is a nurse who is part of the group of nurses
- Valid eHealth Certificate of the Group of nurses
- Consent WS is integrated in the software of the end-user
- The Informed Patient Consent is managed within a group of nurses thru 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 Group of nurses
- 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 Condition(s) | - Request is logged
- Informed Patient Consent is stored in the eHealth Database
| | Test Data |
| | End point(s) | - WS Consent
- eHealth Database
| | Additional Info | Additional information about the software and/or nurse e.g. first name and family name may be added for the audit purpose |
|