We have procedure codes in CCI format and these are structured in a hierarchical manner:
- The first character (field 1) of each code represents a CCI Section which identifies broad types of interventions contained in CCI (e.g. diagnostic, therapeutic, obstetrical, etc.)
- The next two characters (field 2) represent CCI Groups which identify logical groupings of related terms (Note: in the case of at least 3 sections, these groups are anatomy-driven, while others are section-dependent)
- The fourth and fifth characters (field 3) represent CCI Interventions which identify generic procedures/interventions contained in a given section (Note: interventions are section dependent).
- The sixth to tenth characters represent the CCI Qualifier which, may be broken into three separate fields each of which has a discrete meaning. In the case of therapeutic interventions, the first two characters relate to the approach/technique used, the next two characters relate to devices used/implanted, and the last character relates to any tissue used (to perform the intervention).
We need to map 100% of the source records to something in omop, even if it is a generic code. Ideally, we want standard codes so that ATLAS is useful, but if necessary, the source_value field can be queried by end users. We started by trying to map these using usagi but the error rate was too high.
To make the manual task manageable, one option is to choose SNOMED codes for the procedures and then add the anatomical site as a modifier. The other option is to try to map to ICD10PCS hierarchical codes.
As a concrete example:
CCI code: 1.YM.52.HA = Drainage, breast using percutaneous (needle) approach (L side is given in another field)
could goto
- ICD10PCS:
2863326: Medical and Surgical @ Skin and Breast @ Drainage @ Breast, Left @ Percutaneous
or - SNOMED
4046266 Drainage procedure
with SNOMED modifier_concept
4298444 Breast Structure
Has anyone else looked at this? Are there advantages when trying to generate cohorts with atlas of one approach over the other? I can cope with some loss of granularity since the source codes will be preserved but I would like to sync with what others are doing with administrative procedure codes from different sources.
Thanks!