-
Created by Unknown User (gaelle.laurent.ext@imec.be), last modified on May 02, 2019
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 29
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.
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-UC02-BF | Name | Put Patient Consent - Patient through portal of a hub | Description | Patient acts as author of the Informed Patient Consent Request through the portal of a Hub. Certificate used to access the MetaHub WS is the eHealth Certificate of the Hub. | Actor(s) | - Patient through the portal a hub
| Requirements | - End-user is a patient
- Patient manages his consent through a portal provided by one of the hubs
- Valid eHealth certificate of the Hub
- Identification of the Hub: Hub ID, Organization category, Name (optional)
- Identification end-user: SSIN number patient
- Information consent:
°Patient SSIN °Patient SSIN Support card number (optional) °Date of registration of consent by patient °Type of consent: retrospective | Trigger | The user wants to declare a Patient Consent on behalf of the patient | 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 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) | Additional Information | Additional information of the hub as name is optional. If provided, it will be used for audit purposes. |
|
Flow | Specifications |
---|
| ID | AR-UC02-AF01 | Name | Put Patient Consent - Parent of patient through portal of a hub | Description | Parent of concerned patient acts as author of the Informed Patient Consent Request through the portal of a Hub. Certificate used to access the MetaHub WS is the eHealth Certificate of the Hub. | Actor(s) | - Parent of the concerned patient through the portal a hub
| Requirements | - End-user is the parent of the concerned patient
- Parent of patient manages the consent through a portal provided by one of the hubs
- Valid eHealth certificate of the Hub
- Identification of the Hub: Hub ID, Organization category, Name (optional)
- Identification end-user: SSIN number parent of patient
- Information consent:
°Patient SSIN °Patient SSIN Support card number (optional) °Date of registration of consent by patient °Type of consent: retrospective
| Trigger | The user wants to declare a Patient Consent on behalf of the patient | 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 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 | Difference in flow | Identification of end-user → Parent of patient: SSIN number | 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) | Additional Information | Additional information of the hub as name is optional. If provided, it will be used for audit purposes. |
|
Flow | Specifications |
---|
| ID | AR-UC02-AF02 | Name | Put Patient Consent - Mandatary of patient through portal of a hub | Description | Mandatary of concerned patient acts as author of the Informed Patient Consent Request through the portal of a Hub. Certificate used to access the MetaHub WS is the eHealth Certificate of the Hub | Actor(s) | - Parent of the concerned patient through the portal a hub
| Requirements | - End-user is the mandatary of the concerned patient
- Mandatary of patient manages the consent through a portal provided by one of the hubs
- Valid eHealth certificate of the Hub
- Identification of the Hub: Hub ID, Organization category, Name (optional)
- Identification end-user: SSIN number mandatary of patient
- Information consent:
°Patient SSIN °Patient SSIN Support card number (optional) °Date of registration of consent by patient °Type of consent: retrospective
| Trigger | The user wants to declare a Patient Consent on behalf of the patient | 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 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 | Difference in flow | Identification of end-user → Mandatary of patient: SSIN number | Post Condition(s) | - Request is logged
- The informed patient consent is stored in the MetaHub
| Test Data | | End Point(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) | Additional Information | Additional information of the hub as name is optional. If provided, it will be used for audit purposes. |
|