OXOA, the
Technology behind it
You have probably already asked yourself how OXOA works exactly. In the following sections, we will answer this question and provide insights into the technical details, the requirements and show the architecture behind the app.
We also recommend having a look at our privacy policy for further information.
What´s behind the term “OXOA platform”?
OXOA offers more than just an app for customers and their relatives. In addition to the displaying of information for the customers, there is also a lot going back and forth. The organization can be contacted directly and can instantly compare the information with the person on file and add it to the system.
Software system at a glance
Like a good building is supported by its foundation, a smooth operation with all services that support and feed the system with information, is of greatest importance for the OXOA platform. Only in combination everything can run smoothly and in sync. A basis is formed by the OXOA backend service, the OXOA customer portal interface, and the login service. Each element serves a specific purpose.
OXOA Backend Service:
- The OXOA backend service functions like a backbone for the platform. It manages all settings and configurations as well as the orchestration of the platform and the rest of the services.
OXOA customer portal interface:
- This interface is offered by the ERP provider. It is used to obtain customer data and forms the bridge between the app and the organization's digital IT administrative system. An example would be the Perigon ERP system by root-service ag.
Login service:
- The login service´s purpose is to authenticate the users, and thus, enables them to actually log in and use the functions accordingly. Figuratively speaking it´s the gatekeeper of the OXOA platform and decides who gets a key to gain access.
In addition, there is the organization's ERP / IT administrative system, in which the customer files are managed, the mail service for sending notification emails, and the SMS service for multi-factor authentication.
For more clarity, it´s worth taking a look at the data flow diagram.
Now that we know which services are in use and how they are connected, we just need to clarify the order in which they are called.
It is worth taking a look at the data flow diagram.
- 1. It all starts with the login. This is where the customer or the customer´s relative logs in.
- 2. If the login was successful, the app receives a valid access token which enables it to access further functions. (If the login wasn´t successful, the process ends here, and different login data need to be tried).
- 3. Afterwards the OXOA backend service is addressed to load the discovery configurations, which are necessary to access the correct OXOA customer portal interface later.
- 4. Then, all according to the individual organization settings, further information is loaded to which the customer has access to.
- 5. Now customer data such as upcoming appointments can be loaded.
Safety first and foremost
As our work involves sensitive data, all communication touch points are encrypted, and it is ensured that no data can be gathered. The process is also structured in a specific way that the access token is never sent to the OXOA backend service. This prevents sensitive data from merging with the OXOA infrastructure.
How to get in touch with us
Make an inquiry via the contact form
on social media
or visit us on site
22. – 24. Oktober 2024
IFAS Messe Zürich