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 2 / 3 Prev Next

Trading Post

Last Post by Anonymous 1 second ago

34 Posts

3 Users

0 Reactions

215 Views

RSS

wsc27

(@sclayton)

Posts: 142

Estimable Member

Topic starter

Ok, that's what I am currently doing. But I don't understand why the filters wouldn't work in the original report so I wont have to recreate the report from scratch everytime??

Posted : November 11, 2013 3:53 am

baj

(@baj)

Posts: 99

Estimable Member

There may be invalid dates like 11/11/20113, for eg. if someone tried to manually enter (today's) date and pressed 1 twice by mistake.

You can make use of the isdate function to check for invalid dates.

Posted : November 11, 2013 4:00 am

wsc27

(@sclayton)

Posts: 142

Estimable Member

Topic starter

After recreating the report from scratch, the report was running fine until I had to put the ClinicalDate formula field into the report. Getting the same error as I did to start with???

Posted : November 11, 2013 4:17 am

baj

(@baj)

Posts: 99

Estimable Member

try this

add this condition in record selection

and not(isdate({@ClinicalDate}))

Posted : November 11, 2013 4:20 am

wsc27

(@sclayton)

Posts: 142

Estimable Member

Topic starter

Says "The ) is missing" ????

{DOCUMENT.DOCTYPE} = 5.00 and
{DOCUMENT.SUMMARY} = "Handout Printed" and
{DOCDATA.DATA} like "*PATIENT INSTRUCTIONS*" and
not(isdate({@ClinicalDate})

Posted : November 11, 2013 4:25 am

baj

(@baj)

Posts: 99

Estimable Member

sorry, you have to add a ) at the very end. I had edited the post already when I realized it.

Posted : November 11, 2013 4:27 am

joeg1962

(@joeg1962)

Posts: 843

Noble Member

{DOCUMENT.DOCTYPE} = 5.00 and
{DOCUMENT.SUMMARY} = "Handout Printed" and
{DOCDATA.DATA} like "*PATIENT INSTRUCTIONS*" and
not(isdate({@ClinicalDate}))

Need one more ) at end of final line.

Posted : November 11, 2013 4:43 am

wsc27

(@sclayton)

Posts: 142

Estimable Member

Topic starter

Says "A string is required here" ????

{DOCUMENT.DOCTYPE} = 5.00 and
{DOCUMENT.SUMMARY} = "Handout Printed" and
{DOCDATA.DATA} like "*PATIENT INSTRUCTIONS*" and
not(isdate({@ClinicalDate}))

Posted : November 11, 2013 4:58 am

baj

(@baj)

Posts: 99

Estimable Member

try this

and not(isdate(totext({@convertdate})))

Posted : November 11, 2013 5:05 am

joeg1962

(@joeg1962)

Posts: 843

Noble Member

OK, so don't have it in selection logic.

Create a detail report where you print:

{DOCUMENT.DOCTYPE} {DOCUMENT.SUMMARY} {@ClinicalDate}

export it to Excel, if easier for you.

Then review through the data to find the line in error.

Note: DO NOT FORMAT THE @ClinicalDate field - you want to look at the individual items to see what data is bad.

Posted : November 11, 2013 5:05 am

wsc27

(@sclayton)

Posts: 142

Estimable Member

Topic starter

baj, still getting error" The Number of Days is out of Range"

joeg1962, do you prefer to email? for the @ClinicalDate do you mean to use the DOCUMENT.Clinical Date field instead that's not formatted?

Posted : November 11, 2013 5:14 am

joeg1962

(@joeg1962)

Posts: 843

Noble Member

Feel free to email.

I am suggesting to create a separate report to simply look at the data. I, and I think others, suspect that there is something bad in the date field.

Posted : November 11, 2013 5:15 am

baj

(@baj)

Posts: 99

Estimable Member

I now think that, even the conversion formula may give an error if there are invalid dates. Are you able to run the report with @Clinicaldate in the Details section?

Posted : November 11, 2013 5:27 am

wsc27

(@sclayton)

Posts: 142

Estimable Member

Topic starter

Here is example of the data for DOCUMENT.ClinicalDate field

1,665,308,499,000,000.00

I have no idea what that means which is why I had to do the date conversion formula. How can I find out if there is invalid date data? I skimmed through the pages of the report and I don't see anything abnormal.

baj, I am able to run the report with the date conversion, but it freezes in the middle and shows the formula error so therefore it doesn't finish pulling all of the data.

Posted : November 11, 2013 5:39 am

baj

(@baj)

Posts: 99

Estimable Member

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 6:10 am

Page 2 / 3 Prev Next

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