Versions Compared

Old Version 1

changes.mady.by.user Unknown User (gaelle.laurent.ext@imec.be)

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (gaelle.laurent.ext@imec.be)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Used Documentation

Cookbook / Materials

VersionLocation
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.

Image Added


It is not the task of the MetaHub to store or to manage any data regarding ‘therapeutic links’ nor is it the purpose of the MetaHub to register or verify the therapeutic links.
However, for some types of therapeutic links for which an authentic source is defined and available, the MetaHub will offer a ‘relay’ service to the hubs to check the existence of such a therapeutic link.
Again, the interface of the services is more ‘generic’ (in order to be aligned with the specifications defined at the hub level and to potentially support other kinds of therapeutic links if required). For more information on
the methods to use, please refer to the WS TherapeuticLink cookbook. 


PutTherapeuticLink Allows a hub to declare the therapeutic links. Its main purpose is to allow one to declare a therapeutic link.
RevokeTherapeuticLinkAllows a hub to revoke the therapeutic links. Its main purpose is to allow one to “end” the (declaration of a) therapeutic link.
GetTherapeuticLinkAllows a hub to consult therapeutic links according to basic search parameters.
Its main purpose is to allow one to check the existence of the therapeutic links when executing a consultation process.


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


ID
AR
UC-
UC41
606-BF
NamePut Therapeutic Link - Hub as author of the request -non-referral - Information concerned Health care professional
Description

Hub acts as author of the Put Therapeutic Link Request for a non-referral therapeutic link (information on the concerned HC professional is added). The hub does the request. Certificate used to access the MetaHub WS is the eHealth Certificate of the Hub. Only following HC professional end-users are supported:

Physician, Nurse, Dentist, Midwife, Audician, Physiotherapist, Occupational therapist, Practical nurse, Dietician, Audiologist, Podologist, Truss maker, Logopedist, Orthopedist, Lab technologist, Imaging technologist

