KORDEUS - Data retention and deletion concept - Revision history

Stefanseiler at 15:48, 6 February 2026

2026-02-06T15:48:29Z

← Older revision		Revision as of 15:48, 6 February 2026
Line 11:		Line 11:
	** '''data ownership''' - the owner of data has full ownership and may manipulate and keep/delete data as desired.		** '''data ownership''' - the owner of data has full ownership and may manipulate and keep/delete data as desired.
	** '''volatile data 🔥''' - whever the owner of data shares data with another digital, this is done temporarily in the first place. The owner can define on field level which data to make available to the other digital. The future possessor can define on field level, which data he is interested. Although the data is shared, it is still volatile (🔥) and can be physically removed by the data owner <u>at any time</u>. As this is pretransactional, there is no reason and way for the owner to keep the information.		** '''volatile data 🔥''' - whever the owner of data shares data with another digital, this is done temporarily in the first place. The owner can define on field level which data to make available to the other digital. The future possessor can define on field level, which data he is interested. Although the data is shared, it is still volatile (🔥) and can be physically removed by the data owner <u>at any time</u>. As this is pretransactional, there is no reason and way for the owner to keep the information.
	** '''transactional data appropriation''' - whenever the possessor and owner are with mutual consent entering into any transaction, the possessor will typically have to document the transaction in his data-pool and therefore this data becomes [[~~Dev:B-Op~~ data appropriation\|appropriated]]. This means only the specific data required for this transaction (not all shared data) now becomes shared ownership (minimal data principle). These transactions do need to become documented for legal reasons and have a period of time, when this data will be deleted entirely again. At this moment appropriation is reversed and all information is removed and inaccessible to the possessor of information.		** '''transactional data appropriation''' - whenever the possessor and owner are with mutual consent entering into any transaction, the possessor will typically have to document the transaction in his data-pool and therefore this data becomes [[Kordeus PAX data zones and appropriation\|appropriated]]. This means only the specific data required for this transaction (not all shared data) now becomes shared ownership (minimal data principle). These transactions do need to become documented for legal reasons and have a period of time, when this data will be deleted entirely again. At this moment appropriation is reversed and all information is removed and inaccessible to the possessor of information.

	===== Example: Data retention and deletion in healthcare with KORDEUS =====		===== Example: Data retention and deletion in healthcare with KORDEUS =====

Stefanseiler at 15:47, 6 February 2026

2026-02-06T15:47:22Z

← Older revision		Revision as of 15:47, 6 February 2026
Line 10:		Line 10:
	* '''differentiation of possession and ownership''' - to enable all of this, b-op has invented data models, which support this differentiation natively. This differentiates		* '''differentiation of possession and ownership''' - to enable all of this, b-op has invented data models, which support this differentiation natively. This differentiates
	** '''data ownership''' - the owner of data has full ownership and may manipulate and keep/delete data as desired.		** '''data ownership''' - the owner of data has full ownership and may manipulate and keep/delete data as desired.
	** '''volatile data 🔥''' - whever the owner of data shares data with another digital, this is done temporarily. The owner can define on field level which data to make available to the other digital. The future possessor can define on field level, which data he is interested. Although the data is shared, it is still volatile (🔥) and can be physically removed by the data owner at any time. As this is pretransactional, there is no reason and way for the owner to keep the information.		** '''volatile data 🔥''' - whever the owner of data shares data with another digital, this is done temporarily in the first place. The owner can define on field level which data to make available to the other digital. The future possessor can define on field level, which data he is interested. Although the data is shared, it is still volatile (🔥) and can be physically removed by the data owner <u>at any time</u>. As this is pretransactional, there is no reason and way for the owner to keep the information.
	** '''transactional data appropriation''' - whenever the possessor and owner are with mutual consent entering into any transaction, the possessor will typically have to document the transaction in his data-pool and therefore this data becomes [[Dev:B-Op data appropriation\|appropriated]]. This means only the specific data required for this transaction (not all shared data) now becomes shared ownership (minimal data principle). These transactions do need to become documented for legal reasons and have a period of time, when this data will be deleted entirely again. At this moment appropriation is reversed and all information is removed and inaccessible to the possessor of information.		** '''transactional data appropriation''' - whenever the possessor and owner are with mutual consent entering into any transaction, the possessor will typically have to document the transaction in his data-pool and therefore this data becomes [[Dev:B-Op data appropriation\|appropriated]]. This means only the specific data required for this transaction (not all shared data) now becomes shared ownership (minimal data principle). These transactions do need to become documented for legal reasons and have a period of time, when this data will be deleted entirely again. At this moment appropriation is reversed and all information is removed and inaccessible to the possessor of information.

