SanteSuite Help Portal
  • SanteSuite Help Portal
    • Disclaimer
  • Product Overview
    • SanteSuite Products
      • Introducing SanteDB CDR
        • SanteDB Solutions
      • Master Patient Index - SanteMPI
      • Immunization Management System - SanteIMS
      • Privacy & Security - SanteGuard
    • SanteDB Versions
  • Architecture
    • SanteDB Architecture
      • SanteDB History
    • Solution Architecture
    • Software Architecture
      • Publish / Subscribe Architecture
      • New ADO (nuado)
      • Roadmap
    • Data & Information Architecture
      • Conceptual Information Model
        • Concept Dictionary
          • Data Dictionary
        • Acts
          • State Machine
          • Act Relationships
          • Mood Concepts
          • Class Concepts
          • Data Dictionary
        • Entities
          • State Machine
          • Entity Relationships
          • Determiner Codes
          • Class Codes
          • Data Dictionary
        • Null Reasons
        • Extended Data
      • Physical Model
        • Act Data Dictionary
        • Entity Data Dictionary
        • Concept Dictionary Data Dictionary
      • Data Storage Patterns
        • Master Data Storage
      • SanteDB Object Identifiers (OIDs)
    • Security Architecture
    • Privacy Architecture
    • Matching Engine
    • HIE & Interoperability
  • Installation
    • Installation
    • Releases
      • 3.0 Releases
      • Queenston Release
    • Quick Start Guide
      • Seeding ONC Patient Matching Data
    • Operationalizing SanteDB
      • Information Gathering & Analysis
      • Planning & Preparation Work
        • Pre-flight Checklist
        • Develop a Business Architecture
        • Develop an Information Architecture
          • Establishing Minimum Datasets
          • Identity Environment
        • Develop Operational Technology Architecture
        • Developing Privacy Impact Assessments
        • Develop Threat / Risk Assessments
      • Deployment
        • Pre-Flight Checklist
        • Installing Software
          • SanteDB iCDR Server
            • Installation on Virtual or Physical Environments
              • Installation on Microsoft Windows
              • Installation on Linux and Unix
            • Installation using Appliances
              • Using Docker Containers
                • Adding Sample Data
                • Feature Configuration
                • SanteDB within Instant OpenHIE
              • Using Virtual Appliances
            • Installation Qualification
              • Master Patient Index / Client Registry Qualification
                • MPI/CR Test Cases for HL7v2
                  • TEST: OHIE-CR-02-HL7v2
                  • TEST: OHIE-CR-03-HL7v2
                  • TEST: OHIE-CR-04-HL7v2
                  • TEST: OHIE-CR-05-HL7v2
                  • TEST: OHIE-CR-06-HL7v2
                  • TEST: OHIE-CR-07-HL7v2
                  • TEST: OHIE-CR-08-HL7v2
                  • TEST: OHIE-CR-09-HL7v2
                  • TEST: OHIE-CR-10-HL7v2
                  • TEST: OHIE-CR-11-HL7v2
                  • TEST: OHIE-CR-12-HL7v2
                  • TEST: OHIE-CR-13-HL7v2
                  • TEST: OHIE-CR-14-HL7v2
                  • TEST: OHIE-CR-15-HL7v2
                  • TEST: OHIE-CR-16-HL7v2
                  • TEST: OHIE-CR-17-HL7v2
                  • TEST: OHIE-CR-18-HL7v2
                  • TEST: OHIE-CR-01-HL7v2
                  • HL7v2 Test Cases Instructions
                • MPI/CR Test Cases for FHIR
                  • TEST: OHIE-CR-01-FHIR
                  • TEST: OHIE-CR-02-FHIR
                  • TEST: OHIE-CR-03-FHIR
                  • TEST: OHIE-CR-04-FHIR
                  • TEST: OHIE-CR-05-FHIR
                  • TEST: OHIE-CR-06-FHIR
                  • TEST: OHIE-CR-07-FHIR
                  • TEST: OHIE-CR-08-FHIR
                  • TEST: OHIE-CR-09-FHIR
                  • FHIR Test Cases Instructions
              • Security Administration Testing
                • Administrative Panel Validation
                  • User Management Tests
                    • TEST: SECURITY-UM-01
                    • TEST: SECURITY-UM-02
                    • TEST: SECURITY-UM-03
                    • TEST: SECURITY-UM-04
                    • TEST: SECURITY-UM-05
                    • TEST: SECURITY-UM-06
                    • TEST: SECURITY-UM-07
                    • TEST: SECURITY-UM-08
                    • TEST: SECURITY-UM-09
                    • TEST: SECURITY-UM-10
                    • TEST: SECURITY-UM-11
                    • TEST: SECURITY-UM-12
                    • TEST: SECURITY-UM-13
                    • TEST: SECURITY-UM-14
                    • TEST: SECURITY-UM-15
                    • TEST: SECURITY-UM-16
                    • TEST: SECURITY-UM-17
                    • TEST: SECURITY-UM-18
                    • TEST: SECURITY-UM-19
                    • TEST: SECURITY-UM-20
                    • TEST: SECURITY-UM-21
                    • TEST: SECURITY-UM-22
                    • TEST: SECURITY-UM-23
                    • TEST: SECURITY-UM-24
                    • TEST: SECURITY-UM-25
                    • TEST: SECURITY-UM-26
                    • TEST: SECURITY-UM-27
                    • TEST: SECURITY-UM-28
                    • TEST: SECURITY-UM-29
                    • TEST: SECURITY-UM-30
                    • TEST: SECURITY-UM-31
                    • TEST: SECURITY-UM-32
                    • TEST: SECURITY-UM-33
                    • TEST: SECURITY-UM-34
                    • TEST: SECURITY-UM-35
                    • TEST: SECURITY-UM-36
                    • TEST: SECURITY-UM-37
                  • Group/Role Management Tests
                    • TEST: SECURITY-GRM-01
                    • TEST: SECURITY-GRM-02
                    • TEST: SECURITY-GRM-03
                    • TEST: SECURITY-GRM-04
                    • TEST: SECURITY-GRM-05
                    • TEST: SECURITY-GRM-06
                    • TEST: SECURITY-GRM-07
                    • TEST: SECURITY-GRM-08
                    • TEST: SECURITY-GRM-09
                    • TEST: SECURITY-GRM-10
                    • TEST: SECURITY-GRM-11
                    • TEST: SECURITY-GRM-12
                    • TEST: SECURITY-GRM-13
                    • TEST: SECURITY-GRM-14
                    • TEST: SECURITY-GRM-15
                  • Security Policy Management Tests
                    • TEST: SECURITY-PM-01
                    • TEST: SECURITY-PM-02
                    • TEST: SECURITY-PM-03
                    • TEST: SECURITY-PM-04
                  • Device Management Tests
                    • TEST: SECURITY-DM-01
                    • TEST: SECURITY-DM-02
                    • TEST: SECURITY-DM-03
                    • TEST: SECURITY-DM-04
                    • TEST: SECURITY-DM-05
                    • TEST: SECURITY-DM-06
                    • TEST: SECURITY-DM-07
                    • TEST: SECURITY-DM-08
                    • TEST: SECURITY-DM-09
                  • Application Management Tests
                    • TEST: SECURITY-AM-01
                    • TEST: SECURITY-AM-02
                    • TEST: SECURITY-AM-03
                    • TEST: SECURITY-AM-04
                    • TEST: SECURITY-AM-05
                    • TEST: SECURITY-AM-06
                    • TEST: SECURITY-AM-07
                    • TEST: SECURITY-AM-08
          • SanteDB dCDR Instances
            • Installing Web Access Gateway
            • Installing Disconnected Gateway
            • Installing Disconnected Windows Application
            • Installing the dCDR SDK
            • User Interface App Settings
        • Configuring Privacy Controls
        • Post Deployment Tuning
        • Securing SanteDB Configuration
        • Securing SanteDB Databases
        • Securing SanteDB APIs
      • Rollout
    • Demonstration Environments
  • Operations
    • SanteDB Operations
    • Server Administration
      • Configuration Tool
        • Messaging Settings
          • HL7 Version 2 Service
          • FHIR R4 Service
          • GS1 BMS XML Service
          • Health Data Services Interface
          • Administrative Management Interface
        • Diagnostics Settings
        • Persistence Settings
          • Retention Policies
          • Resource Manager Settings
          • Database Connections
        • System Settings
        • Performance Settings
        • Security Settings
          • Data Privacy Filtering
          • Auditing Configuration
        • Operating System Settings
      • Server Configuration File
        • Service API Configuration
          • REST Service Configuration
        • Connection Strings
        • Application Service Context Configuration
        • Applet Configuration
        • Diagnostics Configuration
        • Data Quality Services
      • SanteDB iCDR Host Command
      • Backup Procedures
      • Log File Management
    • CDR Administration
      • SanteDB Administration Portal
        • Logging In
        • Managing Your Profile
        • System Administration
          • Jobs
          • Logs
          • Pub/Sub Manager
          • Server Status
          • Dispatcher Queue
          • Probes
        • Reference Data Administration
          • Place Administration
          • Facility Administration
          • Materials
          • Identity Domain Management
        • Concept Dictionary Administration
          • Concept Sets
          • Concepts
          • Code Systems
        • CDR Administration
          • Importing Data
          • Data Quality Rules
          • Extensions
          • Decision Support Library
            • View CDSS Library
            • Edit CDSS Library
          • Matching Configuration
            • Creating / Viewing Configurations
            • General Configuration
            • Blocking Configuration
            • Scoring Configuration
            • Classification Configuration
            • Testing Match Configuration
            • Match Configuration XML Definition
        • Data Warehouse
        • Reports Centre
        • Security Administration
          • Managing User Accounts
          • Managing Groups
          • Managing Policies
          • Managing Devices
          • Managing Applications
          • Reviewing Audits
      • SanteDB Administration Console
        • User Administration
        • Group / Role Administration
        • Policy Administration
        • Device Administration
        • Application Administration
    • Standard Operating Procedures
      • User Management SOPs
        • SOP: Onboarding Users
        • SOP: User Lockout
        • SOP: Deactivating Users
      • Role Management SOPs
        • SOP: Role Policy Assignment
        • SOP: Assigning Users to Roles
        • SOP: Creating New Roles
      • Device Management SOPs
        • SOP: Onboarding new HL7v2 Device
        • SOP: Onboarding new dCDR Device
      • Application Management SOPs
      • Standard Operating Procedure Template
  • User Guides & Training
    • SanteDB User Guides
    • Common User Interface Elements
    • SanteMPI
      • Getting Started with the MPI
      • SanteMPI Matches
      • SanteMPI Searching
      • SanteMPI Power Search
      • SanteMPI Patient Detail
        • Demographics Tab
          • Demographic Information Panel
          • Identifiers Panel
          • Related Persons Panel
          • Entity Relationships Panel
        • Master Data Management Tab
          • Records of Truth
        • Data Quality Tab
      • SanteMPI Dashboard
    • SanteEMR
      • EMR Administration
        • Care Pathways
        • Visit Types & Flows
        • Clinical Templates
    • SanteGuard
  • Developers
    • Extending & Customizing SanteDB
    • Getting Started
    • SanteDB XML Schemas
    • Applets
      • Applet Use and Lifecycle
      • Applet SDK Components
        • Applet Development Environment
        • SanteDB Brain Bug
        • Package Manager
        • BRE Debugger
      • Applet Structure
      • JavaScript API
      • Business Intelligence Assets
        • BI Asset Definitions
          • Data Sources
          • Parameters
          • Queries
          • Reference Data
          • Views
          • Data Marts
          • Reports
          • Indicators
        • BI Render Controls
      • Localization
      • Customization & Branding
      • Assets
        • HTML Assets
        • HTML Widgets
        • Virtual Assets
      • AngularJS
      • Clinical Decision-Support
        • CDSS Definitions
        • Legacy CDSS
      • Business Rules
      • Dataset Files
      • External Data Maps
      • Applet Solution Packages
      • JavaScript API Reference
      • Recipes
        • Adding Security Policy based on Occupation
        • Assigning a Home Facility
        • Codified Address
        • Generating ID on Registration
    • .NET Plugins
      • Plugin Libraries
      • Host Context & Lifecycle
      • Business Model Objects
      • Services & Configuration
        • Configuration
          • Configuration Panels
          • Custom Docker Feature Configuration
        • Passive Services
        • Daemon Services
        • Service Definitions
          • Ad-Hoc Cache Provider
          • Application Identity Provider
          • Audit Dispatch Service
          • Barcode Generator Provider
          • Business Rules Service
          • Care Plan Generation Service
          • CDSS Clinical Protocol Repository
          • Concept/Terminology Provider
          • Configuration Manager Service
          • Daemon Service
          • Data Archiving Service
          • Data Privacy Enforcement Provider
          • Data Signing Service
          • dCDR Subscription Definition Provider
          • dCDR Subscription Execution Provider
          • Device Identity Provider
          • Exec-Once Message Persistence
          • Freetext Search Provider
          • IDataPersistenceService{TData}
          • IDataPersistenceServiceEx{TModel}
          • IDataQualityConfigurationProviderService
          • Identity Domain Provider
          • IDispatcherQueueManagerService
          • IElevatableIdentityProviderService
          • IExtensionTypeRepository
          • IFastQueryDataPersistenceService{TEntity}
          • IFastQueryRepositoryService{TEntity}
          • IPersistableQueryRepositoryService{TEntity}
          • IPubSubManagerService
          • IRecordMergingService{T}
          • IRepositoryService
          • ISecurityRepositoryService
          • ISqlDataPersistenceService
          • IStoredQueryDataPersistenceService{TEntity}
          • ITagPersistenceService
          • ITemplateDefinitionRepositoryService
          • IThreadPoolService
          • IUnionQueryDataPersistenceService{TEntity}
          • IValidatingRepositoryService{TModel}
          • Job Management Service
          • Localization Provider
          • Mail Repository Provider
          • Name Alias Provider
          • Network Metadata Provider
          • Password Hashing Service
          • Password Validation Service
          • Policy Decision Provider (PDP)
          • Policy Enforcement Provider (PEP)
          • Policy Information Provider (PIP)
          • Primary Data Caching Provider
          • Query Result Scoring Provider
          • Record Matching Configuration Provider
          • Record Matching Provider
          • Record Merging Provider
          • Repository Service
          • Repository Service with Cancellation Support
          • Repository Service with Extended Functions
          • Repository Service with Notification Support
          • Resource Checkout/Locking Provider
          • Resource Patching Provider
          • Resource Pointer Service
          • Role Provider
          • Security Challenge Authentication Provider
          • Security Challenge Storage Provider
          • Session Authentication Provider
          • Session Storage Provider
          • Stateful Query Provider
          • Stock Management Provider
          • Symmetric Encryption Provider
          • TFA/MFA Secret Generator
          • User Identity Provider
          • User Notification Relay Provider
          • User Notification Template Filler
          • User Notification Template Repository
      • Plugin Metadata
      • Database Patching
      • Custom Match Algorithms
      • Unit Testing Framework
      • Digital Signing Requirements
      • .NET API Reference
    • Service APIs
      • OpenID Connect
        • Consent & Privacy
      • Business Intelligence Service (BIS)
      • Administration Management Interface (AMI)
      • Health Data Service Interface (HDSI)
        • HTTP Request Verbs
        • HDSI Query Syntax
          • Filter Functions
        • API Responses
        • Patching
        • MDM Extensions for HDSI
        • Synchronization API
        • Visual Resource Pointer API
      • HL7v2
        • Enabling HL7v2 Interfaces
        • HL7 Authentication
        • SanteDB HL7v2 Implementation
      • HL7 FHIR
        • Enabling FHIR Interfaces
        • SanteDB FHIR Implementation
          • FHIR Subscriptions
          • Related Persons
        • Extending FHIR Functionality
      • GS1 BMS XML
      • Examples
        • Connecting to the FHIR API
        • Obtaining A Session
    • SanteDB Software Publishers
  • Knowledgebase
    • Knowledgebase
      • SanteDB 2.1.161+ on PostgreSQL 10 returns "websearch_to_tsquery" error
      • Upgrading SanteDB iCDR with large databases
      • Upgrading Gateway to SanteDB Langley (v2.0.30+) from SanteDB Kelowna and earlier
      • When sending a National Scoped ID in PID-19 (SSN) you receive "AuthorityUuid" missing error
      • After Installing dCDR you receive an error on SecurityUser
      • When logging into the dCDR you are immediately logged back out
      • PostgreSQL connections fail with block message
      • Backing up HDSI server database
      • You receive an "out of disk space" error on the IMS server
      • Setting up the "sherlock" service
      • Diagnosing service port issues
      • You receive a certificate expired or certificate not found error on startup
      • After updating a database field the values are not reflected in the application layer
      • Diagnosing Submission Errors From Mobile Device
      • Migrating A SanteDB Server
      • Pruning and Cleaning the Database
      • Improving Download Speeds on Slow Connections
      • You receive a client already running error message
      • Resetting the configuration of the Windows & Linux Applications
      • After setting up the application data appears to be missing
      • Disconnected Client Window is Scaled Improperly
      • Fatal Error on Startup
      • Synchronization Issues on Mobile
      • Installation on Mono 4.x does not permit joining of realm
      • Creating A Public Backup
      • Installing the SanteDB Disconnected Server
    • Fixes & Patches
      • 20170721-01
      • 20170725-01
      • 20170803-01
      • 20170804-01
      • 20170913-01
      • 20171003-01
      • 20171011-01
      • 20171016-01
      • 20171023-01
      • 20171030-01
      • 20171108-01
      • 20171124-01
      • 20180126-01
      • 20180131-01
      • 20180211-01
      • 20181112-01
      • 20181113-01
      • 20190322-01
      • 20190522-01
      • 20190625-01
      • 20200105-01
  • OpenIZ
    • About OpenIZ
      • Upgrading from OpenIZ to SanteDB
    • FAQ
    • OpenIZ Demonstration Servers
