...
For all user generated connect messages from a patient registry to an donor registry or vice versa the generic message flow consists of the message sent (e.g. a Sample Request) and a corresponding message response (6.2). This default answer is shown in the message flow below, but will be ommited for better readability in later request message flows in chapter 5.
For further details on the message response see chapter 6.2.
...
| PlantUML Macro | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
participant "Patient Registry" as PR control "Match-Connect" as MC control "Search & Match\nService" as SM participant "Donor Registry" as DR skinparam SequenceMessageAlign center skinparam dpi 92 == Making RequestSending a user generated message == PR -[#dodgerblue]> DR : Send message A MC -> PR : 400 Bad Request (optional) MC -> PR : 200 OK (possibly with warnings) PR -> MC : Check not-picked up messages MC -> PR : 200 OK - Array of messages not yet delivered == Getting Response == Providing the default response == DR -> MC : Check not-picked up messages MC -> DR : 200 OK - Array of messages not yet delivered (Message A) DR -[#dodgerblue]> PR : Message response (ack, reject, warning to "Message A") \nshould always include messageId of referring message MC -> DR : 400 Bad Request (optional) MC -> DR : 200 OK (possibly with warnings) == Getting the default response == |
2.4.5 Automatically generated and manually curated Swagger
...