THIS SPACE IS UNDER CONSTRUCTION

  • Created by Unknown User (gaelle.laurent.ext@imec.be), last modified on Sept 25, 2019

Used Documentation

CookbookVersionLocation
MetaHub V2 Cookbook1.9https://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.


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.

Basic Flow

FlowSpecifications

IDUC-1004-BF
NameGet Metahub Delta - Hub as author of the request - Patienthublinks
DescriptionGet MetaHub Delta allows a hub to obtain all requests that have been registered in the metahub regarding consents, exclusions and/or hub hub-patient link data, for a certain period.
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)
  • Period: begin & end
  • Delta type: Patienthublinks
TriggerUser wants to Get MetaHub Delta
Precondition(s)
  • The user has an account for the application
  • The user is logged out
Flow
  1. The user attempts to access to the eHealth MetaHub WS
  2. The user needs to request a SAML Token by using the eHealth Certificate of the Hub
  3. A request for a SAML Token is sent to the Secure Token Service (STS)
  4. The STS responds with a SAML Token
  5. The user has access to the eHealth WS MetaHub
  6. The user does a request for Get MetaHub Delta
  7. The Get MetaHub Delta Request is sent to the MetaHub WS
  8. The list of recorded delta elements that fulfill the provided criteria
  9. The request is logged 
  10. The MetaHub WS responds with a Get MetaHub Delta Response
Post Condition(s)
  • The request is logged 
  • The list of recorded delta elements that fulfill the provided criteria

      °The occurrence time is contained in the period (Begin-End) 

      °Type of Delta element corresponds to timeperiod

Test Data
End point(s)WS MetaHub
Additional Information
  • If the end of the interval is not provided, the interval is considered to be (Begin-Present Date Time)
  • We strongly recommend minimizing the period by using the request criteria ‘begindate’,’ begintime’, ‘enddate’ and ‘endtime’. Indeed, the maximum of the records returned in the result set by the service is currently 1500. A ‘Warning' is returned when there are more results than supported by the service.
RemarksIf there is no delta element that fulfills the provided criteria, the returned list is empty.
Comments
  • Due to technical limitations, the availability of the delta elements throughout the service is limited in time. The size of the response is also limited.
  • The hubs are expected to update their systems with the metahub deltas once in a certain period, as to assure to their patients that their application information is up to date.
  • No labels

THIS SPACE IS UNDER CONSTRUCTION