Powered by GitBook
On this page
  • Entity
  • Entity Tag
  • Entity Version
  • Entity Relationship
  • Entity Note
  • Entity Address
  • Entity Address Component
  • Entity Name
  • Entity Name Component
  • Entity Identifier
  • Entity Extension
  • Entity Telecom Address
  • Place
  • Place Service
  • Application Entity
  • Device Entity
  • Material
  • Manufactured Material
  • Person
  • Person Communication Language
  • Organization
  • Provider
  • Patient

Was this helpful?

  1. Architecture
  2. Data & Information Architecture
  3. Conceptual Information Model
  4. Entities

Data Dictionary

PreviousClass CodesNextNull Reasons

Last updated 4 years ago

Was this helpful?

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.

Entity

The entity table is responsible for the storage of immutable attributes of an entity.

Column

Type

Description

EntityId

[1..1]

UUID

Uniquely identifies the entity within the context of the SanteDB implementation.

TemplateDefinitionId [0..1]

UUID

Identifies the template which the entity instance implements.

ClassConceptId [1..1] ~EntityClassConcept

UUID

Identifies the concept that classifies the entity by a type. The classifier is used to determine “WHAT TYPE” of entity the tuple represents such as a person, material, manufactured material, organization, place, etc.

DeterminerConceptId [1..1] ~EntityDeterminerConcept

