Version 2026.05.15 · Effective 15 May 2026
Offline/PWA Usage Notice
How installable app mode, offline cache, delayed sync, and recovery work.
Installable App Behavior
DR.CORD can run as a Progressive Web App when supported by the browser and operating system. Installation depends on Chrome, Edge, or another compatible browser accepting the manifest and service worker.
Installed mode does not change clinical responsibility, user permissions, audit logging, or patient privacy obligations.
Offline Operation
Offline mode is designed to preserve selected workflows during temporary network loss. Drafts, queues, upload metadata, and operational events may be stored locally and replayed when connectivity returns.
Some workflows require network access for final cloud persistence, realtime visibility, authentication refresh, attachment upload, notifications, or cross-device coordination.
Sync Recovery
When the app reconnects, DR.CORD attempts to process sync queues, replay events, recover subscriptions, upload pending media, and run due background jobs.
Users must verify that queued actions have synced before relying on cross-device visibility, reports, billing totals, stock levels, or patient journey completion.
Delayed Synchronization
Offline or degraded network conditions may delay records, notifications, patient timeline updates, inventory movements, invoice status, or lab report availability.
If conflicting local and remote versions exist, DR.CORD may apply conflict handling or surface operational warnings. Staff must resolve conflicts according to clinic policy.
Terms
Rules for using DR.CORD as a clinical operations platform.
Privacy
How DR.CORD handles patient, staff, clinic, authentication, attachment, audit, and sync data.
Storage Policy
Browser storage, IndexedDB, service worker, offline cache, and notification permission behavior.
AI Disclaimer
AI outputs are assistive and must be verified by qualified professionals.