You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If there's a body_parts defined at the top level, copy it over to the index_codes at the top level
Dealing with the values in value sets:
Map definition to description in general
If definition is just the same text as name, you can skip it (even if capitalized)
The name in FM should come from either value or name in the CDE
If both name and value are defined in CDE, put the CDE value in the FM name and put the CDE name into the FM description field (combine it with the CDE definition separated by a : if definition is also defined)
If the values are just (1, 2, 3, 4, ...) (as in RDES126), just skip the values and use CDE name as the name in the FM
Get the CDE definitions (*.cde.json) from the OIDM CDE repository and convert them all
Create a new branch on findingmodels and put the new *.fm.json files in the defs directory.
OIFM_CDE_000195(forRDES195)OIFMA_CDE_001300(forRDE1300){ // ... "index_codes": [ { "system": "RADELEMENT", "code": "RDES195", "display": "pulmonary nodule" } ] // ... }body_partsdefined at the top level, copy it over to theindex_codesat the top leveldefinitiontodescriptionin generaldefinitionis just the same text asname, you can skip it (even if capitalized)namein FM should come from eithervalueornamein the CDEnameandvalueare defined in CDE, put the CDEvaluein the FMnameand put the CDEnameinto the FMdescriptionfield (combine it with the CDEdefinitionseparated by a:ifdefinitionis also defined)(1, 2, 3, 4, ...)(as in RDES126), just skip the values and use CDEnameas thenamein the FM*.cde.json) from the OIDM CDE repository and convert them allfindingmodelsand put the new*.fm.jsonfiles in thedefsdirectory.