Is using Fileman a wise choice? Do you think efforts would be better spent using RPC's?
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jim Self Sent: Tuesday, October 04, 2005 4:21 PM To: hardhats-members@lists.sourceforge.net Subject: Re: [Hardhats-members] Regsitration GUI Nancy wrote: >There is one in development using M2Web as well. Hopefully Jim Self or Rick >Marshall will comment and let folks know how/if they can help. Rick and David Whitten and I spent a weekend focusing on patient registration in VistA a few weeks ago, but we haven't been able to get back to it since. David and I worked up a basic framework for representing the 15 or so screens of the current registration application while Rick worked to identify the data fields used and any special logic that could be separated from the roll-and-scoll. The current patient registration application is rather obscurely written and much more complex than expected (by me at least) so it took most of the weekend before the fields from screens 1, 1.1, and 2 were mostly identified. For anyone interested in viewing the source code as it is (experimental, under construction), the URL for the main routine is http://openforum.worldvista.org/~forum/m.cgi/rtn/htDG Some of the things currently functional: - a simple framework for representing the 15+ screens of the current VistA patient registration with a common header and footer and navigation between screens. - get data from an existing patient record (using GETS^DIQ) and present it in an input form (per screen, screen 1 only so far) - post data from a form and show that it was received. Some of the things to do: - identify the data fields and logic to be included in screens 3-15 (screen 2 fields have been identified but not yet coded.) - Lookup a patient (use FIND^DIC or existing M2Web query tools?) - verify posted data (I have experimented with CHK^DIE from ^htDIQ) - save posted data (I am not yet familiar with the Fileman API's for saving data. We are not currently using them in VMACS.) - rework input form generation to follow a specified field order rather than the field numbers and to present multiples more clearly. - bring in newer code from VMACS that provides popup calendar for dates and lookup for pointer fields, etc. - --------------------------------------- Jim Self Systems Architect, Lead Developer VMTH Computer Services, UC Davis (http://www.vmth.ucdavis.edu/us/jaself) ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
