Used Documentation

MetaHub

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.

KMEHR

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.

• cd : This is the key element used to code information: this section is completely based on the description from the KMEHR standard, as can be found on: https://www.ehealth.fgov.be/standards/kmehr/en/page/key-elements#cd 

• id: This element is used to uniquely identify key elements like request, response of the WS, patient, HCParty. It can also be used to specify any unique identifier: this section is completely based on the description from the KMEHR standard, as can be found on: https://www.ehealth.fgov.be/standards/kmehr/en/page/key-elements#id 

• HC Party: The hcparty element is a generic element that aims to represent any kind of healthcare party: organization, physician, medical specialty, or even IT systems: this section is entirely based on the description from the KMEHR standard, as can be found on: https://www.ehealth.fgov.be/standards/kmehr/en/page/hcparty 

Basic Flow

Flow	Specification
	ID

AR

UC-

UC01

501-BF Name Put Patient Consent - Hub as author of the request Description Hub acts as author of the Informed Patient Consent Request. The hub does the request. Certificate used to access the MetaHub WS is the eHealth Certificate of the Hub.  Actor(s) Hub Requirements End-user is

the Hub

a Hub (Hub acts as author of the request) Valid eHealth certificate of the Hub Identification of the Hub: Hub ID, organization category, Name (optional) Information consent :        °Patient SSIN        °Patient SSIN Support card number (optional)       °Date of registration consent by the 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

Consent      °

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 Informed Patient Consent is stored in the MetaHub

The request is logged

      ° The Informed Patient Consent is stored in the MetaHub

The MetaHub WS responds with a Put Patient Consent Response Post condition(s) Request is logged The informed patient consent is stored in the MetaHub Test Data  Example Request Hub Example DeclarePatientConsentRequest Example Succesful DeclarePatientConsentResponse Endpoint(s) MetaHub WS 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) Hub Third Trusted Party Additional Information Additional information of the hub as name is optional. If provided, it will be used for audit purposes.

Exception Flow