THIS SPACE IS UNDER CONSTRUCTION

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

Used Documentation

Cookbook / MaterialsVersionLocation
Consent WS1.9https://www.ehealth.fgov.be/ehealthplatform/nl/service-ehealthconsent

General Information

Informed Consent 

The existence of an active ‘informed patient consent’ is one of the fundamental prerequisites for the healthcare providers to access patient’s medical data. Therefore, the eHealth platform makes available to the concerned patients and the health care actors involved in the exchange,

storage or referencing personal data a service to manage the ‘informed patient consent’ as defined by the deliberation 12/047 of the CSSSS/SCSZG1.

Technically, we identify the following attributes for an ‘informed patient consent’:

  • The SSIN of the patient.
  • The date of the consent registration (at the end-user side).
  • The “type” of the consent If the consent is only valuable for data posterior to the signing date, it is called ‘prospective’ and ‘retrospective’ in the other case . According to the rules defined now, the only possible value for this attribute is ‘retrospective’. The attribute is present for backwards compatibility.
  • The identity of the HCParty acting in the patient’s name (if applicable).


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 Consent WS.

Basic Flow

FlowSpecifications

IDUC-129-BF
NameGet Patient Consent - Patient
DescriptionGet Patient consent allows end-users to check the existence and the latest status of the informed patient consent for the concerned patient. Get consent is done by the concerned patient.
Actor(s)A patient
Requirements
  • End-user is a patient
  • End-user acts as author of the request through his software and manages himself throughout his usual software
  • Valid eID
  • Consent WS is integrated in the software of the end-user
  • Identification end-user 

     °Patient Software information

     °Identification patient: SSIN number

  • Criteria relative to the consent

     °INSS patient

     °Support card (optional)

  • Type of consent (optional)
TriggerThe user wants to retrieve the status of the informed consent
Precondition(s)
  • The user has an account for the application
  • The user is logged out
Flow
  1. The user attempts to access the eHealth Consent WS
  2. The user needs to request a SAML Token by using a eHealth Certificate
  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 Get Patient Consent 
  7. The Get Patient Consent Request is sent to the WS Consent 
  8. The information relative to the consent is returned
  9. The request is logged 
  10. The WS Consent responds with a Get Patient Consent Response
Post Condition(s)
  • The request is logged
  • The information relative to the consent is returned

      °SSIN of concerned patient

      °Consent type

      °Date of declaration

      °Author of declaration

Test Data
End point(s)
  • WS Consent
  • eHealth Database
Additional InformationSSIN support card number is not mandatory, if provided then it is discarded i.e. not submitted to the compliance validation in order to increase the performance of the consultation
RemarkShould be available soon for clinical orthopedic pedagogue, clinical psychologist & dental hygienist

Alternative Flow

FlowSpecifications

IDUC-129-AF01
NameGet Patient Consent - Parent of patient
DescriptionGet Patient consent allows end-users to check the existence and the latest status of the informed patient consent for the concerned patient. Get consent is done by a parent of the concerned patient.
Actor(s)Parent of the concerned patient, who is younger than 18 years of age
Requirements
  • End-user is a parent of the concerned patient
  • End-user acts as author of the request through his software and manages himself throughout his usual software
  • Valid eID
  • Consent WS is integrated in the software of the end-user
  • Identification end-user 

     °Parent Software information

     °Identification parent: SSIN number

  • Criteria relative to the consent

     °INSS patient

     °Support card optional

  • Type of consent (optional)
TriggerThe user wants to retrieve the status of the informed consent
Precondition(s)
  • The user has an account for the application
  • The user is logged out
Flow
  1. The user attempts to access the eHealth Consent WS
  2. The user needs to request a SAML Token by using a eHealth Certificate
  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 Get Patient Consent 
  7. The Get Patient Consent Request is sent to the WS Consent 
  8. The information relative to the consent is returned
  9. The request is logged 
  10. The WS Consent responds with a Get Patient Consent Response
Post Condition(s)
  • The request is logged
  • The information relative to the consent is returned

      °SSIN of concerned patient

      °Consent type

      °Date of declaration

      °Author of declaration

Test Data
End point(s)
  • WS Consent
  • eHealth Database
Additional InformationSSIN support card number is not mandatory, if provided then it is discarded i.e. not submitted to the compliance validation in order to increase the performance of the consultation
RemarkShould be available soon for clinical orthopedic pedagogue, clinical psychologist & dental hygienist

Alternative Flow

FlowSpecifications

IDUC-129-AF02
NameGet Patient Consent - Mandatary of patient
DescriptionGet Patient consent allows end-users to check the existence and the latest status of the informed patient consent for the concerned patient. Get consent is done by a mandatary of the concerned patient.
Actor(s)Mandatary of the concerned patient
Requirements
  • End-user is a mandatary of the concerned patient
  • End-user acts as author of the request through his software and manages himself throughout his usual software
  • Valid eID
  • Consent WS is integrated in the software of the end-user
  • Identification end-user 

     °Mandatary Software information

     °Identification mandatary: SSIN number

  • Criteria relative to the consent

     °INSS patient

     °Support card optional

  • Type of consent (optional)
TriggerThe user wants to retrieve the status of the informed consent
Precondition(s)
  • The user has an account for the application
  • The user is logged out
Flow
  1. The user attempts to access the eHealth Consent WS
  2. The user needs to request a SAML Token by using a eHealth Certificate
  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 Get Patient Consent 
  7. The Get Patient Consent Request is sent to the WS Consent 
  8. The information relative to the consent is returned
  9. The request is logged 
  10.  The WS Consent responds with a Get Patient Consent Response
Post Condition(s)
  • The request is logged
  • The information relative to the consent is returned

      °SSIN of concerned patient

      °Consent type

      °Date of declaration

      °Author of declaration

Test Data
End point(s)
  • WS Consent
  • eHealth Database
Additional InformationSSIN support card number is not mandatory, if provided then it is discarded i.e. not submitted to the compliance validation in order to increase the performance of the consultation
  • No labels

THIS SPACE IS UNDER CONSTRUCTION