Extracting whole standard tables from the patched VistA FOIA copies should
work for those tables where all entries are standard and their IENs are
fixed.  In fact, that's the only way to get the updates for the Lexicon
since the patches for the Lexicon's standard tables include copyrighted CPT
codes and redacting those codes from the patches is too hard to do.
(Instead, the codes are removed for the VistA FOIA copy after the patches
are applied.)  But the updates for the National Drug File tables are
distributed in un-redacted patches which should generally be less work to
use than trying to copy large globals.

New entries are added with the patches, I don't know off hand what the
process is for inactivating old drugs ... I just know that old entries must
not get deleted.

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kevin
Toppenberg
Sent: Friday, November 25, 2005 10:26 PM
To: [email protected]
Subject: Re: [Hardhats-members] Importing FDA national drug files: Request
for Comments

Cameron,

When I asked before how to get an updated VA PRODUCT file, I mused that I
thought the answer would be to keep up with the patch stream.  But the
impression I got was that I should get a FOIA release and extract the global
from there.  My understanding is that there may well be data in databases
(for example in a FOIA release) that wouldn't be put out in patch streams. 

So are you saying that if I get up to date with patches, that drug
corrections (such as adding new drugs and removing outdated drug entries
like rezulin) would be effected?

Thanks
Kevin




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members

Reply via email to