Changes between Version 36 and Version 37 of RxNormForVista

Timestamp:

Nov 21, 2013, 6:03:34 PM (11 years ago)

Author:

Sam Habiel

Comment:

--

RxNormForVista

@@ -311 +311 @@
 
 ==== Update API ====
-To update RxNorm to a newer monthly version from the NLM, run the following:
+To update !RxNorm to a newer monthly version from the NLM, run the following:
 {{{
 D IMPORT^C0CRXNRD("/path/to/rrf/folder/",optional include restricted/copyrighted sources (1 -> yes). Default is no.)
@@ -360 +360 @@
 C0CRXNLK comes with Unit Tests. To run them, make sure M-Unit is installed and run !^C0CRXNLK from the top.
 
-==== Automatic Drug Addition API using RxNorm ====
+==== Automatic Drug Addition API using !RxNorm ====
 To add a drug to the drug file using the !RxNorm CUI, call the following entry point:
 
@@ -439 +439 @@
 
 === Supported APIs ===
-All non-testing APIs in C0CRXNLK are supported.[[BR]]
-D IMPORT!^C0CRXNRD[[BR]]
+All non-testing APIs in C0CRXNLK are supported.
+
+D IMPORT!^C0CRXNRD
+
 $$ADDDRUG!^C0CRXNAD
+
+For details, see the Programmer APIs section.
 
 === External Interfaces, External Relations ===
@@ -457 +461 @@
 
 === Security ===
-This software implements no security of its own. It inherits pharmacy security.
-
-### File Structure
+This software implements no security of its own beyond Fileman access codes on the fields which can be seen below in the File Structure section. None of the data contained is sensitive in any way.
+
+=== File Structure ===
 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.