Motivation:
No distinction between CDT defined in CCTs and User-definable BDT.
Inappropriate to add CDT AWD PRI data when adding BDT SC.
Must copy the same SCs and AWD PRI data for each duplicate inheritance step. and trank and reflect all rows copied when base SC changes.
As-Is:
Proposal:
Separate CDT / BDT tables to separate the user-definable data and invariant data.
The CDT only has mapping data with the primitive value, and only the BDT has the mapping data with the XBT.
The BDT use the based CDT’s AWD PRI data and managed the code list / agency id list restriction data by BDT_PRI_RESTRI table.
Like as ACC-based ACC, The SCs that defined by based BDT are used current BDT.
To change the property of DT_SC, the corresponding level of BDT must be revised.
Example:
BDT
Tax_ Code. Type
use the SCs from based DT's.
Tax_ Code. Type
Tax_ Code Content. Type
Code Content. Type
Code_1E7368. Type
Code. Type
List Idenfier
List Agency Idenfier
List Version Idenfier