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-805-BF
Name	Get Patient Audit Trail - Hub - All criteria
Description	Get Patient Audit Trail allows a hub to audit the MetaHub operations on a given patient (audit list of consent, exclusions and link operations) for a certain period. All criteria in input.
Actor(s)	Hub
Requirements	Identification of the hub: Hub ID, Organization category, Hub name (optional) INSS patient Period (Begin-End) Operation list Completion status (all, success, failed) Maximum number of allowed results
Trigger	User wants to Get Patient Audit Trail
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 Get Patient Audit Trail The Get Patient Audit Trail Request is sent to the MetaHub WS The list of recorded audit elements that fulfill the provided criteria The request is logged ° The MetaHub WS responds with a Get Patient Audit Trail Response
Post Condition(s)	The request is logged The list of recorded audit elements that fulfill the provided criteria °The audit element is related to the patient °The occurrence time is contained in the period (Begin-End) °The requested operation °The completion status of the requested operations
Test Data	Example Get Patient Audit Trail Request Example Successful Get Patient Audit Trail Response with audit result Example Successful Get Patient Audit Trail Response without audit result Example Unsuccessful Get Patient Audit Trail Response
End point(s)	WS MetaHub
Remarks	if there is no audit element that fulfills the provided criteria, the returned list is empty. only successful Put (Declare) and Revoke operations audit are returned. Failed operations are not returned the successful or failed Get operations are not returned if the maximum number of allowed results is exceeded, the service returns the more recent access audits that fulfill the provided criteria. Completion status: if omitted, the status is by default 'success'
Comments	The availability of the audit elements throughout the service is limited in time. The hub can always contact eHealth Platform in order to retrieve the archived access audits.

Page tree

UC-805-MH-Get Patient Audit Trail-All criteria

Used Documentation

General Information

KMEHR

Basic Flow