• At least two message in one of the message boxes.

• The user is logged in.
• The user wants to delete one or more messages.

1. See use case: login.
2. The user wants to view the contents of one of his message boxes.
   The user will see a list with all of his message for the specific folder he/she requested.
   See use case: consultation for more information about the GetMessagesList method.
3. The user selects one or more messages. The user wants to delete this/these message(s).
4. The user gets a confirmation screen. The user can chose to confirm (4a) or not (4b).
   1. The user confirms and the message(s) get(s) deleted.
      A request will be sent to delete the message(s). Afterwards,
      a request will be sent to update the message list.
   2. The message(s) remain(s) the same. Nothing happens.

Path 4a:

• The deleted message(s) is/are no longer available.

Path 4b:

• The message(s) is/are still available. Nothing has changed.

GetMessagesList

• Example request
• Example response

DeleteMessage

• Example request
• Example response

• ehBoxConsultation (https://services-acpt.ehealth.fgov.be/ehBoxConsultation/v3)
  → GetMessagesList
  → DeleteMessage

• Atleast one message in one of the message boxes.

• The user is logged in.
• The user wants to delete a message.

1. See use case: login.
2. The user wants to view the contents of one of his message boxes.
   The user will see a list with all of his message for the specific folder he/she requested.
   See use case: consultation for more information about the GetMessagesList method.
3. The user selects one message to read. The message will be opened.
   See use case: read message for more information about the GetFullMessage method.
4. The user moves this message to a different message box.
5. The user gets automatically returned to the list view of the message box he/she was in.
   The list gets updated automatically.

• The message is no longer available in the message box it was consulted in.
• The message is available in the message box it was moved to.

GetMessagesList

• Example request
• Example response

GetFullMessage

• Example request
• Example response

DeleteMessage

• Example request
• Example response

• ehBoxConsultation (https://services-acpt.ehealth.fgov.be/ehBoxConsultation/v3)
  → GetMessagesList
  → GetFullMessage
  → DeleteMessage

• Atleast two message in one of the message boxes.

• The user is logged in.
• The user wants to delete one or more messages.

1. See use case: login.
2. The user wants to view the contents of one of his message boxes.
   The user will see a list with all of his message for the specific folder he/she requested.
   See use case: consultation for more information about the GetMessagesList method.
3. The user attempts the select a message with an invalid message id. The user wants to delete this message.
4. The user gets a confirmation screen. The user can chose to confirm (4a) or not (4b).
   1. The user confirms and an error message is shown.
   2. The message remains the same. Nothing happens.

Path 4a:

• An error message is shown. Afterwards the application keeps working as intended.

Path 4b:

• The message is still available. Nothing has changed.

GetMessagesList

• Example request
• Example response

DeleteMessage

• Example request
• Example response

• ehBoxConsultation (https://services-acpt.ehealth.fgov.be/ehBoxConsultation/v3)
  → GetMessagesList
  → DeleteMessage