Hello back again!
Today there will be a brief introduction on how to get your needed information out of Molis.
By pressing "Esc", then "F1" and then "n" you can display the name of the current mask.
As an alternative you can read out the system parameter No. 1000. In this parameter the name of the current mask is saved.
If you want to combine your logic with the current mask you need to code:
$mask=ssysparam(xxx)
The xxx stands for your numerical register. In our case it will be the name of the current mask.
Watch out for the double "s" at the beginning!
So if you want to display it with the "mess" function you could write:
mess("Name of the mask: %%ssysparam(1000)%%%")
This function will only display the text in the message frame, which you can pop up at the bottom of your screen. This won't interrupt the user with any pop ups.
That's all for now, but the next entry comes soon!
Until then: Happy coding!!!!
Freitag, 7. Februar 2014
Sonntag, 2. Februar 2014
Those dates!!!!
Hi and welcome back to the MPL blog of your choice...
...well it's the only blog about the molis programming language. :D
As I described in the last post I will show you this time the huge difference between sample_dt.-1 and DT.-1.
So lets just begin with sample_dt.ORD. In this field the date of the currenct order is saved. If you want the date of not the current order but the order before you only have to write sample_dt.-1. If you want the date of the oder before that you write sample_dt.-2 and so on.
In comparison to sample_dt.ord we have DT{XX} and DT.-1{XX}. DT give us the date of the analytical procedure specified with XX.
So what is all the fuzz about it?
Well there is a big difference between these two functions. While sample_dt.-1 returns the date of the oder befor of the actual order DT.-1{XX} returns the date of the procedure befor the actual procedure.
An example: In your actual oder you want to measure hemoglobin, but only if you didn't measured it in the last week for the same patient. So you could check on sample_dt.-1 but that would only return the date of the last order not the date of your last hemoglobin procedure. So you see, there is room for many logical mistakes if you use sample_dt.-1 instead of DT.-1{XX}.
We will see a implementation of this post in the future.
Until then: Happy MPL coding!
...well it's the only blog about the molis programming language. :D
As I described in the last post I will show you this time the huge difference between sample_dt.-1 and DT.-1.
So lets just begin with sample_dt.ORD. In this field the date of the currenct order is saved. If you want the date of not the current order but the order before you only have to write sample_dt.-1. If you want the date of the oder before that you write sample_dt.-2 and so on.
In comparison to sample_dt.ord we have DT{XX} and DT.-1{XX}. DT give us the date of the analytical procedure specified with XX.
So what is all the fuzz about it?
Well there is a big difference between these two functions. While sample_dt.-1 returns the date of the oder befor of the actual order DT.-1{XX} returns the date of the procedure befor the actual procedure.
An example: In your actual oder you want to measure hemoglobin, but only if you didn't measured it in the last week for the same patient. So you could check on sample_dt.-1 but that would only return the date of the last order not the date of your last hemoglobin procedure. So you see, there is room for many logical mistakes if you use sample_dt.-1 instead of DT.-1{XX}.
We will see a implementation of this post in the future.
Until then: Happy MPL coding!
Anouncement
Hello back again!
Today I wont deliver a long informative post. But I wil outline the shape of a little series of post regarding one topic.
The topic is: how to get the most out of the REM field of an analytical procedure.
The REM field is a kind of commentary field open for any input you like.
At first I will introduce to you the concepts of nindex() and substrings, then I show you hor to build a multi level parser with your freshly gained knowlegde.
At the end of the mini series of posts I will show all of this in work as we redesigne or own "delta check" function.
"Why?" you migth ask, well because the build in function is all fucked up because of sample_dt.-1 vs DT.-1 and other reasons like totally awefulness ;)
So stay tuned! And happy coding!
Today I wont deliver a long informative post. But I wil outline the shape of a little series of post regarding one topic.
The topic is: how to get the most out of the REM field of an analytical procedure.
The REM field is a kind of commentary field open for any input you like.
At first I will introduce to you the concepts of nindex() and substrings, then I show you hor to build a multi level parser with your freshly gained knowlegde.
At the end of the mini series of posts I will show all of this in work as we redesigne or own "delta check" function.
"Why?" you migth ask, well because the build in function is all fucked up because of sample_dt.-1 vs DT.-1 and other reasons like totally awefulness ;)
So stay tuned! And happy coding!
Labels:
DELTA CHECK,
DT{},
MOLIS,
MPL,
nindex,
PROGRAMMING,
SAMPLE_DT,
substr
Abonnieren
Posts (Atom)