Logs
Role: Clinical Manager / Administrator
Purpose: The Logs feature records all background system activity happening locally on the Android tablet, including startup events, background jobs, synchronization attempts, and error messages.
Reviewing these logs allows Clinical Managers and Administrators to identify when and why a problem occurred, confirm successful synchronization, and share diagnostic details with technical support teams when issues require escalation.
Logs are local only — they do not show server-side (CDR) activity.
🧭 Navigation
From the sidebar, open System → Logs.
This opens the Logs screen, where each log file represents one day of tablet activity. Logs are automatically created and updated by the SanteDB runtime that powers the SanteIMS Clinical Portal.
📁 About Android Logs
The log viewer displays local system events recorded on the tablet itself. These logs are useful for diagnosing issues before data reaches the CDR.
🧩 Example: If synchronization fails, the tablet’s log shows what happened locally (for example: “server unreachable” or “authentication expired”). The CDR (server) log, viewed by IT administrators, shows what happened on the central system.
When both are compared, the technical team can pinpoint the exact cause of the failure.
🗂️ Log Dashboard Overview
Each file listed in this view is automatically named by date and includes a timestamp, size, and View button.
Log File
File name, automatically generated by date (for example: santedb_20251104.log).
Last Modified
The most recent time the system updated this file.
Size
File size in kilobytes (KB).
View
Opens the log file to display all events recorded that day.
New log files begin automatically at midnight. Older files remain available for viewing or export as needed.
🧠 Understanding Log Levels
Each log entry includes a severity level that indicates how important the message is.
Informational
Routine background events — such as startup, checks, or successful syncs.
No action required; confirms the app is running normally.
Warning
A minor issue or unexpected condition occurred, but the system continued to operate.
Review details. Monitor if repeated frequently.
Error
A process failed or was unable to complete.
Note details or export the log for review by support.
⚠️ Focus on Warning and Error entries. These are the lines that help identify technical issues that may affect synchronization or app performance.
🩺 Step-by-Step: Troubleshooting with Logs
When the Clinical Portal behaves unexpectedly — for example, if a sync fails, the app freezes, or data doesn’t appear correctly — follow this process to review the logs on your Android tablet.
1️⃣ Open Logs
From the sidebar, go to System → Logs.
2️⃣ Identify the Correct File
You may see several log files listed. Each represents one day of system activity. Use the following information to select the right file:
File Name
Includes the date it was created — for example, santedb_20251104.log = November 4 2025.
Match this to the date of the issue.
Last Modified
Shows when the system last updated the file.
Choose the file modified near the time the issue occurred.
File Size (KB)
Larger files contain more detailed entries.
If unsure, start with the larger file.
🧩 Example: If the app froze during synchronization at 10:15 AM on Nov 4, open the file
santedb_20251104.log(last modified near that time). Tap View or Download to open it.
3️⃣ Open the File
Tap View to display all recorded events. Each line represents one system message, warning, or error.
4️⃣ Scroll to the Bottom
Newest entries appear at the end of the file. Start from the bottom when reviewing recent issues.
5️⃣ Look for Warning or Error Entries
Lines marked <Warning> or <Error> often indicate the cause of a failed process or crash.
6️⃣ Read the Lines Before and After
The surrounding entries show what was happening right before or after the error occurred.
7️⃣ Capture the Details
Take a screenshot or export the file for the technical team. Include the time and what you were doing when the issue appeared.
8️⃣ Retry the Action
After resolving the likely cause (e.g., reconnecting Wi-Fi or correcting a user role), retry synchronization or reopen the visit to confirm the issue is fixed.
🧾 Common Examples from Android Logs
Could not setup subscription to SanteDB.Core.Templates.Definition.DataTemplateDefinition
The system couldn’t load one data template during startup.
Harmless if it appears once; ignore unless startup repeatedly fails.
Policy Unrestricted Security Certificate Management was violated by 'beitzb'
The logged-in user tried to open a restricted area (e.g., Certificates).
Ensure you’re logged in as an Administrator.
Error executing PING / : hostname nor servname provided
The tablet was offline or unable to reach the CDR.
Reconnect Wi-Fi or mobile data, then retry sync.
Using slow loading of observation data
Database fallback mode; system is responding slowly.
No action needed unless persistent.
Cannot verify SanteDB.BusinessRules.JavaScript – no assembly file exists
Component not required on Android build.
Safe to ignore.
📤 Exporting a Log File (Android)
Go to System → Logs and locate the relevant log file.
Tap View, then tap Download to Export.
The file saves (/storage/emulated/0/Documents)
Send the file through the approved UNICEF or Ministry secure transfer method.
🚫 Do not email or message log files. They may contain sensitive system information. Always use approved secure transfer channels.
🧩 Connection to CDR and Support Workflow
Tablet logs record local device behavior, not central system activity. If a synchronization or service failure occurs, both sides may need to be checked.
Tablet Logs
From System → Logs
Clinical Manager / Field Support
Server Logs
From the CDR (central system)
System Administrator / UNICEF IT
Network & Sync Issues
Cross-checked using both
SanteSuite / MHMS Technical Team
Even when offline, logs continue recording every local action — including retries — so investigators can trace exactly what the tablet attempted and when.
🩺 Good Practices for Clinical Managers
Review Logs weekly to spot recurring warnings early.
After app updates, confirm startup completes without new errors.
When a sync fails, always check the log before retrying.
After offline use, confirm that the next synchronization uploads successfully.
Keep at least the most recent 7 days of logs for possible follow-up.
🧾 Summary
The Logs module provides insight into how the SanteIMS app is functioning on the Android tablet. By reviewing logs regularly, Clinical Managers can:
Confirm that background services and synchronization are operating correctly.
Detect and describe issues accurately before escalation.
Provide precise evidence when reporting problems to technical support.
Maintain accountability and improve overall system reliability.
Last updated