Changeset 1413
- Timestamp:
- Apr 17, 2012, 11:15:23 AM (13 years ago)
- Location:
- pharmacy-utils/drug-file-cleanup
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
pharmacy-utils/drug-file-cleanup/README.txt
r1410 r1413 20 20 Workflow (using KIDS): 21 21 ; On the Origin System: 22 ; - Create a KIDS build that calls the follwing: 23 ; 1. This Routine Name to call from top is the Environment Check for the Build 24 ; 2. TRAN is the Pre-Transport Routine for your originating system drug data 25 ; 3. PRE is the Pre-Init for the Destination System 26 ; 4. POST is the Post-Init for the Destination System 22 ; - Create a KIDS build that calls the following: 23 ; 1. This Routine Name to call from top is the Environment Check for the 24 ; Build 25 ; 2. PRE is the Pre-Init for the Destination System 26 ; 3. POST is the Post-Init for the Destination System 27 ; 4. TRAN is the Pre-Transport Routine for your originating system drug data 27 28 ; - Generate the KIDS Build. The file will have all the Drug Data from the 28 29 ; Origin System. 30 ; 29 31 ; On the Destination System: 30 32 ; - Install the KIDS Build … … 39 41 into a destination system. 40 42 41 --- KIDS TEXT ----43 --- END KIDS TEXT ---- 42 44 License is AGPL. 43 45 … … 45 47 46 48 Limitations/Ideas for Future Development: 47 - Not sure if the MEDICATION ROUTES should be transmitted or not. While additions are allowed, they are by my experience uncommon. 48 - 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. 49 50 Remarks on Broken Pointers in Destination Systems as a result of using this package: 51 Because many files point to the Pharmacy Orderable Item and Drug files, you practically cannot use this package on a database that contains pharmacy data since all data will be corrupted. 52 When installing a new drug and pharmacy orderable item file, the following may be broken: 49 - Not sure if the MEDICATION ROUTES should be transmitted or not. While 50 additions are allowed, they are by my experience uncommon. 51 - Many reference files (e.g. PACKAGE SIZE or DRUG UNITS) are not part of the 52 NDF, yet they are not user modifiable. Yet, they are referenced almost 53 exclusively from the National Drug Files; which means that they cannot be 54 changed without corrupting the NDF data. I am trying to find documentation 55 to say that they are standard. 56 - If the Administration Schedules from the originating system and destination 57 system don't match, you need to either change the schedules on the orderable 58 items, or make the schedules on the destination system the same as the 59 ones from incoming drug file, otherwise, the problems you run into is this: 60 - Orders do not calculate frequency correctly if the schedule is not present 61 in the destination system. This means that the proper number of pills 62 cannot be calculated. 63 - In Outpatient Pharmacy, Schedules do not expand into patient readable 64 instructions 65 - If the National Drug Files are not up to date in the destination system, 66 there will be some broken pointers. All you have to do is update the NDF with 67 the latest patches. 68 - If some drugs are linked with lab tests, these need to be re-linked. 69 Preferably, these should be removed prior to transporting the drug file. 70 71 72 Remarks on Broken Pointers in Destination Systems as a result of using this 73 package: 74 Because many files point to the Pharmacy Orderable Item and Drug files, you 75 practically cannot use this package on a database that contains patient- 76 specific pharmacy data since all data will be corrupted. 77 78 When installing a new drug and pharmacy orderable item file, the following may 79 be broken: 53 80 For Drug File: 54 81 - LAB TEST MONITOR field. … … 67 94 - MEDICATION ROUTES (additions are allowed, not deletions) 68 95 69 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. 70 71 To check for broken pointer, use the VERIFY FIELDs option in Fileman. 96 The National Drug Files are Standardized. However, a system may be out of date. 97 If you do not have the latest National Drug Files, you have will broken 98 pointers if the source of your drug files has a more recent National Drug File. 99 For best results, the source system and the destination system should have a 100 commensurate NDF patch level. 101 102 To check for broken pointers, use the VERIFY FIELDs option in Fileman. 72 103 Here is an example of a drug file from a patched system installed on a system 73 104 that is not patched: … … 107 138 ============================================================================== 108 139 109 See detailed analysis below. 110 111 File/Package: PHARM ORD ITEM Date: APR 12,2012 112 113 FILE (#) POINTER (#) FILE 114 POINTER FIELD TYPE POINTER FIELD FILE POINTED TO 115 ------------------------------------------------------------------------------------------------------------------------------------ 116 L=Laygo S=File not in set N=Normal Ref. C=Xref. 117 *=Truncated m=Multiple v=Variable Pointer 118 119 ------------------------------- 120 DRUG (#50) | | 121 PHARMACY ORDERABLE ITEM ........................ (N S C L)-> | 50.7 PHARMACY ORDERABLE I* | 122 PRESCRIPTION (#52) | | 123 PHARMACY ORDERABLE ITEM ........................ (N S )-> | DOSAGE FORM |-> DOSAGE FORM (file locked down) 124 PENDING OUTPATIENT O (#52.41) | | 125 PHARMACY ORDERABLE ITEM ........................ (N S )-> | MED ROUTE |-> MEDICATION ROUTES (addable) 126 IV ADDITIVES (#52.6) | | 127 PHARMACY ORDERABLE ITEM ........................ (N S C )-> | m DIVISION/SI:DIVISION/SI* |-> OUTPATIENT SITE (not used) 128 IV SOLUTIONS (#52.7) | | 129 PHARMACY ORDERABLE ITEM ........................ (N S C L)-> | m OI-DRUG TEX:OI-DRUG TEX* |-> DRUG TEXT (used -- included) 130 NON-VERIFIED ORDERS (#53.1) | | 131 ORDERABLE ITEM ................................. (N S )-> | | 132 UNIT DOSE ORDER SET (#53.22) | | 133 ORDERABLE ITEM ................................. (N S )-> | | 134 PICK LIST (#53.52) | | 135 PATIENT:ORDER:ORDERABLE ITEM ................... (N S )-> | | 136 BCMA MEDICATION LOG (#53.79) | | 137 ADMINISTRATION MEDICATION ...................... (N S )-> | | 138 PHARMACY PATIENT (#55.01) | | 139 IV:ORDERABLE ITEM .............................. (N S )-> | | 140 NON-VA MEDS:ORDERABLE ITEM ..................... (N S )-> | | 141 UNIT DOSE:ORDERABLE ITEM ....................... (N S )-> | | 142 ------------------------------- 140 Below you will find the pointer relations of all the files that are transmitted in this KIDS build. 141 143 142 File/Package: DRUG Date: APR 12,2012 144 143 … … 277 276 ------------------------------- 278 277 278 File/Package: PHARM ORD ITEM Date: APR 12,2012 279 280 FILE (#) POINTER (#) FILE 281 POINTER FIELD TYPE POINTER FIELD FILE POINTED TO 282 ------------------------------------------------------------------------------------------------------------------------------------ 283 L=Laygo S=File not in set N=Normal Ref. C=Xref. 284 *=Truncated m=Multiple v=Variable Pointer 285 286 ------------------------------- 287 DRUG (#50) | | 288 PHARMACY ORDERABLE ITEM ........................ (N S C L)-> | 50.7 PHARMACY ORDERABLE I* | 289 PRESCRIPTION (#52) | | 290 PHARMACY ORDERABLE ITEM ........................ (N S )-> | DOSAGE FORM |-> DOSAGE FORM (file locked down) 291 PENDING OUTPATIENT O (#52.41) | | 292 PHARMACY ORDERABLE ITEM ........................ (N S )-> | MED ROUTE |-> MEDICATION ROUTES (addable) 293 IV ADDITIVES (#52.6) | | 294 PHARMACY ORDERABLE ITEM ........................ (N S C )-> | m DIVISION/SI:DIVISION/SI* |-> OUTPATIENT SITE (not used) 295 IV SOLUTIONS (#52.7) | | 296 PHARMACY ORDERABLE ITEM ........................ (N S C L)-> | m OI-DRUG TEX:OI-DRUG TEX* |-> DRUG TEXT (used -- included) 297 NON-VERIFIED ORDERS (#53.1) | | 298 ORDERABLE ITEM ................................. (N S )-> | | 299 UNIT DOSE ORDER SET (#53.22) | | 300 ORDERABLE ITEM ................................. (N S )-> | | 301 PICK LIST (#53.52) | | 302 PATIENT:ORDER:ORDERABLE ITEM ................... (N S )-> | | 303 BCMA MEDICATION LOG (#53.79) | | 304 ADMINISTRATION MEDICATION ...................... (N S )-> | | 305 PHARMACY PATIENT (#55.01) | | 306 IV:ORDERABLE ITEM .............................. (N S )-> | | 307 NON-VA MEDS:ORDERABLE ITEM ..................... (N S )-> | | 308 UNIT DOSE:ORDERABLE ITEM ....................... (N S )-> | | 309 ------------------------------- 310 311 File/Package: DRUG TEXT Date: APR 16,2012 312 313 FILE (#) POINTER (#) FILE 314 POINTER FIELD TYPE POINTER FIELD FILE POINTED TO 315 ------------------------------------------------------------------------------------------------------------------------------------ 316 L=Laygo S=File not in set N=Normal Ref. C=Xref. 317 *=Truncated m=Multiple v=Variable Pointer 318 319 ------------------------------- 320 DRUG (#50.037) | | 321 DRUG TEXT ENTRY ................................ (N S C )-> | 51.7 DRUG TEXT | 322 PHARMACY ORDERABLE I (#50.76) | | 323 OI-DRUG TEXT ENTRY ............................. (N S )-> | | 324 ------------------------------- 325 326 File/Package: IV FILES Date: APR 16,2012 327 328 FILE (#) POINTER (#) FILE 329 POINTER FIELD TYPE POINTER FIELD FILE POINTED TO 330 ------------------------------------------------------------------------------------------------------------------------------------ 331 L=Laygo S=File not in set N=Normal Ref. C=Xref. 332 *=Truncated m=Multiple v=Variable Pointer 333 334 ------------------------------- 335 IV ADDITIVES (#52.62) | | 336 ELECTROYLTES:ELECTROLYTE ....................... (N )-> | 50.4 DRUG ELECTROLYTES | 337 IV SOLUTIONS (#52.702) | | 338 ELECTROLYTES ................................... (N )-> | | 339 ------------------------------- 340 ------------------------------- 341 IV CATEGORY (#50.2) | | 342 IV DRUG v ........................................(N S L)-> | 52.6 IV ADDITIVES | 343 IV DRUG v ........................................(N S L)-> | GENERIC DRUG |-> DRUG 344 NON-VERIFIED ORDERS (#53.157) | | 345 ADDITIVE ....................................... (N S C )-> | PHARMACY ORDERABLE ITEM |-> PHARMACY ORDERABLE ITEM 346 BCMA MISSING DOSE RE (#53.686) | | 347 ADDITIVES ...................................... (N S C )-> | *PRIMARY DRUG |-> PRIMARY DRUG 348 BCMA UNABLE TO SCAN (#53.7711) | | 349 ADDITIVE ....................................... (N S C )-> | QUICK CODE:USUAL IV SO* |-> IV SOLUTIONS 350 BCMA MEDICATION LOG (#53.796) | | 351 ADDITIVES ...................................... (N S C )-> | QUICK CODE:MED ROUTE |-> MEDICATION ROUTES 352 PHARMACY PATIENT (#55.02) | | 353 IV:ADDITIVE .................................... (N S )-> | m ELECTROYLTES:ELECTROLYTE |-> DRUG ELECTROLYTES 354 BCMA ID:ADDITIVE ............................... (N S )-> | | 355 PHARMACY QUICK ORDER (#57.17) | | 356 ADDITIVE ....................................... (N S )-> | | 357 ------------------------------- 358 ------------------------------- 359 IV CATEGORY (#50.2) | | 360 IV DRUG v ........................................(N S L)-> | 52.7 IV SOLUTIONS | 361 IV DRUG v ........................................(N S L)-> | GENERIC DRUG |-> DRUG 362 IV ADDITIVES (#52.61) | | 363 QUICK CODE:USUAL IV SOLUTION ................... (N )-> | PHARMACY ORDERABLE ITEM |-> PHARMACY ORDERABLE ITEM 364 NON-VERIFIED ORDERS (#53.158) | | 365 SOLUTION ....................................... (N S C )-> | *PRIMARY DRUG |-> PRIMARY DRUG 366 BCMA MISSING DOSE RE (#53.687) | | 367 SOLUTIONS ...................................... (N S C )-> | m ELECTROLYTES:ELECTROLYTES |-> DRUG ELECTROLYTES 368 BCMA UNABLE TO SCAN (#53.7712) | | 369 SOLUTIONS ...................................... (N S C )-> | | 370 BCMA MEDICATION LOG (#53.797) | | 371 SOLUTIONS ...................................... (N S C )-> | | 372 PHARMACY PATIENT (#55.1058) | | 373 BCMA ID:SOLUTION ............................... (N S )-> | | 374 IV:SOLUTION .................................... (N S )-> | | 375 PHARMACY QUICK ORDER (#57.18) | | 376 SOLUTION ....................................... (N S )-> | | 377 ------------------------------- 378 -
pharmacy-utils/drug-file-cleanup/VWPSSXPD.m
r1410 r1413 1 VWPSSXPD ; VW/SMH - Update the Drug File and friends... ; 4/16/12 12:15pm1 VWPSSXPD ; VW/SMH - Update the Drug File and friends... ; 4/16/12 3:24pm 2 2 ;;1.0;WorldVista Modifications;;;Build 5 3 3 ; (C) Sam Habiel … … 25 25 ; Workflow (using KIDS): 26 26 ; On the Origin System: 27 ; - Create a KIDS build that calls the foll wing:27 ; - Create a KIDS build that calls the following: 28 28 ; 1. This Routine Name to call from top is the Environment Check for the Build 29 29 ; 2. TRAN is the Pre-Transport Routine for your originating system drug data
Note:
See TracChangeset
for help on using the changeset viewer.