Local processing
Patient profiles, RR intervals, ECG data and analytical results are designed to remain within the local Kardio·AS workflow unless the user explicitly exports or shares them.
Kardio·AS is designed around local acquisition, local analysis and user-controlled study storage. The exact storage location differs between the Windows desktop and Android environments, but core analysis does not require a cloud account.
Patient profiles, RR intervals, ECG data and analytical results are designed to remain within the local Kardio·AS workflow unless the user explicitly exports or shares them.
Bluetooth is used for direct communication with a compatible chest sensor during recording. The sensor connection is part of the local measurement path.
Reports are generated locally. When a user chooses to save, share or export a report or data package, handling of the exported file then depends on the selected destination or third-party application.
Removing application data, deleting study folders or uninstalling software may remove locally stored patient and study information. Important reports and research data should therefore be backed up when necessary.
Patient information may contain sensitive personal or health-related data. Protect access to the computer or smartphone with appropriate operating-system security, and share exported files only with intended recipients.