FB_BUC_01_EN | Lexipedia

EESSI – CDM 4.3

FB-Family Benefits

FB_BUC_01-v4.3.4

Determine Competences

Business Use Case

Table of Contents

Table of Contents 2

1. Introduction 6

1.1. Purpose 6

1.2. Scope 6

1.3. Definitions, Acronyms and Abbreviations 6

1.4. References 7

1.5. Overview 7

2. Description 8

2.1. Business Scenario 8

2.2. Legal Base 8

3. Actors & Roles 10

4. Use Case 11

4.1. RUP Table Representation 11

4.2. Request – Reply SEDs 26

4.3. Attachments Allowed 26

4.4. Artefacts used 26

5. Business Processes 28

5.1. Main Scenario – Case Owner and Counterparty 28

5.2. Sub Processes 29

6. Appendices 30

6.1. Issues 30

Document Control Information

Document Control

Value

Project Title

Electronic Exchange of Social Security Information (EESSI)

Document Name

FB_BUC_01_Mainproc_Specification_v4.3.4

Document Category

BUC specifications

Revision

CDM Package

CDM 4.3.4

Last Update

Project Milestone

30/04/2024

EESSI - 2024

Document Status

Final

Sensitivity (TLP)

Distribution terms

Traffic Light Protocol (TLP) = “GREEN”

The distribution of this document is done strictly in line with the Traffic Light Protocol (TLP) established by the European Commission's note AC 790/15 REV for the EESSI project documentation.

In line with the note AC 790/15 REV, this document is labelled as TLP = “Green”. Therefore, it can be circulated widely within the EESSI community. However, the document or the information herein may not be published or posted on the Internet, nor released outside of the EESSI

community.

Connected/Embedded Files

None

Authors

European Commission, DG EMPL A4, EESSI BA

Revised by

European Commission, DG EMPL A4, EESSI BA

Approved by

European Commission, DG EMPL A4, EESSI PMO

Document history

Milestone /

Component version

Publication Date

Changes/Corrections

Description

v0.2

04.06.2014

Adding BPMN diagrams; adding Horizontal and administrative branches.

V0.3

08.08.2014

Updating the BPMN diagrams

v2.1

04.02.2015

Including the observations from AHG

v2.2

23.03.2015

Including internal observations

v2.3

10.04.2015

Including observation from AHG

v0.24

28/04/2015

Change version system

Remove former flow reference

Add 3 branches for counterparty being able to send F023, F025 and F027

v0.26.0

19/11/2015

Update to align with business architecture principles

v0.99.0

19/01/2016

Candidate for AHG Approval

Integrated the feedback received (minor changes, not involving the process itself)

v0.99.1

10/02/2016

Candidate for AC Approval

Minor textual changes following the review made by the Rapporteur

v.1.0.0

15/05/2016

AC Approved version

v1.0.1

15/06/2016

Added the reference to Art F2 under point 2.2 Legal Regulations / Policy Issues / Other Mentions following AHGs approval

v1.0.2

19/07/2016

Deleted Branch 18 (H_BUC_04)

v1.0.3

02/08/2016

Alignment to the standard description and layout of the BUCs

v1.1.0

14/03/2016

Replaced F024/F025 reply-request with H_BUC_08 and F025 with H_BUC_09

The Counterparty can reply directly with F022, F023, etc after receiving the F001 from the Case Owner. There is no obligation for the Counterparty to reply to F001 with F002, before sending F022, F023, etc

(Change approved by the Change Management Board)

v1.1.1

28/06/2107

Added the last version of BPMN

(CR EESSI 1760)

Cosmetic changes (headings)

Correction in the sub-process table in section 4.5.

- removed Use Case diagram

v1.1.2

13/11/2017

Align wording for Invalidate SED and Forward participant

v4.1.0

03/08/2018

- Section 4.4 merged 2 tables (for SED & for Subprocesses) into 1 BUC Artefact table.

- Version adaptations to release 4.1.0.

- Add SR for [Branch 21] regarding H_BUC_07 – Notification of Death

- Update table Section 3, regarding Counterparty role.

v4.2.0

29/05/2019

Version adaptations to release 4.2.0

v4.3.0

31/08/2021

Version adaptations to release 4.3.0

v4.3.4

30/04/2024

Implementation of change request EESSI-11289 by removing sub process H_BUC_04 from the 4.4 Artefacts used table.

Introduction

Purpose

The purpose of this document is to construct an external view of, part of, the 'EESSI business system' as described in EC Regulations 883/2004 and 987/2009. The ‘EESSI Business System’ describes the business and expected business processes without consideration as to which part(s) may be realised by an IT System (i.e. the proposed EESSI IT System).

The external view comprises of models and descriptions of business use cases, the services of a business system offered to business actors: customers, business partners, or other business systems.

A business use case is described from an actor's perspective; it describes the interaction between an actor and the business system, meaning it describes the behaviours of the business system that the actor utilises. The Business Use Case includes Use Case Diagrams and Business Process Models.

Use case diagrams show actors, business use cases, and their relationships. Use case diagrams do not describe procedures. Alternative scenarios also remain hidden. These diagrams give a good overview of the behaviours of the EESSI business system which will direct and govern part of the expected behaviours and functionality delivered by the EESSI IT System.

Scope

This document is limited to the external view on the Family Benefit sector process of Determine Competences. The different elements like use case description, business actors, and business process as well as supporting UML diagrams and BPMN models pertaining to the Determine Competences.

Definitions, Acronyms and Abbreviations

Please see the EESSI Project Glossary here.

References

Description

EC Regulation 883/2004

Regulation EC No 883- 2004.pdf

EC Regulation 987/2009

Regulation EC No 987-2009.pdf

UML 2.x

http://www.omg.org/spec/UML/

BPMN 2.0

http://www.omg.org/spec/BPMN/index.htm

UML 2.0 In Action

Henriette Baumann, Patrick Grassle & Philippe Baumann, 2005, ISBN 1904811558

RUP@EC standard 5.0

http://www.cc.cec/RUPatEC_Standard/

RUP op maat

http://www.rupopmaat.nl/

Overview

Chapter 1 introduces the external view on the business system under review and lists the elements of this specification.

Chapter 2 introduces the Determine Competences business processes. The chapter gives a short and detailed description as well as a reference to business process legal base.

Chapter 3 lists the actors involved in the Determine Competences business process.

Chapter 4 describes in detail the Determine Competences business process based on the RUP use case template, as well as the relationship to other use cases.

Chapter 5 describes the Determine Competences business process using business process modelling notation (BPMN).

Description

Business Scenario

The present business process in the Family Benefits sector describes the communication necessary in order to implement the provisions concerning family benefits in the coordination regulations. Situations covered by this process:

new claim;

change in circumstances;

disagreement procedure;

annual check;

offsetting situations between Member States according to article 72 and

73 of Regulation (EC) No 987/2009;

reimbursement situations between Member States according to article

58 of Regulation (EC) No 987/2009.

Legal Base

This document's legal base is found in the following EC Regulations:

Basic Regulation (EC) No 883/2004

Implementing Regulation (EC) No 987/2009

According to the Decision F2:

'An institution shall reply promptly to a request for information from another Member State and in any event, no later than:

a. two months after the day of receipt of the request in a case concerning a request for a position on a provisional decision on the priority rules referred to at Article 60(3) of Regulation (EC) No 987/2009), or

b. three months after the day of receipt of the request for information in all other cases.'

The following matrix derived from version 3 SEDs, documented by the expert AHGs, lists the SEDs used in this Business Use Case and their relation with the articles mentioned above.

Basic Reg (883/04)

Implementing Reg (987/09)

SED

1(i)

2(2)

6(2)

60(1)

60(2)

60(3)

60(4)

60(5)

F001

F002

F004

F005

F022

F023

F026

F027

Table 1: SED – Legal base relationship matrix

Actors & Roles

This chapter captures details of the actors which are important to understanding the different types of system users. An actor is anyone or anything that exchanges data with the business system. An actor can be a user, external hardware, or another system.

The overarching description of each actor described in this Business Use Case can be found in the Glossary. Below you will find a short description which provides further clarity of this actor within the context of this Business Use Case.

Actor name

Description

Case Owner

Institution of a Member State that handles the Family Benefit Claim on behalf of the Petitioner. Initiates the determination of Competences specific to the Claim.

Counterparty

Is the Competent Institution who performs the role of Institution Concerned, as described by the Regulations

Petitioner

Person that applies for family benefits.

Table 2: Actors & Roles

Use Case

RUP Table Representation

Use Case ID:

FB_BUC_01

Use Case Name:

Determining Competences

Created By:

Mihai Dinca

Last Updated By:

Violeta Popescu

Date Created:

25/03/2014

Last Revision Date:

31/08/2021

Actors:

Case Owner

Counterparty

Petitioner

Description:

A competent institution from a Member State asks for information about a person (who applied for family benefits) to a Counterparty institution in a different Member State. The information may be related to:

- new claims on family benefits

- existing claims on family benefits

- that person's employment record

- that person's medical history

- that person's family

