-
Created by Unknown User (gaelle.laurent.ext@imec.be), last modified on Apr 15, 2019
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 2
Next »
| Flow | Specifications |
|---|
| | ID | AR-UC43-BF | | Name | Put Therapeutic Link - Hub as author of the request - Referral - Global Medical File (GMD) | | Description | Hub acts as author of the Put Therapeutic Link Request for a referral therapeutic link. The hub does the request. Certificate used to access the MetaHub WS is the eHealth Certificate of the Hub. Only a Physician as end-user. | | Actor(s) | Health care professional through a Hub | | Requirements | - End-user does the request through a Hub (Hub acts as author of the request)
- End-user only following HC professionals: Physician
- Valid eHealth certificate of the Hub
- SSIN of the patient
- Patient Support card number
- Information on the concerned HC professional: INSS, NIHII (if available)
| | Trigger | The user wants to declare a Therapeutic Link | | 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 MetaHub
- The user does a request for Put Therapeutic Link
- The Put Patient Consent Request is sent to the MetaHub WS
- ° The MetaHub WS responds with a Put Therapeutic Link Response
° The request is logged ° The Therapeutic Link is created in the MetaHub | | Post condition(s) | - Request is logged
- The therapeutic link is created in the MetaHub Database
| | Test Data |
| | End point(s) | WS MetaHub Database | | Remarks | The period of validity of the therapeutic link is optional for GMD |
|