Kordeus PAX data zones and appropriation

The Special Assistance Request is a object which consists of these data zones:

Passenger request information

• Patient / Passenger master data - holds basic information
• Request information - holds itinerary and requested services
• Managing Travel partner information - holds group membership and responsible travel agent information
• Requested services itinerary specific information - holds information on the segments (free capacity, ... )
• Medical state passenger data - these are information which the passenger has to deliver to the MOC to make a fit-to-fly decision
• Medical decision process data - these are information on the internal process of MOC to
• Service delivery plan - information on deliverable services (which service is delivered when and by which delivery partner)
• Service delivery process data - information entered by the delivery partners
• Internal billing information - the services of MOC get billed to the carriers.

Appropriation events & Retention plan

Appropriation of data means that the appropriating parties include volatile data provided by another party are adopted into process information for a certain purpose. Depending on the purpose, the duration of appropriation defined. After duration of appropriation information must be removed from the processing system either by phyical deletion (if referential integrity permits this) and/or anonymization.

Data zone	Owner	Appropriating Party	Purpose of appropriation	Permitted duration of appropriation
				DS-GVO (EU)	nSDC (CH)	US HIPAA & US Cloud Act (USA)
Patient / Passenger master data	PAX	Operation Center	Processing of request	12 months after last communication
			Proove of decision	12 months after last communication or 12 months after requested intererary end (if itinerary is part of request)
			Proove of service	6 years after intererary end, if no itineraray took place 2 years (except with FREMEC)
			Proove of service associated with medical state of PAX	10 years after intererary end, if no itineraray took place 2 years (except with FREMEC)
Request information	PAX	Operation Center	Proove of decision	12 months after last communication or 12 months after requested intererary end (if itinerary is part of request)
			Proove of service	6 years after intererary end, if no itineraray took place 2 years
			Proove of service associated with medical state of PAX	10 years after intererary end, if no itineraray took place 2 years
Managing Travel partner information	Travel Partner	Operation Center	Proove of decision	12 months after last communication or 12 months after requested intererary end (if itinerary is part of request)
Medical state passenger data	PAX	Operation Center	Medical decision process	10 years after intererary end, if no itineraray took place 2 years
			Proove of service associated with medical state of PAX
Service delivery plan	Operation Center	Delivery Partners	Proove of service request	6 years after intererary end
Service delivery process data	Delivery Partner	Operation Center	Proove of service performance	6 years after intererary end

See also

• KORDEUS - Data retention and deletion concept