-
Created by Unknown User (gaelle.laurent.ext@imec.be), last modified on Apr 16, 2019
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 2
Next »
Basic Flow
Flow | Specifications |
---|
| ID | AR-UC71-BF | Name | Revoke Therapeutic Link - Patient - Patient management | Description | Revoke Therapeutic Link, service used to revoke 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 a patient
- End-user manages the therapeutic links throughout his usual software
- e-ID of the patient
| Trigger | The user wants to revoke 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 personal eHealth Certificate
- 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 Revoke Therapeutic Link
- The Revoke Therapeutic Link Request is sent to the WS Therapeutic Link
- ° The WS Consent responds with a Revoke Therapeutic Link Response
° The request is logged ° The given therapeutic link, if found, is revoked in the eHealth Database ° All overlapped period of validity of the same relation are revoked | Post Condition(s) | - The given therapeutic link, if found, is revoked in the eHealth Database
- All overlapped period of validity of the same relation are revoked
| Test Data | | End point(s) | Therapeutic Links Database |
|