Skip to content

Incorporate CDE definitions from RadElement as FindingModel objects #25

Description

@talkasab
  • Script that converts JSON in the CDE format (v1.0) to a FindingModel
    • Model IDs should look like, OIFM_CDE_000195 (for RDES195)
    • Attribute IDs should look like, OIFMA_CDE_001300 (for RDE1300)
    • Value IDs should follow the pattern
    • At each level, incorporate a code reference to the original CDE:
      {
        // ...
        "index_codes": [
          {
            "system": "RADELEMENT",
            "code": "RDES195",
            "display": "pulmonary nodule"
          }
        ]
        // ...
      }
    • 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.

Metadata

Metadata

Assignees

Labels

contentAdding new content to the repository

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions