Page History
Data Sources for Composite Views
Composite views need to get data from snapshot views. In most cases the requirements will be met by use of the current snapshot view
| Footnote Macro |
|---|
As noted in 4.6.3. Optimizing Versioned Table Views the current snapshot may be represented as tables or database views. While this may make a difference to performance it does not make any difference to the design of composite views. |
of each of the relevant tables. However, when reviewing past data the relevant retrospective views will need to be accessed. For this reason, consideration should be given to creating similar composite views for each supported snapshot view
| Footnote Macro |
|---|
In the SNOMED CT example database, most composite views have been created for the current snapshot (snap) and for both of the configurable retrospective snapshot views (snap1 and snap2). However, composite views that access either the transitive closure (snap_transclose) or proximal primitives (snap_proxprim) are not supported for the retrospective snapshots. This is because those tables are at present on available for the current snapshot view. |
.
Most composite views should to gather all the required data from the table views for the same snapshot as illustrated in .
| Composite View | snap_pref | snap1_pref | snap2_pref |
| Description View | snap_description | snap1_description | snap2_description |
| Language Refset View | snap_refset_language | snap1_refset_language | snap2_refset_language |
Composite views may themselves gather data from other composite views. For example as shown in gets preferred term data from the preferred term composite views shown above.
| Composite View | snap_rel_pref | snap1_rel_pref | snap2_rel_pref |
| Concept View | snap_concept | snap1_concept | snap2_concept |
| Relationship View | snap_relationship | snap1_relationship | snap2_relationship |
Preferred Term View | snap_pref | snap1_pref | snap2_pref |
Composite views designed to support review of changes may gather data from different views as illustrated in .
| Composite View | delta_inactive_concepts | delta1_inactive_concepts | delta2_inactive_concepts | ||
| Concept View | delta_concept | delta1_concept | delta2_concept | ||
| Association Refset View | snap_refset_association | snap_refset_association | snap_refset_association | ||
| Attribute Value Refset View | snap_refset_attributevalue | snap_refset_attributevalue | snap_refset_attributevalue | ||
Preferred Term View | snap_pref | snap_pref | snap_pref | ||
Fully Specified Name View
| snap_fsn | snap_fsn | snap_fsn |
Representation of Composite Views
Composite views should be represented as database views rather than a physical database tables. Composite views denormalize data by combining the same data in different views therefore attempts to represent composite views as database tables is likely to rapidly multiply the size of the database. The example below is just one of many cases where creating concrete database tables to accommodate composite views might seem an attractive idea. However, pursuing this would create redundant data with few benefits, a major impact on storage requirements and a significantly more complex maintenance process when reviewing and installing future release packages. In contrast, representing composite views as database views, ensures the data is derived in real-time from tables representing the authoritative content of the full and/or snapshot release files.
| Info | ||
|---|---|---|
| ||
Most English language descriptions are either preferred or acceptable in both US and GB english. Therefore instantiating tables that represent the sets of preferred and acceptable terms in either or both dialects would not only duplicate much of the data in that table but would require even more space to duplicate the relevant indexes. In addition to the impact of disk space, data duplicated in these composite tables would need updating to take account of new releases. |
| Display Footnotes Macro |
|---|
Overview
Content Tools
Apps