Difference between revisions of "EProcedure Back-office Backend"

From DE4A
Jump to navigation Jump to search
Line 30: Line 30:
 
|-
 
|-
 
| Subscription Initiation
 
| Subscription Initiation
|  
+
| To initiate subscription data is collected and the subscription need is formulated:
 +
 
 +
* subject identifier
 +
* data owner identifier
 +
* subscriber identifier
 +
 
 +
* event catalogue
 +
 
 +
* action 'subscribe'
 +
* subscription start and end date
 +
 
 +
The subscription need is forwarded to the Data Requestor (if applicable).
 
| [[Subscription and Notification Pattern|S&N]]
 
| [[Subscription and Notification Pattern|S&N]]
 
|-
 
|-
 
|Update Subscription Log
 
|Update Subscription Log
|
+
|The notified event doesn't have impact on the procedures of the Data Evaluator and is dismissed. No further actions need to be taken.
 
|[[Subscription and Notification Pattern|S&N]]
 
|[[Subscription and Notification Pattern|S&N]]
 
|-
 
|-
Line 60: Line 71:
 
|-
 
|-
 
|Update Notification Response Log
 
|Update Notification Response Log
|
+
|The confirmation is logged to complete the audit trail.
 +
 
 +
Note: register in a way that it is easily readable (optional: include subscription id).
 
|[[Subscription and Notification Pattern|S&N]]
 
|[[Subscription and Notification Pattern|S&N]]
 
|-
 
|-

Revision as of 11:41, 4 June 2021

eProcedure Back-office Backend

Classification/description
Item Description
name eProcedure Back-office Backend
description TODO
pattern(s) S&N
application collaboration EProcedure Back-office

Application Services realized by this component
Application Service Description Pattern
Subscription Initiation To initiate subscription data is collected and the subscription need is formulated:
  • subject identifier
  • data owner identifier
  • subscriber identifier
  • event catalogue
  • action 'subscribe'
  • subscription start and end date

The subscription need is forwarded to the Data Requestor (if applicable).

S&N
Update Subscription Log The notified event doesn't have impact on the procedures of the Data Evaluator and is dismissed. No further actions need to be taken. S&N
Event Evaluation


The notified event is analysed and the appropriate response is determined.

Depenting on the event, different courses of action are possible (see details below):

  • Event is not relevant
  • Event requires a new (i.e. updated) evidence
  • Business response required
  • Exception: The notification does not match the record or the record is not active, hence the subscription needs to be changes (i.e. cancelled)

The determination result is logged as a part of the audit trail:

  • Subject identifier
  • Notified event
  • Request id
  • Determined response
  • Timestamp of determination
S&N
Update Notification Response Log The confirmation is logged to complete the audit trail.

Note: register in a way that it is easily readable (optional: include subscription id).

S&N

DE4A Common Components & BBs & MS Solutions
Component Source UC Description
xyz descr xyz [[]] Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin suscipit mauris eu dui aliquet, feugiat porttitor eros placerat.
abc descr abc [[]] Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin suscipit mauris eu dui aliquet, feugiat porttitor eros placerat.