UC-C-PIC-I: Individual use cases (SERVICES)
Following are the use-case descriptions required for individual consent service operations: viewing, giving, withdrawing and verification of consent as well as getting notifications about changes.
Table of Contents
UC-C-PIC-I-001: View Agreements
UC-C-PIC-I-002: Give consent to fetching data
Option A: Self-Registration to healthcare application
Option B: Assisted registration to healthcare application
Option C: Individual “holding” the data for registering to healthcare application
UC-C-PIC-I-003: Withdraw or update existing consent
UC-C-PIC-I-004: Consent agreement change notification
UC-C-PIC-I-001: View Agreements
Context: Postpartum and infant care
ID | UC-C-PIC-I-001 |
---|---|
Name | View agreements - Postpartum and infant care |
Description | The use case implements the viewing and understanding consent agreements, data policies applied to personal data processing. This includes obtaining copies of the consent agreement. |
Trigger (the event that triggers the use case) |
|
Preconditions (list of conditions that MUST be met in order for the use case to be successful) |
|
Data inputs |
|
Actors (a person, a company or organisation, a computer program, or a computer system - hardware, software, or both) |
Optionally: a data intermediary or a data operator. |
Normal Course (what happens if the event is triggered and the preconditions have been met) |
|
Alternative Course (links to other use cases in case there are different ways how to solve the same use case) |
The individual is able to withdraw consent or update existing consents as the next step of viewing all consent agreements at one place. |
Data output | None |
Post-Conditions (the success criteria) |
|
Exceptions (error situations) | |
Related BBs (working groups related to that particular use case) |
|
Sequence diagram
Diagram Source
UC-C-PIC-I-002: Give consent to fetching data
There are three alternatives possible for giving consent:
The above are detailed in the subsequent chapters.
Option A: Self-Registration to healthcare application
ID | UC-C-PIC-I-002A |
---|---|
Name | Consent - Postpartum and infant care (Give consent) |
Description | The use case allows an end-user to consent to fetch data from existing sources (possibly external to the application) or to manually fill in details during new mother registration.
In this option, the patient is doing a self-registration without any help of a healthcare assistant |
Trigger (the event that triggers the use case) |
|
Preconditions (list of conditions that MUST be met in order for the use case to be successful) |
|
Data inputs |
|
Actors (a person, a company or organisation, a computer program, or a computer system - hardware, software, or both) |
|
Normal Course (what happens if the event is triggered and the preconditions have been met) |
|
Alternative Course (links to other use cases in case there are different ways how to solve the same use case) |
|
Data output |
|
Post-Conditions (the success criteria) |
|
Exceptions (error situations) |
|
Related BBs (working groups related to that particular use case) |
|
Sequence diagram
Option B: Assisted registration to healthcare application
ID | UC-C-PIC-I-002B |
---|---|
Name | Consent - Postpartum and infant care (Give consent) |
Description | The use case implements end-user to consent to fetch data from existing sources or to manually fill in details during new mother registration.
In this option, the patient is assisted by a healthcare assistant |
Trigger (the event that triggers the use case) | Same as UC-C-PIC-I-002A |
Preconditions (list of conditions that MUST be met in order for the use case to be successful) | Same as UC-C-PIC-I-002A |
Data inputs |
Rest same as UC-C-PIC-I-002A |
Actors (a person, a company or organisation, a computer program, or a computer system - hardware, software, or both) |
Rest same as UC-C-PIC-I-002A |
Normal Course (what happens if the event is triggered and the preconditions have been met)
|
|
Alternative Course (links to other use cases in case there are different ways how to solve the same use case) |
|
Data output | Same as UC-C-PIC-I-002A |
Post-Conditions (the success criteria) |
|
Exceptions (error situations) |
|
Related BBs (working groups related to that particular use case) | Same as UC-C-PIC-I-002A |
Sequence diagram
Option C: Individual “holding” the data for registering to healthcare application
ID | UC-C-PIC-I-002C |
---|---|
Name | Consent - Postpartum and infant care (Give consent) |
Description | The use case implements end-user to consent to fetch data from existing sources or to manually fill in details during new mother registration.
In this option, the patient is using a physical or digital document or data card as a data source that is verifiable |
Trigger (the event that triggers the use case) |
|
Preconditions (list of conditions that MUST be met in order for the use case to be successful) | Same as UC-C-PIC-I-002A |
Data inputs | Same as UC-C-PIC-I-002A |
Actors (a person, a company or organisation, a computer program, or a computer system - hardware, software, or both) | Same as UC-C-PIC-I-002A or UC-C-PIC-I-002B
|
Normal Course (what happens if the event is triggered and the preconditions have been met) |
|
Alternative Course (links to other use cases in case there are different ways how to solve the same use case) |
|
Data output |
|
Post-Conditions (the success criteria) |
|
Exceptions (error situations) |
|
Related BBs (working groups related to that particular use case) | Same as UC-C-PIC-I-002A |
Sequence diagram
Note: Here, the sequence shows the case for assisted registration flow. The same applies also for self-registration.
UC-C-PIC-I-003: Withdraw or update existing consent
ID | UC-C-PIC-I-003 |
---|---|
Name | Withdraw or update existing consent - Postpartum and infant care |
Description | The use case implement the withdrawal or updating of existing signed consent agreements. |
Trigger (the event that triggers the use case) |
|
Preconditions (list of conditions that MUST be met in order for the use case to be successful) |
|
Data inputs |
|
Actors (a person, a company or organisation, a computer program, or a computer system - hardware, software, or both) |
Optionally: a data intermediary or a data operator. |
Normal Course (what happens if the event is triggered and the preconditions have been met) |
|
Alternative Course (links to other use cases in case there are different ways how to solve the same use case) |
|
Data output | NA |
Post-Conditions (the success criteria) |
|
Exceptions (error situations) | |
Related BBs (working groups related to that particular use case) |
|
Sequence diagram
UC-C-PIC-I-004: Consent agreement change notification
ID | UC-C-PIC-I-004 |
---|---|
Name | Consent agreement change notification- Postpartum and infant care |
Description | The use case implement the Consent agreement change notification for existing consent agreements |
Trigger (the event that triggers the use case) |
|
Preconditions (list of conditions that MUST be met in order for the use case to be successful) |
|
Data inputs |
|
Actors (a person, a company or organisation, a computer program, or a computer system - hardware, software, or both) |
Optionally: a data intermediary or a data operator. |
Normal Course (what happens if the event is triggered and the preconditions have been met) |
|
Alternative Course (links to other use cases in case there are different ways how to solve the same use case) |
|
Data output | NA |
Post-Conditions (the success criteria) |
|
Exceptions (error situations) | |
Related BBs (working groups related to that particular use case) |
|
Sequence diagram
Diagram Source
Last updated