GTM-E-RPARENMISSING error when signing meds in CPRS / VistA - mumps

I have an instance of OSEHRA VistA set up using the Vagrant autoinstaller, and using an imported KIDS drug file following these instructions. Users with correct permissions are able to enter and save med orders in CPRS using entries from the drug file, but when they try to sign the orders, CPRS throws this error:
M ERROR=ES1+12^ORCACT01, Right Parenthesis Expected, 150373642,-%GTM-E-RPARENMISSING LAST REF=^PSDRUG(“ASP”,6,1254)
As yet, this installation has no customized code. What might be causing this error?

Wow. A question in a subject I am an expert in.
I know this error well. It's caused by a developer using || or &&. These work on Cache; but not on GT.M, as they are not standard MUMPS. If you change the || to ! and the && to &, it will work in GT.M using the exact same semantics. I won't add more here as this is will get into the weeds.
The bug has been reported and will be fixed in future releases from the VA.
FYI, I am the author of the KIDS drug file. I am glad you find it useful.

Related

STM32 StdPeriph library USART example

I downloaded Stdperiph library and i want to make USART example run on STM32F4 - Discovery. I chose STM32F40_41xxx workplace, added stm32f324x7i.c file and compiled without any errors.
Issue is that I cant receive expected message in my terminal (using Hercules), also when I check RxBuffer it is receiving some bytes but not that I sent.
I checked baudrate, wordlength, parity several times. Do you have any idea what could I do wrong?
USART conf:
USART_InitStructure.USART_BaudRate = 9600;
USART_InitStructure.USART_WordLength = USART_WordLength_8b;
USART_InitStructure.USART_StopBits = USART_StopBits_2;
USART_InitStructure.USART_Parity = USART_Parity_Odd;
USART_InitStructure.USART_HardwareFlowControl = USART_HardwareFlowControl_None;
USART_InitStructure.USART_Mode = USART_Mode_Rx | USART_Mode_Tx;
STM_EVAL_COMInit(COM1, &USART_InitStructure);
Thank you.
First of all if you want to use hihg level abstraction libraries stop using obsolete SPL and start using HAL. Install the Cube. Generate the code - import into your favorite IDE and compile. Should work.
Your code does not show anything as USART clock may be net enabled as well as GPIOs. GPIOs may be configured wrong way. You system and peripheral clock may have wrong frequency. There are many more potential problems.

Alexa can't launch skill in beta test

I wrote an alexa-Skill whitch is running on my own server.
everthing looks good at developer.amazon configuration seems ok.
Also I can use at the menu point "test" the Service Simulator everything is fine. I get responses from my server can invoke Intents everything looks like it is working.
Now I gave me test free for beta testing. Used the invite link to added the skill to my list and set him active.
Here comes the strange part, if try to launch my skill with alexa, with the invoke name, Alexa response with "entschuldigung ich habe gerade schwierigkeiten versuche es später nochmal" (translated to english "sorry, I got some trouble (issues) try again later")
This is a German skill, so I set german in "Skill information" and set it available in germany under "Countries & Region"
I have no clue why I can't start my skill from my Alexa… maybe some of you had the same Problem and can help me with this issue.
thanks a lot
the amazon echo is configured for Germany too? IMO, did you implement the skill for US version too? change the echo to US lang, and test it there... when I developed the skill, I needed to use US version to beta test... not sure if that was fixed, or how you can test in other versions (I'm in UK)
I got it……
My Invocation Name were "Alexa start |skillname|" as it is shown in the example. So I tried to add another language like the first post suggest, I typed it in the field and got an error msg Invocation Name isn't allowed to contain "alexa".
I had to type "|skillname|" thats all… everything works now…

Getting rid of errors from using arrays as constants

So, as you may know, in PHP 5.6+, you can use arrays as constants. e.g.:
const MEMBER_TYPES = array("User", "Moderator", "Admin");
However, in my PHPStorm installation, I get an error when doing this, even though when running the code I get no errors at all, using PHP 5.6.8. None of the inspections I'm seeing via Alt+Enter are doing anything.. is there a way to suppress this specific error detection?
This functionality is not yet supported by PhpStorm
https://youtrack.jetbrains.com/issue/WI-26366 -- watch this ticket (star/vote/comment) to get notified on progress.
Reported as fixed in 10.0.2 by PhpStorm folks. https://youtrack.jetbrains.com/issue/WI-26366#comment=27-1257245

Itunes connect has changed to invalid binary

After i upload my application to app store after is done is show me in iphone application "has changed to invalid binary" and in the itunesconnect is show
http://i.stack.imgur.com/4vPJN.png
any solution ?
My experience:
There are many potential bug in your project.
1 .there may be private function(the third part SDK ,e.g. Reveal) in the project
2 .Missing Info.plist key - the app attempts to access privacy-sensitive data without a usage description.
Solve:
Generally,you will receive email from apple. I suggest you read it seriously.
It will tell you what should you do because they find out "invalid binary"...
Then solve the problem.

Find out running on XP embedded

Is there a way to find out if my program is running on XP embedded? I've tried .NET System.Environment.OSVersion, but the version information looks like that of a "normal" Windows XP, except for the minor version number, and relying on that seems to fragile to me.
A Microsoft eMVP (Bing Chen) on Egg Head Cafe suggests GetVersionEx and a particular version registry key...
1. Call API
BOOL GetVersionEx(LPOSVERSIONINFO lpVersionInfo);
OSVERSIONINFOEX structure (which is
the output of this call)
One of the members is wSuiteMask (a
WORD variable).
Check the VER_SUITE_EMBEDDEDNT
(0x00000040) flag in this variable.
2. Query value in Registry [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Product-Options]
Key Name: ProductSuite Type:
MULTI_SZ Value: EmbeddedNT
(In XP Pro, it seems that no
content in this key)
While Helen Elcock suggests looking for the FBA registry value:
I check for for the DWORD registery value
[HKEY_LOCAL_MACHINE\SYSTEM\FBA]
You only get first boot assistant on embedded.
GetVersionEx seems like the more stable approach, because someone might remove the FBA key in an effort to save another couple bytes, but I'm not sure if removing that key would cause the FBA to run again anyway. You'll probably be fine with either approach.