Getting the error, while when we create an Allergy in Vista CPRS - Regarding

[Karuppasamy S]

Hi Team,

I am getting the error message in CPRS, while we create an allergy from my application and integrated to Vista. I passed the below fields value to EDITSAVE^ORWDAL32(ORY, ORALIEN, ORDFN, OREDITED) RPC. then allergy created in Vista, and it is shows in CPRS. but I am getting the LOCK ^XTMP("GMRAED",123) for that patient in Manage Locks. it is not release after allergy completion

But if after that, I create an allergy from CPRS, that time, I am getting the error. Shall you please guide me step by step process, why this error is happening and how to resolve it.

I am passing the parameters to EDITSAVE^ORWDAL32 RPC
ORY = " "

ORALIEN = 0

ORDFN = Patient ID (123)

OREDITED = ("GMRACHT",0) =1

                       ("GMRACHT",1) =3240624.0301
                       ("GMRACMTS",0) =4
                       ("GMRACMTS",1) ="TEST"
                       ("GMRACMTS",2) ="TEST1"
                       ("GMRACMTS",3) ="TEST2"
                       ("GMRACMTS",4) ="TEST3"
                       ("GMRAGNT") ="RED BELL PEPPERS^568^120.82,"
                       ("GMRANATR") ="A^ALLERGY"
                       ("GMRAOBHX") ="o^OBSERVED"
                       ("GMRAORDT") =3240624.0301
                       ("GMRAORIG") =64
                       ("GMRARDT") =20240624
                       ("GMRASEVR") =1
                       ("GMRASYMP",0) =5
                       ("GMRASYMP",1) ="528^ABNORMAL VISION"
                       ("GMRASYMP",2) ="52^CHILLS"
                       ("GMRASYMP",3) ="9^DIARRHEA"
                       ("GMRASYMP",4) ="67^DRY MOUTH"
                       ("GMRASYMP",5) ="51^CHEST PAIN"
                       ("GMRATYPE") ="F^FOOD"



Thanks,
Karuppasamy S

[Sam Habiel]

I took a look at the source code in UPDATE^GMRAGUI1. I see this:

 90  L +^XTMP("GMRAED",DFN):1 I '$T D MESS Q

...

151  L -^XTMP("GMRAED",DFN)

So it's correctly locking and unlocking. So my guess you either have an old version, or you modified the code.

The way I would troubleshoot it is to either use DEBUG^XWBTCPM with an appropriate breakpoint, or run the call EDITSAVE^ORWDAL32 from the command line and do a step by step debugging to see what is happening.

--Sam

--
--
http://groups.google.com/group/Hardhats
To unsubscribe, send email to Hardhats+u...@googlegroups.com

---
You received this message because you are subscribed to the Google Groups "Hardhats" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hardhats+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hardhats/2e79c077-56f9-4068-abde-6ec550eca06cn%40googlegroups.com.