Versions Compared

Old Version 24

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

Saved on

compared with

New Version 25

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
eHealth Consent WS1.9https://www.ehealth.fgov.be/ehealthplatform/nl/service-ehealthconsent
Secure Token Service1.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

Basic Flow 


FlowSpecifications


IDAR-UC02-BF
NamePut Patient Consent -Health care professional of AR 78 in a hospital 
DescriptionA health care professional of AR 78 in a hospital declares an Informed Patient Consent on behalf of the patient by using the WS Consent. The eHealth Certificate of the hospital is used to log inaccess the WS Consent. 
Actor(s)
  • A health care professional of AR 78 in a hospital (e.g. a physician)
Requirements
  • End-user is a professional of AR 78 working in a hospital
  • Valid eHealth certificate of the hospital
  • Consent WS is integrated in the software of the end-user
TriggerThe user wants to declare a Patient Consent on behalf of the patient
Preconditions
  • The user has an account for the application
  • The user is logged out
Flow
  1. The user attempts to login to access the eHealth Consent WS
  2. The user needs to request a SAML Token by using the eHealth Certificate of the hospital
  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 WS Consent 
  8. ° The WS Consent responds with a Put Patient Consent Response

      ° The request is logged 

      ° The Informed Patient Consent is stored in eHealth Database

Postcondition(s)
  • Request is logged
  • The informed patient consent is stored in the eHealth Database
Test Data
Endpoint(s)



Alternative Flow 


FlowSpecifications


IDAR-UC02-AF01
NamePut Patient Consent -Administrative working in hospital  
Description

An administrative working in a hospital under the responsibility of a doctor declares an Informed Patient Consent on behalf of the patient by using the WS Consent. The eHealth Certificate of the hospital is used to log in. 

Actor(s)
  • An administrative working in a hospital under the responsibility of a doctor
Requirements
  • Administrative working a hospital under the responsibility of a doctor
  • Valid eHealth certificate of the hospital
  • Consent WS is integrated in the software of the end-user
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 login to the eHealth Consent WS
  2. The user needs to request a SAML Token by using the eHealth Certificate of the hospital
  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 WS Consent 
  8. ° The WS Consent responds with a Put Patient Consent Response

      ° The request is logged 

      ° The Informed Patient Consent is stored in eHealth Database

Difference in flowPut Patient Consent Request - Request: Identification of the admin: SSIN number, the professional category is mandatory
Post conditions
  • Request is logged
  • The informed patient consent is stored in the eHealth Database
Test Data
Endpoint(s)