Used Documentation

Cookbook / Materials	Version	Location
Consent WS	1.9	https://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.

cd : This is the key element used to code information: this section is completely based on the description from the KMEHR standard, as can be found on: https://www.ehealth.fgov.be/standards/kmehr/en/page/key-elements#cd
id: This element is used to uniquely identify key elements like request, response of the WS, patient, HCParty. It can also be used to specify any unique identifier: this section is completely based on the description from the KMEHR standard, as can be found on: https://www.ehealth.fgov.be/standards/kmehr/en/page/key-elements#id
HC Party: The hcparty element is a generic element that aims to represent any kind of healthcare party: organization, physician, medical specialty, or even IT systems: this section is entirely based on the description from the KMEHR standard, as can be found on: https://www.ehealth.fgov.be/standards/kmehr/en/page/hcparty

Basic Flow

Flow

Specifications

ID	UC-131-BF
Name	Get Patient Consent - HC professional AR78 in a hospital
Description	Get 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 HC professional of AR78 in a hospital.
Actor(s)	HC professional of AR78 in a hospital
Requirements	End-user is a HC professional of AR78 in a hospital The informed patient consent is managed in a recognized hospital throughout its usual software Valid eHealth certificate of the hospital Consent WS is integrated in the software of the end-user Identification hospital: NIHII , organization category Identification end-user: SSIN number, NIHII (if available), professional category Criteria relative to the consent °Information concerned patient: INSS, Support card number (optional) °Type of consent (optional)
Trigger	The 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	The user attempts to access the eHealth Consent WS The user needs to request a SAML Token by using a eHealth Certificate A request for a SAML Token is sent to the Secure Token Service (STS) The STS responds with a SAML Token The user has access to the eHealth WS Consent The user does a request for Get Patient Consent The Get Patient Consent Request is sent to the WS Consent The information relative to the consent is returned The request is logged 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	Example Get Patient Consent Request Example Get Patient Consent Resonse successful with active consent Example Get Patient Consent Resonse successful with inactive consent Example Get Patient Consent Response Unsuccessful
End point(s)	WS Consent eHealth Database
Additional Information	The SSIN & NIHII of the doctor end-user are optional for consultation method. If provided, they must be compliant with SSIN, NIHII validation (format and check-digit) SSIN 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

Alternative Flow