eodoll posted:
Its very hard at first but gets easy when you figure it out.
Like any language... Youre probably more hung up in the grammar/vocabulary than the actual complexity of the softwatre if youre talking about college level programming.
Yeah, it's syntax that gives me a headache.
We are trying to filter orders coming from our EMR based on which ones need to be routed to Cardiology.
Basically if it is cardiology, in location A or B, and not a certain type of EKG or TT we send it.
If it is Cardiology and it is not in location A or B and not among another set of order types, we send it.
Otherwise we discard it.
The code someone wrote before I took over the interface used a series of nested IF statements, which always seem to be difficult to get right in eSQL. I am probably going to just change it to several independent functioms that each set a variable to true or false and then check all of those at the end.
This is only a small part of my job, most of it is analyzing the data needs on both ends, creating HL7 specifications for the transfer, building the interface mappings, testing, troubleshooting, and documentation. But almost every interface has at least some kind of filter logic to make it work right. Eventually we'll have enough examples that I can just copy and edit other code that people wrote. Although a real programmer would knock it out in like five minutes blindfolded.
-----signature-----
Using the mirror of ridicule to force conservatives to
confront their own stupidity.
. 
.
