Welcome to the NEW CHUG— your ultimate destination for cutting-edge insights and discussions at the intersection of healthcare and technology.

Our platform is dedicated to exploring the dynamic landscape of healthcare technology, empowering professionals, enthusiasts, and innovators alike with the knowledge and resources to navigate the rapidly evolving field.

From telemedicine revolutionizing patient care to the transformative potential of artificial intelligence in diagnostics, we delve into a myriad of topics shaping the future of healthcare delivery. Whether you’re a seasoned healthcare IT professional, an aspiring entrepreneur in the digital health space, or simply curious about the latest innovations, our curated content, expert interviews, and thought-provoking articles provide a comprehensive exploration of healthcare technology’s most pressing issues.

Join us as we navigate the forefront of innovation, driving forward the transformation of healthcare for a healthier, more connected world.

Have questions or suggestions? Please use the contact button below.

Notifications

Clear all

Error during July 2014 Knowledgebase Update - Anyone else?

CPS, C-EMR, PM

Last Post by Anonymous 1 second ago

14 Posts

5 Users

0 Reactions

70 Views

RSS

mdoak

(@mdoak)

Posts: 92

Estimable Member

Topic starter

Has anyone else tried applying the July 2014 Incremental Knowledgebase update on CPS 12 yet? I did it on one of our databases and received an error. It looks like they have an SPR script in there near the end, but their update command is invalid in certain cases. I'm not sure if it would fail for everyone or only in certain cases. I opened an e-service ticket, but if anyone gets a solution over the weekend, please let us know. Here is the relevant section of the log.

08/01/14 20:34:05  Running Script: \KBInfo\kbdatafixes.sql
08/01/14 20:34:06  CInstall::RunSqlScript File: -- ==========================================================
-- SQL fix for SPR 59891 to address the problem description
-- ==========================================================

Begin
update ProblemDescriptionMap set SNOMEDMasterDiagnosisId = (select MasterDiagnosisId from 
MasterDiagnosis where code = '1221000119103' and status = '1') where (ICD9MasterDiagnosisId = 
'726996' and SNOMEDMasterDiagnosisId = '1412');
update Problem set SNOMEDMasterDiagnosisId =  (select MasterDiagnosisId from 
MasterDiagnosis where code = '1221000119103' and status = '1') where (ICD9MasterDiagnosisId = 
'726996' and SNOMEDMasterDiagnosisId = '1412');
End
 Exception: Number=512  State=21000  Source=Microsoft SQL Server Native Client 11.0

Description=Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.

Number=3621  State=01000  Source=Microsoft SQL Server Native Client 11.0

Description=The statement has been terminated.

, SQL=-- ==========================================================
-- SQL fix for SPR 59891 to address the problem description
-- ==========================================================

Begin
update ProblemDescriptionMap set SNOMEDMasterDiagnosisId = (select MasterDiagnosisId from 
MasterDiagnosis where code = '1221000119103' and status = '1') where (ICD9MasterDiagnosisId = 
'726996' and SNOMEDMasterDiagnosisId = '1412');
update Problem set SNOMEDMasterDiagnosisId =  (select MasterDiagnosisId from 
MasterDiagnosis where code = '1221000119103' and status = '1') where (ICD9MasterDiagnosisId = 
'726996' and SNOMEDMasterDiagnosisId = '1412');
End

Unspecified error
08/01/14 20:34:06  Execution Failed: \\pcmd\c$\201407kbupdate\EMRKB12.inf

Posted : August 1, 2014 11:17 am

Anonymous

(@Anonymous)

Posts: 0

New Member Guest

We recieved the same error this weekend. Opening up a ticket also.

Thanks,

Tonya Racine

Bone & Joint

Posted : August 3, 2014 11:45 pm

mdoak

(@mdoak)

Posts: 92

Estimable Member

Topic starter

I looked at the MasterDiagnosis table in our other three EMR databases and they all contain the exact same number of rows and they contain TWO rows that meet the criteria of code = '1221000119103' and status = '1'.

I haven't bothered to try running this on any of the others because I am 99% sure I will have the same issue with them. I'm also 99% sure this will affect anyone who applies this update although perhaps there is some scenario of upgrade paths that cause the problem and thus it apply to some customers and not everyone.

I'd be curious if anyone has applied it successfully and if so, what is the rowcount of your MasterDiagnosis table and the result of this query…

select MasterDiagnosisId from MasterDiagnosis where code = '1221000119103' and status = '1'

Our table contains 276029 rows and the above query yields two rows which means their script will fail.

-Matt

Posted : August 4, 2014 12:09 am

