Since Fileman will, at least in the future, will let you translate the name of the field as seen by the user in a query, then I would think you could ask for a patient record number but store it in the SS number field IF it were 10 digits long, or something along those lines, as a first "fix". Of course, then there are all the pseudoSS# checks, etc., that would have a problem. OR, you could wait for VistAOffice and hope they dealt with it. ;-)
On Tuesday 19 April 2005 11:59 am, Kevin Toppenberg wrote: > I wouldn't do that. Yes, you could change the database parameters so that > other numbers could be stored in it. But then you have to think about > every single application already written that might access that datafield. > What assumptions have been made about the length of the number. If it was > suddenly a different format, would one of those programs break? I don't > know, and without careful research it would be difficult to know. > > I think it would be better to simply add a new data field, or use the one > set up by the IHS. > > Kevin > > Nancy Anthracite <[EMAIL PROTECTED]> wrote: > Could you please address the poison in a little more detail, starting with > the part of not using field. Could you reassign the name of the field and > change the length, for instance, for the SS number to create the patient > record number that would continue to function properly? > > On Tuesday 19 April 2005 10:33 am, Richard G. DAVIS wrote: > > The design of the VistA system anticipated the requirement to create new > > data elements (fields) indefinitely into the future. VistA provide for a > > formal method of allowing for the addition of data elements without > > adverse impact. It is, however, a matter for competent (master craftsman) > > personnel. > > > > Likewise, the underlying M(UMPS) technology does not carry a penalty for > > the presence of unused data elements in the database. > > > > There is, unfortunately, no easy remedy for the problem of how new data > > elements appear in the application software dialogs and processing there > > of. The presence of unwanted dialog related to data elements not being > > used, such as SSN, is also an significant problem to be overcome. > > > > Any existing system that presents the difficulties about which you are > > asking, Mark, will require some substantial investment to adapt to your > > specific circumstances. > > > > The question is: Which SET OF PROBLEMS to you want to be working on? > > > > Choose your poison, Mark. ...but, drink some poison you must. :-) > > > > Regards, > > > > Richard. > > > > > From: "Mark Painter" > > > Organization: Mark Painter > > > Reply-To: hardhats-members@lists.sourceforge.net > > > Date: Tue, 19 Apr 2005 14:06:04 +0200 > > > To: > > > Subject: [Hardhats-members] Configurability of fields in FileMan > > > > > > I am new to Vista; have installed Cache and Vista, and it seems to be > > > running OK. What I'd like to know is how easy it is to configure Vista > > > tables; for example, we would not need SSN, VA numbers, combat service > > > location etc for patients but we might need other fields which aren't > > > present in the system 'off the shelf'. > > > > > > Would we need to 'redesign' the patient table(s) - this is likely to > > > impact on many areas of other tables/forms - and then redesign the > > > forms? > > > > > > I'm a Pediatrician in a government hospital in South Africa, have > > > programmed in VB and Perl. It is a shame to waste scarce resources ($) > > > on commercial software if one can modify one of, if not The, most > > > successful HIS so far. > > > > > > Mark Painter > > > East London > > > South Africa > > > > > > -- > > > No virus found in this outgoing message. > > > Checked by AVG Anti-Virus. > > > Version: 7.0.308 / Virus Database: 266.9.17 - Release Date: 19/04/2005 > > > > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email is sponsored by: New Crystal Reports XI. > > > Version 11 adds new functionality designed to reduce time involved in > > > creating, integrating, and deploying reporting solutions. Free runtime > > > info, new features, or free trial, at: > > > http://www.businessobjects.com/devxi/728 > > > _______________________________________________ > > > Hardhats-members mailing list > > > Hardhats-members@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/hardhats-members > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: New Crystal Reports XI. > > Version 11 adds new functionality designed to reduce time involved in > > creating, integrating, and deploying reporting solutions. Free runtime > > info, new features, or free trial, at: > > http://www.businessobjects.com/devxi/728 > > _______________________________________________ > > Hardhats-members mailing list > > Hardhats-members@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/hardhats-members -- Nancy Anthracite ------------------------------------------------------- This SF.Net email is sponsored by: New Crystal Reports XI. Version 11 adds new functionality designed to reduce time involved in creating, integrating, and deploying reporting solutions. Free runtime info, new features, or free trial, at: http://www.businessobjects.com/devxi/728 _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