Actor(s)Health care professional through a Hub (Physician, Nurse, Dentist, Midwife, Audician, Physiotherapist, Occupational therapist, Practical nurse, Dietician, Audiologist, Podologist, Truss maker, Logopedist, Orthopedist, Lab technologist, Imaging technologist)
Requirements
  • End-user does the request through a Hub (Hub acts as author of the request)
  • End-user only following HC professionals: Physician, Nurse, Dentist, Midwife, Audician, Physiotherapist, Occupational therapist, Practical nurse, Dietician, Audiologist, Podologist, Truss maker, Logopedist, Orthopedist, Lab technologist, Imaging technologist
  • Valid eHealth certificate of the Hub
  • SSIN of the patient
    • Identification Hub: Hub ID, Organization category, Hub name (optional)
    • Identification HC professional end-user: INSS, NIHII (if available), HC professional category
    • Criteria relative to Therapeutic Link

          °Information concerned patient: INSS

          °Therapeutic Link type: non-referral

          °Period of validity: 15 months

    • Information concerned HC Professional

          °SSIN number or NIHII (if available)

          °HC professional category

          °First and last name (optional)

    TriggerThe user wants to declare a Therapeutic Link
    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 Put Therapeutic Link
    7. The Put Therapeutic Link Request is sent to the MetaHub WS
    8. The Therapeutic Link is created in the MetaHub
    9. The request is logged 
    10. The MetaHub WS responds with a Put Therapeutic Link Response
    Post Condition(s)
    • Request is logged
    • The therapeutic link is created in the MetaHub Database
    Test Data
    End point(s)WS MetaHub Database



    Exception Flow 1

  • Information on the concerned HC professional: INSS, NIHII (if available)
    • FlowSpecifications


    IDUC-606-EF01
    NamePut Therapeutic Link - Hub as author of the request -non-referral - Information concerned Health care professional - The HC party performing the declaration does not belong to the same category as the HC party concerned by the therapeutic link
    Description

    Hub acts as author of the Put Therapeutic Link Request for a non-referral therapeutic link (information on the concerned HC professional is added). The hub does the request. Certificate used to access the MetaHub WS is the eHealth Certificate of the Hub. Only following HC professional end-users are supported:

    Physician, Nurse, Dentist, Midwife, Audician, Physiotherapist, Occupational therapist, Practical nurse, Dietician, Audiologist, Podologist, Truss maker, Logopedist, Orthopedist, Lab technologist, Imaging technologist. The HC party performing the declaration does not belong to the same category as the HC party concerned by the therapeutic link

    Actor(s)Health care professional through a Hub (Physician, Nurse, Dentist, Midwife, Audician, Physiotherapist, Occupational therapist, Practical nurse, Dietician, Audiologist, Podologist, Truss maker, Logopedist, Orthopedist, Lab technologist, Imaging technologist)
    Requirements
    • End-user does the request through a Hub (Hub acts as author of the request)
    • End-user only following HC professionals: Physician, Nurse, Dentist, Midwife, Audician, Physiotherapist, Occupational therapist, Practical nurse, Dietician, Audiologist, Podologist, Truss maker, Logopedist, Orthopedist, Lab technologist, Imaging technologist
    • Valid eHealth certificate of the Hub
    • Identification Hub: Hub ID, Organization category, Hub name (optional)
    • Identification HC professional end-user: INSS, NIHII (if available), HC professional category
    • Criteria relative to Therapeutic Link

          °Information concerned patient: INSS

          °Therapeutic Link type: non-referral

          °Period of validity: 15 months

    • Information concerned HC Professional

          °SSIN number or NIHII (if available)

          °HC professional category

          °First and last name (optional)

    • The HC party performing the declaration does not belong to the same category as the HC party concerned by the therapeutic link
    TriggerThe user wants to declare a Therapeutic Link
    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 Put Therapeutic Link
    7. The Put
    Patient Consent
    1. Therapeutic Link Request is sent to the MetaHub WS
    °
    1. The MetaHub WS responds with a Put Therapeutic Link Response: error message
    Post Condition(s)Error message
    Test Data
    End point(s)WS MetaHub Database



    Exception Flow 2

    FlowSpecifications


    IDUC-606-EF02

          ° The request is logged 

          ° The Therapeutic Link is created in the MetaHub

    NamePut Therapeutic Link - Hub as author of the request -non-referral - Information concerned Health care professional - A valid therapeutic link of the same tye and for the same HC party already exists
    Description

    Hub acts as author of the Put Therapeutic Link Request for a non-referral therapeutic link (information on the concerned HC professional is added). The hub does the request. Certificate used to access the MetaHub WS is the eHealth Certificate of the Hub. Only following HC professional end-users are supported:

    Physician, Nurse, Dentist, Midwife, Audician, Physiotherapist, Occupational therapist, Practical nurse, Dietician, Audiologist, Podologist, Truss maker, Logopedist, Orthopedist, Lab technologist, Imaging technologist. A valid therapeutic link of the same tye and for the same HC party already exists

    Actor(s)Health care professional through a Hub (Physician, Nurse, Dentist, Midwife, Audician, Physiotherapist, Occupational therapist, Practical nurse, Dietician, Audiologist, Podologist, Truss maker, Logopedist, Orthopedist, Lab technologist, Imaging technologist)
    Requirements
    • End-user does the request through a Hub (Hub acts as author of the request)
    • End-user only following HC professionals: Physician, Nurse, Dentist, Midwife, Audician, Physiotherapist, Occupational therapist, Practical nurse, Dietician, Audiologist, Podologist, Truss maker, Logopedist, Orthopedist, Lab technologist, Imaging technologist
    • Valid eHealth certificate of the Hub
    • Identification Hub: Hub ID, Organization category, Hub name (optional)
    • Identification HC professional end-user: INSS, NIHII (if available), HC professional category
    • Criteria relative to Therapeutic Link

          °Information concerned patient: INSS

          °Therapeutic Link type: non-referral

          °Period of validity: 15 months

    • Information concerned HC Professional

          °SSIN number or NIHII (if available)

          °HC professional category

          °First and last name (optional)

    • A valid therapeutic link of the same tye and for the same HC party already exists
    TriggerThe user wants to declare a Therapeutic Link
    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 Put Therapeutic Link
    7. The Put Therapeutic Link Request is sent to the MetaHub WS
    8. The MetaHub WS responds with a Put Therapeutic Link Response: error message
    Post Condition(s)Error message
    Test Data
    Post Condition(s)
    • Request is logged
    • The therapeutic link is created in the MetaHub Database
    Test Data
    End point(s)WS MetaHub Database