UUID

Identifies the concept that classifies or determines the type of entity. This is either an INSTANCE or CLASS concept identifier.

Entity Tag

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.

Column

Type

Description

EntityTagId [1..1]

UUID

Uniquely identifies the entity tag.

EntityId [1..1]

UUID

Identifies the entity to which the tag is associated.

Key [1..1]

VARCHAR

Qualifies the type of tag associated with the entity. That is to say, type of tag is represented in the tuple of the determiner.

Value [1..1]

VARCHAR

A value that carries the data associated with the tag value.

CreationTime [1..1]

DATETIME

Indicates the date/time at which time the tag was created.

CreatedBy [1..1]

UUID

Identifies the user that was responsible for the creation of the tag.

ObsoletionTime [0..1] ?(>CreationTime)

DATETIME

When populated, indicates the time when the tag is no longer associated with the entity.

ObsoletedBy [0..1] ?(ObsoletionTime)

UUID

Identifies the user that was responsible for obsoleting the tag.

Entity Version

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.

Column

Type

Description

EntityVersionId [1..1]

UUID

Uniquely identifies the version of the entity represented in the tuple.

EntityId [1..1]

UUID

Identifies the entity to which this version applies.

ReplacesVersionId [0..1]

UUID

Identifies the version of the entity that the current tuple is responsible for replacing.

