THIS SPACE IS UNDER CONSTRUCTION

Used Documentation

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-702-BF
NameRevoke Therapeutic Exclusion - Hub as author of the request
DescriptionRevoke Therapeutic Exclusion allows a hub to revoke an exclusion patient - HC party
Actor(s)Hub
Requirements
  • User through a Hub (mentioned in "Actors")
  • Valid eHealth cerificate of the hub
  • Identification Hub: Hub ID, Organization category, Hub name (optional)
  • Information about the exclusion: INSS concerned patient, INSS support card number (optional)Information about the excluded HC Party
  • Information about the excluded HC party: 

     °INSS number

     °NIHII number (optional)

     °Professional category

TriggerThe end-user wants to Revoke 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 Revoke Therapeutic Exclusion 
  7. The Revoke Therapeutic Exclusion  Request is sent to the MetaHub WS
  8. The exclusion is revoked in the MetaHub
  9. The request is logged 
  10. The MetaHub WS responds with a Revoke Therapeutic Exclusion  Response
Post Condition(s)
  • The request is logged
  • The exclusion is revoked in the MetaHub with following information: 

      °Target patient

      °Sender

      °Excluded HC Party

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
  • INSS 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))
  • NIHII is optional, if provided then NIHII must be compliant. If not provided then not enriched. Cross validation INSS vs NIHII is not applicable. 
  • 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 revoked
  • First and last name if not provided then they are enriched based on provided INSS and category professional
  • No labels