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-116-BF
Name	Put Patient Consent - Health Care professional of AR78 (Physician, Dentist, Nurse, midwife)
Description	A health care professional of AR78 (Physician - Dentist - Nurse - Midwife) declares an "Informed Patient Consent" on behalf of the patient by using the WS Consent. The personal eHealth Certificate of the health care giver is used to access to the WS Consent.
Actor(s)	A health care giver of AR78 (Physician - Dentist - Nurse - Midwife)
Requirements	End-user is a health care professional AR78 (Physician - Dentist - Nurse - Pharmacist - Midwife) End-user acts as author of the request through his software and manages himself Valid personal eHeatlh Certificate Consent WS is integrated in the software of the end-user Health care professional is not holder of the Global Medical File of the concerned patient Identification of end-user: SSIN number, NIHII number (if available), professional category Information on the consent °Identification concerned patient: SSIN, SSIN support card number, First and family name (optional) °Type of consent: Retrospective °Signing date of consent
Trigger	The 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	The user attempts to access the eHealth Consent WS The user needs to request a SAML Token by using his eID 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 Put Patient Consent The Put Patient Consent Request is sent to the WS Consent The informed Patient Consent is stored in eHealth Database The request is logged The WS Consent responds with a Put patient consent response
Post condition(s)	Request is logged The informed patient consent is stored in the eHealth Database
Test Data	Example Request AR78 - Physician Example Request AR78 - Nurse Example Request AR78 - Midwife Example Request AR78 - Dentist Example PutPatientConsentRequest Example PutPatientConsentResponse
Endpoint(s)	WS Consent eHealth Database
Remarks	If support card number is provided then it must be compliant e.g. correct format, check-digit and combination Support card number is not mandatory if the concerned patient is a new born (0 < patient < 3 months)
Additional Information	Additional information about the software and/or end-user e.g. first name and family name may be added for the audit purpose
Remark end-users	Should be available soon for Physician, Nurse, Dentist, Midwife, Audician, Physiotherapist, Occupational therapist, Practical nurse, Dietician, Audiologist, Podologist, Truss maker, Logopedist, Orthoptist, Lab technologist, Imaging technologist, clinical orthopedic pedagogue, clinical orthopedic pedagogue, clinical psychologist, dental hygienist If the HC party is the GMF holder, then the number of the support card is not required

Alternative Flow

Flow

Specifications

ID	UC-116-AF01
Name	Put Patient Consent - Physician who is holder of the concerned patient Global Medical File
Description	A physician who is holder of the concerned patient Global Medical file declares an "Informed Patient Consent" on behalf of the patient by using the WS Consent. The personal eHealth Certificate of the physician is used to access the Consent WS.
Actor(s)	Physician who is holder of the concerned patient Global Medical File
Requirements	Physician is holder of the patient's Global Medical File End-user acts as author of the request through his software and manages himself Valid personal eHeatlh Certificate Consent WS is integrated in the software of the end-user Identification of end-user: SSIN number, NIHII number (if available), professional category Information on the consent °Identification concerned patient: SSIN, First and family name (optional) °Type of consent: Retrospective °Signing date of consent
Trigger	The 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	The user attempts to access the eHealth Consent WS The user needs to request a SAML Token by using his eID 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 Put Patient Consent The Put Patient Consent Request is sent to the WS Consent The informed Patient Consent is stored in eHealth Database The request is logged The WS Consent responds with a Put patient consent response
Difference in flow	Put Patient Consent - Consent : Patient SSIN support card NOT mandatory
Post conditions	Request is logged The informed patient consent is stored in the eHealth Database
Test Data	Example Request AR78 - Physician Example PutPatientConsentRequest Example PutPatientConsentResponse
Endpoint(s)	WS Consent eHealth Database
Remarks	If support card number is provided then it must be compliant e.g. correct format, check-digit and combination Support card number is not mandatory if the concerned patient is a new born (0 < patient < 3 months)
Additional information	Additional information about the software and/or physician e.g. first name and family name may be added for the audit purpose

