#146: map CDM-in-i2b2 to existing i2b2 data and/or ontologies --------------------------+---------------------------------- Reporter: dconnolly | Owner: dconnolly Type: enhancement | Status: new Priority: major | Milestone: initial-data-domains Component: data-stds | Keywords: Blocked By: | Blocking: --------------------------+---------------------------------- splitting the "map CDM-in-i2b2 to existing i2b2 data and/or ontologies" part out of #109.
See especially ticket:109#comment:14 Strategies may vary from site to site. For example: - UNMC can deploy changes to their EMR quickly enough to embed mappings there, so that their i2b2 concept codes are based on standard terms (e.g. LOINC:xyz); so all they have to do is put those concept codes in the `c_basecode` column of the CDM-in-i2b2 metadata rows. - KUMC doesn't expect to deploy mappings in their EMR until later in the project, so their i2b2 concept codes are those codes native to the ERM (e.g. COMPONENT_ID:nnn). These component IDs can be assigned to children of the CDM-in-i2b2 concept paths. In either case, a query that uses the CDM-in-i2b2 terminology will find the relevant patients and data. -- Ticket URL: <http://informatics.gpcnetwork.org/trac/Project/ticket/146> gpc-informatics <http://informatics.gpcnetwork.org/> Greater Plains Network - Informatics _______________________________________________ Gpc-dev mailing list Gpc-dev@listserv.kumc.edu http://listserv.kumc.edu/mailman/listinfo/gpc-dev