- offsetting according to articles 72 and 73 of Regulation (EC) No987/2009

- reimbursement according to article 58 of 987/2009 Or

- annual check between institutions of different Member States.

Trigger:

The Petitioner applies for family benefits in the state where he is resident, but he was previously insured in another Member State. The Petitioner may also apply for family benefits e.g. in the Member State of employment or previous employment. The trigger may also be the change of Member State of residence for child(ren) or any other change in the circumstances.

Preconditions:

The person has previously worked in a state other than his/her state of residence.

Post conditions:

The Competent institution in the state of residence now has enough information to calculate the requested family benefits

The Competent Institutions have updated information on their ongoing granted benefits.

Main Scenario:

Identify Participants

The Case Owner identifies the Member State where the Petitioner used to work; or the new Member State where the child(ren) has/have moved;

The Case Owner then identifies the correct institution (the Counterparty) or institutions in the respective Member State that is responsible for determining the Family Benefits. The Case Owner and the Counterparty(ies) are herein collectively referred to as the Participants.

Send the request for information

The Case Owner fills in a F001 SED requesting information in order to determine the competence;

The Case Owner sends the F001 SED to the Counterparty(ies);

The Counterparty(ies) receive(s) the F001 SED;

Each Counterparty fills in a F002 SED, by providing the relevant information in order to determine the competence;

Each Counterparty sends their F002 to the Case Owner only. Steps 6 and 7 can be repeated;

The Case Owner waits until a F002 from each Counterparty has been received;

The Case Owner fills in a F002 SED, in order to inform the Counterparties on his decision;

The Case Owner sends F002 to the Counterparties. Steps 9 and 10 can be repeated;

The Counterparty(ies) receive(s) the F002 SED;

The BUC Ends.

Alternative Scenarios:

After the completion of [step 4] the Case Owner decides he needs information about the periods of employment of the Petitioner in the corresponding Member State:

The Case Owner fills in a F022 SED, requesting information on periods;

The Case Owner sends the F022 SED to one or more Counterparties;

The Counterparty(ies) receive(s) the F022 SED;

Each Counterparty that received the F022 fills in the F023 SED by providing the relevant periods of employment in their Member State;

Each Counterparty that received the F022 sends the F023 to the Case Owner;

The Case Owner receives the F023;

[This branch] Ends. (The main scenario resumes at step 6).

[REMOVED]

After the completion of [step 4] the Case Owner decides he needs more information about the Petitioner:

The Case Owner fills in a F026 SED, requesting more information about the Petitioner;

The Case Owner sends the F026 SED to one or more Counterparties;

The Counterparty(ies) receive(s) the F026 SED;

Each Counterparty that received the F026 SED fills in the F027 SED thus providing the requested information;

Each Counterparty that received the F026 sends the F027 to the Case Owner;

The Case Owner receives the F027;

[This branch] Ends. (The main scenario resumes at step 6)

After the completion of [step 4] the Case Owner concludes the Counterparties need information about the periods of employment of the Petitioner:

The Case Owner fills in a F023 SED, providing more information about the periods of employment of the Petitioner;

The Case Owner sends the F023 SED to one or more Counterparties;

The Counterparty(ies) receive(s) the F023 SED;

[This branch] Ends. (The main scenario resumes at step 6).

[REMOVED]

After the completion of [step 4] the Case Owner concludes the Counterparties need more information about the Petitioner:

The Case Owner fills in a F027 SED, providing more information about the Petitioner;

The Case Owner sends the F027 SED to one or more Counterparties;

The Counterparty(ies) receive(s) the F027 SED;

[This branch] Ends. (The main scenario resumes at step 6).

After the completion of [step 5] a Counterparty decides he needs information about the periods of employment of the Petitioner in the corresponding Member State(s):

The Counterparty fills in a F022 SED, requesting information on periods;

The Counterparty sends the F022 SED to the Case Owner and/or the Counterparty(ies);

The Case Owner and/or the Counterparty(ies) in question receive(s) the F022 SED;

The Case Owner and/or the Counterparty(ies) in question fill(s) in the F023 SED by providing the relevant periods of employment in their Member State;

The Case Owner and/or the Counterparty(ies) in question send(s) the

F023 to the requesting Counterparty;

The Counterparty receives the F023;

The Counterparty repeats the step 6 until all the answers have been received;

[This branch] Ends. (The main scenario resumes at step 6).

[REMOVED]

After the completion of [step 5] a Counterparty decides he needs more information about the Petitioner:

The Counterparty fills in a F026 SED, requesting more information about the Petitioner;

The Counterparty sends the F026 SED to one or more Participants;

