Notifications
Clear all
Topic starter
We upgraded from EMR 9.8.9 to Service Pack 10 in our Test environment today. So far....
JBoss server upgrade, in the Program Files\Centricity Practice Solution\jboss\server\default\deploy\ directory, we had folders where the Oracle SID was uppercase and it converted it to lower case. Broke Qvera and Medfusion web service calls so they URL string had to be changed to account for the case change.
JBoss JMX Console - disabling or enabling contraindications. If you have a split JBoss system, it looks like to have to make changes to these on both servers. Changing one doesn't seem to change the other.
ADD_FORM_COMP is broken. In an encounter with 3 forms, if you specify a new for to be added in position 3, it used to put your new form in 3 and move the existing 3 to position 4. Now, 3 stays put and your new form ends up in position 4. Breaks a lot of our encounters as far as order.
Hear from another user that flags over a year old were deleted. Can't confirm in our test environment.
I'm sending this to GE support also.
Posted : August 27, 2015 12:05 pm
Being a SQL house and single JBoss system, I can't check my end to confirm or deny this happened to us as well. Still a good read to see what others are experiencing with SP10.
Posted : August 28, 2015 2:12 am
We've seen similar add form component behavior in test as well; was planning to upgrade this weekend, but this may be a show-stopper. Still working on a workaround.
Posted : August 28, 2015 7:25 am
Hi David,
For Qvera do you have the CQR channels or do you have others as well? We have a single Qvera engine that runs Test and Live channels - we took the 9.8.10 update into Test about a week ago and none of my test channels are having issues, I just want to make sure I'm not seeing a false positive since I cannot disconnect a few channels from Live to test Test.
Thanks
Mike
Posted : August 28, 2015 8:15 am
David, Any fix found for ADD_FORM_COMP?
FYI I heard flag over a year issue is just a display issue. They changed the default display to only show flags newer than a year.
Posted : August 30, 2015 6:53 pm
We upgrading over the weekend also and have the issue with the ADD_FORM_COMP. Is there an SPR already open?? Thanks, Misty
Posted : August 31, 2015 6:10 am
Please post the SPR # when you get one. Thanks.
Posted : August 31, 2015 7:31 am
Any workarounds for the ADD-FORM_COMP issue?
Posted : September 1, 2015 2:03 am
It's not very practical, but you could have the form entered into the encounter and use the open form string. Our Add Form functionality has not worked since SP7.
Posted : September 1, 2015 2:16 am
Hello everyone,
I have a solution for the add_form_comp() issue that I am testing. From what I can tell the bug either inserts at the beginning or the end depending on what you do, so the workaround function basically figures out where you want it, removes everything in front of it, adds the new form, then add everything else back. It could cause slowness depending on your forms and how far down the list you are adding forms but it seems to be working for me so far, especially for ordinal numbers. Its kind of hard for me to test before and after current as I don't have many of those. I plan to put it in a userlib file and rename all of my functions, then before SP 10 is in production I will uncomment the second line and when we do the install until it is fixed I will just comment it out again. Any feedback would be appreciated if anyone sees a better way to do anything here.
EDIT: This was made for CPS, not tested at all in EMR but I think it will work
{fn ADD_FORM_COMP_FIX(folderpath,name,insert_position,OPEN,label){
//Use this until upgrade to SP 10, then comment out
//ADD_FORM_COMP(folderpath,name,insert_position,OPEN,label) return ""
//at beginning and at end work okay
//fix is for ordinal numbers and before and after current
local formList = getfield(Get_form_list(),"|","")
local temp
local CurForm
local ordNum = "0" //just a default to keep it from crashing if it doesn't find the correct page (page refresh bug)
//needed right now for testing before and after current
cond
case (TOUPPER(insert_position) == "AT_BEGINNING" or TOUPPER(insert_position) == "AT_END")
//works fine
ADD_FORM_COMP(folderpath,name,toupper(insert_position),OPEN,label)
return ""
case (TOUPPER(insert_position) == "BEFORE_CURRENT" or TOUPPER(insert_position) == "AFTER_CURRENT")
//use _FormData from mldef1 to determine current form location
CurForm = CurrentForm()
for i = 1,i < size(formList), i = i + 1 do
temp = getfield(formList[i],"^","")
if temp[2] == curForm then
if insert_position == "BEFORE_CURRENT" then
ordNum = str(i) //insert at current lcoation to bump the rest back
else
ordNum = str(i + 1)
endif
endif
endfor
//continue
else
//assume ordinal number
ordNum = insert_position
//continue
endcond
if val(ordNum)size(formList) then
ADD_FORM_COMP(folderpath,name,"AT_END",OPEN,label)
return ""
endif
//its somewhere in the middle,remove first few
for i = 1,i 0, i = i - 1 do
temp = getfield(formList[i],"^","")
ADD_FORM_COMP(temp[1],temp[2],"AT_BEGINNING","","")
endfor
// --Now using open in the new form add instead, this is causing problems
//if toupper(OPEN) == "OPEN" then
// Delay(500)
// OPEN_FORM_COMP(folderpath + "\\" + name ,"")
//endif
return ""
}
}
{fn Delay(var){
local cnt = 0
for i = 1, i<=var,i = i + 1 do
cnt= cnt + i
endfor
return ""
}
}
{fn CurrentForm(){
//GE bug with tracking forms (related to page close handlers) may make this inaccurate but its the best we can do
// get page ID, this will be contained in one form set
local hold = getrow("_formData",0,"FID")
//need to parse out and read FSID from notetext, get it here
local temp = find("document","notetext")
local tmp = ""
local FormID = ""
local CheckOut= 0
//start with first fid
while CheckOut 0 then
return find("_MasterFormSets","Name","FSID",FormID)
endif
if match(temp,"[MLI_FORM:")<1 then CheckOut = CheckOut + 1 endif
endwhile
return ""
}
}
Posted : September 1, 2015 3:02 am
FYI, as a follow-up to the Flag issue, note that the Flags are not deleted from the tables, those >1 yr-old are just not visible from the Desktop. Those with patient context, however, can be seen within a Chart.
If desired, you can easily do a workaround via SQL, setting the Sent Date to 1/1/2015, for example (as if it were refreshed for the current year). That puts it back on the Desktop. Many of the Flags in question, however, are administrative and not patient-related.
It hasn't been an issue so far, since SP10 went in this past weekend.
Posted : September 2, 2015 1:34 am
Topic starter
Mike, to answer your Qvera question - we have 3 Qvera installs - each on a separate server. One for inbound messages, one for outbound messages, and one for CQR and VPN based channels. I don't know what your directory structure looked like before the upgrade. It may be that you didn't have anything capitalized in your folder structure and it didn't cause an issue.
Posted : September 2, 2015 4:36 am
Have you guys noticed a much higher Jboss (java.exe) memory load? It is more than double in my test environment.
java.exe is currently about 4.2 GB in production (about 120 users)
java.exe is currently about 8.95 GB in my test environment (about 2 users)
Mike Zavolas
Tallahassee Neurological Clinic
Posted : September 2, 2015 9:46 am
Our JBOSS.exe for 12.0.07 ran about 5.8 GB (25 users)
Now JBOSS .exe for 12.0.10 runs about 8.7 GB (25 users)
So far no real noticeable different in user experience
JJC
Posted : September 2, 2015 9:59 am
RE: the flag issue. There is an easy config file in the client to change for this. Ask GE and they will give you the directions. Super easy only problem is you have to roll it out to all the clients
RE: ADD_FORM_COMP issue. I hope to have an update from GE on Wednesday about this. I'll keep you guys posted.
Posted : September 8, 2015 6:06 pm
Page 1 / 2
Next
