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

Duplicate OBS in table

Bugs, Known Issues, Open Cases

Last Post by Anonymous 1 second ago

2 Posts

2 Users

0 Reactions

79 Views

RSS

joeg1962

(@joeg1962)

Posts: 843

Noble Member

Topic starter

Is anyone else having difficulty with duplicated OBS codes?

Per GE:

KNOWN DEFECT: It was determined that duplicate data item (“ALK PHOS”) in the ObsDef table is a KNOWN DEFECT (KM38323) as part of the ObsTerm Kit released from MediSpan (3^rd-party)

Vendor identified issue back in March 2018 and has been actively working on a fix

Resolution Timeline: No definitive timeline at this time. Likely will be resolved with a KB update (typically 2-3 cycles after issue is identified albeit, again, no definitive timeline at this point)

This means that VFE forms, GE Letters, etc..., that retrieve OBS values is getting inconsistent results. Sometimes it may grab the correct code, and other times the bogus (duplicate) code.

In real terms, 'ALK PHOS' is a lab test result. So, if you are trying to see or print last value, you might get a result or you might not. This impacts clinical care.

The list, as I know it, includes the following OBS Codes. If you utilize any of these codes, beware of results you retrieve.

AFB SMEAR
AGITATION
ALBUMIN BF
ALK PHOS
BBSALTFOOT
BBSBEHIND
BBSFINAL
BBSFTFRONT
BBSINITIAL
BBSSITSTAND
BNSARCASTG1
BREAST INSP
C STD PAN
CHLAMYD DFA
CMV AB IGG
DERMPLAN
DTAPHBIPV1
DTAPHBIPV2
DTAPHBIPV3
HAND1CAST
HAND2CAST
HOMELESS
HXACTINICKER
KNEE1INCHEAL
KNEEPALPL
KNEEPALPR
LP(A)
LYMPHS %
NAME OF OBSE
NAVRN SCHAPP
NEVIRAPINE
NORDIAZEPAM
NOVAREL_STE
PAINSCALE
PHENOBARBITA
PREGNANT
PRG#11DELVDT
PYRAZINAMIDE
RELOCATTPL
REPRONEX_STE
VC PREBD
VENTRIC RATE

Posted : July 3, 2018 12:14 am

chaddix

(@chaddix)

Posts: 177

Estimable Member

We are experiencing the same issue; LYMPHS % is causing havoc on one particular form that uses LASTOBSVALUE and LASTOBSDATE. When I spoke with GE, the message I received is that this will be resolved in NorthStar.

The good news...after upgrading to CPS 12.3.1, this issue appears to be resolved. The duplicate terms are still present in the OBSHEAD table, but LASTOBSVALUE("LYMPHS %") and LASTOBSDATE("LYMPHS %") no longer return NULL.

Disclaimer: I have a sample size of 1 and my team is still testing. However, I don't recall LASTOBSVALUE("LYMPHS %") ever working prior to the upgrade.

Posted : July 11, 2018 9:35 am

Share:

24 Forums
9,940 Topics
39.9 K Posts
13 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

Powered by wpForo Powered by wpForo version 2.4.0