Kordeus.PAX: Difference between revisions

From Kordeus Wiki
Jump to navigation Jump to search
Stefanseiler (talk | contribs)
Stefanseiler (talk | contribs)
Line 24: Line 24:


== Data domains & data ownership ==
== Data domains & data ownership ==
A [[Travel assistance service request|travel assistance service requests]] holds these data domains, which are each handled differently due to the ownership and sensitivity of contained information:
A [[Travel assistance service request|travel assistance service requests]] holds these data domains, which are each handled differently due to the ownership and sensitivity of contained information. See this article on [[SARA data domains]] for further details.
{| class="wikitable"
|+
!O=Owner, S=Shared, P=Processor
! colspan="4" |Ownership & Storage
! rowspan="2" |Details
|-
!
!Agent
!PAX
!MOC
!Delivery Partners
|-
|Travel Group information
|O
|S
|S
|
|
|-
|Personal information
|S
|O
|S
|
|
|-
|Medical information
|S
|O
|P
|
|
|-
|Journey Information
|S
|S
|O
|
|Shared ownership, based on transport contract
|-
|[[Travel Assistance Service Case]]
|S
|S
|O
|P
|This holds the case and its meta-information
|-
|Delivery requests & instructions
|
|
|O
|P
|
|-
|Delivery status information
|
|
|O
|P
|LH ownership, due to service contract
|}


== Service bundles ==
== Service bundles ==

Revision as of 05:10, 26 June 2025

Interacting parties of Kordeus.PAX

Kordeus SARA is an platform designed to streamline the end-to-end management of travel assistance service requests through a secure, peer-to-peer ecosystem.

Why SARA stands out from traditional centralized or generic task platforms:

  • Purpose-built for travel assistance – Tailored specifically to meet the complex needs of the travel assistance industry.
  • Data ownership, redefined – Ensures that individuals maintain full control over their personal data at all times.
  • Secure by design – Enables trusted, encrypted communication between all involved parties.
  • Scalable and open architecture – Ready to grow and adapt with your business needs.
  • Compliance without compromise – Supports data residency in required legal jurisdictions while operating as a unified system.

Interacting parties & Business processes

The travel assistance service delivery ecosystem hosts 6 different roles, which are represented by types of digitals:

  • Carrier digitals - delivering core information on available services and access to reservation systems
  • Passenger digital - storing health information and status of special assistance requests from the patients perspective.
  • Travel partner digital - supporting passengers on creation and management of their travel service requests (optional)
  • Travel assistance service operation center digital - the operation central, which processes requests and governs the service delivery process. Sometimes also called medical operation center (MOC)
  • Delivery partner digital - the partners of the operation center digital, which ultimately perform the services ordered by the operation center
  • PAX Portal digital - this is an application digital, typically operated by a carrier, to allow its passengers (PAX) or associated travel agents to create file and manage their special assistance requests

Each of these parties have:

Data domains & data ownership

A travel assistance service requests holds these data domains, which are each handled differently due to the ownership and sensitivity of contained information. See this article on SARA data domains for further details.

O=Owner, S=Shared, P=Processor Ownership & Storage Details
Agent PAX MOC Delivery Partners
Travel Group information O S S
Personal information S O S
Medical information S O P
Journey Information S S O Shared ownership, based on transport contract
Travel Assistance Service Case S S O P This holds the case and its meta-information
Delivery requests & instructions O P
Delivery status information O P LH ownership, due to service contract

Service bundles

Kordeus.PAX consists of three service bundles, each delivering the required tools for the interacting parties:

  • Carrier Admininistration Tools - for carrier's core digital to define service and service delivery processes
  • Travel Service Operation Center Administration Tools - the tools for defining:
    • service delivery options and constraints
    • process automation rules within SARA.Core
  • SARA.PAXPortal - for passengers and their agents
    • allowing patients to request services and communicate with the operations centers responsible at the travel carrier
    • allowing patient proxies (e.g. travel agencies) to file requests on behalf of the patients
  • SARA.DeliveryPartnerPortal - for service delivery partner digitals
    • interact with operation centers of the carriers
    • allowing to see and confirm pending tasks
  • SARA.Core - the main tool for management of travel service requests and travel service delivery governance
  • SARA.ProcessAutomationEngine - the main tool for automation of work in SARA.Core
  • SARA.PartnerCreationPortal - the main tool for creating new digitals, which can take part in the travel assistance service peer-to-peer ecosystem.

See also