Reset Search
 
Article

Encryption module

« Go Back

Support article

 
Last Modified Date6/28/2017 1:45 PM
SummaryEncryption module
Content
While HD4DP is developed by healthdata.be, the EM module is not. It can be developed by data providers or third party vendors.

The architecture workgroup of the eHealth platform have strict rules concerning the encoding. Encryption and decryption from the HD4DP software are kept separate.

A new component, whose main functionality, is the encryption of the data before it leaves the organization. Since “data encryption” is the main purpose of this module, it will be referred to as Encryption Module (or EM).

Development by Data Providers

cookbook containing detailed instructions on how to implement the module are attached.

HD4DP needs to be configured for the encryption module (cf How to configure HD4DP for an encryption module).

Finally, validation (cf. Encryption module validation scenario) the encryption module implementations is done by healthdata.
 

Development by Third Parties

The two main functionalities of the encryption module are:
  •   Encryption and decryption data
  •   Sending and receiving data

HD4DP needs to be configured for the encryption module (cf. How to configure HD4DP for an encryption module​).
 

Encryption and decryption

Healthdata.be has validated (cf. Encryption module validation scenario) the encryption module implementations, developed by the following parties:

 

Sending and receiving data

In Belgium, different eHealthBox client software applications are available.

An eHealthBox client application provides an interface to use the eHealthBox service. The eHealth-platform communicates medical files, lab results or other sensible information.

​The use of an eHealthBox client application is required for sending data to healthdata.

The main vendors are:  

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255