Line 58:		Line 58:
	\|'''CH nDSG'''		\|'''CH nDSG'''
	\|}		\|}

			== See also ==

			* [[Kordeus PAX data zones and appropriation]]

Stefanseiler at 15:45, 6 February 2026

2026-02-06T15:45:59Z

← Older revision		Revision as of 15:45, 6 February 2026
Line 1:		Line 1:
	~~KORDEUS is based on b~~-op~~, which~~ enables:		B-op enables:

	* '''decoupling of data and applications'''		* '''data pools are freely movable (physically)''' between realms. This enables:
	* '''the separation of data by owner''' - each patient receives its own data pool, LH has their data pool.
	* '''data pools are freely movable (physically)''' between realms~~, which~~ enables:
	** hosting the data in the legeslative region where they belong without breaking the system (e.g. EU patients cloud, CH patients cloud, US patients cloud)		** hosting the data in the legeslative region where they belong without breaking the system (e.g. EU patients cloud, CH patients cloud, US patients cloud)
	** adhering to all possible regional data retention and deletion plans at the same time - no decisions or compromises has to be done		** adhering to all possible regional data retention and deletion plans at the same time - no decisions or compromises has to be done
	** protect data owners and their data from laws which dont apply to them		** protect data owners and their data from laws which dont apply to them
	* '''differentiation of possession and ownership'''		* '''decoupling of data and applications''' - Applications can use data of remote digitals according to trust levels defined by the data owner. This enables:
	** '''~~perspectives~~''' - ~~for each~~ data ~~category~~ and ~~possessor you can define retention~~ and ~~deletion policies~~		** applications may read, access and even write data owned by a using digital or its user. This even works, if the application is hosted at another physical location
	** '''~~shared~~ volatile data''' - data can be shared ~~temporarily~~ and ~~revoked from~~ the owner ~~by trust relations~~, ~~which are definable by~~ the owner~~. This happens without destroying referential integrity on temporary possessor~~.		** applications may reside in another legal region than the data owners. This delivers true data sovereignty as the application may adhere to other legal regions then the data owner.
	** '''data appropriation~~'''~~ '''-~~''' by data appropriation~~, ~~data is used in~~ the ~~business process of~~ the ~~processor~~. ~~Deleting may hurt referential integrity and~~ (~~only~~) ~~therefore~~ a data ~~deletion concept~~ is ~~required~~.		* '''differentiation of possession and ownership''' - to enable all of this, b-op has invented data models, which support this differentiation natively. This differentiates
			** '''data ownership''' - the owner of data has full ownership and may manipulate and keep/delete data as desired.
			** '''volatile data 🔥''' - whever the owner of data shares data with another digital, this is done temporarily. The owner can define on field level which data to make available to the other digital. The future possessor can define on field level, which data he is interested. Although the data is shared, it is still volatile (🔥) and can be physically removed by the data owner at any time. As this is pretransactional, there is no reason and way for the owner to keep the information.
			** '''transactional data appropriation''' - whenever the possessor and owner are with mutual consent entering into any transaction, the possessor will typically have to document the transaction in his data-pool and therefore this data becomes [[Dev:B-Op data appropriation\|appropriated]]. This means only the specific data required for this transaction (not all shared data) now becomes shared ownership (minimal data principle). These transactions do need to become documented for legal reasons and have a period of time, when this data will be deleted entirely again. At this moment appropriation is reversed and all information is removed and inaccessible to the possessor of information.

	===== Data retention and deletion in healthcare with KORDEUS =====		===== Example: Data retention and deletion in healthcare with KORDEUS =====
	With thiese new conceptual options, generally all regional data protection laws come with the same requirements on data retention and deletion (see table below):		With thiese new conceptual options, generally all regional data protection laws come with the same requirements on data retention and deletion (see table below):
	{\| class="wikitable"		{\| class="wikitable"
Line 37:		Line 38:
	! colspan="2" \|Service Delivery Information		! colspan="2" \|Service Delivery Information
	\|-		\|-
	\|Policy by		\|Policy by
	'''EU DS-GVO'''		'''EU DS-GVO'''
	\| rowspan="3" \|'''Owner'''		\| rowspan="3" \|'''Owner'''
	(Never automatically,		(Never automatically,

Line 45:		Line 46:
	\| rowspan="3" \|10 years		\| rowspan="3" \|10 years
	\| rowspan="3" \|purpose-limited		\| rowspan="3" \|purpose-limited
	\| rowspan="3" \|'''Owner'''		\| rowspan="3" \|'''Owner'''
	(Never automatically,		(Never automatically,

Line 57:		Line 58:
	\|'''CH nDSG'''		\|'''CH nDSG'''
	\|}		\|}

	~~== See also ==~~

	* [[Kordeus PAX data zones and appropriation]]
	*

Stefanseiler: /* See also */

2026-01-10T15:04:36Z

Stefanseiler at 14:33, 10 January 2026

2026-01-10T14:33:08Z

← Older revision		Revision as of 14:33, 10 January 2026
Line 55:		Line 55:
	\|'''CH nDSG'''		\|'''CH nDSG'''
	\|}		\|}

			== See also ==

			* [[Kordeus PAX Data Zones and appropriation zones]]

Stefanseiler: Created page with "KORDEUS is based on b-op, which enables: * '''decoupling of data and applications''' * '''the separation of data by owner''' - each patient receives its own data pool, LH has their data pool. * '''data pools are freely movable (physically)''' between realms, which enables: hosting the data in the legeslative region where they belong without breaking the system (e.g. EU patients cloud, CH patients cloud, US patients cloud) adhering to all possible regional data ret..."

2026-01-05T12:22:56Z

Created page with "KORDEUS is based on b-op, which enables: * '''decoupling of data and applications''' * '''the separation of data by owner''' - each patient receives its own data pool, LH has their data pool. * '''data pools are freely movable (physically)''' between realms, which enables: ** hosting the data in the legeslative region where they belong without breaking the system (e.g. EU patients cloud, CH patients cloud, US patients cloud) ** adhering to all possible regional data ret..."

New page

KORDEUS is based on b-op, which enables:

* '''decoupling of data and applications'''
* '''the separation of data by owner''' - each patient receives its own data pool, LH has their data pool.
* '''data pools are freely movable (physically)''' between realms, which enables:
** hosting the data in the legeslative region where they belong without breaking the system (e.g. EU patients cloud, CH patients cloud, US patients cloud)
** adhering to all possible regional data retention and deletion plans at the same time - no decisions or compromises has to be done
** protect data owners and their data from laws which dont apply to them
* '''differentiation of possession and ownership'''
** '''perspectives''' - for each data category and possessor you can define retention and deletion policies
** '''shared volatile data''' - data can be shared temporarily and revoked from the owner by trust relations, which are definable by the owner. This happens without destroying referential integrity on temporary possessor.
** '''data appropriation''' '''-''' by data appropriation, data is used in the business process of the processor. Deleting may hurt referential integrity and (only) therefore a data deletion concept is required.

===== Data retention and deletion in healthcare with KORDEUS =====
With thiese new conceptual options, generally all regional data protection laws come with the same requirements on data retention and deletion (see table below):
{| class="wikitable"
!Owner
! colspan="6" |Patient
! colspan="2" |Medical Service Provider
|-
! rowspan="2" |Possesor
! rowspan="2" |Patients
! colspan="2" |Medical Service Provider
! rowspan="2" |Patients
! colspan="2" |Medical Service Provider
! rowspan="2" |Medical Service Provider
! rowspan="2" |Non-medical service provider
|-
!treating
!non-treating
!treating
!non-treating
|-
!Data Category
! colspan="3" |(Medical) Patient-Data
! colspan="3" |(Regular Patient-Data)
! colspan="2" |Service Delivery Information
|-
|Policy by
'''EU DS-GVO'''
| rowspan="3" |'''Owner'''
(Never automatically,
Self-Service anytime)
| rowspan="3" |10 years
| rowspan="3" |purpose-limited
| rowspan="3" |'''Owner'''
(Never automatically,
Self-Service anytime)
| colspan="2" rowspan="3" |purpose-limited
| rowspan="3" |6 years
| rowspan="3" |6 years
|-
|'''HIPAA / US''' Cloud Act
|-
|'''CH nDSG'''
|}

← Older revision		Revision as of 15:04, 10 January 2026
Line 41:		Line 41:
	\| rowspan="3" \|'''Owner'''		\| rowspan="3" \|'''Owner'''
	(Never automatically,		(Never automatically,

	Self-Service anytime)		Self-Service anytime)
	\| rowspan="3" \|10 years		\| rowspan="3" \|10 years
Line 46:		Line 47:
	\| rowspan="3" \|'''Owner'''		\| rowspan="3" \|'''Owner'''
	(Never automatically,		(Never automatically,

	Self-Service anytime)		Self-Service anytime)
	\| colspan="2" rowspan="3" \|purpose-limited		\| colspan="2" rowspan="3" \|purpose-limited
Line 58:		Line 60:
	== See also ==		== See also ==

	* [[Kordeus PAX ~~Data Zones~~ and appropriation ~~zones~~]]		* [[Kordeus PAX data zones and appropriation]]
			*