Skip to main content

Order Code Load/Update Utility via FDB Database

  1. Last updated
  2. Save as PDF

Import multiple drug codes from the First Databank database of drug interaction and reference.

Avatar Order Entry > Order Entry System Definitions > Order Code Load/Update Utility Via FDB Database

  • The First Databank database includes information used for drug-to-drug interactions, drug-to-allergy warnings, drug-to-disease checking, and client education monographs.
  • If clinical screening is available and the Send Message To All Terminals When Screening Database Out of Date registry setting is enabled, an alert displays on the RADplus 2010 banner screen indicating the screening database needs to be updated. Use the Order Code Load/Update Utility Via FDB Database and the Allergen Code Load/Update Utility Via FDB Database forms to update the FDB database.
  • If Guardiant is used with myAvatar Order Entry, a background process will run once a day to check for out-of-date data in the First Databank database being used. If the process detects an out-of-date condition, Guardiant will periodically send an alert to Netsmart until the out-of-date condition is resolved. See Avatar Order Entry 2011 Enhancement 37 Release Notes for details.
  • The order code load/update process takes into account myAvatar Order Entry order codes that are mapped from the First Databank database to the Micromedex Red Book database.
  1. In the Namespace That Contains The First DataBank Database field, enter the namespace where the First DataBank database is stored.
  2. For the Order Type To Assign To New Generated Order Codes field, select the order type that will be assigned to the uploaded order codes.
  3. In the Define New Generated Order Codes As Formulary field, select Yes to define new order codes as formulary.
  4. In the Define New Generated Order Codes As Deactivated field, select Yes to define new imported order codes as deactivated.
  5. For the Generate Separate Order Codes For Brand Name Items field, select whether to generate separate order codes. If Yes is selected, the Include Generic Name (Parenthetically) Within Order Code Description For Brand Name Entries - For Example: TYLENOL (ACETAMINOPHEN) field is enabled and required.
  6. In the Include Generic Name (Parenthetically) Within Order Code Description For Brand Name Entries - For Example: TYLENOL (ACETAMINOPHEN) field, select whether to include the generic name for brand name drugs.
    Once the choices for the Generate Separate Order Codes For Brand Name Items and Include Generic Name (Parenthetically) Within Order Code Description For Brand Name Entries - For Example: TYLENOL (ACETAMINOPHEN) fields are made, the same choices should be used for all subsequent runs of the load/update process. Failure to use the same choices will result in duplications with slightly different descriptions.
  7. Click Change Processing Options to select the processing options for the load/update process. A warning message displays that indicates that changing the options for handling brand and generic names will result in the creation duplicate order codes. To change the processing options, click Yes. If Yes is selected, the Generate Separate Order Codes For Brand Name Items and Include Generic Name (Parenthetically) Within Order Code Description For Brand Name Entries - For Example: TYLENOL (ACETAMINOPHEN) fields are enabled and required.
  8. Click Print Audit Report For Latest Load/Update Process to view a report of information about the last order code upload.
  9. Click Submit.