[CTAKES-107] Add mapping of RxNORM to NDF-RT

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Fix Version/s: future enhancement
• Component/s: ctakes-dictionary-lookup, ctakes-drug-ner
• Assignee: Unassigned
• Reporter: James Joseph Masanz
• Created: 27/Nov/12 17:22
• Updated: 27/Nov/12 17:22

Description

Possibly following this algorithm:

Step 1: For a given RxCUI, find the re-mapped concept identifiers using the
“findRemapped” RxNav API call
a. If more than one identifier is returned, use the last identifier.
Step 2: Query the RxCUI against “getAllRelatedInfo” via RxNav API to retrieve the RxNorm
properties
a. If empty set, then use “getSpellingSuggestions” via RxNav API to find
mentions related to full drug text designation
I. Use “findRxcuiByString” via RxNav API to retrieve new drug name
II. If empty set, use brand name extracted from full drug text if available via
“getAllRelatedInfo” in the RxNav API
i. If still empty, go to Step 2 above using the first word in drug name
ii. Else capture concept node entry
a. Else if not empty, capture concept node entry
Step 3: Check contents of concept node entry:
a. If entry exists for “SDC”, “SBC”, add to list fitByDrugPackList
b. If entry exists for ”SCDC”, “PIN”, add to list fitByIngredientList
c. If entry exists for “DF”, store value as drugForm
Step 4: For each entry in fitByDrugPackList:
a. Use “findConceptsByID” in the NDF-RT API to retrieve NDF-RT data
i. For each NDF-RT concept node (NUI) returned, invoke findVAClass
i. If no ndfrtCode found, use fitByIngredientList using logic at Step 4 above
passing drugForm to findVAClass
findVAClass:
Step 1: Get list of concept properties for a given NUI via “getConceptProperties” in the NDFRT
API
a. For each node returned, use “getAllInfo” in the NDF-RT API
I. If the node is at “VA Product” level, find all the child and sibling nodes
II. For each node, get a list of concept properties via “getConceptProperties”
query in the NDF-RT API
i. If “VA Class” is available, capture ndfrtCode