From whatever VistA knowledge that I could gather in a couple of months, I could come across the following UI modules in VistA.
1. VistA CPRS 2. VistA Outreach (For Patient Registration) 3. VistA Configuration Utility (By Kevin) 4. VistA Patient Registration Module on the lines of CPRS (By Kevin)
It would be really helpful if the community can help identify if there are any other UI efforts which I might have missed.
> From whatever VistA knowledge that I could gather in a couple of months, I > could come across the following UI modules in VistA.
> 1. VistA CPRS > 2. VistA Outreach (For Patient Registration) > 3. VistA Configuration Utility (By Kevin) > 4. VistA Patient Registration Module on the lines of CPRS (By Kevin)
> It would be really helpful if the community can help identify if there are > any other UI efforts which I might have missed.
> ---- Harshal Shah <shahhars...@gmail.com> wrote:
> > Hi All,
> > From whatever VistA knowledge that I could gather in a couple of months, I
> > could come across the following UI modules in VistA.
> > 1. VistA CPRS
> > 2. VistA Outreach (For Patient Registration)
> > 3. VistA Configuration Utility (By Kevin)
> > 4. VistA Patient Registration Module on the lines of CPRS (By Kevin)
> > It would be really helpful if the community can help identify if there are
> > any other UI efforts which I might have missed.
> ---- Harshal Shah <shahhars...@gmail.com> wrote: > > Hi All,
> > From whatever VistA knowledge that I could gather in a couple of months, > > I could come across the following UI modules in VistA.
> > 1. VistA CPRS > > 2. VistA Outreach (For Patient Registration) > > 3. VistA Configuration Utility (By Kevin) > > 4. VistA Patient Registration Module on the lines of CPRS (By Kevin)
> > It would be really helpful if the community can help identify if there > > are any other UI efforts which I might have missed.
Where can one find the software and its documentation for all these packages ? I am plodding thru the VistA site and am trying to link up the Vistamonograph, with the VEHU documentation and the ER Diagrams. Vipen
On Mon, Sep 8, 2008 at 8:00 PM, Nancy Anthracite <nanthrac...@verizon.net>wrote:
>> ---- Harshal Shah <shahhars...@gmail.com> wrote: >>> Hi All,
>>> From whatever VistA knowledge that I could gather in a couple of months, >>> I could come across the following UI modules in VistA.
>>> 1. VistA CPRS >>> 2. VistA Outreach (For Patient Registration) >>> 3. VistA Configuration Utility (By Kevin) >>> 4. VistA Patient Registration Module on the lines of CPRS (By Kevin)
>>> It would be really helpful if the community can help identify if there >>> are any other UI efforts which I might have missed.
>> ---- Harshal Shah <shahhars...@gmail.com> wrote:
>>> Hi All, >>> From whatever VistA knowledge that I could gather in a couple of months, I >>> could come across the following UI modules in VistA. >>> 1. VistA CPRS >>> 2. VistA Outreach (For Patient Registration) >>> 3. VistA Configuration Utility (By Kevin) >>> 4. VistA Patient Registration Module on the lines of CPRS (By Kevin) >>> It would be really helpful if the community can help identify if there are >>> any other UI efforts which I might have missed. >>> -Thanks >>> Harshal- Hide quoted text - >> - Show quoted text -
This is why the community is so important. Nobody knows all of these interfaces and as people get to work with this code, there will be more and even more clever approaches tried by those who need access. The community is a place where these needs and attempts can come together and organizations can put a little money or resources (paid personnel) to these projects and get them done faster. The more you want these interfaces, the more you should invest in time and resources to make it possible for these things to happen out in the community. The more an organization invests in such an interface, the more say they have in the outcome. Look at UC Davis Veteranary School. With a team of less than ten they built m2web and have continually upgraded the tools to become something pretty remarkable. With some small measure of funding, such interfaces should be much more common. This is the power of the VistA Model, it is polymorphic. It can be reached by nearly every access method someone has decided to use to get at it. It can work with Roll and scroll, to GUI, to messageing. Money and resources are accellerators for these processes. There are a lot of clinics and hospitals who could use these access methods, small investments by these users of the software can move things along much faster.
> Where can one find the software and its documentation for all these > packages > ? > I am plodding thru the VistA site and am trying to link up the > Vistamonograph, with the VEHU documentation and the ER Diagrams. > Vipen
> On Mon, Sep 8, 2008 at 8:00 PM, Nancy Anthracite > <nanthrac...@verizon.net>wrote:
>> Query Tool >> Nurses Clincal Dashboard (maybe a Physician's too?) >> Mental Health
>> On Monday 08 September 2008, rga...@tampabay.rr.com wrote: >> > Probably more, these come to mind immediately
Yeah but are there some interfaces built to say the RPC broker so that
we can build stuff in other languages like PHP, Python, etc rather
than the default Delphi? -- IV
> This is why the community is so important. Nobody knows all of these
> interfaces and as people get to work with this code, there will be more
> and even more clever approaches tried by those who need access. The
> community is a place where these needs and attempts can come together
> and organizations can put a little money or resources (paid personnel)
> to these projects and get them done faster. The more you want these
> interfaces, the more you should invest in time and resources to make it
> possible for these things to happen out in the community. The more an
> organization invests in such an interface, the more say they have in
> the outcome. Look at UC Davis Veteranary School. With a team of less
> than ten they built m2web and have continually upgraded the tools to
> become something pretty remarkable. With some small measure of
> funding, such interfaces should be much more common. This is the power
> of the VistA Model, it is polymorphic. It can be reached by nearly
> every access method someone has decided to use to get at it. It can
> work with Roll and scroll, to GUI, to messageing. Money and resources
> are accellerators for these processes. There are a lot of clinics and
> hospitals who could use these access methods, small investments by
> these users of the software can move things along much faster.
> > Hi,
> > Where can one find the software and its documentation for all these
> > packages
> > ?
> > I am plodding thru the VistA site and am trying to link up the
> > Vistamonograph, with the VEHU documentation and the ER Diagrams.
> > Vipen
> > On Mon, Sep 8, 2008 at 8:00 PM, Nancy Anthracite
> > <nanthrac...@verizon.net>wrote:
> >> Query Tool
> >> Nurses Clincal Dashboard (maybe a Physician's too?)
> >> Mental Health
> >> On Monday 08 September 2008, rga...@tampabay.rr.com wrote:
> >> > Probably more, these come to mind immediately
On Mon, 2008-09-08 at 08:35 -0700, I, Valdes wrote: > Yeah but are there some interfaces built to say the RPC broker so that > we can build stuff in other languages like PHP, Python, etc rather > than the default Delphi? -- IV
Medsphere's open source release of OpenVistA CIS includes a C# library for communicating to the RPC broker. Being built on .NET, it can actually be used from C#, VB .NET, etc. It's also fully cross-platform, and works on Linux/OS X via Mono.
-pete
The information contained in this email may be confidential and/or may be covered under the Privacy Act, 5 USC 552(a), and/or the Health Insurance Portability and Accountability Act (PL 104-191) and its various implementing regulations and must be protected in accordance with those provisions.. It has been sent for the sole use of the intended recipient(s). If the reader of this message is not an intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and destroy all copies of the original message. To contact our email administrator directly, send to an email message to helpd...@medsphere.com. Thank you.
Those that come immediately to mind are VistALink, EsiObjects, M2Web, and HL7, and RPC calls wrapped as Web Services like we have been hearing about on hardhats. The CCR-CCD project will eventually be using those.
> Yeah but are there some interfaces built to say the RPC broker so that
> we can build stuff in other languages like PHP, Python, etc rather
> than the default Delphi? -- IV
> > This is why the community is so important. Nobody knows all of these
> > interfaces and as people get to work with this code, there will be more
> > and even more clever approaches tried by those who need access. The
> > community is a place where these needs and attempts can come together
> > and organizations can put a little money or resources (paid personnel)
> > to these projects and get them done faster. The more you want these
> > interfaces, the more you should invest in time and resources to make it
> > possible for these things to happen out in the community. The more an
> > organization invests in such an interface, the more say they have in
> > the outcome. Look at UC Davis Veteranary School. With a team of less
> > than ten they built m2web and have continually upgraded the tools to
> > become something pretty remarkable. With some small measure of
> > funding, such interfaces should be much more common. This is the power
> > of the VistA Model, it is polymorphic. It can be reached by nearly
> > every access method someone has decided to use to get at it. It can
> > work with Roll and scroll, to GUI, to messageing. Money and resources
> > are accellerators for these processes. There are a lot of clinics and
> > hospitals who could use these access methods, small investments by
> > these users of the software can move things along much faster.
> > > Hi,
> > > Where can one find the software and its documentation for all these
> > > packages
> > > ?
> > > I am plodding thru the VistA site and am trying to link up the
> > > Vistamonograph, with the VEHU documentation and the ER Diagrams.
> > > Vipen
> > > On Mon, Sep 8, 2008 at 8:00 PM, Nancy Anthracite
> From whatever VistA knowledge that I could gather in a couple of months, I
> could come across the following UI modules in VistA.
> 1. VistA CPRS
> 2. VistA Outreach (For Patient Registration)
> 3. VistA Configuration Utility (By Kevin)
> 4. VistA Patient Registration Module on the lines of CPRS (By Kevin)
> It would be really helpful if the community can help identify if there are
> any other UI efforts which I might have missed.
I, Valdes wrote: > Yeah but are there some interfaces built to say the RPC broker so that > we can build stuff in other languages like PHP, Python, etc rather > than the default Delphi? -- IV
What sort of stuff do you want to build? What building blocks do you need? Do you have anything specific in mind?
--
--------------------------------------- Jim Self Systems Architect, Lead Developer VMTH Information Technology Services, UC Davis (http://www.vmth.ucdavis.edu/us/jaself) --------------------------------------- M2Web Demonstration with VistA (http://vista.vmth.ucdavis.edu/) ---------------------------------------
Based on the set of responses I have compiled an excel sheet which will help the community/newbies get this information regarding the total UI efforts at one location. I am not sure if this can be posted at some central place.
Also there are certain columns (like the location for certain user interface binaries) which I was not aware of and therefore are empty. It would be great if this can be filled up to have a single point of contact for the user interfaces in and around VistA.
Harshal Shah wrote: > Thank you all for the responses.
> Based on the set of responses I have compiled an excel sheet which will > help the community/newbies get this information regarding the total UI > efforts at one location. I am not sure if this can be posted at some > central place.
> Also there are certain columns (like the location for certain user > interface binaries) which I was not aware of and therefore are empty. It > would be great if this can be filled up to have a single point of > contact for the user interfaces in and around VistA.
I wanted to thank Harshal for putting together this initial list. As Chris said, it's vital that this community put our heads together and share the knowledge. I wanted this information to be dynamic and collaborative -- i.e., a wiki page, rather than a spreadsheet. I'm not sure if I was doing something wrong, but I could not find the listing of software at the link below. Also, I'm not sure if the community can edit those pages.
I took the list from this thread and added what I knew to it. It's now posted here and ready for others to add/update as they see fit: http://medsphere.org/docs/DOC-1195
Thanks, Ben
PS... A few on this list are aware that Medsphere.org has been relaunched into community platform. We are in "soft launch" mode, as we test out the site. That said, all Hardhats are welcome to browse around the site and join in if they so choose.
On Thu, Sep 11, 2008 at 6:31 AM, Joseph Dal Molin <dalmo...@e-cology.ca>wrote:
Harshal contacted me off list yesterday to ask for a Plone account which we have provided at members.worldvista.org which is a community editable (if that's a word) site that was established last year. I was holding off doing anything else as he indicated that he wanted to tweak the categories some more.
> I wanted to thank Harshal for putting together this initial list. As > Chris said, it's vital that this community put our heads together and > share the knowledge. I wanted this information to be dynamic and > collaborative -- i.e., a wiki page, rather than a spreadsheet. I'm not > sure if I was doing something wrong, but I could not find the listing of > software at the link below. Also, I'm not sure if the community can > edit those pages.
> I took the list from this thread and added what I knew to it. It's now > posted here and ready for others to add/update as they see fit: > http://medsphere.org/docs/DOC-1195
> Thanks, Ben
> PS... A few on this list are aware that Medsphere.org has been > relaunched into community platform. We are in "soft launch" mode, as we > test out the site. That said, all Hardhats are welcome to browse around > the site and join in if they so choose.
> On Thu, Sep 11, 2008 at 6:31 AM, Joseph Dal Molin <dalmo...@e-cology.ca > <mailto:dalmo...@e-cology.ca>> wrote:
> Thank you for creating the table Harshal.... I have started a new page > WorldVistA website which will contain the information in your table:
On Fri, Sep 12, 2008 at 8:48 PM, Joseph Dal Molin <dalmo...@e-cology.ca>wrote:
> Harshal contacted me off list yesterday to ask for a Plone account which > we have provided at members.worldvista.org which is a community editable > (if that's a word) site that was established last year. I was holding > off doing anything else as he indicated that he wanted to tweak the > categories some more.
Okay, sounds good. I definitely think "community editable" is must-have! Is there someway community members can register so we can keep the lists updated?
I didn't see anything online just yet for the GUIs, but we can combine the lists when you're ready. I also went ahead and published the list of Development Toolkits. We looked at this sometime ago, so I added all the toolkits we had evaluated here: http://medsphere.org/docs/DOC-1198
> Harshal contacted me off list yesterday to ask for a Plone account which > we have provided at members.worldvista.org which is a community editable > (if that's a word) site that was established last year. I was holding > off doing anything else as he indicated that he wanted to tweak the > categories some more.
> Cheers,
> Joseph
> Ben Mehling wrote: > > Group-
> > I wanted to thank Harshal for putting together this initial list. As > > Chris said, it's vital that this community put our heads together and > > share the knowledge. I wanted this information to be dynamic and > > collaborative -- i.e., a wiki page, rather than a spreadsheet. I'm not > > sure if I was doing something wrong, but I could not find the listing of > > software at the link below. Also, I'm not sure if the community can > > edit those pages.
> > I took the list from this thread and added what I knew to it. It's now > > posted here and ready for others to add/update as they see fit: > > http://medsphere.org/docs/DOC-1195
> > Thanks, Ben
> > PS... A few on this list are aware that Medsphere.org has been > > relaunched into community platform. We are in "soft launch" mode, as we > > test out the site. That said, all Hardhats are welcome to browse around > > the site and join in if they so choose.
> > On Thu, Sep 11, 2008 at 6:31 AM, Joseph Dal Molin <dalmo...@e-cology.ca > > <mailto:dalmo...@e-cology.ca>> wrote:
> > Thank you for creating the table Harshal.... I have started a new > page > > WorldVistA website which will contain the information in your table:
The link you provided for M2Web is an ancient document (at least 10 years old) describing MHTTP, our old DTM based web server. That does not link very directly to VistA or GT.M or M2Web development from the last 10 years. The links in my sig below are more current
--
--------------------------------------- Jim Self Systems Architect, Lead Developer VMTH Information Technology Services, UC Davis (http://www.vmth.ucdavis.edu/us/jaself) --------------------------------------- M2Web Demonstration with VistA (http://vista.vmth.ucdavis.edu/) ---------------------------------------
> The link you provided for M2Web is an ancient document (at least 10 > years old) describing MHTTP, our old DTM based web server. That does not > link very directly to VistA or GT.M or M2Web development from the last > 10 years. The links in my sig below are more current
> --
> --------------------------------------- > Jim Self > Systems Architect, Lead Developer > VMTH Information Technology Services, UC Davis > (http://www.vmth.ucdavis.edu/us/jaself) > --------------------------------------- > M2Web Demonstration with VistA > (http://vista.vmth.ucdavis.edu/) > ---------------------------------------
