the Id of the user. We encourage using either a v4 UUID or a HL7 Id.
the revision of the user in the database, used for conflict management / optimistic locking.
hard delete (unix epoch in ms) timestamp of the object. Filled automatically when deletePatient is called. format: int64.
Last name of the user. This is the official last name that should be used for official administrative purposes.
Extra properties for the user. Those properties are typed (see class Property)
If permission to modify patient data is granted or revoked
Roles specified for the user
Authorization source for user. 'Database', 'ldap' or 'token' Values: database, ldap, token
State of user's activeness: 'Active', 'Disabled' or 'Registering' Values: ACTIVE, DISABLED, REGISTERING
Username for this user. We encourage using an email address
Hashed version of the password (BCrypt is used for hashing)
Secret token used to verify 2fa
Whether the user has activated two factors authentication
id of the group (practice/hospital) the user is member of
Id of the healthcare party if the user is a healthcare party.
Id of the patient if the user is a patient
Delegations that are automatically generated client side when a new database object is created by this user
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.
email address of the user.
Long lived authentication tokens used for inter-applications authentication.
Encrypted and time-limited Authentication tokens used for inter-applications authentication