Those look like valid NDCs, so they deserve their own concept. Then,
hopefully those concepts will successfully map to an appropriate standard
concept in the DEVICE domain.
The challenge we’ll need to dig into is, why didn’t these NDCs get
identified by our current sources for NDCs, since a code with the same
9-digit prefix (53885024510) did make it in (but didn’t get mapped to a
standard concept). @christian_reich, when these situations occur, how do
we want to address them?
My immediate proposal. Map SOURCE_CONCEPT_ID = 0 and then map the standard
_CONCEPT_ID field to the appropriate place. That appropriate place could
be attempted to be identiifed by first looking to see if the 9-digit prefix
has a home, and if not, then use a tool like Usagi to attempt to find a map.
Chris_Knoll http://forums.ohdsi.org/users/chris_knoll
August 5
@Christian_Reich http://forums.ohdsi.org/users/christian_reich:
I’m working on my ETL for the CDMv5 on Optum, and I have a couple of NDC
codes that I would like to know if the were simply omitted or if I should
not use them for some reason:
NDCs:
53885024510 (n= 2,164,418)
53885024450 (n= 1,265,861)
Those are the top 2, and you can see that makes up 3 million records in our
dataset, so I’m thinking I’d like to address it.
To make sure that those could be valid NDCs, i search for them, and i found
both these two in the same document here:
http://www.hfs.illinois.gov/assets/teststrips.pdf
In this situation, would you create new concepts for these? Or is there
something wrong with these NDCs such that they wouldn’t be identified by
the vocabulary?