WASHINGTON DC, USA -- PHARMA UPDATE NEWS SERVICE(TM) -- NOVEMBER 15,
2005: Evolving requirements and the FDA's new risk-based view of
information management can transform your computer systems,
applications and even email into warning
The Check/Fix DD option does work
nicely. We run this against the entire range of files to ensure things
are clean. Probably not a bad idea to do this to the FOIA database.
I’m not aware of any untoward side effects of doing so.
Repointing entries is even more complex
than depicted h
Thanks. Yes, a modest project, but it still takes newbies like me a
day or so to get all the stars aligned.
Thanks
Kevin
On 11/15/05, James Gray <[EMAIL PROTECTED]> wrote:
> Are the
> ^DD(50,0,"PT",
> nodes not a complete list of the files and fields pointing to file 50?
> Isn't this a fairly m
Surely you are not surprised.Nancy Anthracite <[EMAIL PROTECTED]> wrote:
Oh joy.
===Gregory Woodhouse <[EMAIL PROTECTED]>
"Einstein was a giant. He had his head in the clouds and his feet on the ground."
-- Richard P. Feynman
Oh joy.
On Tuesday 15 November 2005 04:34 pm, Ruben Safir wrote:
-Forwarded Message-
> From: Pharma Update News Service <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Press Release: Second Annual FDA Information Management
> Summit Nov. 30 - Dec. 3, 2005
> Date: Tue, 15 Nov 2005
-Forwarded Message-
> From: Pharma Update News Service <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Press Release: Second Annual FDA Information Management
> Summit Nov. 30 - Dec. 3, 2005
> Date: Tue, 15 Nov 2005 16:18:31 -0500
>
>
>
>
I just got the word that the request to have the story posted in the public
viewing area has been approved courtesy of Kevin O'Neil and the Editor of the
AMA News. The link should be arriving shortly!
--
Nancy Anthracite
---
This SF.Net emai
That’s an interesting bug. FM
should remove the “PT” node. Using the Check/Fix DD Structure
option does clean it up if you select the file(s) previously pointed to.
I wonder if the Duplicate Resolution and
Merge processes could be used to advantage to address the mass correction of “b
You need to be a bit careful using the “PT”
xref as it can be inaccurate. Try this:
1) Create a pointer type field in a file
2) Look at the “PT” xref in the target (pointed to) file
for a reference to the source (pointed from) file. It should be there.
3) Change the f
Yes, that's where they're found. I'm not 100% that variable pointers create "PT" nodes, but I believe they do.James Gray <[EMAIL PROTECTED]> wrote:
Are the^DD(50,0,"PT",nodes not a complete list of the files and fields pointing to file 50?
===Gregory Woodhouse <[EMAIL PROTECTED]>
"Einstei
Are the
^DD(50,0,"PT",
nodes not a complete list of the files and fields pointing to file 50?
Isn't this a fairly modest project in Mumps to $Order through these nodes
and then through each of the files. Of course you need a complete list of
all of the bad entries/IENs that are in file 50.
Ji
Well, you know how to identiffy the files pointing to a given file (obviously), and so you need to scan these files for records having the given pointer value. But it sounds like you're already well into coding a solution.Kevin Toppenberg <[EMAIL PROTECTED]> wrote:
I mean being able to find all poi
I mean being able to find all pointers in the database that point to a
given IEN in a given file, so that they could then be manipulated.
Kevin
On 11/15/05, Greg Kreis <[EMAIL PROTECTED]> wrote:
> Do you mean by 'point them all' to fix the pointers, wherever they are
> found, that point to the
On 11/14/05, Gregory Woodhouse <[EMAIL PROTECTED]> wrote:
>
> On Nov 14, 2005, at 8:00 PM, Kevin Toppenberg wrote:
>
-snip-
>
> If you know which IENs correspond to bad pointers, then you just
> delete the corresponding field values. My preferred method is to use
> the DBS API, but it can be done i
Here's some information from the VistA HL7 developer who wrote the new Vista HL7 software I referred to earlier...
The HLO software has already been released as patch HL*1.6*126. Though it was released as a patch to the HL7 1.6
package, it is really a separate independent HL7 messaging system.
This conversation has shifted slightly, but significantly, and I think this might confuse some readers. Just so everyone understands...
The original post read...
Other than the HL7 documentation on the VA website, does anyone know of any resources to help me create a working HL7 interface. It
Do you mean by 'point them all' to fix the pointers, wherever they are
found, that point to the DRUG file?
Kevin Toppenberg wrote:
OK, lets say my Drug file (50) has 200 unwanted ZZDRUGNAME entries.
So I did a search for these and stored them in a set. (search template)
I circumvented the D
Greg,
That is the info I needed. I had overlooked that section of the
manual. Thanks for pointing it out.
Kevin
On 11/14/05, Gregory Woodhouse <[EMAIL PROTECTED]> wrote:
>
> On Nov 14, 2005, at 7:56 PM, Kevin Toppenberg wrote:
>
> > So you are saying that the value stored is the [global
> > re
I want a list of all record instances (i.e. actual records contianing
a pointer) of a pointer to a given IEN, that I can then act upon
progromatically. VPE just lists files that could potentially point to
given file. Plus, I could not act programatically upon the list.
Kevin
On 11/15/05, Steven
Variable pointers are stored as ien_";"_
Why not use VPE to list the pointers?
20 matches
Mail list logo