Data Dictionary
Last updated
Last updated
The SanteDB entity model represents a series of tables which are responsible for the tracking of entities within the SanteDB data model. Entities represent people, places, organizations, things, etc. and are responsible for participating within acts in some capacity.
The entity table is responsible for the storage of immutable attributes of an entity.
The entity tag table is used to store version independent tags associated with an entity. A tag does not result in new versions of the entity and is used to track additional data related to security and/or workflow related metadata.
The entity version table is used to store the mutable attributes of an entity, that is to say, any fields associated with an entity that may evolve over the lifespan of the entity are tracked in this table.
The entity association table is used to associate two or more entities together. An association is made between a source entity and a target entity.
The entity note table is used to store textual notes related to an entity.
The entity address table is used to store address information (physical addresses) related to an entity.
The entity address component table is used to store the address components associated with a particular entity address.
The entity name table is used to store master list of names associated with an entity.
The entity name component table is responsible for the storage of name components that comprise an entity name.
The entity identifier is table is responsible for the storage of alternate identifies associated with the entity.
The entity extension table is used to store additional, clinically relevant, versioned data attached to an entity that cannot be stored in the native data model.
The entity telecommunications address table is used to store data related to telecommunications addresses (email, fax, phone, etc.) for an entity.
The place table represents a specialization of the Entity table which is used to represent physical places such as clinics, outreach activity sites, etc.
The place service table is used to identify the services that are provided at a particular place. Services may include stocking, transfer depots, immunization.
The application entity table is used to store entity data related to an application. An application is a software program that runs on a device. This differs from a security application, in that an application may be referenced clinically without needing access to the SanteDB system. For example: The patient uses MyPHR
The device table is used to store clinical information related to a physical device. Like an application entity, this table is used to describe the clinical attributes of a device used in the provisioning of care. Example: Bob’s Insulin Pump. The insulin pump itself may have no security device as it doesn’t require access to SanteDB.
A material represents a physical thing (syringe, drug, etc.) which participates in an act or is assigned to a person.
A manufactured material is a specialization of a material that is manufactured.
A person is a specialization of Entity that is used to represent a human.
The person language communication table is used to store information related to the person’s language preferences. This can be used by the user interface to determine which language to display, however is also clinically relevant to indicate the language in which a patient wishes to receive communciations.
The organization table represents a specialization of an entity representing a logical organization.
A provider is a specialization of the Person table which is used to store provider related information about a person.
The patient entity is a specialization of the Person table which is used to track primary attributes related to a patient.