Versions Compared

Old Version 20

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

Saved on

compared with

New Version 21

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 / MaterialsVersionLocation
Consent WS1.9https://www.ehealth.fgov.be/ehealthplatform/nl/service-ehealthconsent
Secure Token Service 1.3https://www.ehealth.fgov.be/ehealthplatform/nl/service-iam-identity-access-management
MetaHub V2 Cookbook1.9https://www.ehealth.fgov.be/ehealthplatform/nl/service-verwijzingsrepertorium-hubs-metahub


General Information

SAML - Secure Token Service

Prior to calling the MetaHub, a SAML token proving that the call comes from a certified hub must be obtained
from the eHealth STS WS. This token is used by MetaHub to validate the received requests (e.g., to verify if the
request comes from a certified hub).

Basic Flow - A hub


FlowSpecification


IDAR-UC03-BF
NamePut Patient Consent - Hub as author of the request
DescriptionHub acts as author of the Informed Patient Consent Request. The hub does the request. Certificate used to access the MetaHub WS is the eHealth Certificate of the Hub. 
Actor(s)
  • Hub
Requirements
  • End-user is the Hub
  • Valid eHealth certificate of the Hub
TriggerThe user wants to declare a Patient Consent on behalf of the patient
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 Consent
  6. The user does a request for Put Patient Consent 
  7. The Put Patient Consent Request is sent to the MetaHub WS
  8. ° The MetaHub WS responds with a Put Patient Consent Response

      ° The request is logged 

      ° The Informed Patient Consent is stored in the MetaHub

Post condition(s)
  • Request is logged
  • The informed patient consent is stored in the MetaHub
Test Data 
Endpoint(s)
  • MetaHub WS
Remarks *Patient 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)



Alternative Flow :  The patient himself via the hub 

Alternative Flow : Professional of AR78 (via the hub)

FlowSpecifications


ID
Name
Description
ActorsPhysician - Dentist - Nurse - Midwife - Pharmacy 
Requirements
Trigger
Preconditions
Flow
Post Conditions
Test Data
Endpoint(s)



Alternative Flow : Professional in a hospital (via the hub) Physician - Dentist - Nurse - Midwife - Pharmacy

Alternative Flow : An Administrative Assistant in a hospital (via the hub)