Used Documentation

Cookbook	Version	Location
MetaHub V2 Cookbook	1.9	https://www.ehealth.fgov.be/ehealthplatform/nl/service-verwijzingsrepertorium-hubs-metahub

General Information

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

Specifications

ID	UC-902-BF
Name	Revoke Patient Link - Hub as author of the request
Description	Revoke Patient Link allows a hub to revoke the link between the patient and 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	Authorized end-user through a Hub (mentioned in "Actors") Valid eHealth cerificate of the hub Identification Hub: Hub ID, Organization category, Hub name (optional) Information concerned patient °INSS °INSS support card number (optional)
Trigger	User wants to revoke a Patient 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 Revoke Patient Link The Revoke Patient Link Request is sent to the MetaHub WS The link between the hub and patient is stored within the MetaHub The request is logged The MetaHub WS responds with a Declare Patient Link Response
Post Condition(s)	The request is logged The link between the hub and patient is revoked within the MetaHub
Test Data	Example Revoke Patient Link Request Example Successful Revoke Patient Link response Example Unsuccessful Revoke Patient Link Response
End point(s)	WS MetaHub
Additional Information	If the link between the patient and hub is revoked then it will no be returned anymore by the method Get Patient Links If provided INSS and support card number are not submitted to status validation (Hub Third trusted party)
Comments	A link between a patient and a hub indicates that at least a transaction is declared within the hub about the patient. The revocation should be performed when there is no more transaction available within the hub about the patient. A patient link can be revoked before the registration of a patient’s consent. It is only possible to revoke a patient link for the hub that sends the request. The hub is identified in the sender of the request and the coherence is checked with the technical identification and authentication system

Exception Flow