Re: [Hardhats-members] Vista-Office - ..worldvista..openvista...opensource... off-topic eh?
Yes, you can argue about licenses from now until Sunday (in fact today :) I admit arguing about licenses is a bit like a religious argument. However, from what Mark says the issue of the license is completely moot. Because, Vista is NOT opensource. In fact it isn't even really free. It is a free copy of something closed. And just like you can make an origami bird from a copy of the bill of rights, if you did such to the original people would be quite miffed, and rightly so (actually they would probably be miffed if you did it to a copy too... but not as miffed). My main reason for being a proponent of GPL.. even though, as you point out there are issues with it.. Is because it DOES foster a unified development, despite the other issues surrounding it. For instance, how many people/companies have developed Gynecology or Pediatrics or modules for vista, and not released them as opensource to the comunity? So the wheel has to be reinvented time and time again. Who exactly, defines clearly distinct? What does that mean? Does it need VistA to run? Yours, mine, and ours... are not really community sentiments. Oh.. and even, if something is opensourced you can still sell it. Ah... whatever... (DAMN soapbox broke) Manolis P.S. I joined the mailing list, but it doesn't seem like there is too much action lately. On Sat, 2005-04-23 at 17:56 -0500, Maury Pepper wrote: Drs Kevin Bones (alias Rosanne Rosanneadanna, alias Emily Litella) Yes, the line must have been staticky. WorldVistA will definitely be putting an open source license on OpenVistA. Which license it will be is under discussion. GPL has both fans and critics, and in the fine print, it's not exactly clear where the boundaries are that separate what's yours from what's ours when it comes to packages bundled like VistA, written in code like M[UMPS]. Kevin's comment is correct, and that is why it's important to pick a license that will allow add-ons that are clearly distinct from VistA. That said, we also want a license that will foster a strong central repository -- not a fragmented one. A reminder: comments regarding this topic are welcome on the discussion list vista-open-source: http://groups.yahoo.com/group/vista-open-source -maury- - Original Message - From: Kevin Toppenberg To: hardhats-members@lists.sourceforge.net Sent: Saturday, April 23, 2005 5:27 PM Subject: Re: [Hardhats-members] Vista-Office - ..worldvista..openvista...opensource... off-topic eh? The understanding I got was that we wanted to allow companies to be able to develop modules that work with VistA, and have them be propriatary. Even on Linux, one can make a commercial program that makes use of open source technology. Kevin Doctor Bones [EMAIL PROTECTED] wrote: I realize, that I am doing nothing but muckraking at the moment... and, I know that I am NOT by any means a core vista person or personality. BUT... I am offended that we call openvista, openvista... it isn't covered by the GPL or another license that ensures development happens in the open. HENCE the open for the OPEN source. I realize I may be going off half cocked here and the connection was bad but from the meeting in Boston... I remember someone from world vista saying that they want to ensure that developers who develop code are not bound to release it as open source. ALTHOUGH it is a really good idea and we really appreciate it. This to me just sounds extremely wrong. You are just asking for a fragmented code base... and you are ensuring that NO major new developments happen from anyone outside the VA, unless out of some personal or corporate guiding principle decide to release it as open source. Thank you Sanchez and your new owners. I can assure you that whatever development I may/will/probably do will be opensourced and GPL'd... Does this mean that I don't want money... NO But, this does mean that I don't want money for making whatever changes I make to a FREE Software product. I know that no matter what I do will not equal the work done by one of the many hero's of
Re: [Hardhats-members] Error message when enterering D^ZU
You may have to edit the %ZOSV routine. What you edit depends upon which
version of Cache you are running. In any case, you may trick the Kernel
into believing you have enough licenses. But you may eventually encounter
another message which is generated by Cache with some comment about job
process limit exceeded. Your only recourse then is to limit the number of
jobs running if you wish to sign in.
- Original Message -
From: Nancy Anthracite [EMAIL PROTECTED]
To: hardhats-members@lists.sourceforge.net
Sent: Saturday, April 23, 2005 5:44 PM
Subject: Re: [Hardhats-members] Error message when enterering D^ZU
There are only a few changes, so no need to start all over. Look at 38
and
39, and fix the mode of Taskman and see what happens. If that doesn't
work,
comment out the lines in ZU and see if that does it.
On Saturday 23 April 2005 04:33 pm, Butch Jones wrote:
No,
I am using a version that might be a little older.
I guess it would be a good thing to download and start from scratch.
Sorry for the silly question.
Butch
--- Nancy Anthracite [EMAIL PROTECTED] wrote:
Are you using the current set of instructions that is online at
Hardhats?
There have been some changes in steps 38 and 39 and one other place
that
I
think were made to deal with this. I am thinking that this may be the
problem with the number of users on Cache again, or maybe that you
need
to
change the Mode of Taskman to general processor in the Taskman site
parameters file. Or that the primary menu needs to be set as EVE. I
am
loosing it because this has come up multiple times before and I can't
remember what the fix is.
Thurman, help! Didn't you have to fix this?
On Saturday 23 April 2005 12:08 pm, Butch Jones wrote:
I have just gotten back into community and am again trying to set up
a
new
installation of CACHE. I have been pretty successful in following
the
instructions on setting up a system.
When I sing onto Cache terminal and change the namespace to VISTA, I
am
getting an error message that displays ever-so-briefly when I type
D^ZU
from the prompt:
VISTA D^ZU
{I then get some error code that displays really fast and logs the
terminal off.}
any one know what I have missed in the setup process?
Thanks,
Butch Jones
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real
users.
Discover which products truly live up to the hype. Start reading
now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
--
Nancy Anthracite
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real
users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
--
Nancy Anthracite
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
Re: [Hardhats-members] Vista-Office - ..worldvista..openvista...opensource... off-topic eh?
There is nothing preventing anyone from working with VistA as an open source code base. As far as licensing is concernec, there is an old saying you can lead a horse to water but you can't make it drinkwith emphasis on the make. What is more of a challenge is opening the mindset of those who have built businesses with or have bought into the legacy paradigms that we are all familiar with. An appropriate license is necessary but it is not sufficient to stimulate open source behaviouruntil there is a compatible and significantly more valuable alternative to FOIA VistA there is no incentive to seriously consider and understand the open source process. The interesting thing is that there will always be a FOIA alternative so companies will be free to continue pursuing whatever approach they prefer with that code base. Joseph Doctor Bones wrote: Yes, you can argue about licenses from now until Sunday (in fact today :) I admit arguing about licenses is a bit like a religious argument. However, from what Mark says the issue of the license is completely moot. Because, Vista is NOT opensource. In fact it isn't even really free. It is a free copy of something closed. And just like you can make an origami bird from a copy of the bill of rights, if you did such to the original people would be quite miffed, and rightly so (actually they would probably be miffed if you did it to a copy too... but not as miffed). My main reason for being a proponent of GPL.. even though, as you point out there are issues with it.. Is because it DOES foster a unified development, despite the other issues surrounding it. For instance, how many people/companies have developed Gynecology or Pediatrics or modules for vista, and not released them as opensource to the comunity? So the wheel has to be reinvented time and time again. Who exactly, defines clearly distinct? What does that mean? Does it need VistA to run? Yours, mine, and ours... are not really community sentiments. Oh.. and even, if something is opensourced you can still sell it. Ah... whatever... (DAMN soapbox broke) Manolis P.S. I joined the mailing list, but it doesn't seem like there is too much action lately. On Sat, 2005-04-23 at 17:56 -0500, Maury Pepper wrote: Drs Kevin Bones (alias Rosanne Rosanneadanna, alias Emily Litella) Yes, the line must have been staticky. WorldVistA will definitely be putting an open source license on OpenVistA. Which license it will be is under discussion. GPL has both fans and critics, and in the fine print, it's not exactly clear where the boundaries are that separate what's yours from what's ours when it comes to packages bundled like VistA, written in code like M[UMPS]. Kevin's comment is correct, and that is why it's important to pick a license that will allow add-ons that are clearly distinct from VistA. That said, we also want a license that will foster a strong central repository -- not a fragmented one. A reminder: comments regarding this topic are welcome on the discussion list vista-open-source: http://groups.yahoo.com/group/vista-open-source -maury- - Original Message - From: Kevin Toppenberg To: hardhats-members@lists.sourceforge.net Sent: Saturday, April 23, 2005 5:27 PM Subject: Re: [Hardhats-members] Vista-Office - ..worldvista..openvista...opensource... off-topic eh? The understanding I got was that we wanted to allow companies to be able to develop modules that work with VistA, and have them be propriatary. Even on Linux, one can make a commercial program that makes use of open source technology. Kevin Doctor Bones [EMAIL PROTECTED] wrote: I realize, that I am doing nothing but muckraking at the moment... and, I know that I am NOT by any means a core vista person or personality. BUT... I am offended that we call openvista, openvista... it isn't covered by the GPL or another license that ensures development happens in the open. HENCE the open for the OPEN source. I realize I may be going off half cocked here and the connection was bad but from the meeting in Boston... I remember someone from world vista saying that they want to ensure that developers who develop code are not bound to release it as open source. ALTHOUGH it is a really good idea and we really appreciate it. This to me just sounds extremely wrong. You are just asking for a fragmented code base... and you are ensuring that NO major new developments happen from anyone outside
Re: [Hardhats-members] Vista-Office - ..worldvista..openvista...opensource... off-topic eh?
Several people (as in more than one but less than a billion) have written to me and said that a big reason that they do not participate, even though they are interested in VistA is the lack of an open license. In my previous post I mentioned something about wheels... we should be flying by now... I am still writing the documentation that I said would be done yesterday. I already know it is going to suck... but it will be released GNU FDL which means that you can modify it and make it better :P Manolis On Sun, 2005-04-24 at 02:19 +0300, Doctor Bones wrote: BLAH BLAH BLAH --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
Re: [Hardhats-members] Vista-Office - ..worldvista..openvista...opensource... off-topic eh?
Perhaps I am wrong... wait... I know... hard to believe :) BUT My point about FOIA's freeness is that it is free, not open. That is why people take it modify it and make other products from it. If it where open...it would foster more development. Several people I know are interested in Peds, and Gyne... which are notably absent. Several groups from my understanding have developed peds and gyne. But, have not shared them, simply because they don't have to. Now, if someone else develops peds and shares it to the community with a gpl'd vista then everyone can use it. And, the people who wanted to develop peds, now can focus their energies on other aspects. Let's say then that Kevin writes a completely new imaging system for vista because all the time he would have devoted to replicating a peds module is freed for him to work on imaging. He can horde it, but if he uses the gpl'd vista and the peds module that has been added then he is ethically and legally bound to release it gpl. Kevin's name was chosen at random but, the example wasn't. By saying that people will not use GPL until someone makes a GPL contribution is in my mind the exactly wrong way to look at it. You make it GPL and people will grow it to the point were companies will actually prefer to use a much modified GPLd VistA than the FOIA which of course will still be incorporated into the GPLd product. The idea isn't leading the horse to water and trying to make him drink... It is rather ... you lead the horse to water... there is an overhanging rock formation that nearly bridges the water. The overhang has been built by years of water erosion due to some beavers upstream diverting water into this particular channel. Now... the horse with his MIT doctorate in civil engineering takes leftover wood from the beavers dam building and completes the small portion remaining of this bridge He then claims the bridge is his and requires toll to pass. Oh... and he won't tell you how he made the remaining portion of the bridge. But, you are free to go find your own overhang.. or perhaps just to go hang. Or something like that. Manolis The Opensource mother goose On Sun, 2005-04-24 at 09:48 -0400, Joseph Dal Molin wrote: There is nothing preventing anyone from working with VistA as an open source code base. As far as licensing is concernec, there is an old saying you can lead a horse to water but you can't make it drinkwith emphasis on the make. What is more of a challenge is opening the mindset of those who have built businesses with or have bought into the legacy paradigms that we are all familiar with. An appropriate license is necessary but it is not sufficient to stimulate open source behaviouruntil there is a compatible and significantly more valuable alternative to FOIA VistA there is no incentive to seriously consider and understand the open source process. The interesting thing is that there will always be a FOIA alternative so companies will be free to continue pursuing whatever approach they prefer with that code base. Joseph --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
[Hardhats-members] Selling OpenVistA
Not a big deal, but please consider: Whenever I come in contact with health care professionals outside of the VA, and it's seems appropriate, I bring up and explain a little about OpenVistA. I'll give them the URLs for WorldVistA, Hardhats or both. Thing is, it's always on some scrap of paper that I'm sure gets lost. What I was thinking that it might be nice to print out some OpenVistA business cards. They wouldn't have my name on them, just maybe a logo, OpenVistA displayed prominently and the WorldVista and Hardhats URLs. This would seem to me to be much better than scraps of paper to spread the word. If there is interest in this, I would prefer to use an official, standard, design. What I'd really is be able to include some sort of catch phrase, something like Very affordable, very comprehensive healthcare IT. (I feel I need to point out that I wouldn't include open-source in this phrase, it just seems to muddy the waters at first.) And if I was WorldVistA, I'd copyright the phrase. MORE IMPORTANTLY Thinking about that catch phrase got me believing that WorldVistA should produce http://openvista.worldvista.org - a site with the primary purpose of selling OpenVistA. A site that would be designed to grab visitors and pique their interest about the product itself. Something with a screenshot of CPRS prominently displayed. This is the URL I'd like to put on the business cards. And I'm not trying to take away from the WorldVistA and Hardhats Web sites. They of course have plenty of great information on VistA, but you have to go fishing for it. Thanks, Chuck --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
Re: [Hardhats-members] Selling OpenVistA
I agree wholeheartedly, but I think we need to be sure OpenVistA really is going to continue to belong to WorldVistA first, or replace it with something that we know will. I recently bought the url OpenSourceVistA.net for my home server because I, like you, feel educating people about the meaning of Open Source is important. Once the concept of Open Source is more widely recognized, I am sure the demand will grow for Open Source healthcare solutions and others may see the value of converting their products to Open Source or to joining a great cause. On Sunday 24 April 2005 01:05 pm, chuck5566 wrote: Not a big deal, but please consider: Whenever I come in contact with health care professionals outside of the VA, and it's seems appropriate, I bring up and explain a little about OpenVistA. I'll give them the URLs for WorldVistA, Hardhats or both. Thing is, it's always on some scrap of paper that I'm sure gets lost. What I was thinking that it might be nice to print out some OpenVistA business cards. They wouldn't have my name on them, just maybe a logo, OpenVistA displayed prominently and the WorldVista and Hardhats URLs. This would seem to me to be much better than scraps of paper to spread the word. If there is interest in this, I would prefer to use an official, standard, design. What I'd really is be able to include some sort of catch phrase, something like Very affordable, very comprehensive healthcare IT. (I feel I need to point out that I wouldn't include open-source in this phrase, it just seems to muddy the waters at first.) And if I was WorldVistA, I'd copyright the phrase. MORE IMPORTANTLY Thinking about that catch phrase got me believing that WorldVistA should produce http://openvista.worldvista.org - a site with the primary purpose of selling OpenVistA. A site that would be designed to grab visitors and pique their interest about the product itself. Something with a screenshot of CPRS prominently displayed. This is the URL I'd like to put on the business cards. And I'm not trying to take away from the WorldVistA and Hardhats Web sites. They of course have plenty of great information on VistA, but you have to go fishing for it. Thanks, Chuck --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members -- Nancy Anthracite --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
RE: [Hardhats-members] VistA licensing.
VistA is Public Domain, not Open Source, always has been, always (at least should) will be. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ignacio Valdes Sent: Sunday, April 24, 2005 4:38 PM To: hardhats-members@lists.sourceforge.net Subject: [Hardhats-members] VistA licensing. I would suspect that the license would have to come down to either GNU GPL or FreeBSD type-license. Now, deciding between the two: let the games begin! :-) -- IV --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
Re: [Hardhats-members] VistA licensing.
I can understand how new modules (a.k.a packages) built on top of VistA infrastructure could be licensed under GPL, but I cannot believe that software obtained via FOIA could simply declared to be open source. Gregory Woodhouse [EMAIL PROTECTED] On Apr 24, 2005, at 1:44 PM, Roy Gaber wrote: VistA is Public Domain, not Open Source, always has been, always (at least should) will be. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ignacio Valdes Sent: Sunday, April 24, 2005 4:38 PM To: hardhats-members@lists.sourceforge.net Subject: [Hardhats-members] VistA licensing. I would suspect that the license would have to come down to either GNU GPL or FreeBSD type-license. Now, deciding between the two: let the games begin! :-) -- IV --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
Re: [Hardhats-members] VistA licensing.
Exactly, it couldn't, but the install routines, the additional modules, the documentation (non-VA) all of that could. My little attempt at getting greek to work even though it isn't much more than a hack and a hack explained to me by others could. And that could aid other Greek or foreign language implementers work on other things that are more important. So, if you use the modules, if you use the routines, if you use gpl software than you should gpl your source. By the way... VistA isn't exactly public domain either, because the VA will not allow external modifications to find it's way back to the codestream. It is a public domain copy. Which you can do with what you want, except alter the original. And, because Vista FOIA is released every so often, that would also have to be incorporated into the GPL modifications... We ( well not me per ce) are kind of doing that now (but without the license)... with viva .x instead of the foia. ... And NO, it isn't a perfect way to do GPL, but I don't really see the Government GPL'ing Vista, so it is up to us to GPL the modifications we make. ... I notice that I use GPL a lot... nothing wrong with the BSD license either... In fact I am even a Berkeley grad. On Sun, 2005-04-24 at 14:09 -0700, Gregory Woodhouse wrote: I can understand how new modules (a.k.a packages) built on top of VistA infrastructure could be licensed under GPL, but I cannot believe that software obtained via FOIA could simply declared to be open source. Gregory Woodhouse [EMAIL PROTECTED] On Apr 24, 2005, at 1:44 PM, Roy Gaber wrote: VistA is Public Domain, not Open Source, always has been, always (at least should) will be. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ignacio Valdes Sent: Sunday, April 24, 2005 4:38 PM To: hardhats-members@lists.sourceforge.net Subject: [Hardhats-members] VistA licensing. I would suspect that the license would have to come down to either GNU GPL or FreeBSD type-license. Now, deciding between the two: let the games begin! :-) -- IV --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
Re: [Hardhats-members] VistA licensing.
I should add that we're discussing OpenVistA of course and not FOIA VistA or any other name to replace OpenVistA as pointed out by Nancy. Molly Dr Molly Cheah wrote: Ignacio, The games, nay, the discussions started seriously in two other mailing lists last year, Vista-vendors and Vista-open-source on yahoogroups. That discussion fizzled out... simply because the decision making entity isn't the discussants. Maury just reminded us of the existence of vista-open-source mailist. Besides, we need to use those lists soon otherwise yahoogroups will deactivate them after a certain specified timeframe ?6months. Molly Ignacio Valdes wrote: I would suspect that the license would have to come down to either GNU GPL or FreeBSD type-license. Now, deciding between the two: let the games begin! :-) -- IV --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
[Hardhats-members] Clarification on Install notes for Installing Vista on Cahce
I had a question on the install notes that are posted on Hardhats. In item #20; == 20. Repeat the same thing for Routine Mapping for: %RCR, %XU*, %ZIS*, %ZO*, %ZT*, %ZV*. == why does %RCR not have an asterick appended? Should it be %RCR or %RCR* ? --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
Re: [Hardhats-members] VistA licensing.
It's the process not the license that really mattersPublic Domain could work just as well as an open source license in providing a collaborative medium if improvements are made available to others via public domainbut IMHO it is naive to expect this to happen given the past 15+ years of experience. It is important to note that we all have come to expect the VA to make its improvements available to everyone via FOIAis it not reasonable to expect others who benefit from the VA's and taxpayer investment in VistA to do the same. If that is not reason enough then let me point out that it is this quid pro quo that fuels a virtuous spiral of improvement that in turn positively impacts health outcomes...this is essentiallly the kind of process that created VistA and has fueled the VA's success in health quality. The fact that we are still chasing the holy grail of integrated EHR's and health information systems outside of the VA is ample proof that the legacy software business models are incapable of spawning this kind of improvement in software. Joseph Roy Gaber wrote: VistA is Public Domain, not Open Source, always has been, always (at least should) will be. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ignacio Valdes Sent: Sunday, April 24, 2005 4:38 PM To: hardhats-members@lists.sourceforge.net Subject: [Hardhats-members] VistA licensing. I would suspect that the license would have to come down to either GNU GPL or FreeBSD type-license. Now, deciding between the two: let the games begin! :-) -- IV --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members . --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
Re: [Hardhats-members] Selling OpenVistA
Only this: Trademark web site of OpenVistA http://tess2.uspto.gov/bin/showfield?f=docstate=4fule4.2.1 On Sunday 24 April 2005 05:36 pm, Dr Molly Cheah wrote: Nancy Anthracite wrote: I agree wholeheartedly, but I think we need to be sure OpenVistA really is going to continue to belong to WorldVistA first, or replace it with something that we know will. Any idea or update on the status of the claim to the name OpenVistA by Medsphere? Molly --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members -- Nancy Anthracite --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
Re: [Hardhats-members] Clarification on Install notes for Installing Vista on Cahce
It is correct without the *. On Sunday 24 April 2005 06:17 pm, Butch Jones wrote: I had a question on the install notes that are posted on Hardhats. In item #20; == 20. Repeat the same thing for Routine Mapping for: %RCR, %XU*, %ZIS*, %ZO*, %ZT*, %ZV*. == why does %RCR not have an asterick appended? Should it be %RCR or %RCR* ? --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members -- Nancy Anthracite --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
Re: [Hardhats-members] Clarification on Install notes for Installing Vista on Cahce
Butch; %RCR is an old routine but only a single routine in the namespace. It is a routine which accomplishes the MERGE command before the MERGE command was implemented. - Original Message - From: Butch Jones [EMAIL PROTECTED] To: Hardhats-members@lists.sourceforge.net Sent: Sunday, April 24, 2005 3:17 PM Subject: [Hardhats-members] Clarification on Install notes for Installing Vista on Cahce I had a question on the install notes that are posted on Hardhats. In item #20; == 20. Repeat the same thing for Routine Mapping for: %RCR, %XU*, %ZIS*, %ZO*, %ZT*, %ZV*. == why does %RCR not have an asterick appended? Should it be %RCR or %RCR* ? --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
[Hardhats-members] Re: Trying new install of Cache and Vista
All the new instructions were to be is what is there on Hardhats now plus the changes I suggested you do in the email to the ZU routine. I didn't want to add it unless you confirmed it worked OK. It seems that Mark Street found out the ?ZISF routine was missing as I recall, for his GTM install, so it may be missing for yours as well, but it may not be needed or something. I do not have Cache installed as I just got a new Windows machine, so I am going to post this out for someone who has done this to comment as I am still back working on a much older version with the CPRS/WIne issue. So, please fellow Hardhats, can you please give him some help here? On Sunday 24 April 2005 07:22 pm, you wrote: Nancy, Do you have a copy of the newer instructions that you will post on Hardhats? If so, care to send them to me and lets see if I can follow them to get an install up and running? I have begun my install and have gotten down to #34 of the old install notes and have run into the same problem. I don't want to change any of the routines today.. Was hoping to see the new instructions that you say you have. here is what I got when I attempted to perform step #34.. == USERZN VISTA VISTAD ^ZTMGRSET ZTMGRSET Version 8.0 **34,36,69,94,121,127,136,191,275** HELLO! I exist to assist you in correctly initializing the current account. D UCI^%ZOSV\ ^ | Not sure what all of this means, but it is what I received NOROUTINEA+2^ZTMGRSET |when I attempted to run ZTMGRSET. VISTA 3x2 / === I am running Cache version 5.0.13.5607.1 Vista (CACHE.DAT dated 2/27/2005) -- Nancy Anthracite --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
RE: [Hardhats-members] Re: Trying new install of Cache and Vista
Did you map the % routines? The error you are receiving is indicating that the routine %ZOSV is missing. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nancy Anthracite Sent: Sunday, April 24, 2005 8:34 PM To: Butch Jones; Hardhats Subject: [Hardhats-members] Re: Trying new install of Cache and Vista All the new instructions were to be is what is there on Hardhats now plus the changes I suggested you do in the email to the ZU routine. I didn't want to add it unless you confirmed it worked OK. It seems that Mark Street found out the ?ZISF routine was missing as I recall, for his GTM install, so it may be missing for yours as well, but it may not be needed or something. I do not have Cache installed as I just got a new Windows machine, so I am going to post this out for someone who has done this to comment as I am still back working on a much older version with the CPRS/WIne issue. So, please fellow Hardhats, can you please give him some help here? On Sunday 24 April 2005 07:22 pm, you wrote: Nancy, Do you have a copy of the newer instructions that you will post on Hardhats? If so, care to send them to me and lets see if I can follow them to get an install up and running? I have begun my install and have gotten down to #34 of the old install notes and have run into the same problem. I don't want to change any of the routines today.. Was hoping to see the new instructions that you say you have. here is what I got when I attempted to perform step #34.. == USERZN VISTA VISTAD ^ZTMGRSET ZTMGRSET Version 8.0 **34,36,69,94,121,127,136,191,275** HELLO! I exist to assist you in correctly initializing the current account. D UCI^%ZOSV\ ^ | Not sure what all of this means, but it is what I received NOROUTINEA+2^ZTMGRSET |when I attempted to run ZTMGRSET. VISTA 3x2 / === I am running Cache version 5.0.13.5607.1 Vista (CACHE.DAT dated 2/27/2005) -- Nancy Anthracite --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
RE: [Hardhats-members] VistA licensing.
You are absolutely correct, I stand corrected. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jim Self Sent: Sunday, April 24, 2005 8:44 PM To: hardhats-members@lists.sourceforge.net Subject: RE: [Hardhats-members] VistA licensing. I don't understand why suddenly there is so much repetition on this list of the mistaken notion that software in the Public Domain is not Open Source. It is surely the oldest form of Open Source and has been accepted as such since the term Open Source was originated. It was explicitly added to version 1.2 of the Open Source definition. Please see http://opensource.org/docs/definition.php VistA is Public Domain, not Open Source, always has been, always (at least should) will be. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ignacio Valdes Sent: Sunday, April 24, 2005 4:38 PM To: hardhats-members@lists.sourceforge.net Subject: [Hardhats-members] VistA licensing. I would suspect that the license would have to come down to either GNU GPL or FreeBSD type-license. Now, deciding between the two: let the games begin! :-) --- Jim Self Systems Architect, Lead Developer VMTH Computer Services, UC Davis (http://www.vmth.ucdavis.edu/us/jaself) --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
Re: [Hardhats-members] VistA licensing.
I think there is a distinction being made between varieties of open source. I don't think anyone is trying to say that public domain isn't open source. On Sunday 24 April 2005 08:43 pm, Jim Self wrote: I don't understand why suddenly there is so much repetition on this list of the mistaken notion that software in the Public Domain is not Open Source. It is surely the oldest form of Open Source and has been accepted as such since the term Open Source was originated. It was explicitly added to version 1.2 of the Open Source definition. Please see http://opensource.org/docs/definition.php VistA is Public Domain, not Open Source, always has been, always (at least should) will be. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ignacio Valdes Sent: Sunday, April 24, 2005 4:38 PM To: hardhats-members@lists.sourceforge.net Subject: [Hardhats-members] VistA licensing. I would suspect that the license would have to come down to either GNU GPL or FreeBSD type-license. Now, deciding between the two: let the games begin! :-) --- Jim Self Systems Architect, Lead Developer VMTH Computer Services, UC Davis (http://www.vmth.ucdavis.edu/us/jaself) --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members -- Nancy Anthracite --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
[Hardhats-members] Re: VistA licensing
LMN was honored to have RMS specifically weigh in on the subject of VistA licensing in November 2000: http://www.linuxmednews.com/974769856/index_html He covered just about everything. Excerpt: I am not a lawyer, but I have spoken extensively with lawyers about copyright questions. Presuming that the VistA software is in the public domain, if you combine it with a GPL-covered program you must release the combination *as a whole* under the GPL. Using the VistA code in this way is allowed because public domain status permits practically anything. However, the specific code that was in the public domain remains in the public domain. In other words, the fact that person A released the VistA code in a GPL-covered combination does not stop person B from using the VistA code in some other way. There's more, so please see the link. And have a good day, eat right, exercise and buy a LMN T-shirt :-) Only 1 sale to date :-( Thanks Nancy :-) -- IV On Sun, 24 Apr 2005 15:45:11 -0700 [EMAIL PROTECTED] wrote: From: Roy Gaber [EMAIL PROTECTED] To: hardhats-members@lists.sourceforge.net Subject: RE: [Hardhats-members] VistA licensing. Date: Sun, 24 Apr 2005 16:44:19 -0400 Reply-To: hardhats-members@lists.sourceforge.net VistA is Public Domain, not Open Source, always has been, always (at least should) will be. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ignacio Valdes Sent: Sunday, April 24, 2005 4:38 PM To: hardhats-members@lists.sourceforge.net Subject: [Hardhats-members] VistA licensing. I would suspect that the license would have to come down to either GNU GPL or FreeBSD type-license. Now, deciding between the two: let the games begin! :-) -- IV --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
Re: [Hardhats-members] Re: VistA licensing
1 sale, but 2 shirts! I showed them off at the Boston meeting where Iwegot the story of the WorldVistA meeting out in Linux Med News before the Associated Press even considered it! A real Scoop. ;-) On Sunday 24 April 2005 09:10 pm, Ignacio Valdes wrote: LMN was honored to have RMS specifically weigh in on the subject of VistA licensing in November 2000: http://www.linuxmednews.com/974769856/index_html He covered just about everything. Excerpt: I am not a lawyer, but I have spoken extensively with lawyers about copyright questions. Presuming that the VistA software is in the public domain, if you combine it with a GPL-covered program you must release the combination *as a whole* under the GPL. Using the VistA code in this way is allowed because public domain status permits practically anything. However, the specific code that was in the public domain remains in the public domain. In other words, the fact that person A released the VistA code in a GPL-covered combination does not stop person B from using the VistA code in some other way. There's more, so please see the link. And have a good day, eat right, exercise and buy a LMN T-shirt :-) Only 1 sale to date :-( Thanks Nancy :-) -- IV On Sun, 24 Apr 2005 15:45:11 -0700 [EMAIL PROTECTED] wrote: From: Roy Gaber [EMAIL PROTECTED] To: hardhats-members@lists.sourceforge.net Subject: RE: [Hardhats-members] VistA licensing. Date: Sun, 24 Apr 2005 16:44:19 -0400 Reply-To: hardhats-members@lists.sourceforge.net VistA is Public Domain, not Open Source, always has been, always (at least should) will be. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ignacio Valdes Sent: Sunday, April 24, 2005 4:38 PM To: hardhats-members@lists.sourceforge.net Subject: [Hardhats-members] VistA licensing. I would suspect that the license would have to come down to either GNU GPL or FreeBSD type-license. Now, deciding between the two: let the games begin! :-) -- IV --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members -- Nancy Anthracite --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
Re: [Hardhats-members] Need help with an input transform.
Greg, I'm lost. I thought that the input transform code WAS the screening process. Can you discribe how these two differ? Thanks Kevin --- Gregory Woodhouse [EMAIL PROTECTED] wrote: This is hows Fileman sets screens on pointers. Rather than edit the input transform, you should modify the screen. Gregory Woodhouse [EMAIL PROTECTED] On Apr 23, 2005, at 6:46 PM, Kevin Toppenberg wrote: I need help understanding an input transform In file 50.7/PHARMACY ORDERABLE ITEM, in field MED ROUTE (.06), I am being limited in the choices available to me. I want to be able to put in ORAL or PO for a drug route. Here is a screen log: INPUT TO WHAT FILE: PHARMACY ORDERABLE ITEM// EDIT WHICH FIELD: ALL// Select PHARMACY ORDERABLE ITEM NAME: dilTIAZEM TAB NAME: DILTIAZEM// DOSAGE FORM: TAB// (No Editing) IV FLAG: INACTIVE DATE: DAY (nD) or DOSE (nL) LIMIT: MED ROUTE: BUCCAL// PO?? Enter the most common MED ROUTE associated with this medication. ONLY MED ROUTES MARKED FOR USE BY ALL PACKAGES ARE SELECTABLE. MED ROUTE: BUCCAL// - Here I show that PO is a valid record in the MEDICATION ROUTE file (50.1)--and that it DOES appear to be marked for use by all packages OUTPUT FROM WHAT FILE: MEDICATION ROUTES// Select MEDICATION ROUTES NAME: PO 1 PO ORAL PO 2 PO SC ORAL/SUBCUTANEOUS PO SC CHOOSE 1-2: 1 ORAL PO ANOTHER ONE: STANDARD CAPTIONED OUTPUT? Yes// (Yes) Include COMPUTED fields: (N/Y/R/B): NO// b BOTH Computed Fields and Record Num ber (IEN) NUMBER: 1 NAME: ORAL OUTPATIENT EXPANSION: MOUTH ABBREVIATION: PO PACKAGE USE: ALL PACKAGES Here is the input transform for the field (field .06 of file 50.7). INPUT TRANSFORM: S DIC(S)=I $P(^(0),^)'=ORAL,$P(^(0),^,4) D ^DIC K DIC S DIC=DIE,X=+Y K:Y0 X The node;piece 0;4 -- Package Use(0:national drug file only, 1:All packages) So each entry is tested for $P(^(0),^)'=ORAL and $P(^(0),^,4)0 both must be true. 1. I don't understand how all an input transform is setup. For example, before calling d ^DIC, doesn't DIC=FileNum have to be set, and DIC(0)=AEQ or something. Also what is the naked reference ^(0) referring to. Also, how does the input transform communicate back? By setting $T, or by killing X? If X is killed is any further processing carried out by fileman? 2. Looking at this specific example, there seems to be a specific restriction against having a route to be ORAL--why? Thanks Kevin __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
RE: [Hardhats-members] GT.M question: ZBREAK questions
In other flavors of M you can turn BREAK on and then place breaks in your code, I am on my windows box right now so I cannot give a more precise answer, sorry. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Toppenberg Sent: Sunday, April 24, 2005 11:05 PM To: hardhats-members@lists.sourceforge.net Subject: Re: [Hardhats-members] GT.M question: ZBREAK questions I had figured out the answer for the first part of this post. But I was hoping someone would comment on the second part. I copy it here again, Also, it seems that there is ONE breakpoint held by GT.M. I.e. $ZBREAK is a variable that holds the one breakpoint for the system, rather than a function that allows creating of multiple breakpoints scattered across a source file. Is this correct? Thanks Kevin --- Kevin Toppenberg [EMAIL PROTECTED] wrote: I have been playing with the GT.M function ZBREAK. I can do this, and it works: set pos=A1^test ZBREAK @pos And I can do this: ZBREAK A1^test:n tmg s tmg=$$STEPTRAP^TMGTPSTP($ZPOS,1) but I CAN'T do this: ZBREAK @pos:n tmg s tmg=$$STEPTRAP^TMGTPSTP($ZPOS,1) Any ideas why? Or how to achieve the above? I am wanting to be able to ask the user to specify an address, and then set a custom breakpoint dynamically. Also, it seems that there is ONE breakpoint held by GT.M. I.e. $ZBREAK is a variable that holds the one breakpoint for the system, rather than a function that allows creating of multiple breakpoints scattered across a source file. Is this correct? Thanks Kevin __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
Re: [Hardhats-members] Need help with an input transform.
The input transform is (usually) generated code. Rather than manually set the screen in the input transform, you should specify the screen (e.g., when creating the field) and let Fileman create the input transform for you. Sometimes you need to create your own input transform, but most of the time, you should let Fileman do it for you. Gregory Woodhouse [EMAIL PROTECTED] On Apr 24, 2005, at 7:42 PM, Kevin Toppenberg wrote: Greg, I'm lost. I thought that the input transform code WAS the screening process. Can you discribe how these two differ? Thanks Kevin --- Gregory Woodhouse [EMAIL PROTECTED] wrote: This is hows Fileman sets screens on pointers. Rather than edit the input transform, you should modify the screen. Gregory Woodhouse [EMAIL PROTECTED] On Apr 23, 2005, at 6:46 PM, Kevin Toppenberg wrote: I need help understanding an input transform In file 50.7/PHARMACY ORDERABLE ITEM, in field MED ROUTE (.06), I am being limited in the choices available to me. I want to be able to put in ORAL or PO for a drug route. Here is a screen log: INPUT TO WHAT FILE: PHARMACY ORDERABLE ITEM// EDIT WHICH FIELD: ALL// Select PHARMACY ORDERABLE ITEM NAME: dilTIAZEM TAB NAME: DILTIAZEM// DOSAGE FORM: TAB// (No Editing) IV FLAG: INACTIVE DATE: DAY (nD) or DOSE (nL) LIMIT: MED ROUTE: BUCCAL// PO?? Enter the most common MED ROUTE associated with this medication. ONLY MED ROUTES MARKED FOR USE BY ALL PACKAGES ARE SELECTABLE. MED ROUTE: BUCCAL// - Here I show that PO is a valid record in the MEDICATION ROUTE file (50.1)--and that it DOES appear to be marked for use by all packages OUTPUT FROM WHAT FILE: MEDICATION ROUTES// Select MEDICATION ROUTES NAME: PO 1 PO ORAL PO 2 PO SC ORAL/SUBCUTANEOUS PO SC CHOOSE 1-2: 1 ORAL PO ANOTHER ONE: STANDARD CAPTIONED OUTPUT? Yes// (Yes) Include COMPUTED fields: (N/Y/R/B): NO// b BOTH Computed Fields and Record Num ber (IEN) NUMBER: 1 NAME: ORAL OUTPATIENT EXPANSION: MOUTH ABBREVIATION: PO PACKAGE USE: ALL PACKAGES Here is the input transform for the field (field .06 of file 50.7). INPUT TRANSFORM: S DIC(S)=I $P(^(0),^)'=ORAL,$P(^(0),^,4) D ^DIC K DIC S DIC=DIE,X=+Y K:Y0 X The node;piece 0;4 -- Package Use(0:national drug file only, 1:All packages) So each entry is tested for $P(^(0),^)'=ORAL and $P(^(0),^,4)0 both must be true. 1. I don't understand how all an input transform is setup. For example, before calling d ^DIC, doesn't DIC=FileNum have to be set, and DIC(0)=AEQ or something. Also what is the naked reference ^(0) referring to. Also, how does the input transform communicate back? By setting $T, or by killing X? If X is killed is any further processing carried out by fileman? 2. Looking at this specific example, there seems to be a specific restriction against having a route to be ORAL--why? Thanks Kevin __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
Re: [Hardhats-members] Need help with an input transform.
I should add that Fileman allows you to edit the input transform (and sometimes this is precisely what you need to do), but there's a downside: once the input transform becomes code that you write, Fileman is no longer able to maintain it itself. If at a later time, you need to modify the field definition, you will need to edit the input transform yourself (unless, of course, you want to throw away your changes and go back to a vanilla input transform.) Gregory Woodhouse [EMAIL PROTECTED] On Apr 24, 2005, at 8:19 PM, Gregory Woodhouse wrote: The input transform is (usually) generated code. Rather than manually set the screen in the input transform, you should specify the screen (e.g., when creating the field) and let Fileman create the input transform for you. Sometimes you need to create your own input transform, but most of the time, you should let Fileman do it for you. --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
RE: [Hardhats-members] VistA licensing.
I find that the most flexible license is one that doesn't exist - such as Public Domain. One of my favorite little programs is a Photoshop like replacement for Windows called Paint.NET. The license is: Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the Software), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. By far the most flexible, quickest to read, and easiest to understand. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nancy Anthracite Sent: Sunday, April 24, 2005 9:07 PM To: hardhats-members@lists.sourceforge.net Subject: Re: [Hardhats-members] VistA licensing. I think there is a distinction being made between varieties of open source. I don't think anyone is trying to say that public domain isn't open source. On Sunday 24 April 2005 08:43 pm, Jim Self wrote: I don't understand why suddenly there is so much repetition on this list of the mistaken notion that software in the Public Domain is not Open Source. It is surely the oldest form of Open Source and has been accepted as such since the term Open Source was originated. It was explicitly added to version 1.2 of the Open Source definition. Please see http://opensource.org/docs/definition.php VistA is Public Domain, not Open Source, always has been, always (at least should) will be. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ignacio Valdes Sent: Sunday, April 24, 2005 4:38 PM To: hardhats-members@lists.sourceforge.net Subject: [Hardhats-members] VistA licensing. I would suspect that the license would have to come down to either GNU GPL or FreeBSD type-license. Now, deciding between the two: let the games begin! :-) --- Jim Self Systems Architect, Lead Developer VMTH Computer Services, UC Davis (http://www.vmth.ucdavis.edu/us/jaself) --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members -- Nancy Anthracite --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95alloc_id396op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
