Let me clarify that when I use the VistA manual registration methods (i.e. a user inputs the data by hand), it works fine. But then I think I always specify a ssnum, or a pseudossnum. Maybe that is the key.
Kevin
Re-wording the subject line …
Manual entry is the usual means of registration. What you're describing is automated entry using a "silent" API. This problem sounds like a bug that should be corrected in Registration code in the course of supporting VOE. There should be a cross-reference on file 2 that automatically creates the parallel in 90000001, rather than having that code (I'm guessing) in the lookup routine set DPTLK*.
In the mean time, in your background code you'll need to add a stub entry in 90000001 as well.
Cameron
On 1/11/06, Kevin Toppenberg wrote:
A different be related question is how SHOULD I manually put patients into the database? I have just established a communication channel between out billing system (our primary source of demographic info), and I am now back to the point where I can automatically register patients in VistA. Its been awhile, but I think I used standard Fileman calls to create records in the PATIENT file, and filled them with appropriate information. This resulted in the corresponding entries in file 90000001 not being created. Am I supposed to create these automatically? Is there some trigger or something that is supposed to do this?
I'm trying to avoid future problems.
Thanks
Kevin
