Not a complete answer, but some of the following might help...
You can control the output slightly more by invoking the standard captioned output used by Inquire as follows...
Select OPTION: INQUIRE TO FILE ENTRIES
OUTPUT FROM WHAT FILE: STATE//Select STATE NAME: MISSOURIANOTHER ONE:STANDARD
I'm a M developer now learning Java and all the host of technologies similar to those mentioned in the original job posting above. I somewhat agree with the sentiment that these non-Mtechnologies out there are relatively easy to learn on a rudimentary level,BUT take a lot of experience and time to
When VistA is installed in commercial hospitals and environments, how is billing handled? Are there some examples that could be provided where a billing package was successfully added to VistA?
I would be interested in the approach taken by the billing softwares added to VistA by varous non-VistA
THE FIELD SEPARATOR ('^') AND THEN ENCODING CHARACTERS (~|\) if left blank.
On 12/20/05, Larry Andreassen [EMAIL PROTECTED] wrote:
Per the VistA HL7 team, the answer is that you must enter the field separator at the programmers prompt.
Details following...
BACKGROUND
The encoding characters
There are nowtwo different flavors of the VistA HL7 package on VistA...
(1) VistA HL7 (I'll call it) CLASSIC
(2) VistA HL7 NEW
The VistA HL7 package has been totally rewritten recently. I have little awareness of the features in the NEW VistA HL7 package, but will make inquiries of the VistA
to the local site. This unblocks the queue, but is done in such a way to guarantee that the site isn't flooded with huge numbers of errorred messages.
Hope this helps!LJA
On 12/22/05, Larry Andreassen [EMAIL PROTECTED] wrote:
There are nowtwo different flavors of the VistA HL7 package on VistA
STCP2(Rd-err) S:$G(HLPRIO)=I HLERROR=1
08^Read Error D UNWIND^%ZTER Q
To remove the message from queue:
kill the x-ref, "AC","O",ien of link,ien of message in file #773
The status of the message may optionally be set to error(4).
On 12/22/05, Larry Andreassen [EMAIL PROTECTED] wrote:
I will send a message to the VistA HL7 team asking for clarification, and will respond back here with their answer.
(As I recall, the answer is a kludge... hard set the delimiters containing ^ from the programmer's prompt. But, please wait for a reply from the team.)
On 12/20/05, Robert Leonardo
Per the VistA HL7 team, the answer is that you must enter the field separator at the programmers prompt.
Details following...
BACKGROUND
The encoding characters and the field separator are stored in the HL7 Application Parameter file (#771.)
Here's the global map...
^HL(771,D0,0)= (#.01) NAME
Thanks for the AutoHotkey recommendation Kevin!!!
AutoHotkey is slightly harder to understand theusage, syntax, invocation, etc, than some other macro programs. But, the power and features are completely impressive! It seems to have a small footprint... I've had other macro systems seemingly
This conversation has shifted slightly, but significantly, and I think this might confuse some readers. Just so everyone understands...
The original post read...
Other than the HL7 documentation on the VA website, does anyone know of any resources to help me create a working HL7 interface. It
the system.I'm not sure when this software will be included in the FOIA release disk. But, typically it is included in the next FOIA release after the software is officially incorporated into VistA. (And, this software is now officially part of VistA.)
On 11/15/05, Larry Andreassen [EMAIL PROTECTED] wrote
Check out Shortkeys macro program. Their entry program is fully functional and free, with the limit that you can only enter 15 macros. But, that should be enough. http://www.shortkeys.com/lite.htm
(Everyone should be using a macro program of some sort anyway! Why type your name, or your address,
Comparing small and large team projects I've been involved with...
Small teams... Do the work...
Large teams... Do the process...
By process I mean a pre-defined set of steps, documents and stages. And, often these stages do not fit naturally withthe work.
On 10/5/05, Kevin Toppenberg [EMAIL
Use the first line, and other approaches to find the routines your interested in. After that, with a small number of routines, experiment with the ^XINDEX utility. That includes some very useful information about the linkages and relationships between routines and globals, plus more. It is not
If this is in a Cache environment, check out their debugger...
http://platinum.intersystems.com/csp/docbook/DocBook.UI.Page.cls?KEY=GCOS_debug#GCOS_debug_debugger
Their debugger allows setting break and watch points, stepping thru code, etc.
LJA
On 9/20/05, Greg Woodhouse [EMAIL PROTECTED]
I'd beware of using Google as part of a backup system. If you send too many messages (files embedded in a message) to your account in a 24 hour period, Google locks you out for a day, and may elect to pull the plug on your account I assume.
On 9/6/05, K.S. Bhaskar [EMAIL PROTECTED] wrote:
I agree
17 matches
Mail list logo