The Participant(s) in question receive(s) the F026 SED;

The Participant(s) in question fill(s) in an F027 SED thus providing the requested information;

The Participant(s) in question send(s) the F027 to the requesting Counterparty;

The Counterparty receives the F027;

The Counterparty repeats the step 6 until all the answers have been received;

[This branch] Ends. (The main scenario resumes at step 6).

After the completion of [step 9] the Case Owner decides he needs clarifications about a previously sent message:

The Case Owner fills in a F004 SED, requesting for clarification about a previous sent message;

The Case Owner sends the F004 SED to one or more Counterparties;

The Counterparty(ies) receive(s) the F004 SED;

Each Counterparty that received the F004 fills in the F005 SED thus providing the requested clarifications;

Each Counterparty that received the F004 sends the F005 to the Case Owner;

The Case Owner receives the F005;

The Case Owner sends the F002 to the Counterparty(ies);

[This branch] Ends. (The main scenario resumes at step 6).

After the completion of [step 5] a Counterparty decides he needs more information

The Counterparty fills in a F004 SED, requesting for clarification about a previous sent message;

The Counterparty sends the F004 to the Case Owner and/or other Participants;

The Case Owner and/or other Participants receive(s) the F004 SED;

The Case Owner and/or other Participants fill(s) in an F005 SED thus providing the requested information;

The Case Owner and/or other Participants optionally send(s) the F005 to the Counterparty;

The Counterparty optionally receives the F005 (the reply/replies are not blocking; the flow can be carried on without it/them);

[This branch] Ends. (The main scenario resumes at step 6).

After the completion of [step 5] a Counterparty concludes the Case Owner needs information about the periods of employment of the Petitioner:

The Counterparty fills in a F023 SED, providing more information about the periods of employment of the Petitioner;

The Counterparty sends the F023 SED to the Case Owner and any other Counterparty(ies);

The Participants receive the F023 SED;

[This branch] Ends. (The main scenario resumes at step 6).

[REMOVED]

After the completion of [step 5], a Counterparty concludes the Case Owner needs more information about the Petitioner:

The Counterparty fills in a F027 SED, providing more information about the Petitioner;

The Counterparty sends the F027 SED to the Case Owner and any other Counterparty(ies);

The Participants receive the F027 SED;

[This branch] Ends. (The main scenario resumes at step 6).

The Following Branches determine the use of Horizontally defined Sub- Processes within this Business Process. Once a branch is completed, the case resumes from the step where it was when the branch was started.

at any step between [step 5] and [step 12] any Participant may optionally choose to request AdHoc Information from another

Participant

The Participant executes business use case H_BUC_01_Subprocess – AdHoc Exchange of Info;

[This Branch] Ends.

at any step between [step 5] and [step 12] any Participant may optionally choose to determine the residence of the Person with another Participant

The Participant executes business use case H_BUC_02_Subprocess – Determine Residence;

[This Branch] Ends.

at any step between [step 5] and [step 12] any Participant may optionally choose to notify another Participant of a change of Legislation Applicable

The Participant executes business use case H_BUC_03a_Subprocess – Change of Legislation Applicable-Notification;

[This Branch] Ends.

at any step between [step 5] and [step 12] any Participant may optionally choose to notify another Participant of a change of Legislation Applicable

1. The Participant executes business use case H_BUC_03b_Subprocess –

Change of Legislation Applicable-Request for Information;

2. [This Branch] Ends.

at any step between [step 5] and [step 12] any Participant may

optionally choose to Exchange the PIN of a citizen with another Participant

The Participant executes business use case H_BUC_05_Subprocess – Exchange of PIN;

[This Branch] Ends.

at any step between [step 5] and [step 12] any Participant may optionally choose to Exchange a Claim document with another Participant

The Participant executes business use case H_BUC_06_Subprocess – Exchange Claim;

[This Branch] Ends.

at any step between [step 5] and [step 12] any Participant may optionally choose to notify another Participant of a Death of a Person

The Participant executes business use case H_BUC_07_Subprocess – Notification of Death;

[This Branch] Ends.

[REMOVED]

The Following Branches Determine the use of Administrative Processes within this Business Process

at any step between [step 5] and [step 12] any Participant may choose to Forward this Business Process to another Competent Institution within their MS who assumes responsibility for handling it

The Participant executes business use case AD_BUC_05_Subprocess – Forward Case;

[This Branch] Ends.

at any step between [step 5] and [step 12] any Participant may choose to Add a new Participant to this Business Process

The Participant executes business use case AD_BUC_03_Subprocess – Add Participant;

[This Branch] Ends.

