Versions Compared

Old Version 14

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

Saved on

compared with

New Version 15

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

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-902-BF
NameRevoke Patient Link - Hub as author of the request
DescriptionRevoke Patient Link allows a hub to revoke the link between the patient and hub.
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)
  • Information concerned patient

      °INSS

      °INSS support card number (optional)

TriggerUser wants to revoke a Patient 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 Revoke Patient Link
  7. The Revoke Patient Link Request is sent to the MetaHub WS
  • ° The MetaHub WS responds with a Revoke Patient Link Response
    1. The
    request is logged       ° The
    1. link between the hub and patient is
    revoked
    1. stored within the MetaHub
    2. The request is logged
    3. The MetaHub WS responds with a Declare Patient Link Response
    Post Condition(s)
    • The request is logged 
    • The link between the hub and patient is revoked within the MetaHub
    Test Data
    End point(s)WS MetaHub
    Additional Information
    • If the link between the patient and hub is revoked then it will no be returned anymore by the method Get Patient Links
    • If provided INSS and support card number are not submitted to status validation (Hub Third trusted party)
    Comments
    • A link between a patient and a hub indicates that at least a transaction is declared
         within the hub about the patient. The revocation should be performed when there is
         no more transaction available within the hub about the patient. A patient link can be
         revoked before the registration of a patient’s consent.
    • It is only possible to revoke a patient link for the hub that sends the request. The hub
          is identified in the sender of the request and the coherence is checked with the
          technical identification and authentication system



    Exception Flow

    FlowSpecifications


    IDUC-902-EF
    NameRevoke Patient Link - Hub as author of the request - No active link between provided hub and patient
    DescriptionRevoke Patient Link allows a hub to revoke the link between the patient and hub. No active link between provided hub and patient
    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
    • Information concerned patient

          °INSS

          °INSS support card number (optional)

    • No active link between provided hub and patient
    TriggerUser wants to revoke a Patient 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 Revoke Patient Link
    7. The Revoke Patient Link Request is sent to the MetaHub WS
    8. The MetaHub WS responds with a Revoke Patient Link Response: error message
    Post Condition(s)Error message
    Test Data
    End point(s)WS MetaHub