> I'd start by looking at the option XUSERNEW and thinking about how to
> make it non-interactive. Trying to add a whole record in one fell swoop
> might be possible for file 200. File 2, well, I think trying to add
> everything in one UPDATE^DIE call would be a disaster.
>From having tried to do the code, I know that you can't create an entry in
file #2 (PATIENT File, "^DPT(" global) using a single UPDATE^DIE call.
As I recall this requires at least three or four calls at least. I was only
trying to put in selected information, which included employment status,
employer name, and employment telephone number. These three fields must be
added in seperate UPDATE^DIE calls, as I remember, since there is a causal
dependency that one must be in the database (checked by the input transform
of the next one) prior to the next field successfully being stored.
The multiple calls are required, if I recall correctly, because UPDATE^DIE
processes/stores in field number order, and the dependency chain is not in
field number order.
In my opinion, this dependency should NOT be encoded in the Input
Transforms of fields. This should be in integrity constraints, that are
independent of the actual order of data storage. As we are tying VistA
systems to more sophisticated ontologies and rule based systems, these kinds
of issues will slow our work.
David Whitten
713-870-3834
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