at any step between [step 5] and [step 12] any Counterparty may choose to Remove himself from this Business Process

The Counterparty executes business use case AD_BUC_04_Subprocess – Remove Participant;

[This Branch] Ends.

at any step between [step 4] and [step 12] the Case Owner may choose to advise all recipients that their F001 is Invalid under Art 5 of 987/09

The Case Owner executes business use case AD_BUC_06_Subprocess - Invalidate_SED;

Optionally, the Case Owner creates a new F001 SED requesting information in order to determine the competence;

Optionally, the Case Owner sends the F001 SED to the Counterparty(ies);

[This Branch] Ends.

at any step between [step 7] and [step 12] a Counterparty may choose to advise all recipients that their F002 is Invalid under Art 5 of 987/09

The Counterparty executes business use case AD_BUC_06_Subprocess - Invalidate_SED;

Optionally, the Counterparty fills in F002, by entering all the required data;

Optionally, the Counterparty sends F002, including any attachments, to all Counterparties;

[This Branch] Ends.

at any step between [step 10] and [step 12] the Case Owner may choose to advise all recipients that their F002 is Invalid under Art 5 of 987/09

The Case Owner executes business use case AD_BUC_06_Subprocess - Invalidate_SED;

Optionally, the Case Owner fills in F002, by entering all the required data;

Optionally, the Case Owner sends F002, including all the attachments, to all Counterparties;

[This Branch] Ends.

where [Branch 1 Step 2] has been executed then at any step between [Branch 1 Step 2] and [step 12] the Case Owner may choose to advise all recipients that their F022 is Invalid under Art 5 of 987/09

The Case Owner executes business use case AD_BUC_06_Subprocess - Invalidate_SED;

Optionally, the Case Owner sends F022, by entering all the required

data;

Optionally, the Case Owner sends F022, including all the attachments, to all Counterparties;

[This Branch] Ends.

where [Branch 1 Step 5] has been executed then at any step between [Branch 1 Step 5] and [step 12] the Counterparty may choose to advise all recipients that their F023 is Invalid under Art 5 of 987/09

The Counterparty executes business use case AD_BUC_06 - Invalidate_SED;

Optionally, the Counterparty fills in F023, by entering all the required data;

Optionally, the Counterparty sends F023, including all the attachments, to all Counterparties;

[This Branch] Ends.

[REMOVED]

where [Branch 3 Step 2] has been executed then at any step between [Branch 3 Step 2] and [step 12] the Case Owner may choose to advise all recipients that their F026 is Invalid under Art 5 of 987/09

The Case Owner executes business use case AD_BUC_06_Subprocess - Invalidate_SED;

Optionally, the Case Owner fills in F026, by entering all the required

data;

Optionally, the Case Owner sends F026, including all the attachments, to all Counterparties;

[This Branch] Ends.

where [Branch 3 Step 5] has been executed then at any step between [Branch 3 Step 5] and [step 12] the Counterparty may choose to advise all recipients that their F027 is Invalid under Art 5 of 987/09

The Counterparty executes business use case AD_BUC_06_Subprocess - Invalidate_SED;

Optionally, the Counterparty fills in F027, by entering all the required data;

Optionally, the Counterparty sends F027, including any attachments to all Counterparties;

[This Branch] Ends.

where [Branch 4 Step 2] has been executed then at any step between [Branch 4 Step 2] and [step 12] the Case Owner may choose to advise all recipients that their F023 is Invalid under Art 5 of 987/09

The Case Owner executes business use case AD_BUC_06_Subprocess - Invalidate_SED;

Optionally, the Case Owner fills in F023, by entering all the required data;

Optionally, the Case Owner sends F023, including all the attachments, to all Counterparties;

[This Branch] Ends.

[REMOVED]

where [Branch 6 Step 2] has been executed then at any step between [Branch 6 Step 2] and [step 12] the Case Owner may choose to advise all recipients that their F027 is Invalid under Art 5 of 987/09

The Case Owner executes business use case AD_BUC_06_Subprocess - Invalidate_SED;

Optionally, the Case Owner fills in F027, by entering all the required data;

Optionally, the Case Owner sends F027, including any attachments to all Counterparties;

[This Branch] Ends.

where [Branch 10 Step 2] has been executed then at any step between [Branch 10 Step 2] and [Branch 10 step 7] the Case Owner may choose to advise all recipients that their F004 is Invalid under Art 5 of 987/09

The Case Owner executes business use case AD_BUC_06_Subprocess - Invalidate_SED

Optionally, the Case Owner fills in F004, by entering all the required data;

Optionally, the Case Owner sends F004, including any attachments, to all Counterparties;

