Difference between revisions of "EProcedure Back-office Backend"
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
| Item | Description |
|---|---|
| name | eProcedure Back-office Backend |
| description | TODO |
| pattern(s) | S&N |
| application collaboration | EProcedure Back-office |
| Application Service | Description | Pattern |
|---|---|---|
| Subscription Initiation | To initiate subscription data is collected and the subscription need is formulated:
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 |
Depenting on the event, different courses of action are possible (see details below):
The determination result is logged as a part of the audit trail:
|
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 |
| 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. |
