Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • When the expiration date of a message is reached, it has been read, AND it has already been placed in
    the recycle bin, the message is definitely removed from the application.

  • When a message is older than 1 year (counted from publication date), it is definitely removed from the
    application, even if it has not been read.

Treatment of NIHII-11 numbers

When sending a message via the Publication WS, the identification of the sender is by default, retrieved from
the STS Token. The recipient will see the identifier of the sender when retrieving the message via the
Consultation WS. If the sender is a healthcare professional, his SSIN can be retrieved from the STS token and
used as identifier for the sender. If the sender is a hospital or some other healthcare organization, the identifier
in the STS token will be of the type NIHII. Finally, if the sender is an organization, the identifier type will be a
CBE. Exception is made if BoxId (optional element) is filled out. In that case, the person connected to the WS is
sending the message “in name of the person or organization” specified in the element BoxId. Thus, if a
healthcare professional (a person) wants to send a message using his NIHII (INAMI) number instead of his SSIN
number, he has to submit the request and fill out his NIHII number in the BoxId.

For example, the sender is connected as a doctor with an STS token containing his INSS number as attribute:

x

But he does not want to display his SSIN number to the recipient, since he prefers to display his NIHII number;
he then uses the BoxId element in the request, and fills it out as follows:

x

The sender will then be stored in the application with the data found in BoxId (after access validation).
Note: a NIHII number consists out of 11 numbers (with the 3 qualification numbers) or 8 numbers (without the
3 qualification numbers).
When authenticated as an organization, it is not possible to use the BoxId.

Out-of-Office

This system enables the sender to know whether one of the recipients is absent and send his message to a
substitute or substitutes, so the sender’s message can be treated. For example, physicians on holiday may want
to ensure continuity of healthcare services for their patients. To do this, they can automatically transfer their
messages to another colleague responsible during their holidays thanks to the “Out-of-Office” system. If a
recipient is absent, a special SendMessageResponse with the substitutes is returned.

...