[This Branch] Ends.

where [Branch 10 Step 5] has been executed then at any step between [Branch 10 Step 5] and [Branch 10 Step 7] the Counterparty may choose to advise all recipients that their F005 is Invalid under Art 5 of 987/09

The Counterparty executes business use case AD_BUC_06_Subprocess - Invalidate_SED;

Optionally, the Counterparty fills in F005, by entering all the required data;

Optionally, the Counterparty sends F005, including any attachments, to all Counterparties;

The Main Scenario reverts to [step 12].

Where [Branch 11 Step 2] has been executed then at any step between [Branch 11 Step 2] and [Branch 11 step 7] the Counterparty may choose to advise all recipients that their F004 is Invalid under Art 5 of 987/09

The Counterparty executes business use case AD_BUC_06_Subprocess - Invalidate_SED;

Optionally, the Counterparty fills in F004, by entering all the required data;

Optionally, the Counterparty sends F004, including any attachments, to all Counterparties;

The Main Scenario reverts to [step 12].

where [Branch 11 Step 5] has been executed then at any step between [Branch 11 Step 5] and [Branch 11 step 7] the Case Owner may choose to advise all recipients that their F005 is Invalid under Art 5 of 987/09

The Case Owner executes business use case AD_BUC_06_Subprocess - Invalidate_SED;

Optionally, the Case Owner fills in F005, by entering all the required data;

Optionally, the Case Owner sends F005, including any attachments, to

all Counterparties;

The Main Scenario reverts to [step 12].

at any step between [step 4] and [step 12] the Case Owner may choose to send an updated version of F001

The Case Owner executes business use case AD_BUC_10_Subprocess - Update_SED;

[This Branch] Ends

at any step between [step 7] and [step 12] a Counterparty may choose to send an updated version of F002

The Counterparty executes business use case AD_BUC_10_Subprocess - Update_SED;

[This Branch] Ends.

where [Branch 1 Step 2] has been executed then at any step between [Branch 1 Step 2] and [step 12] the Case Owner may choose to send an updated version of F022

The Case Owner executes business use case AD_BUC_10_Subprocess - Update_SED;

[This Branch] Ends.

where [Branch 1 Step 5] has been executed then at any step between [Branch 1 Step 5] and [step 12] the Counterparty may choose to send an updated version of F023

The Counterparty executes business use case AD_BUC_10_Subprocess -

Update_SED;

[This Branch] Ends.

at any step between [step 10] and [step 12] the Case Owner may choose to send an updated version of F002

The Case Owner executes business use case AD_BUC_10_Subprocess - Update_SED;

[This Branch] Ends.

[REMOVED]

where [Branch 3 Step 2] has been executed then at any step between [Branch 3 Step 2] and [step 12] the Case Owner may choose to send an updated version of F026

The Case Owner executes business use case AD_BUC_10_Subprocess - Update_SED;

[This Branch] Ends.

where [Branch 3 Step 5] has been executed then at any step between [Branch 3 Step 5] and [step 12] the Counterparty may choose to send an updated version of F027

The Counterparty executes business use case AD_BUC_10_Subprocess - Update_SED;

[This Branch] Ends.

where [Branch 4 Step 2] has been executed then at any step between [Branch 4 Step 2] and [step 12] the Case Owner may choose to send an updated version of F023

The Case Owner executes business use case AD_BUC_10_Subprocess - Update_SED;

[This Branch] Ends.

[REMOVED]

where [Branch 6 Step 2] has been executed then at any step between [Branch 6 Step 2] and [step 12] the Case Owner may choose to send an updated version of F027

The Case Owner executes business use case AD_BUC_10_Subprocess - Update_SED;

[This Branch] Ends.

where [Branch 10 Step 2] has been executed then at any step between [Branch 10 Step 2] and [step 12] the Case Owner may choose to send an updated version of F004

The Case Owner executes business use case AD_BUC_10_Subprocess - Update_SED;

The Main Scenario reverts to [step 12].

where [Branch 10 Step 5] has been executed then at any step between [Branch 10 Step 5] and [step 12] the Counterparty may choose to send an updated version of F005

The Counterparty executes business use case AD_BUC_10_Subprocess - Update_SED;

The Main Scenario reverts to [step 12].

where [Branch 11 Step 2] has been executed then at any step between [Branch 11 Step 2] and [step 12] the Counterparty may choose to send an updated version of F004

The Counterparty executes business use case AD_BUC_10_Subprocess - Update_SED;

The Main Scenario reverts to [step 12].

where [Branch 11 Step 5] has been executed then at any step between [Branch 11 Step 5] and [step 12] the Counterparty may choose to send an updated version of F005

