iCure. eHealth Solutions
  • Developer Documentation
  • iCure Software Modules
  • Get Started
    • Create your own Database
      • Receive an invitation
      • Create new User
      • Create a new Healthcare Party
    • Structure your Database
    • Access your database
    • Use the Console
  • Data Stack Module
    • The Data Stack
      • Install iCure
      • Get Started with a Database
    • iCure Data Model
      • Overview
      • User
        • Permission
      • Healthcare Party
      • Patient
        • Insurability
        • Relationship
        • Patient Hcp care period
          • Referral period
      • Contact
        • Service
          • Content
            • Medication
              • Regimen item
            • Measure
        • SubContact
      • Healthcare Element
        • Care team member
        • Healthcare approach
      • Form
      • Additional Classes
        • AccessLog
        • Address
          • Telecom
        • Message
        • Document
        • FilterChain
          • Filter
          • Predicate
        • Group
        • Insurance
        • Invoice
          • Invoicing code
        • Tarification
          • Valorisation
    • Hybrid Cloud Storage
    • Mobile/Web SDKs
      • JavaScript/Typescript
        • Setting up your environment
        • Logging in
        • Managing patients
        • iCure for MedTech: Getting Started
          • Exchange data using FHIR model
          • Exchange data using iCure SDK
      • Java/Kotlin
      • Swift/Objective C
    • REST API calls
      • User
      • Patient
      • HealthcareParty
      • Contact
      • HealthcareElement
      • Form
      • Document
      • Message
      • Invoice
      • Additional endpoints
        • AccessLog
        • Authentication
        • Codification
        • Document template
        • Entity reference
        • Entity template
        • Insurance
        • Receipt
        • Tarification
    • Access Rights management
    • End-to-End-Encryption
    • ATNA Audit Records
  • Interoperability Module
    • IHE XDS calls
      • The XDS Concept
      • ITI-18 get associations api call
      • ITI-41 provide and register document set api call
      • Iti-42 register document set api call
    • IHE IPS call
      • The IPS Concept
    • FHIR API Data Exchange
      • The FHIR Concept
    • Freehealth Connector 🇧🇪
    • Encrypted Data Exchange
      • Internal
      • External
  • Customizable Features Module
    • Input Forms
    • Medical Records
    • Data Dashboards
    • Custom Connectors
    • Secure Log-in App
  • Support
    • Download
    • Contact Us
  • Advanced topics
    • Healthcare Data
      • Business intelligence
      • Anonymized Data
    • Encryption Key Creation and Storage
    • Multi-Master database replication
    • Cross Databases Sharing
    • Complex queries
Powered by GitBook
On this page
  • A full feature Data Stack
  • Secured by end-to-end encryption

Was this helpful?

  1. Data Stack Module

The Data Stack

PreviousUse the ConsoleNextInstall iCure

Last updated 3 years ago

Was this helpful?

A full feature Data Stack

The iCure Data Stack facilitates a smooth data management cycle, that includes Data creation, Structuring, Transformation, Sharing, Storage, Recalling, Analyzing and Disposal.

Every iCure implementation regardless of size utilizes the full Data Stack properties and features, to ensure that all data are managed scalably_ _to the highest standards.

The iCure Data Stack has been built on top of the Data Storage and ensures the Integrity, Security, Structure and Exchange of Data in a compliant manner. It is also Data Model agnostic, as it imposes minimal restrictions to the type and structure of stored Data.

Secured by end-to-end encryption

When you look at the definition of a or a , you see many properties that are related to encryption. They are detailed . Understanding how they are used to guarantee the privacy of the data is not a small task but fortunately, you do not need to grasp the intricacies of the cryptographic scheme to encrypt and decrypt the data.

The high-level methods of the APIs take care of the encryption for you if you respect a few steps :

  1. Always use the APIs returned by the Api() method. Those APIs have been instrumented to automatically encrypt or decrypt the data before transmitting it.

  2. Always call newInstance on the API before using a model object. This method makes sure that all the information needed to handle the encryption properly has been added to the model before you use it.

  3. Make sure that your private key is available before starting to use APIs that rely on encryption.

patient
contact
here