Skip to content

Basic progress monitor for mappings #12

@matentzn

Description

@matentzn

We need a way to understand how far we are along the mapping process and how far we still need to go.

Functional requirements:

  • We have statistics and tables about:
    • Number of ICD terms (100%)
    • ICD terms that are
      • not mapped
        • unmapped-in-scope: but in scope (it is a disease)
        • unmapped-excluded: but excluded (because out of scope)
      • mapped.
    • unmapped-in-scope, unmapped-excluded and mapped add up to 100%.

Inputs to analysis:

Output:

  • a table with all ICD codes that have a column category that is either unmapped-excluded, mapped or unmapped-in-scope
  • Summary summary statistics across

### Example Table:

code category
ICD10CM:ABC unmapped-in-scope
ICD10CM:A12 unmapped-excluded

Non-functional requirements:

  • We need to be able to do the same for any incoming ontology - the code should be agnostic to which ontology, mappingset etc it takes as an input
  • Should be delivered as a Makefile goal here
analysis/icd10cm-mapping-progress.tsv: mirror/icd10cm.owl exclusions/icd10.tsv mappings/icd10cm.sssom.tsv
     python........

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions