Changes between Version 35 and Version 36 of RxNormForVista


Ignore:
Timestamp:
Nov 21, 2013, 5:56:53 PM (10 years ago)
Author:
Sam Habiel
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • RxNormForVista

    v35 v36  
    1212== Why do I want this? ==
    1313!RxNorm is necessary for interoperability with other systems. If you use VISTA alone without having to talk to any other system, then you don't need !RxNorm. However, if you perform external drug interactions, send CCDA documents, or archive patient records for CCR, you are going to need !RxNorm. For Meaningful Use, you are required to have !RxNorm for various purposes.
    14 
    15 
    1614
    1715== What does this release contain? ==
    … …  
    4644
    4745== Contents of the KIDS file ==
    48 
    49 
     46=== File list ===
     47||'''Name'''||'''Number'''||'''Global'''||'''!RxNorm NLM File'''||'''Approx # of entries at the end of 2013'''||
     48||RXNORM CONCEPT NAMES AND SOURCES||176.001||!^C0CRXN(176.001)||RXNCONSO.RRF||1,000,000||
     49||RXNORM SIMPLE CONCEPT AND ATOM ATTRIBUTES||176.002||!^C0CRXN(176.002)||RXNSAT.RRF||7,000,000||
     50||RXNORM SOURCE INFORMATION||176.003||!^C0CRXN(176.003)||RXNSAB.RRF||13||
     51||RXNORM SEMANTIC TYPES||176.004||!^C0CRXN(176.004)||RXNSTY.RRF||400,000||
     52||RXNORM RELATED CONCEPTS||176.005||!^C0CRXN(176.005)||RXNREL.RRF||5,000,000||
     53||RXNORM DOCUMENTATION FOR ABBREVIATED VALUES||176.006||!^C0CRXN(176.006)||RXNDOC.RRF||3,000||
     54
     55=== Pharmacy Files Computed Fields ===
     56||'''File Name'''||'''File number'''||'''Field Name'''||'''Field Number'''||'''Description'''||
     57||DRUG||50||RXNCUI||176.001||Pointer to the Semantic Clinical Drug in 176.001 that corresponds to this drug.||
     58||DRUG||50||RXN SCD NAME||176.002||Canonical Clinical Drug name according to !RxNorm.||
     59||VA PRODUCT||50.68||COMPUTED GCNSEQNO||176.001||Multiple of GCNs corresponding to a VA PRODUCT||
    5060
    5161=== Routines ===
    … …  
    5767
    5868== What can I do with !RxNorm ==
    59 === User Mode Interactions ===
     69=== User Mode use ===
    6070All files are shipped with no file access code security for reading, and as such they can be read by all users if they are granted access to Fileman and don't have Kernel Part III security turned on. If Kernel Part III security is turned on, you will need to grant users access to files 176.001 through 176.006. If you don't know what Part III security is, then you don't have it.
    6171
    … …  
    351361
    352362==== Automatic Drug Addition API using RxNorm ====
    353 To add a drug to the drug file using the RxNorm CUI, call the following entry point:
     363To add a drug to the drug file using the !RxNorm CUI, call the following entry point:
    354364
    355365{{{
    … …  
    359369Please note that this routine does not check to see if the drug is already there; it will add it again.
    360370
    361 This routine can be enhanced to use the barcode to figure out which drug it is that is being added from RxNorm. As such, it will enable you to add drugs to the drug file by just bar-code scanning them.
     371This routine can be enhanced to use the barcode to figure out which drug it is that is being added from !RxNorm. As such, it will enable you to add drugs to the drug file by just bar-code scanning them.
    362372
    363373== Technical Details ==
    … …  
    429439
    430440=== Supported APIs ===
    431 All non-testing APIs in C0CRXNLK are supported.
    432 D IMPORT^C0CRXNRD
    433 $$ADDDRUG^C0CRXNAD
     441All non-testing APIs in C0CRXNLK are supported.[[BR]]
     442D IMPORT!^C0CRXNRD[[BR]]
     443$$ADDDRUG!^C0CRXNAD
    434444
    435445=== External Interfaces, External Relations ===
    … …  
    450460
    451461### File Structure
    452 All files have only a zero node for each entry and correspond as much as possible to the RxNorm file format, except that the '|' has been substitued with a "^". The exception to that rule is when a file's first field cannot be the .01 because it's missing for some entries. In this case, the first field and a key field are switch so that the key field can be the .01.
     462All files have only a zero node for each entry and correspond as much as possible to the !RxNorm file format, except that the '|' has been substitued with a "!^". The exception to that rule is when a file's first field cannot be the .01 because it's missing for some entries. In this case, the first field and a key field are switch so that the key field can be the .01.
    453463
    454464{{{