Entity Data Dictionary

The Conceptual Entity Data Dictionary expressed in ADO.NET tables.

Physical Table	Conceptual Entity	Description
app_ent_tbl	Application Entity	This table is used to describe the clinical attributes of an application such as vendor, version etc. This differs from the security definition of an application. A security application may exist without a clinical application existing.
dev_ent_tbl	Device Entity	This table is used to describe the clinical attributes of a device. For example an insulin pump. Like an application, a clinical device may not be a security device or vice versa. For example when describing an event in which a device was involved , but that device does not need access to the system.
ent_addr_cmp_tbl	Entity Address Component	This table is used to store entity address components. In order to normalize addresses, the values of the addresses themselves are not stored in this table, rather, stored in a unique datatable.
ent_addr_cmp_val_tbl	N/A	This table stores the unique values of all address components found in the SanteDB system.
ent_addr_tbl	Entity Address	Stores information related to an entity’s physical, mailing or other postal addresses
ent_ext_tbl	Entity Extension	Stores the data related to entity extensions. Entity extensions are versioned, additional values for a particular entity.
ent_id_tbl	Entity Identifier	The entity identifier table is used to store alternate, external identifiers associated with a particular entity
ent_name_cmp_tbl	Entity Name Component	The entity name component table is used to store the individual components (family, given, prefix, suffix) of an entity’s name.
ent_name_tbl	Entity Name	The entity name table is used to store the names associated with a particular entity. For example, a patient may have a married and maiden name.
ent_note_tbl	Entity Notes	The entity note table is used to store freetext notes about a patient.
ent_rel_tbl	Entity Relationship	Entity relationships are relationships between one or more entities with one another. For example, a service delivery location may have one or more employees.
ent_tag_tbl	Entity Tags	Entity tags are non-versioned extensions of an entity. That is their value can change however changes are not tracked over time.
ent_tbl	Entity	Represents a non-versioned parts of the core entity such as class, determiner, etc.
ent_tel_tbl	Entity Telecom Addresses	Stores telecommunications addresses related to the entity and their associated type (phone, email, etc) and use (work, home, mobile, etc.)
ent_vrsn_tbl	Entity Versions	This table is used to store the data which can change over time for an entity such as status, additional classifier, etc.
mat_tbl	Material	This table is used to store information related to materials.
mmat_tbl	Manufactured Materials	This table is used to store information related to manufactured materials.
org_tbl	Organization	This table is used to store information related to organizations, which are groupings of people, places for administrative purposes.
pat_tbl	Patient	This table is used to store information related to patients, or those who are receiving care.
plc_svc_tbl	Place Services	This table is used to store information related to the services which occur at a particular place.
plc_tbl	Place	This table is used to store information about a physical place. In Open IZ places can represent delivery locations (hospitals, clinics, etc.) or administrative units (states, cities, etc.)
psn_lng_tbl	Person Languages	This table is used to store information related to the languages which a person (including patients) speak.
psn_tbl	Person	This table is used to store information related to persons (including patients and providers).
pvdr_tbl	Provider	This table is used to store information related to providers (persons who deliver care).
usr_ent_tbl	User Entity	This table is used to link the security subsystem for users to the clinical subsystem of entities (as entities are the ones who participate in Acts rather than Security Users).