CCI Data Structure: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 6: Line 6:


three fields as a single record in [[L_CCI_Component table]]:
three fields as a single record in [[L_CCI_Component table]]:
* [[CCI_1_ID]] - first component, <number between 1-3>.<2 letters>
* [[CCI_1_Code]] - first component, <number between 1-3>.<2 letters>
* [[CCI_2_ID]] - second component, <2 numbers><optionally more letters>
* [[CCI_2_Code]] - second component, <2 numbers><optionally more letters>


For each of those fields, a user of the data on the front end will see a description of the meaning of the chosen code. If the dropdown field is activated, the CCI Code component is seen as well. The actual data stored is a long integer unique ID that resolves to the corresponding [[s_CCI_1 table]], [[s_CCI_2 table]].
For each of those fields, a user of the data on the front end will see a description of the meaning of the chosen code. If the dropdown field is activated, the CCI Code component is seen as well. The actual data stored is a long integer unique ID that resolves to the corresponding [[s_CCI_1 table]], [[s_CCI_2 table]].

Revision as of 21:45, 5 February 2018

CCI data is stored in

and can be viewed comprehensively in

three fields as a single record in L_CCI_Component table:

  • CCI_1_Code - first component, <number between 1-3>.<2 letters>
  • CCI_2_Code - second component, <2 numbers><optionally more letters>

For each of those fields, a user of the data on the front end will see a description of the meaning of the chosen code. If the dropdown field is activated, the CCI Code component is seen as well. The actual data stored is a long integer unique ID that resolves to the corresponding s_CCI_1 table, s_CCI_2 table.

Query L CCI Resolver can be used to see the actual CCI code.