Kordeus.PAX: Difference between revisions
Stefanseiler (talk | contribs) |
Stefanseiler (talk | contribs) No edit summary |
||
| Line 40: | Line 40: | ||
** allowing patient proxies (e.g. travel agencies) to file requests on behalf of the patients | ** 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 ce<nowiki/>nters of the carriers | ** interact with operation ce<nowiki/>nters of the carriers | ||
** allowing to see and confir<nowiki/>m pending tasks | ** allowing to see and confir<nowiki/>m pending tasks | ||
Revision as of 12:22, 22 June 2025
Kordeus SARA is an innovative 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 5 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 representing the delivery
- Travel partner digital - supporting passengers on creation and management of their travel service reuquests (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
Each of these parties have:
- their individual business process domains
- specific interactions with each other. You may see digital interaction flows for further information.
Delivery partners
Once services are granted/confirmed, they are typically not delivered by the operation center (OC) themselves, but by delivery partners. OCs push information and tasks to them within the core process. The delivery partners use a PAX Service Delivery Partner Portal to:
- receive and confirm tasks
- confirm service delivery
- communicate with operation centers
Carrier digitals
They define base information, like flight plans, through simple administation tools or interfaces. They offer transactional integration with their backend systems. (ONERES, SIRAX, ... )
Service bundles
Kordeus.PAX consists of three service bundles, each delivering the required tools for the interacting parties:
- SARA.Core - the main tool for management of travel service requests and travel service delivery governance
- PAX Portal - 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
- PAX Base Administration - for carrier's core digital to define service and service delivery processes