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
  • Download App
  • Functionality
  • Key Management

Was this helpful?

  1. Customizable Features Module

Secure Log-in App

PreviousCustom ConnectorsNextDownload

Last updated 3 years ago

Was this helpful?

iCure data is protected by end-to-end encryption. Users of the iCure platform must make sure they have a copy of their keys. The iCure Access App, available on the Apple App Store and on Google Play, lets you store a copy of your encryption keys on your phone. It is possible, that a single person owns more than one key, as described in.

The iCure access App integrates seamlessly in the daily practice the management of an intricate token scheme, removing technical complexity for the User, who is often untrained in IT concepts.

Download App

Functionality

The app has has spartan design to enable easier use. The initial screen leads to a scanning mode, that automatically recognizes the function to be performed:

A. Store a Private Key

This way the user does not require to download a key in his computer device, that is cumbersome to use. A downloaded key as a physical file (a printed QR code) or a saved file (stored in the file system) can be easily lost and the fact that this key is unique will result in the loss of all the data, that have been encrypted exclusively with this key.

B. Authenticate using a stored key

Keys are stored in the app and the user can select the key to be used in order to authenticate himself, if he has two discrete roles in the IT system.

C. Recover Key

If the user fails to authenticate 3 times, a key recovery action is initiated via the registered email, so that the keys are being restored. The process differs per iCure implementation.

Key Management

The iCure flow that uses the app ensures that the browser is enabled with the proper authentication key. If the user is being used for the first time, then the app helps the user create and store the new encryption key.

If the key is already stored in the browser, then the app uses the encrypted call of the server to confirm the user credentials.

If the key is not stored in the browser, then the app ascertains that a key exchange takes place between the server and the browser, as the QR on the browser to be scanned also sets the question to the app.

The access App is independently available in and the

In the topics and is described, how a user may have two or more private keys.

iCure owner may enable the . This enables unique users to split and share their keys within a number of other users, even outside iCure, who only own one part of the key, that is completely unusable on its own. In that case, recovery would have to be initiated by the user but approved by every other user, who has a part of the key.

Google Play
App Store
Encryption Key Structure
Access Rights Management
Shamir Secret Sharing algorithm
Encryption Key Structure
iCure Authentication App
new encryption key generation