THIS SPACE IS UNDER CONSTRUCTION

  • Created by Unknown User (gaelle.laurent.ext@imec.be), last modified on Sept 25, 2019
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.


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.

Basic Flow

FlowSpecifications

IDUC-703-BF
NameGet Therapeutic Exclusion - Hub as author of the request
DescriptionGet Therapeutic Exclusion allows a hub to retrieve a patient's exclusion list and to check the existence of an exclusion between a patient and a healthcare party
Actor(s)Hub
Requirements
  • User through a Hub (mentioned in "Actors")
  • Valid eHealth cerificate of the hub
  • Information hub: Hub id - organization category, Hub name (optional)
  • Information concerned patient: INSS - Support card number (optional)
TriggerThe end-user wants to Get a Therapeutic Exclusion
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 Therapeutic Exclusion 
  7. The Get Therapeutic Exclusion  Request is sent to the MetaHub WS
  8. List of exclusions that fulfills the provided criteria is returned
  9. The request is logged
  10. The MetaHub WS responds with a Get Therapeutic Exclusion  Response
Post Condition(s)
  • The request is logged 
  • The list of exclusions that fulfill the provided criteria: all the therapeutic exclusions related to the concerned patient
Test Data
End point(s)WS MetaHub
RemarksOnly following HC parties can be excluded: Physician, Nurse, Dentist, Midwife, Audician, Physiotherapist, Occupational therapist, Practical nurse, Dietician, Audiologist, Podologist, Truss maker, Logopedist, Orthopedist, Lab technologist, Imaging technologist 
Additional Information
  • If the provided INSS of the excluded HC party does not correspond to the provided category professional, the exclusion is considered as not found thus not returned. 
  • First and last name if not provided then they are enriched based on provided INSS and category professional
  • No labels

THIS SPACE IS UNDER CONSTRUCTION