The Counterparty executes business use case AD_BUC_10 _Subprocess - Update_SED;

The Main Scenario reverts to [step 12].

at any step between [step 5] and [step 12] any Participant may optionally choose to send a Reminder to another Participant for the return of information they were expecting from that Participant but did not receive

The Participant who invokes this branch executes business use case AD_BUC_07_Subprocess -_Reminder;

[This Branch] Ends.

where [Branch 7 Step 2] has been executed then at any step between [Branch 7 Step 2] and [step 12] the Counterparty may choose to advise all recipients that their F022 is Invalid under Art 5 of 987/09

The Counterparty executes business use case AD_BUC_06_Subprocess - Invalidate_SED;

Optionally, the Counterparty fills in F022, by entering all the required data;

Optionally, the Counterparty sends F022, including any attachments, to all Counterparties;

[This Branch] Ends.

where [Branch 7 Step 5] has been executed then at any step between [Branch 7 Step 5] and [step 12] the Case Owner may choose to advise all recipients that their F023 is Invalid under Art 5 of 987/09

The Case Owner executes business use case AD_BUC_06 - Invalidate_SED;

Optionally, the Case Owner fills in F023, by entering all the required data;

Optionally, the Case Owner sends F023, including any attachments, to all counterparties;

[This Branch] Ends.

[REMOVED]

where [Branch 9 Step 2] has been executed then at any step between [Branch 9 Step 2] and [step 12] the Counterparty may choose to advise all recipients that their F026 is Invalid under Art 5 of 987/09

The Counterparty executes business use case AD_BUC_06_Subprocess - Invalidate_SED;

Optionally, the Counterparty fills in F026, by entering all the required

data;

Optionally, the Counterparty sends F026, including any attachments, to all Counterparties;

[This Branch] Ends.

where [Branch 9 Step 5] has been executed then at any step between [Branch 9 Step 5] and [step 12] the Case Owner may choose to advise all recipients that their F027 is Invalid under Art 5 of 987/09

The Case Owner executes business use case AD_BUC_06_Subprocess - Invalidate_SED;

Optionally, the Case Owner fills in F027, by entering all the required data;

Optionally, the Case Owner sends F027, including any attachments, to all Counterparties;

[This Branch] Ends.

where [Branch 12 Step 2] has been executed then at any step between [Branch 12 Step 2] and [step 12] the Counterparty may choose to advise all recipients that their F023 is Invalid under Art 5 of 987/09

The Counterparty executes business use case AD_BUC_06_Subprocess - Invalidate_SED;

Optionally, the Counterparty fills in F023, by entering all the required data;

Optionally, the Counterparty sends F023, including any attachments, to all Counterparties;

[This Branch] Ends.

[REMOVED]

where [Branch 14 Step 2] has been executed then at any step between [Branch 14 Step 2] and [step 12] the Counterparty may choose to advise all recipients that their F027 is Invalid under Art 5 of 987/09

The Counterparty executes business use case AD_BUC_06_Subprocess - Invalidate_SED;

Optionally, the Counterparty fills in F027, by entering all the required data;

Optionally, the Counterparty sends F027, including any attachments, to all Counterparties;

[This Branch] Ends.

where [Branch 7 Step 2] has been executed then at any step between [Branch 7 Step 2] and [step 12] the Counterparty may choose to send an updated version of F022

The Counterparty executes business use case AD_BUC_10_Subprocess - Update_SED;

[This Branch] Ends.

where [Branch 7 Step 5] has been executed then at any step between [Branch 7 Step 5] and [step 12] the Case Owner may choose to send an updated version of F023

The Case Owner executes business use case AD_BUC_10_Subprocess - Update_SED;

[This Branch] Ends.

[REMOVED]

where [Branch 9 Step 2] has been executed then at any step between [Branch 9 Step 2] and [step 12] the Counterparty may choose to send an updated version of F026

The Counterparty executes business use case AD_BUC_10_Subprocess - Update_SED;

[This Branch] Ends.

where [Branch 9 Step 5] has been executed then at any step between [Branch 9 Step 5] and [step 12] the Case Owner may choose to send an updated version of F027

The Case Owner executes business use case AD_BUC_10_Subprocess - Update_SED;

[This Branch] Ends.

where [Branch 12 Step 2] has been executed then at any step between [Branch 12 Step 2] and [step 12] the Counterparty may choose to send an updated version of F023

The Counterparty executes business use case AD_BUC_10_Subprocess - Update_SED;

[This Branch] Ends.

[REMOVED]

