iCure. eHealth Solutions
Search…
Developer Documentation
iCure Software Modules
Get Started
Create your own Database
Structure your Database
Access your database
Use the Console
Data Stack Module
The Data Stack
iCure Data Model
Hybrid Cloud Storage
Mobile/Web SDKs
REST API calls
Access Rights management
End-to-End-Encryption
ATNA Audit Records
Interoperability Module
IHE XDS calls
IHE IPS call
FHIR API Data Exchange
Freehealth Connector 🇧🇪
Encrypted Data Exchange
Customizable Features Module
Input Forms
Medical Records
Data Dashboards
Custom Connectors
Secure Log-in App
Support
Download
Contact Us
Advanced topics
Healthcare Data
Encryption Key Creation and Storage
Multi-Master database replication
Cross Databases Sharing
Complex queries
Powered By GitBook
Multi-Master database replication
iCure Database is built on Apache CouchDB a web enabled database optimized for use over a network with multiple users, oriented at massively distributed systems with heavy usage that handle "Big Data".

iCure Online/Offline update mode

CouchDB does not store data in a table along with relationships, but uses a B-Tree instead. Each database in every user device is a collection of independent documents that maintain their own data and self-contained schemas. Document metadata contains revision information, so that differences happening while databases were disconnected, may be merged. CouchDB impelements its own version of a Multiversion Concurency Controll system, that supports Master-Master replication.
This enables the iCure to implement a fully Hybrid Cloud Storage. Files are not locked during update and they can be updated both online and offline, allowing the iCure to implement a conflict resolution method.
Locking vs "No-Locking" database files during transactions. Source: CouchDb.org

Data Synchronization in iCure

Under normal conditions database synchronization between connected databases take place in less that 300ms.

Data integrity

Other features include document-level ACID semantics with eventual consistency, (incremental) MapReduce, and (incremental) replication.
CouchDB vs the CAP Theorem. Source: CouchDb.org
CAP Theorem dictates that Databases can be optimized for two of the three most requested qualities: Consistency, Availability and Partition Tolerance. While CouchDB has been optimized for Partition Tolerance and Availability, it has the ability to provide local consistency at local databases and through incremental replication eventual consistency in the iCure database.
Incremental Replication leads to consistency between Db Nodes Source: CouchDb.org
The iCure Data Model has been designed so that it is agnostic to higher level Medical Data conceptual Data Models such as Open EHR and FHIR. It does however make some basic assumptions over the nature of the data, that are to be utilized for. That is in line with the selection of CouchDb. In a healthcare setup one might expect that there are several encryption perimeters and distributed systems, that are to some extend experiencing aberrant disconnections.
Advanced topics - Previous
Encryption Key Creation and Storage
Next - Advanced topics
Cross Databases Sharing
Last modified 1yr ago
Copy link
Outline
iCure Online/Offline update mode
Data Synchronization in iCure
Data integrity