THIS SPACE IS UNDER CONSTRUCTION

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Table of contents

Used documentation

General information

MoveMessage

The MoveMessage method enables the user to move a message from a Source (“INBOX”, “SENTBOX”,
“BININBOX”, “BINSENTBOX”) to a Destination (“INBOX”, “SENTBOX”, “BININBOX”, “BINSENTBOX”). Only some
combinations are allowed as explained below. You need to indicate if a message was received or sent by the
concerned eHealthBox. You can do this by looking where the message is situated or compare the currently
connected user and the Sender and/ or Destination element.

The following table displays the allowed combinations of the MoveMessage method:

SourceDestination
INBOXBININBOX
SENTBOXBINSENTBOX
BININBOXINBOX
BINSENTBOXSENTBOX

A maximum of 100 messages can be moved per request.

Request

In Source specify where the message is currently situated and in Destination where the message must be moved
to. In MessageId specify as many elements as there are messages to be moved. This method can only move 100
messages at a time; consequently, you must use it multiple times if necessary.

Response

The response contains a success status code or a Business Error as defined in Chapter 8. The Business Error
enables you to identify which messages where not successfully moved, even though all other have been moved
successfully.

Basic flow

FlowSpecifications

IDAP-UC08-BF
NameMove a message from one message box to another.
DescriptionA 'message box' can be one of the following: inbox, sent box, bin inbox and bin sent box.
A table of allowed combinations can be found here.
Actor(s)One healthcare professional
Requirements

/

TriggerA healthcare professional wants to move a message.
Precondition(s)
  • The user is logged in.
  • The user wants to read a message.
Flow
  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 GetMessageList method.
  3. The user selects one message to read. The message will be opened.
Postcondition(s)
Test Data
Endpoint(s)
  • No labels