-
Created by Unknown User (gaelle.laurent.ext@imec.be), last modified on May 24, 2019
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 19
Next »
The ‘MetaHub’ component is introduced to support the interconnection between ‘Hubs’. This component is accessible to ‘recognized’ hubs. The word ‘hub’ denotes the kernel of a ‘recognized’ regional or sub regional health network.
The main purpose of the MetaHub is to allow a hub to know where it can find information about a patient outside of its network. More precisely, the MetaHub simply provides the list of hubs that have information about a patient. It is not the MetaHub’s role to know where, within a (sub)regional health network, the information is stored.
The MetaHub is thus more a ‘locator service’ than a ‘routing component’: there are no ‘document’ exchanges transiting throughout the component. MetaHub v2 also allows the hubs to consult and manage the registration of patient consents and exclusions1. A major feature is that the hubs themselves feed the MetaHub. See figure below.
![](/download/attachments/17891394/MetaHub%20overview.PNG?version=1&modificationDate=1556089711394&api=v2)
This service is a ‘KMEHR-based’ WS. We thus strongly recommend consulting the documentation related to the KMEHR normative elements. The KMEHR site aims to offer a central point for the documentation of the KMEHR normative elements.
https://www.ehealth.fgov.be/standards/kmehr/en
The three following generic elements are, in particular, essentials to build the request and the reply of eHealth MetaHub WS.
Flow | Specifications |
---|
| ID | AR-UC132-BF | Name | Revoke Patient Consent - Hub as author of the request | Description | Hub acts as author of the Revoke patient consent. The hub does the request. Certificate used to access the MetaHub WS is the eHealth Certificate of the Hub. | Actor(s) | Authorized end-user through a hub: - Professional of AR78 ( Physician, Dentist, Nurse, Midwife)
- Professional of AR78 in a hospital ( Physician, Dentist, Nurse, Midwife)
- Administrative in a hospital
- Citizen: Patient - Parent of patient - Mandatary of patient
| Requirements | | Trigger | The end-user wants to revoke a Patient Consent | 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 Revoke Patient Consent
- The Revoke Patient Consent Request is sent to the MetaHub WS
- ° The MetaHub WS responds with a Revoke Patient Consent Response
° The request is logged ° The Informed Patient Consent is revoked in the MetaHub | Post Condition(s) | - Request is logged
- The informed patient consent is revoked in the MetaHub
| Test Data | | End point(s) | MetaHub WS | Additional Information | 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) Hub Third Trusted Party |
|
Flow | Specifications |
---|
| ID | AR-UC132-AF01 | Name | Revoke Patient Consent - Hub as author of the request - End-user in a hospital | Description | An authorized end-user in a hospital does the revoke patient request through the Hub. The hub does the request. Certificate used to access the MetaHub WS is the eHealth Certificate of the Hub. | Actor(s) | - Professional of AR78 in a hospital ( Physician, Dentist, Nurse, Midwife) through a hub
- Administrative in a hospital through a hub
| Requirements | | Trigger | The end-user wants to revoke a Patient Consent | 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 Revoke Patient Consent
- The Revoke Patient Consent Request is sent to the MetaHub WS
- ° The MetaHub WS responds with a Revoke Patient Consent Response
° The request is logged ° The Informed Patient Consent is revoked in the MetaHub | Post Condition(s) | - Request is logged
- The informed patient consent is revoked in the MetaHub
| Test Data | | End point(s) | MetaHub WS | Additional Information | 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) Hub Third Trusted Party |
|
Flow | Specifications |
---|
| ID | AR-UC132-EF | Name | Revoke Patient Consent - Hub as author of the request - No active consent for the concerned patient | Description | Hub acts as author of the Revoke patient consent. The hub does the request. Certificate used to access the MetaHub WS is the eHealth Certificate of the Hub. No active consent for the concerned patient | Actor(s) | Authorized end-user through a hub: - Professional of AR78 ( Physician, Dentist, Nurse, Midwife)
- Professional of AR78 in a hospital ( Physician, Dentist, Nurse, Midwife)
- Administrative in a hospital
- Citizen: Patient - Parent of patient - Mandatary of patient
| Requirements | | Trigger | The end-user wants to revoke a Patient Consent | 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 Revoke Patient Consent
- The Revoke Patient Consent Request is sent to the MetaHub WS
- The MetaHub WS responds with a Revoke Patient Consent Response: error message
| Post Condition(s) | - Request is logged
- The informed patient consent is revoked in the MetaHub
| Test Data | | End point(s) | MetaHub WS |
|