StatusConceptId [1..1] ~EntityStatusConcept

UUID

Identifies the status of the entity as of the version represented in the tuple.

CreationTime [1..1]

DATETIME

Indicates the time when the entity was created.

CreatedBy [1..1]

UUID

Identifies the user that was responsible for the creation of the entity.

ObsoletionTime [0..1] ?(>CreationTime)

DATETIME

When populated, indicates the time when the entity version became obsolete.

ObsoletedBy [0..1] ?(ObsoletionTime)

UUID

Identifies the user that was responsible for the obsoleting of the record.

TypeConceptId [0..1]

UUID

Indicates the concept that classifies the subtype of entity. For example, an entity may be a provider; however, the sub-type may be a “physiotherapist”.

Entity Relationship

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.

Column

Type

Description

EntityRelationshipId [1..1]

UUID

Uniquely identifies the entity association.

SourceEntityId [1..1]

UUID

Identifies the source of the entity association.

TargetEntityId [1..1]

UUID

Identifies the target of the entity association.

EffectiveVersionSequenceId [1..1]

UUID

Indicates the version of the source entity at which time this entity association was created or became effective.

ObsoleteVersionSequenceId [0..1]

UUID

When populated, indicates that the entity association is no longer active, and indicates the version of the source entity where the association ceased to be applicable.

RelationshipTypeConceptId [1..1] ~EntityRelationshipType

UUID

Classifies the relationship between the two entities. Can indicate ownership roles such as “Place OWNS Material”, or relationship “Patient CHILD OF Person”.

Quantity [1..1] = 1

INT

Indicates the quantity of target entities contained within the source entity.

Entity Note

The entity note table is used to store textual notes related to an entity.

Column

Type

Description

EntityNoteId [1..1]

UUID

Uniquely identifies the note.

EffectiveVersionSequenceId [1..1]

UUID

Identifies the version of the entity to which the note applies.

ObsoleteVersionSequenceId [0..1]

UUID

When populated, indicates the version of the entity where the note is no longer relevant.

AuthorEntityId [1..1]

UUID

Identifies the entity that was responsible for the authoring of the note.

NoteText [1..1]

TEXT

Indicates the textual content of the note.

Entity Address

The entity address table is used to store address information (physical addresses) related to an entity.

Column

Type

Description

EntityAddressId [1..1]

UUID

Uniquely identifies the entity address.

EffectiveVersionSequenceId [1..1]

UUID

Identifies the version of the entity whereby the address information became active.

ObsoleteVersionSequenceId [0..1]

UUID

When populated, indicates the version of the entity whereby the address is no longer applicable.

AddressUseConceptId [1..1] ~AddressUseType

UUID

Indicates the desired use of the address. Examples include physical visit, vacation home, contact, mailing, etc.

Entity Address Component

The entity address component table is used to store the address components associated with a particular entity address.

Column

Type

Description

EntityAddressComponentId [1..1]

UUID

Uniquely identifies the entity address component.

Value [1..1]

VARCHAR

Identifies the value of the of the address component

ComponentTypeConceptId [1..1] ~NameComponentType

UUID

Classifies the type of address component represented in the value field. For example: street name, city, country, postal code, etc.

EntityAddressId [1..1]

UUID

Identifies the entity address to which the entity address component applies.

Entity Name

The entity name table is used to store master list of names associated with an entity.

Column

Type

Description

EntityNameId [1..1]

UUID

Uniquely identifies the entity name.

EntityNameUseId [1..1]

UUID

Classified the intended use of the entity name. Examples: maiden name, legal name, license name, artist name, etc.

EffectiveVersionSequenceId [1..1]

UUID

Identifies the version of the entity when this name became active.

ObsoleteVersionSequenceId [0..1]

UUID

When populated, identifies the version of the entity where the name is no longer active.

Entity Name Component

The entity name component table is responsible for the storage of name components that comprise an entity name.

Column

Type

Description

NameComponentId [1..1]

UUID

Uniquely identifies the name component.

ValueId [1..1]

UUID

Indicates the phonetic value tuple that stores the name value.

NameComponentTypeConceptId [1..1] ~EntityComponentType

UUID

Classifies the type of name component represented. Examples: first name, title, family name, etc.

EntityNameId [1..1]

UUID

Indicates the entity name to which the name component applies.

Entity Identifier

The entity identifier is table is responsible for the storage of alternate identifies associated with the entity.

Column

Type

Description

EntityIdentifierId [1..1]

UUID

Uniquely identifies the entity identifier.

IdentifierTypeId [1..1]

UUID

Classifies the type of identifier that is represented by the entity identifier. Examples: business identifier, mrn, primary identifier, etc.

EffectiveVersionSequenceId [1..1]

UUID

Indicates the version of the entity when the identifier became active.

