Earlier last week, my colleague
, in which he proposed the idea of "embedded keys" at 01:45 How would James, the fictitious forms designer, do to build a data capture form with these embedded keys?Let's use the same vital signs example. First, we have a few widgets for the physical layer, i.e., variables. Together they form a wireframe of a vital signs data collection module. Each variable has a NCI c-code, a name, and a definition:
Next, we have several widgets for the medical concepts surrounding blood pressure. Similar to the variable widgets, they also have a NCI c-code, a name and a definition.:
In the above diagram, motice how the c-code for Blood Pressure and Vital Signs begins with CUI, or Concept Unique Identifier. The fact is, in the NCI Metathesaurus, these concepts come pre-assembled with relationships, such that:
The last set of widgets are the controlled terminology.
We have all the widgets, allowing us to assemble a well-defined capture form with all necessary "embedded keys".