where [Branch 14 Step 2] has been executed then at any step between [Branch 14 Step 2] and [step 12] the Counterparty may choose to send an updated version of F027

The Counterparty executes business use case AD_BUC_10_Subprocess - Update_SED;

[This Branch] Ends.

The Following Branches determine the use of Horizontally defined Sub- Processes for the exchange of Medical Reports.

at any step after [Step 4] the Case Owner may optionally choose to Request and Exchange Medical Data with another Participant

The Case Owner executes business use case H_BUC_08 _Subprocess – Exchange of Medical Data;

[This Branch] Ends.

at any step after [Step 7] the Counterparty may optionally choose to Request and Exchange Medical Data with another Participant

The Counterparty executes business use case H_BUC_08 _Subprocess – Exchange of Medical Data;

[This Branch] Ends.

at any step after [Step 4] the Case Owner may optionally choose to provide Medical Data to another Participant

The Case Owner executes business use case H_BUC_09 _Subprocess – Notification of Medical Information;

[This Branch] Ends.

at any step after [Step 7] the Counterparty may optionally choose to provide Medical Data to another Participant

The Counterparty executes business use case H_BUC_09 _Subprocess – Notification of Medical Information;

[This Branch] Ends.

Exceptions:

Exception 1: at any step between [step 4] and [step 12] the Case Owner may optionally choose to end the process due to unexpected information becoming known to them during the course of their investigations

The Case Owner executes the business use case AD_BUC_01_Subprocess – Close Case;

This BUC Ends.

Includes:

See figure 4.2

Special Requirements:

SR1: Rules about the invoking of Branches:

Business

[Branch 1] to [Branch 14 - May be invoked more than once, per Participant

Horizontals

[Branch 15] to [Branch 20] and [Branch 77] to [Branch 80] - May be invoked more than once, per Participant

[Branch 21] – May be invoked only once, per Participant

Administrative

[Branch 23] to [Branch 76]– May be invoked more than once

SR2: Rules about the destination for each SED Type:

F001 – Must be Sent to all Active Participants

SR3: The term "Send/Sent to All Active Participants" does not include sending it himself (i.e. to the sender institution)

SR4: Active Participants are defined as those Participants identified at [Step 2] and those Participants added through the execution of [Branch 24] and/or [Branch 25] and not removed through the execution of [Branch 24] and/or [Branch 25]

SR5: Branches 1 – 76 are non-interrupting Branches; Exception 1 is an Interrupting Exception.

Assumptions:

N/A

Notes and Issues:

N/A

Request – Reply SEDs

The following table specifies the SED that have a logical pairing to one another, usually this is known as a request-reply pair.

REQUEST SED

REPLY SED(s)

F001

F002

F022

F023

F026

F027

F004

F005

Attachments Allowed

The following table specifies whether attachments are permitted to be included when sending a SED type.

SED

Attachments

F001

Allowed

F002

Allowed

F004

Allowed

F005

Allowed

F022

Allowed

F023

Allowed

F026

Allowed

F027

Allowed

Artefacts used

The following table specifies the artefacts that are used in this Business Use Case:

Artefact name

Artefact type

F001

SED

F002

SED

F004

SED

F005

SED

F022

SED

F023

SED

F026

SED

F027

SED

H_BUC_01_Subprocess

BUC

H_BUC_02_Subprocess

BUC

H_BUC_03a_Subprocess

BUC

H_BUC_03b_Subprocess

BUC

H_BUC_05_Subprocess

BUC

H_BUC_06_Subprocess

BUC

H_BUC_07_Subprocess

BUC

H_BUC_08_Subprocess

BUC

H_BUC_09_Subprocess

BUC

AD_BUC_01_Subprocess – Close Case

BUC

AD_BUC_03_Subprocess – Add Participant

BUC

AD_BUC_04_Subprocess – Remove Participant

BUC

AD_BUC_05_Subprocess – Forward Case

BUC

AD_BUC_06_Subprocess – Invalidate SED

BUC

AD_BUC_07_Subprocess – Reminder

BUC

AD_BUC_10_Subprocess – Update SED

BUC

AD_BUC_11_Subprocess – Business Exception

BUC

AD_BUC_12_Subprocess – Change of Participant

BUC

Business Processes

This chapter describes the Business Use Case Determine competences.

Main Scenario – Case Owner and Counterparty

Sub Processes

GET CLARIFICATION

Figure 3: Get Clarifications as Case Owner

Figure 4: Get Clarifications as Counterparty

GET PERIODS

Figure 5: Get Periods

GET MORE INFO

Figure 6: Get More Info

GET NOTIFICATION

Figure 7: Notification

Appendices

Issues

N/A