Changeset 1410

Timestamp:

Apr 16, 2012, 3:20:47 PM (13 years ago)

Author:

Sam Habiel

Message:

Now routine transports IVs; updated documentation

Location:

pharmacy-utils/drug-file-cleanup

Files:

• README.txt (modified) (3 diffs)
• VWPSSXPD.m (modified) (3 diffs)

pharmacy-utils/drug-file-cleanup/README.txt

@@ -1 @@
-Documentation for using the Drug File updating utility WITH and WITHOUT KIDS can be found in VWPSSXPD.m.
-
-KIDS file contains this routine plus a sample drug file to be installed into a destination system.
-
+
+                          --- KIDS TEXT ----
+Created by Sam Habiel on Thursday 12 April 2011 for WorldVistA.
+
+                            --- WARNING ---
+If you install the KIDS build produced by this tool on a production system 
+containing pharmacy patient data, you will cause database corruption and 
+jeopardize patient safety. 
+                            --- WARNING ---
+
+This KIDS Build transports the following files from a source system to a 
+destination system and then syncs CPRS OE/RR files with the new files.
+ ; ^PSDRUG      DRUG
+ ; ^PS(50.7)    PHARMACY ORDERABLE ITEM
+ ; ^PS(51.7)    DRUG TEXT
+ ; ^PS(52.6)    IV ADDITIVES
+ ; ^PS(52.7)    IV SOLUTIONS
+ ; ^PS(50.4)    DRUG ELECTROLYTES
+
+Workflow (using KIDS):
+ ; On the Origin System:
+ ; - Create a KIDS build that calls the follwing:
+ ;  1. This Routine Name to call from top is the Environment Check for the Build
+ ;  2. TRAN is the Pre-Transport Routine for your originating system drug data
+ ;  3. PRE is the Pre-Init for the Destination System
+ ;  4. POST is the Post-Init for the Destination System
+ ; - Generate the KIDS Build. The file will have all the Drug Data from the 
+ ;   Origin System.
+ ; On the Destination System:
+ ; - Install the KIDS Build
+ 
+The entry points in the attached routine (VWPSSXPD) can be used by
+themselves to remove an old drug file and add a new one.
+
+Documentation for using the Drug File updating utility WITH and WITHOUT KIDS 
+can be found in VWPSSXPD.m.
+
+KIDS file contains this routine plus a sample drug file to be installed 
+into a destination system.
+
+                          --- KIDS TEXT ----
 License is AGPL.
 
 Author is Sam Habiel for WorldVistA.
+
+Limitations/Ideas for Future Development:
+- Not sure if the MEDICATION ROUTES should be transmitted or not. While additions are allowed, they are by my experience uncommon.
+- Many reference files (e.g. PACKAGE SIZE or DRUG UNITS) are not part of the NDF, yet they are not user modifiable. Yet, they are referenced almost exclusively from the National Drug Files; which means that they cannot be changed without corrupting the NDF data. I am trying to find documentation to say that they are standard.
 
 Remarks on Broken Pointers in Destination Systems as a result of using this package:
@@ -20 +61 @@
 - IFCAP ITEM NUMBER:ITEM NUMBER (field not used currently)
 - Custom UNIT DOSE MED ROUTE (field not used currently)
+- NATIONAL DRUG FILE ENTRY (if you don't have a recently patched NDF)
+- PSNDF VA PRODUCT NAME ENTRY (if you don't have a recently patched NDF).
 
 For Pharmacy Orderable Item File:
@@ -25 +68 @@
 
 The National Drug Files are Standardized. However, a system may be out of date. If you do not have the latest National Drug Files, you have will broken pointers if the source of your drug files has a more recent National Drug File. For best results, the source system and the destination system should have a commensurate NDF patch level.
+
+To check for broken pointer, use the VERIFY FIELDs option in Fileman.
+Here is an example of a drug file from a patched system installed on a system
+that is not patched:
+
+==============================================================================
+GTM>D P^DI
+
+
+VA FileMan 22.0
+
+
+Select OPTION:    UTILITY FUNCTIONS
+Select UTILITY OPTION:    VERIFY FIELDS
+
+MODIFY WHAT FILE: DRUG//  
+VERIFY WHICH FIELD:    PSNDF VA PRODUCT NAME ENTRY
+
+DEVICE: HOME// 
+
+VERIFY FIELDS REPORT
+DRUG FILE (#50)                                   APR 16, 2012  12:40    PAGE 1
+-------------------------------------------------------------------------------
+   POINTER
+(CANNOT CHECK CROSS-REFERENCE)
+
+ENTRY#    GENERIC NAME                  ERROR
+148       GUANFACINE 1MG TAB ER         No '21739' in pointed-to File
+149       GUANFACINE 2MG TAB ER         No '21740' in pointed-to File
+168       LURASIDONE 40MG TAB           No '22028' in pointed-to File
+169       LURASIDONE 80MG TAB           No '22030' in pointed-to File
+221       LEVONORGESTREL 1.5MG TAB      No '21157' in pointed-to File
+450       LIDOCAINE 5% PATCH            No '22004' in pointed-to File
+456       NEOMYCIN/POLYMYXIN/BACITRACIN OINT No '21497' in pointed-to File
+485       MICONAZOLE 4% VAGINAL CREAM   No '22325' in pointed-to File
+585       PALIPERIDONE 234MG INJ SUSP PFSNo '21021' in pointed-to File
+586       PALIPERIDONE 156MG INJ SUSP PFSNo '21022' in pointed-to File
+==============================================================================
 
 See detailed analysis below.

pharmacy-utils/drug-file-cleanup/VWPSSXPD.m

@@ -1 @@
-VWPSSXPD ; VW/SMH - Update the Drug File and friends... ; Wed Apr 13 2012 ; 4/16/12 11:02am
+VWPSSXPD ; VW/SMH - Update the Drug File and friends... ; 4/16/12 12:15pm
  ;;1.0;WorldVista Modifications;;;Build 5
  ; (C) Sam Habiel
@@ -26 +26 @@
  ; On the Origin System:
  ; - Create a KIDS build that calls the follwing:
- ;  1. ENV is the Environment Check for the Build
+ ;  1. This Routine Name to call from top is the Environment Check for the Build
  ;  2. TRAN is the Pre-Transport Routine for your originating system drug data
  ;  3. PRE is the Pre-Init for the Destination System
  ;  4. POST is the Post-Init for the Destination System
- ; - Generate the KIDS Build
+ ; - Generate the KIDS Build. The file will have all the Drug Data from the Origin
+ ;   System.
  ; On the Destination System:
  ; - Install the KIDS Build
@@ -55 +56 @@
  ;
  ; KIDS EPs:
- ;       ENV -> Environment Check (call the routine from the top)
- ;       TRAN -> Pre-Transport Routine (to get data from original system)
+ ;       Top EP Fall through  -> Environment Check (call the routine from the top)
  ;       PRE -> Pre-Init for the Destination System
  ;       POST -> Post-Init for the Destination System
+ ;       TRAN -> Pre-Transport Routine (to get data from original system)
  ;
  ; KIDS EPs call PEPs to do their work.