schung

(@schung)

Posts: 33

Trusted Member

I just applied this update to our test server (CPS 12) and didn't get any problem.

I also ran the query that listed above and it returned only one row.

I was planning to update our live server with this update...

Is there anyone else who is having this problem?

Simon

VNA

Posted : August 4, 2014 2:56 am

mdoak

(@mdoak)

Posts: 92

Estimable Member

Topic starter

I think if you only get one row in response to that query, it will complete for you just fine.

What I'm wondering is how come your database only has one row for that query while all of mine have two. It must be the result of some sort of upgrade path over time or something that we took and you did not. We went from CPS 04 to CPS 10 then to various 10 service packs, then straight to 12 skipping 11 and now to 12 SP3. Wondering what other problems might be caused by all the seemingly extra nonsense in that table. Might our lockups in the orders module when trying to add a new diagnosis be related? Maybe not, but who knows?

I still have not heard back from support on the ticket that I created Friday evening.

Posted : August 4, 2014 3:06 am

schung

(@schung)

Posts: 33

Trusted Member

We just upgraded from CPS 10 to CPS 12 SP3 last month.

BTW, I just ran that query on the live server and it also returned only one row, so I guess this upgrade should be fine for us.

I hope you will find the reason why your servers are having this problem soon.

Thanks

Simon

Posted : August 4, 2014 3:24 am

mdoak

(@mdoak)

Posts: 92

Estimable Member

Topic starter

Just talked to Luis at GE and he was appreciative of the info I provided and said they've had a bunch of calls about this today. He is currently working with one of the developers on a fix script.

He also mentioned this same thing (or something very similar involving the masterdiagnosis table) is happening to some customers during the 12.1 update script. I think 12.1 is early adopter only at this point, but probably has this same SPR script or something similar rolled into it

I'll post back when I get a concrete fix.

Posted : August 4, 2014 4:24 am

Anonymous

(@Anonymous)

Posts: 0

New Member Guest

Awesome. Luis is good he will get back to you . I ran the script and our two totals were 1147200 and 1413369.

Thanks,

Tonya Racine

Bone & Joint

Posted : August 4, 2014 4:30 am

mdoak

(@mdoak)

Posts: 92

Estimable Member

Topic starter

I don't think those are totals, but rather row IDs in that masterdiagnosis table, but yours and mine match exactly. 1147200 and 1413369.

Posted : August 4, 2014 4:40 am

Anonymous

(@Anonymous)

Posts: 0

New Member Guest

You are correct. Thanks for clarifying that for me. Is it strange that our row ID's in the table are the same??

Tonya

Posted : August 4, 2014 4:46 am

mdoak

(@mdoak)

Posts: 92

Estimable Member

Topic starter

Not really because I believe that this table isn't really something that customers manipulate directly - it's populated by installs, service packs, knowledgebases, etc. I suspect one of these along the way (that we both happened to install) is responsible for the duplicate entries. There is probably some cleanup that needs to be done in that table. Here's to hoping that the cleanup fixes other problems too. 🙂

Posted : August 4, 2014 4:50 am

mdoak

(@mdoak)

Posts: 92

Estimable Member

Topic starter

Here is what we ended up finding out. I've been able to successfully apply the KB to this database and will try to execute the query to change the status first before I apply it on the others.

Cause: This error will only happen for customers that have applied the June CPS ICD and CPT codes, before they applied July KB update. To fix this issue run the following and then re-run KB update:

--Set the Status of masterdiagnosis that did not happen during KB update

Update masterdiagnosis

Set status='0'

Where masterdiagnosisID=1147200

--Then you want make sure the version date is back to June

select name, value from symbol where name like '%VERSION%'

--The results should be something like:

Version 2014.07

--Run following script:

update symbol set value='2014.06'

where name='Version'

You should now be able to run July KB without this error.

Posted : August 6, 2014 2:53 am

tgregorich

(@tgregorich)

Posts: 19

Eminent Member

GE has posted a blurb on the service portal related to this

https://engage.gehealthcare.com/docs/DOC-43364

Posted : August 8, 2014 6:25 am

Anonymous

(@Anonymous)

Posts: 0

New Member Guest

tgregorich said:

GE has posted a blurb on the service portal related to this

https://engage.gehealthcare.com/docs/DOC-43364

That procedure does not work.

I tried it yesterday. Still got a failure.

Posted : August 11, 2014 2:16 am

24 Forums
9,940 Topics
39.9 K Posts
0 Online
6,470 Members

Forum Icons: Forum contains no unread posts Forum contains unread posts

Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed