@dave-zibble
Forum Replies Created
-
AuthorReplies
-
Just look what you can learn by posting your old Tcl out there!!! (i.e. You’re a rusty old integrator, you don’t read e-mail for comprehension and you better get current on the Tcl shizzle!)
Here’s an old one that will get you going. Important thing is the foreach construct for looping through the segments in the message. run {
keylget args MSGID mh
set msg [msgget $mh]
set fld_delim [cindex $msg 3]
set disp “CONTINUE”
# Find PV1 segment, get disch date from it.
foreach elem [split $msg “r”] {
if { [cequal [csubstr $elem 0 3] “PV1”] } {
set pv1_list [split $elem $fld_delim]
set disch_date [lindex $pv1_list 45]
if { $disch_date > 0 } {
set disp “KILL”
break
}
}
}
I don’t know how much CDH spent on this. The technology makes the e-mail sender reply to a verification message to release their e-mail from quarantine. If they don’t reply, you don’t get the e-mail. Users can configure specific whitelists, which can contain wildcards like *@*.edu or *@*.il.gov, so all your outside university and government contacts e-mail avoids spam filtration.
Works well.
Your mnemonic is ITCFM, 7 screens back…. We are not setup this way in production, however, I tried flipping the bolded parms to Yes on our test box and bouncing. I expected to have the transmit error out when I stopped the thread on the engine. It did. Then after the inbound on the engine was Up I expected the transmit to start up on its own. It never did. I think I might run this by McKesson since they are here this week for 11.0 upgrade training. If I learn something I’ll post it here. Transmit/Extract Options: Page 1
Extended transaction logging . . . . . . . . . . . . . Y (Y/N)
Auto start transmit/extract in the Nightly Job Stream . Y (Y/N)
Auto restart transmit from the extract program . . . . N (Y/N)Auto restart extract from the transmit program . . . . N (Y/N)
Sleep time after all records have been transmitted . . 20 (seconds)
Number of negative acknowledges before error . . . . . 5 (times)
Transmit job name prefix . . . . . . . . . . . . . . . QDX
Auto restart on timeout/NAK limit error . . . . . . . . N (Y/N/P)Wait time for acknowledgement . . . . . . . . . . . . . 15 (seconds)
Transmit STAT orders before non-STAT orders . . . . . . Y (Y/N)
Send cancel code on order cancel transactions . . . . . Y (Y/N)
September 21, 2006 at 2:30 pm in reply to: Removing parenthesis and dashes from phone numbers #59692There was a small but significant typo in the example. The right parens in the first parameter was mistyped as a }. You can do it Ariba!! It works like a charm!
tcl>set a (630)555-1212
tcl>set b [string map “( {} ) {} – {}” $a]
tcl>echo $b
6305551212
Yes and Yes. You’ll see in this screen shot the first route detail entry is the ADT. I once had a need to get a patient into to a system before the order arrived. I did this as Jim said by creating two Xlates. There was plenty of data in the PID segment of the order message to create an A08 that would post. By placing the ADT Xlate first in the routing table, that message was sent first. Also, its easier to keep track of your magic when you can see it on the route properties.
#!/usr/bin/ksh eval `/quovadx/qdx5.3/integrator/sbin/hcisetenv -root ksh /quovadx/qdx5.3/integrator
` forever is long time!
Try the search button and “Search for Author” I found you and your posts with *lake as the search criteria
“Da Management” is of the opinion that we povide 24/7 and 365 coverage for the enterprise integration platform (in consideration for current compensation). So “we” don’t go on vacation at the same time, or fly in the same plane.
In addition, we rotate through an on-call for our “application team” and we are not compensated for this.
I like the dream shop in Michigan that won’t call me between 12:00 and 4:00!!
I think your CIO thinks your on call pay “looks like” it going bye bye.
Our 80+ person TIS group is rapidly tansitioning frompagers to cell phones as a primary device on ths hip. See link below for info on how we “wired” up the hospital for cell phone and PDA use. The myth of cell phones messing up life support haas been mostly disspelled. http://www.cdh.org/News.aspx?id=9431 (BE SURE TO PRESS PLAY)
-
AuthorReplies
