#243: GPC Procedure Ontology: CPT, HCPCS
---------------------------+---------------------------
Reporter: dconnolly | Owner: gkowalski
Type: design-issue | Status: new
Priority: major | Milestone: data-domains2
Component: data-stds | Keywords:
Blocked By: | Blocking:
---------------------------+---------------------------
For CDM ETL (#145), we need a shared GPC hierarchy to map to the
PROCEDURES table.
As represented on babel, most sites have some design for procedures in
place. Quick survey:
- CMH: ICD9CM
- KUMC: ICD9, CPT (as well as procedure orders in a KUH-local hierarchy)
- MCRF: CPT/HCPCS (I think) under Medical/Procedures
- UIOWA: local orderable hierarchy?
- UMN: CPT
- UMN: CPT, ICD9
- UTHSCSA: ICD9 (Inpatient)
- UTSW: Healthcare Common Procedure Coding System (HCPCS)
- WISC: CPT, HCPCS, ICD9
Design options include:
a. support CPT and ICD9, as per current HERON ETL code
- Note the CPT hierarchy support in HERON isn't great.
b. tackle just CPT initially
- drawback: shared CDM ETL approach would under-report ICD9 data
- drawback: HCPCS data would be "dummed down" (but each procedure with
a HCPCS code would sill be represented using CPT, if I understand
correctly)
c. tackle CPT, ICD9, and HCPCS
- drawback: additional burden for shared ETL code
Recall from DataRepositoryManagement:
the relevant design issue should include:
- identifying clinical workflows the data comes from
- ETL details such as Epic clarity tables or NAACCR ETL scripts
- deliver metadata in i2b2
- as .csv via cdt for sites to use (#76)
- on babel for browsing (#1)
I'd like to see details of how WISC tackles CPT, ICD9, and HCPCS.
--
Ticket URL: <http://informatics.gpcnetwork.org/trac/Project/ticket/243>
gpc-informatics <http://informatics.gpcnetwork.org/>
Greater Plains Network - Informatics
_______________________________________________
Gpc-dev mailing list
[email protected]
http://listserv.kumc.edu/mailman/listinfo/gpc-dev