ObsoleteVersionSequenceId [0..1]

UUID

When populated, indicates the version of the entity where the identifier is no longer active.

AssigningAuthorityId [1..1]

UUID

Identifies the authority that was responsible for the assigning of the identifier.

IdentifierValue [1..1]

VARCHAR

Indicates the value of the entity identifier.

Entity Extension

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.

Column

Type

Description

EntityExtensionId [1..1]

UUID

Uniquely identifies the extension.

EffectiveVersionSequenceId [1..1]

UUID

Indicates the version of the entity when the extension data did become active.

ObsoleteVersionSequenceId [0..1]

UUID

When populated, indicates the version of the entity where the extension value is no longer applicable.

ExtensionTypeId [1..1]

UUID

Indicates the type, or handler, for the extension data.

ExtensionData [1..1]

VARBINARY

Serialized data that contains the raw value of the extension (serialized and de-serialized by the handler).

ExtensionDisplay [1..1]

VARCHAR

A textual, human readable expression of the extension value which can be displayed on reports, etc.

Entity Telecom Address

The entity telecommunications address table is used to store data related to telecommunications addresses (email, fax, phone, etc.) for an entity.

Column

Type

Description

EntityTelecomId [1..1]

UUID

Uniquely identifies the telecommunications address.

TelecomAddressType [1..1] ~TelecomAddressType

UUID

Classifies the type of address represented (example: phone, fax, email, etc.)

TelecomAddress [1..1]

VARCHAR

The value of the telecommunications address in RFC-2396 format.

TelecomUseConceptId [0..1] ~TelecomAddressUse

UUID

Identifies the intended use of the telecom address. (Example: home, work, etc.)

EffectiveVersionSequenceId [1..1]

UUID

Identifies the version of the entity whereby the telecom address became effective.

ObsoleteVersionSequenceId [0..1]

UUID

When populated, identifies the version of the entity where the telecom address is no longer valid.

Place

The place table represents a specialization of the Entity table which is used to represent physical places such as clinics, outreach activity sites, etc.

Column

Type

Description

EntityVersionId [1..1]

UUID

Identifies the version of the entity to which the place data applies.

MobileInd [1..1] = False

BIT

Indicator that is used to identify that a place is mobile.

Lat [0..1]

FLOAT

The latitudinal position of the place expressed in degrees latitude.

Lng [0..1]

FLOAT

The longitudinal position of the place expressed in degrees longitude.

Place Service

The place service table is used to identify the services that are provided at a particular place. Services may include stocking, transfer depots, immunization.

Column

Type

Description

PlaceServiceId [1..1]

UUID

A unique identifier for the place service.

EffectiveVersionSequenceId [1..1]

UUID

The version of the place entity where the service entry is active.

ObsoleteVersionSequenceId [0..1]

UUID

When populated, indicates the version of the place entity where the service entry is no longer valid.

ServiceConceptId [1..1] ~ServiceType

UUID

Indicates a concept that describes the service offered.

ServiceSchedule [0..1]

XML

An XML expression of the service schedule.

ServiceScheduleType [0..1]

VARCHAR

Identifies the type of data stored in the service schedule column (iCal, GTS, etc.)

Application Entity

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

Column

Type

Description

EntityVersionId [1..1]

UUID

Identifies the version of the entity to which the application data applies.

SoftwareName [0..1]

VARCHAR

Identifies the name of the software package (“EMR Package” is an example)

VersionName [0..1]

VARCHAR

Identifies the version of the software (example: “1.0”)

VendorName [0..1]

VARCHAR

The name of the vendor which distributes the software application (example: “ABC Corp”)

ApplicationId [0..1]

UUID

When populated, links the application entity to a security application.

Device Entity

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.

Column

Type

Description

EntityVersionId [1..1]

UUID

Indicates the version of the entity to which the device data applies.

ManufacturerModel [0..1]

VARCHAR

Indicates the name of the manufacturer of the device.

OperatingSystemName [0..1]

VARCHAR

Indicates the name of the operating system installed on the device.

DeviceId [0..1]

UUID

When populated, identifies the security device associated with the device entity.

Material

A material represents a physical thing (syringe, drug, etc.) which participates in an act or is assigned to a person.

Column

Type

Description

EntityVersionId [1..1]

UUID

Identifies the version of the entity to which the material data applies.

