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

Clinical Date Formula Error

Page 3 / 3 Prev

Trading Post

Last Post by Anonymous 1 second ago

34 Posts

3 Users

0 Reactions

216 Views

RSS

wsc27

(@sclayton)

Posts: 142

Estimable Member

Topic starter

After doing some trial and error with the {DOCDATA.DATA} like "*PATIENT INSTRUCTIONS*" I keep getting same date error when I use the following filters:

*PATIENT*

*INSTRUCTIONS*

*PATIENT INS*

But for {DOCDATA.DATA} = "PATIENT INSTRUCTIONS" filter (I find this interesting, the report runs with no error, but blank data which is correct cause there isn't DOCDATA.DATA that only contains "PATIENT INSTRUCTIONS". It seems like to me that the * multiple char is messing up the Patient Instructions filter where as the filter for *VIS* works fine.

Posted : November 11, 2013 6:19 am

wsc27

(@sclayton)

Posts: 142

Estimable Member

Topic starter

baj, I tried running the report with just one day date range, still getting same error. The report runs fine with DOCUMENT.ClinicalDate, but getting error if use the Date Conversion.

baj said:

I am out of ideas. But I checked what happens when we enter invalid date in EMR. Currently, it is auto-correcting to a valid date. I am not sure, if this was done for earlier dates.

You probably can try to run different date ranges and see if you can find out in which range you are getting the error.

Posted : November 11, 2013 11:01 pm

joeg1962

(@joeg1962)

Posts: 843

Noble Member

Start with a brand new report. You simply want to print detail lines, and then as you review through the output data the 'error' should be evident.

The layout might be as simple as:

{PERSON.SEARCHNAME} {DOCUMENT.DOCTYPE} {DOCUMENT.SUMMARY} {DOCUMENT.CLINICALDATE} {DOCDATA.DATA} {@ClinicalDate}

You can experiment with different filters (selects) until you get an error.

By the way, I had to follow a similar route once before as 'some' entries in the OBS table did not have a valid OBSDATE. Once I found them and realized they were old, I added an extra filter for OBS.DBCREATE > date(2007,1,1)

And, if you want to take off-line, feel free to directly email me.

Posted : November 12, 2013 12:07 am

wsc27

(@sclayton)

Posts: 142

Estimable Member

Topic starter

Thanks to Joseph, I ended up having to sort the DOCUMENT.CLINICALDATE which will either show the "bad" data at the beginning or end of the report. Once the bad data was fixed, the date conversion formula works & report is able to run through the whole process.

Posted : November 12, 2013 3:20 am

Page 3 / 3 Prev

Share:

24 Forums
9,942 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

Powered by wpForo Powered by wpForo version 2.4.0