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

Was this helpful?

  1. Data Stack Module
  2. iCure Data Model

User

This entity is a root level object. It represents an user that can log in to the iCure platform. It is serialized in JSON and saved in the underlying icure-base CouchDB database.

Properties

Property
Type
Description

id *

the Id of the user. We encourage using either a v4 UUID or a HL7 Id.

rev

the revision of the user in the database, used for conflict management / optimistic locking.

deletionDate

hard delete (unix epoch in ms) timestamp of the object. Filled automatically when deletePatient is called. format: int64.

created

format: int64.

name

Last name of the user. This is the official last name that should be used for official administrative purposes.

properties *

Extra properties for the user. Those properties are typed (see class Property)

permissions *

If permission to modify patient data is granted or revoked

roles *

Roles specified for the user

type

Authorization source for user. 'Database', 'ldap' or 'token' Values: database, ldap, token

status

State of user's activeness: 'Active', 'Disabled' or 'Registering' Values: ACTIVE, DISABLED, REGISTERING

login

Username for this user. We encourage using an email address

passwordHash

Hashed version of the password (BCrypt is used for hashing)

secret

Secret token used to verify 2fa

use2fa

Whether the user has activated two factors authentication

groupId

id of the group (practice/hospital) the user is member of

healthcarePartyId

Id of the healthcare party if the user is a healthcare party.

patientId

Id of the patient if the user is a patient

autoDelegations *

Delegations that are automatically generated client side when a new database object is created by this user

createdDate

the timestamp (unix epoch in ms) of creation of the user, will be filled automatically if missing. Not enforced by the application server. format: date-time.

termsOfUseDate

the timestamp (unix epoch in ms) of the latest validation of the terms of use of the application format: date-time.

email

email address of the user.

applicationTokens *

Long lived authentication tokens used for inter-applications authentication.

authenticationTokens *

Encrypted and time-limited Authentication tokens used for inter-applications authentication

PreviousOverviewNextPermission

Last updated 3 years ago

Was this helpful?

String
String
Long
Long
String
List
List
List
String
String
String
String
String
Boolean
String
String
String
Map
Date
Date
String
Map
Map