-
Created by Unknown User (gaelle.laurent.ext@imec.be), last modified on Mar 25, 2019
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 16
Next »
SAML - Secure Token Service
Prior to calling the MetaHub, a SAML token proving that the call comes from a certified hub must be obtained
from the eHealth STS WS. This token is used by MetaHub to validate the received requests (e.g., to verify if the
request comes from a certified hub).
Flow | Specification |
---|
| ID | AR-UC03-BF | Name | Put Patient Consent - Hub as author of the request | Description |
| Actor(s) |
| Requirements |
| Trigger |
| Precondition(s) | - The user has an account for the application
- The user is logged out
| Flow | - The user attempts to access to the eHealth MetaHub WS
- The user needs to request a SAML Token by using the eHealth Certificate of the Hub
- 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 MetaHub WS
- ° The MetaHub WS responds with a Put Patient Consent Response
° The request is logged ° The Informed Patient Consent is stored in the MetaHub | Post condition(s) | - Request is logged
- The informed patient consent is stored in the MetaHub
| Test Data |
| Endpoint(s) |
| Remarks * | Patient SSIN Support card number is optional, if provided then the card number is ignored (INSS and support card number are not submitted to status validation) |
|