Exception Flow 1

Flow

Specifications

ID	UC-116-EF01
Name	Put Patient Consent - Health Care professional of AR78 - Deceased patient
Description	A health care professional of AR78 (Physician - Dentist - Nurse - Midwife) updates an "Informed Patient Consent" for a deceased patient by using the WS Consent. The personal eHealth Certificate of the health care giver is used to access to the WS Consent.
Actor(s)	A health care giver of AR78 (Physician - Dentist - Nurse - Midwife)
Requirements	End-user is a health care professional AR78 (Physician - Dentist - Nurse - Pharmacist - Midwife) End-user acts as author of the request through his software and manages himself Valid personal eHeatlh Certificate Consent WS is integrated in the software of the end-user Health care professional is not holder of the Global Medical File of the concerned patient Identification of end-user: SSIN number, NIHII number (if available), professional category Information on the consent °Identification concerned patient: SSIN, SSIN support card number, First and family name (optional) °Type of consent: Retrospective °Signing date of consent Concerned patient is deceased
Trigger	The user wants to update a Patient Consent on behalf of the patient
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 it's personal 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 Put Patient Consent The Put Patient Consent Request is sent to the WS Consent The WS Consent responds with a Put Patient Consent Response: error message
Post Condition(s)	Error message (deceased patient cannot be updated)
Test Data	Example PutPatientConsentRequest Example PutPatientConsentResponse
End point(s)	WS Consent eHealth Database
Remark end-users	Should be available soon for Physician, Nurse, Dentist, Midwife, Audician, Physiotherapist, Occupational therapist, Practical nurse, Dietician, Audiologist, Podologist, Truss maker, Logopedist, Orthoptist, Lab technologist, Imaging technologist, clinical orthopedic pedagogue, clinical orthopedic pedagogue, clinical psychologist, dental hygienist

Exception Flow 2

Flow

Specifications

ID	UC-116-EF02
Name	Put Patient Consent - Health Care professional of AR78 - Active consent already exists for the concerned patient
Description	A health care professional of AR78 (Physician - Dentist - Nurse - Midwife) updates an "Informed Patient Consent" for a patient by using the WS Consent. The personal eHealth Certificate of the health care giver is used to access to the WS Consent. Active consent already exists for the concerned patient.
Actor(s)	A health care giver of AR78 (Physician - Dentist - Nurse - Midwife)
Requirements	End-user is a health care professional AR78 (Physician - Dentist - Nurse - Pharmacist - Midwife) End-user acts as author of the request through his software and manages himself Valid personal eHeatlh Certificate Consent WS is integrated in the software of the end-user Health care professional is not holder of the Global Medical File of the concerned patient Identification of end-user: SSIN number, NIHII number (if available), professional category Information on the consent °Identification concerned patient: SSIN, SSIN support card number, First and family name (optional) °Type of consent: Retrospective °Signing date of consent Active consent already exists for the concerned patient
Trigger	The user wants to put a Patient Consent on behalf of the patient
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 it's personal 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 Put Patient Consent The Put Patient Consent Request is sent to the WS Consent The WS Consent responds with a Put Patient Consent Response: error message
Post Condition(s)	Error message
Test Data	Example PutPatientConsentRequest Example PutPatientConsentResponse
End point(s)	WS Consent eHealth Database
Remark end-users	Should be available soon for Physician, Nurse, Dentist, Midwife, Audician, Physiotherapist, Occupational therapist, Practical nurse, Dietician, Audiologist, Podologist, Truss maker, Logopedist, Orthoptist, Lab technologist, Imaging technologist, clinical orthopedic pedagogue, clinical orthopedic pedagogue, clinical psychologist, dental hygienist

Page tree

UC-116-Put Consent-HCprof AR78

Used Documentation

General Information

Informed Consent

Basic Flow

Alternative Flow

Exception Flow 1

Exception Flow 2