The term table provides a catalog of all HIEBus terms used to described coded concepts throughout the data model. Columns that refer to this table will be named using the pattern *termid.
This table is a composite of two sources of terms:
- HIEBus Data Sources When integrated into HIEBus, all coded concepts received from a data source create a unique termid in the HIEBus terms model. This “data source” term represents the code and name (or description) that was supplied by the data source. Data source terms are commonly mapped to reference terms in reference code systems maintained by Rosetta.
- Reference Code Systems Rosetta maintains an up-to-date catalog of reference code systems (such as ICD10, HCPCS, LOINC, etc.). These termids are not used in HIEBus data rows. Data source terms will be mapped to reference terms. Most terminology value sets will be composed of reference terms and data source terms will be related to value sets through term mappings. Terms created by Rosetta to represent reference code systems will have column term.domain = Reference.
See also:
Source Concepts
- HIEBus terms
- HIEBus termnamespaces
- HIEBus termmappings
- terminstance
Table Schema
| Name |
Type
|
Description |
| termid |
INTEGER |
Unique identifier (in the context of a deployment) representing a unique term that may be either from a source system (claims, clinical data), or a canonical reference set (e.g. LOINC, CPT).
|
| deployment |
VARCHAR |
The name of the originating HIEBus deployment. In some data marts, terms may be consolidated across deployments for analysis. Termids are unique within a deployment. In multi-deployment data marts, deployment+termid uniquely identifies a term.
|
| tenant |
VARCHAR |
The name of the originating HIEBus tenant. NULL for terms in reference code systems indicated by domain = Reference.
|
| code |
VARCHAR |
Code of the term (e.g. Female or Y93.D).
|
| display |
VARCHAR |
Human-readable label of the term.
|
| domain |
VARCHAR |
Corresponds to “family” in HIEBus. This column will be populated with “Reference” for terms in reference code systems that are created and managed by Rosetta.
|
| codesystem |
VARCHAR |
The name of the code system (corresponds to HIEBus termnamespace.name) for the term. For example: ICD10, HCPCS, LOINC, etc. for terms in a reference system. If the term originated from a data source, this commonly describes the data source.
|
| codesystemidentifier |
VARCHAR |
Corresponds to HIEBus termnamespace.code.
|
| primarymappedcode |
VARCHAR |
NULL if the term is unmapped or domain = Reference. If the term originated from a data source and has one or more term mappings, a primary mapping is selected via a prioritizaiton algorithm. The code of the primary mapped term is represented in this column. Refer to the termmappings table for alternate term mappings.
|
| primarymappeddisplay |
VARCHAR |
NULL if the term is unmapped or domain = Reference. The display name of the term associated with the primarymappedcode.
|
| primarymappedcodesystem |
VARCHAR |
NULL if the term is unmapped or domain = Reference. The codesystem of the term associated with the primarymappedcode.
|
| instances |
INTEGER |
If domain = Reference, the number of data rows in HIEBus that include a reference to a termid THAT IS MAPPED to this termid. Otherwise, the number of data rows in HIEBus that include a reference to the termid.
|
| inserteddate |
TIMESTAMP |
The date and time the term was first created in HIEBus.
|
| mostrecentmappingdate |
TIMESTAMP |
The date and time of the most recent term mapping that uses this term as a sourcetermid.
|
Back to Tables