ExpiryTime [1..1]

DATETIME

Indicates the time when the material will expire.

ExpiryTimePrecision [1..1]

CHAR

Indicates the precision that the expiry time has.

FormConceptId [0..1] ~MaterialForm

UUID

Identifies a concept that denotes the form that the material takes. Examples: capsule, injection, nebulizer, etc. For drugs and vaccines, the form will imply the route of administration.

QuantityConceptId [0..1] ~UnitOfMeasure

UUID

Indicates the unit of measure for a single unit of the material. Examples: dose, mL, etc.

Quantity [0..1] = 1

NUMERIC

Indicates the reference quantity in UOM. For example, BCG MMAT is 5 mL of BCG Antigen

IsAdministrative [1..1] = false

BIT

An indicator that is used to identify whether the material is a real material or an administrative material for the purpose of management.

Manufactured Material

A manufactured material is a specialization of a material that is manufactured.

Column

Type

Description

EntityVersionId [1..1]

UUID

Indicates the version of the material to which the specialized data applies.

LotNumber [1..1]

VARCHAR

Indicates the manufacturer lot for the material.

Person

A person is a specialization of Entity that is used to represent a human.

Column

Type

Description

EntityVersionId [1..1]

N/A

The version of the entity to which the person data applies.

DateOfBirth [0..1]

DATE

Indicates the date on which the person entity was born.

DateOfBirthPrecision [0..1]

CHAR

Indicates the precision of the date of birth field.

Person Communication Language

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.

Column

Type

Description

PersonLanaugeCommunication Id [1..1]

UUID

Uniquely identifies the language of communication.

EffectiveVersionSequenceId [1..1]

UUID

Indicates the version of the person entity whereby the language of communication is effective.

ObsoleteVersionSequenceId [0..1]

UUID

When present, indicates the version of the person entity where the language of communication is no longer effective.

LanguageCommunication [1..1] ~ISO639-2

VARCHAR

An ISO-639-2 language code indicating the language preference.

PreferenceIndicator [0..1] = False

BIT

Indicates whether the person prefers the language for communications.

Organization

The organization table represents a specialization of an entity representing a logical organization.

Column

Type

Description

EntityVersionId [1..1]

UUID

Indicates the version of the entity to which the organization specialization applies.

IndustryConceptId [0..1] ~IndustryConcept

UUID

Indicates the industry in which the organization operates. Examples: logistics, healthcare, etc.

Provider

A provider is a specialization of the Person table which is used to store provider related information about a person.

Column

Type

Description

EntityVersionId [1..1]

UUID

Indicates the version of the entity to which the provider specialization applies.

SpecialtyConceptId

[1..1]

UUID

Indicates the primary specialty of the provider at this version of the record.

Patient

The patient entity is a specialization of the Person table which is used to track primary attributes related to a patient.

Column

Type

Description

EntityVersionId [1..1]

UUID

Indicates the version of the entity to which the patient specialization applies.

GenderConceptId

[1..1] ~AdministrativeGender

UUID

Identifies the logical gender concept of the patient. These values are drawn from the administrative gender concept set.

DeceasedTime

[0..1]

DATETIME

When populated, indicates the date/time that the patient was indicated as deceased.

DeceasedTimePrecision

[0..1]

INT

When populated, controls the precision of the value in DeceasedTime

MultipleBirthOrder

[0..1]

INT

When populated, indicates the order of the patient in a multiple birth. A non-null value in this column (0 or -1) indicates special indicators that the exact order is unknown, however the patient is part of a multi-birth.

MaritalStatusConceptId

[0..1] ~MaritalStatus

UUID

The codified status of the patient's marital state (example: single, married, divorced, etc.). Drawn from the MaritalStatus concept set.

EducationLevelConceptId

[0..1] ~EducationLevel

UUID

The codified value indicating the patient's highest level of education obtained (college, high school, etc.)

LivingArrangementConceptId

[0..1] ~LivingArrangement

UUID

The codified value indicating the patient's living arrangement (cohabitating, supervised care, etc.)

ReligionConceptId

[0..1] ~Religion

UUID

The codified value indicating the patient's religion. Note that the religion concept may be blocked based on national profiles and local legislation.

EthnicGroupConceptId

[0..1] ~EthnicGroup

UUID

The codified value indicating the patient's ethnicity.