Kevin, as you know RPC's and screenman are separate entities, so this would not be possible. RPC's would have to be developed for the backend that would service the GUI requests. Much work would need to be done on the backend.
A general concensus of the requirements of any office practice/hospital would need to be specified in a software specification. Customization is possible but may not be work the effort, fields that are not desired could simply be overlooked by the person perfoming the registration. ----- Original Message ----- From: Kevin Toppenberg <[EMAIL PROTECTED]> Date: Monday, October 3, 2005 9:32 am Subject: Re: [Hardhats-members] CPRS and New patient registration > I also have thought about taking this project on, but it could be > quite awhile before I get to it. As I have been playing with VistA > imaging, and making RPC calls, it is getting easier to image how to > make a GUI. > > Here were my thoughts: > Not everyone wants to query the same fields. And there are MANY > fields that could be put on a GUI. So it would be best to make this > customizable. Perhaps by having a configuration file that specifies > the fields and the order of their appearance. > Also, it would allow for default values for some fields. In our site, > NONE of the patients are vetarans, and I get tired of answering the > question when I register a patient. And then have to answer Patient > Type? with NON-VETARAN. > > The absolutely best way to do this would be to make some RPC- Screenman > interface, so that Screenman forms automatically appear on a windows > GUI. > > Kevin > > > On 10/3/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Understood, the company I work for may take on this endeavor. > > > > Trust me, it is not as easy a task as you may like to think. > > > > D ^XQ1 > > > > VAH>d ^XQ1 > > > > Select OPTION NAME: Register a Patient > > > > Select PATIENT NAME: > > > > > > > > VAH>D ^DII > > > > > > VA FileMan 22.0 > > > > > > Select OPTION: INQUIRE TO FILE ENTRIES > > > > > > > > OUTPUT FROM WHAT FILE: INSTALL// 19 OPTION (13795 entries) > > Select OPTION NAME: DG REGISTER PATIENT Register a Patient > > ANOTHER ONE: > > STANDARD CAPTIONED OUTPUT? Yes// (Yes) > > Include COMPUTED fields: (N/Y/R/B): NO// - No record number (IEN), > > no Computed > > Fields > > DISPLAY AUDIT TRAIL? No// NO > > > > NAME: DG REGISTER PATIENT MENU TEXT: Register a > Patient> TYPE: run routine CREATOR: POSTMASTER > > LOCK: DGZ REGISTER A PATIENT PACKAGE: REGISTRATION > > DESCRIPTION: This option is used to process an application for > > care. The > > user may also use this option to establish or edit a specific > > patient's data > > base. After an application for care has been processed the patient > > should > > either be dispositioned from care using the DISPOSITION option > or the > > registration should be deleted using the DELETE REGISTRATION > option.> ROUTINE: DGREG TIMESTAMP: > 55630,33824> TIMESTAMP OF PRIMARY MENU: 60040,53225 > > UPPERCASE MENU TEXT: REGISTER A PATIENT > > > > > > > > Select OPTION NAME: > > > > > > ----- Original Message ----- > > From: Kin Ho <[EMAIL PROTECTED]> > > Date: Monday, October 3, 2005 1:39 am > > Subject: Re: [Hardhats-members] CPRS and New patient registration > > > > > > > > That is disappointing, and I don't mean it in a negative way. > > > > > > Apparently CPRS is such a fine product with extensive > functionalities> > in setting personal preference, entering > orders, vitals and > > > medications, > > > etc. > > > That is beyond retrieve only. > > > > > > Compare with the available functions, it will be a relative small > > > task > > > technically > > > to add an option to enter a new patient (of course, check against > > > existing > > > to > > > avoid duplications). It is only reasonable to have data > > > entry/edit/retrieve > > > all in > > > one place. Now it become a show stopper for me because I don't > know> > the old way of patient registration yet. > > > > > > Wonder what is the designing philosophy keeping patient > > > registration away > > > from CPRS GUI? > > > > > > Back to evaluate CPRS, how do I start patient registration in the > > > r&s way? > > > For example, <<<D Reg^FMPtEnt>>> > > > > > > Thanks and regards > > > Kin > > > > > > > > > > > > ----- Original Message ----- > > > From: "Roy Gaber" <[EMAIL PROTECTED]> > > > To: <[email protected]> > > > Sent: Sunday, October 02, 2005 4:35 PM > > > Subject: RE: [Hardhats-members] CPRS and free version of Cache > > > > > > > > > > Yes, that is correct, CPRS was designed to be a retrieval > system.> > > The roll-and-scroll patient registration is the way > to enter the > > > patient> info, it will then be available via CPRS. > > > > > > > > I like to use the word archaic as opposed to clumsy. I am sure > > > there will > > > > be many new features added to the VOE. > > > > > > > > -----Original Message----- > > > > From: [EMAIL PROTECTED] > > > > [mailto:[EMAIL PROTECTED] On Behalf > > > Of Kin Ho > > > > Sent: Sunday, October 02, 2005 7:24 PM > > > > To: [email protected] > > > > Subject: Re: [Hardhats-members] CPRS and free version of Cache > > > > > > > > Hi Roy, > > > > > > > > That is interesting. > > > > > > > > Does it mean that CPRS cannot be used to enter 'New patients'? > > > > I cannot enter new patient through the 'Patient selection > pop-up' > > > > window. When I close the pop-up, the main screen goes too. > > > > > > > > The CPRS and VOE demonstrations show that you can add > > > > information i.e. dx, medications, to a selected patient. > > > > > > > > Do I have to enter minimal patient information from the > 'roll and > > > > scroll' option, then proceed to CPRS GUI? How to do it in the > > > old way? > > > > That sounds clumsy, isn't it? > > > > > > > > Regards > > > > Kin > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > 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 > > > [email protected] > > > 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 > > [email protected] > > 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 > [email protected] > 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 [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members
