THIS SPACE IS UNDER CONSTRUCTION

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

Used Documentation

Cookbook / MaterialsVersionLocation
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-505-BF
NameRevoke Patient Consent - Hub as author of the request
DescriptionHub acts as author of the Revoke patient consent. The hub does the request. Certificate used to access the MetaHub WS is the eHealth Certificate of the 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)
  • Identification end-user
  • Information consent: 

         °Patient SSIN

         °Patient SSIN Support card number (optional)

         °Date of revocation

TriggerThe end-user wants to revoke a Patient Consent
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 Consent 
  7. The Revoke Patient Consent Request is sent to the MetaHub WS
  8. The Informed Patient Consent is revoked in the MetaHub
  9. The request is logged 
  10. The MetaHub WS responds with a Revoke Patient Consent Response 
Post Condition(s)
  • Request is logged
  • The informed patient consent is revoked in the MetaHub
Test Data
End point(s)MetaHub WS
Additional InformationPatient SSIN 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

Alternative Flow

FlowSpecifications

IDUC-505-AF01
NameRevoke Patient Consent - Hub as author of the request - End-user in a hospital
DescriptionAn authorized end-user in a hospital does the revoke patient request through the Hub.  The hub does the request. Certificate used to access the MetaHub WS is the eHealth Certificate of the Hub. 
Actor(s)
  • Professional of AR78 in a hospital ( Physician, Dentist, Nurse, Midwife) through a hub
  • Administrative in a hospital through a hub
Requirements
  • Authorized end-user through a Hub (mentioned in "Actors")
  • Identification Hub: Hub ID, Organization category, Hub name (optional)
  • Identification end-user
  • Information consent: 

         °Patient SSIN

         °Patient SSIN Support card number (optional)

         °Date of revocation


TriggerThe end-user wants to revoke a Patient Consent
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 Consent 
  7. The Revoke Patient Consent Request is sent to the MetaHub WS
  8. The Informed Patient Consent is revoked in the MetaHub
  9. The request is logged 
  10. The MetaHub WS responds with a Revoke Patient Consent Response 
Post Condition(s)
  • Request is logged
  • The informed patient consent is revoked in the MetaHub
Test Data
End point(s)MetaHub WS
Additional InformationPatient SSIN 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

Exception Flow

FlowSpecifications

IDUC-505-EF
NameRevoke Patient Consent - Hub as author of the request - No active consent for the concerned patient
DescriptionHub acts as author of the Revoke patient consent. The hub does the request. Certificate used to access the MetaHub WS is the eHealth Certificate of the Hub.  No active consent for the concerned 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")
  • Identification Hub: Hub ID, Organization category, Hub name (optional)
  • Identification end-user
  • Information consent: 

         °Patient SSIN

         °Patient SSIN Support card number (optional)

         °Date of revocation

  • No active consent for the concerned patient
Trigger

The end-user wants to revoke a Patient Consent

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 Consent 
  7. The Revoke Patient Consent Request is sent to the MetaHub WS
  8. The MetaHub WS responds with a Revoke Patient Consent Response: error message
Post Condition(s)
  • Request is logged
  • The informed patient consent is revoked in the MetaHub
Test Data
End point(s)MetaHub WS
  • No labels

THIS SPACE IS UNDER CONSTRUCTION