-
Created by Unknown User (gaelle.laurent.ext@imec.be), last modified on Apr 19, 2019
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 5
Next »
Basic Flow
| Flow | Specifications |
|---|
| | ID | AR-UC23-BF | | Name | Put Therapeutic Link - Patient - Patient management | | Description | Put Therapeutic Link, service used to declare a therapeutic link between a patient and a HC party. Patient acts as author of the Therapeutic Link. | | Actor(s) | Patient | | Requirements | - End-user is mandatary of the concerned patient
- End-user manages the therapeutic links throughout his usual software
- e-ID of the patient
- Patient software information
| | Trigger | The user wants to put a therapeutic link | | Precondition(s) | - The user has an account for the application
- The user is logged out
| | Flow | - The user attempts to access the eHealth WS Therapeutic Link
- The user needs to request a SAML Token by using it's e-ID
- 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 Therapeutic Link
- The user does a request for Put Therapeutic Link
- The Put Therapeutic Link Request is sent to the WS Therapeutic Link
- ° The WS Consent responds with a Therapeutic Link Response
° The request is logged ° The Therapeutic link is created in eHealth Database | | Post Condition(s) | - Request is logged
- The Therapeutic Link is created in eHealth Database
| | Test Data | | | End point(s) | Therapeutic Link Database | | Additional Information | Patient first name and family name may be added for the audit purpose |
|
