NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 41

changes.mady.by.user Warzel, Denise (NIH/NCI) [E]

Saved on

compared with

New Version 42

changes.mady.by.user Warzel, Denise (NIH/NCI) [E]

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Run Transform

CDE Match transforms the Source input into one row per column and permissible value. The command to transform the Source input details is "opt"+"cmd"+"t".

See InstructionsPlease see the CDE Match Instructions document attached to this page. 
Special FeaturesCDE Match has a command "Run DEC Match". This will run the match algorithm on the imported files using just the CDE names, ignoring the permissible values. Click the "Matched DEC" node to see results.

Tips for DEC

...

Import and Update

Validating Lots of RowsSometimes, the system throws an error when attempting to validate more than 4 rows at a time. If that happens, try validating a few rows at a time.
DEC Import Required FieldsDEC Context, OC Concepts, Property Concepts and DEC CD Name/ID are required.
DEC Update Required FieldsThe DEC Public ID and Version are required for an Update. Any other columns that are populated will be treated as a change to teh existing DEC, such as DEC CD, OC Concepts, Property Concepts and Context.

Tips for DEC Match

DescriptionDEC match will run matching algorithms on the names in the template and display results in the "Matched DEC" node. You can select one of the DECs as "Preferred" and then download the results using the Delivery Options feature. 
Context Column

In the Context column, you can enter one or more contexts to search for matching DECs. Separate each DEC with a comma. Do not use spaces between DECs. For example:

XXX,CTEP,CCR

...

After Importing

The results after importing are displayed one row per Value Meaning. All VM Match user results are kept in one database table, and without filtering results, they are all displayed in the same grid. So, after selecting "Go to Data Manager" enter your batch name and click "Apply Filter" to see just your results.

"User Tips" Column

The User Tips column is used by the system instead of the VM Name. Sometimes the VM Name from your form or data is not very representative of the its meaning, or consists of too many terms. If a "User Tip" is entered it is used instead of the VM Name. User Tips can be entered through the front end, or starting in Sprint 47, can be entered into the Template for each row and imported. 

Algorithm

Punctuation and spaces are removed. The "Rule Description" explains why each match was selected. The algorithm does not currently account for spelling errors.

"Run Match" Command

Select the rows to run the match algorithm against and select the "RUN MATCH" Command. Punctuation and spaces are removed. This command will try to find Exact or Like Matches using the VM preferred name for existing VMs, Concept Preferred name and Synonyms.

Click "VM Matched Results" to review recommended matches. If you do not find a desired match, select "Run VM Match Unrestricted".

"Run VM Match Unrestricted" 

Command

This match searches on the longest term in addition to more extensive matches. 

"VM Matched Results "

If there is only one exact match, the system will automatically associate the matched result with the imported VM Name.

If there are multiple matches the user can select a row from "VM Matched Results" and select the "Set Preferred" command.

Multiple Concepts can be selected one at a time to post coordinate concepts. The system will appended the concept to the preferred concept string and generate the resulting name in the order the concepts are selected.  This can be viewed by selecting the Node with the Concept Name to view the selected items. The concepts and be reordered manually, but be sure to reorder the concept names, or clear the results, "Save" and then select concepts again from the matched results. 

Advancing through the imported VMs

When on the "VM Match Header" you can advance to the next VM in your imported file by using the "Rows x of xxx" arrows.

VM Match Header.

Column Order

The main column in VM Match is the VM Name. The processing is designed to find matching concepts based on the name and insert the Concept Name and Concept Code into the table next to the VM NAME unless "User Tips" are entered. This order of the columns makes it easier to populate the PV/VM Template using cut and paste. 

Exporting results

Use the "Delivery Options" command to export the VM Match results into and Excel file. This simplifies creating the list of PV/VMs for PV/VM Import to populate and existing Value Domain.

Tips for Form Imports

Import from REDCap Data Dictionary Format

The Form Import Template is an xslm filetype and contains several Excel Macros, so please be sure to select "Enable Macros" when opening the template. This has been tested for use only on a Windows PC platform, not Mac laptops.

  1. Paste your form content into the template starting on Row 3, column E. At a minimum you must run the Macro "Standardize", see instructions below.
  2. If importing a PhenX REDCap Data Dictionary, you must run "Standardize", then "PhenxStandarize".
  3. "CombineZip" is optional, it automates copying form content into the template from one or more REDCap dictionary csv files. See instructions below. 
  4. Enter a Batch User, Batch Name and ensure that each row has a unique "Seq Id"
  5. Save the Form Template file as csv.
  6. Run Form Import from Manage>>Manage Data (or your bookmarked Favorites)
  7. Select "Import" from the toolbar, then "Conceptual Data Object" from the drop-down
  8. Select the checkbox next to "Form Import RedCAP v1" and select "Import" option from the toolbar (Between "Add New Mapping" and "Go To Data Manager")
  9. Select the "Choose File" and select the Form Import Template from our desktop that you have prepared for loading
  10. Change the last row in the table "Start at Row" from 2 → 3
  11. Select "Import" at the bottom of the Table
  12. After "Success" message, Select "Go to Data Manager" or Manage>>Manage Data>> Form Import (or from your bookmarked Favorites)
  13. Use the filter to search for your form, Click "Apply Filter"
  14. Select "Edit" for your form
  15. Select a "Context" from the dropdown
  16. Save
  17. Select "Parse Form"
  18. If successful, select "Validate Form"
  19. Review the results
  20. After successful Validate, Select "Create Form"
  21. Copy the Public Id and choose "Forms" from Manage>>Manage Data (or your bookmarked Favorites) to view the newly created form in caDSR
Running the Macros

There are 3 macros in the Excel Template. The Macro run key sequence can be viewed by selecting "Tools" from the Excel menu bar, then "Macro". 

Macro NameDescriptionExecute macro
CombineZipThis macro allows the user to import one or more forms in REDCap Data Dictionary format into the Form Template from a desktop folder.  This allows the user to run Form Import on a file containing multiple forms instead of one form import at a time. After choosing the keys as indicated in Execute Macro, select a Folder from your desktop and select the forms that you want to combine and import into the spreadsheet. Then run the "Standardize" macro, instructions below.Choose "Option" + "Command" + "w"
StandardizeEach row must have a Section Header and a few other details. This macro transforms content from REDCap structure into the structure suitable for caDSR Form Import.Choose "Control" + "Shift" + "x"
PhenxStandardizeFiles sent to us by PhenX team contained a row with Question Text "Record ID", and the Protocol ID was inserted into the Field Note Column. This macro removes the extra row for "Record ID", and clears the "Field Note" columnChoose "Control" + "Shift" + "t"
Filling the template with form dataThe 1st row of headings are the REDCap DD headings. The 2nd row of headings match caDSR headings. Enter a short name in the Variable / Field Name, this can be used for matching to an existing CDE. Paste content into the template starting in the 3rd row. Please see the template for the mappings between the REDCap Data Dictionary column names and the caDSR form column names.
Form ContextREDCap does not have a column for Context. Context for all the forms in the templates is selected after importing the template into caDSR.

...