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

Using DOCUMENT.SUMMARY in a handout that can be printed outside of an update

Trading Post

Last Post by Anonymous 1 second ago

8 Posts

3 Users

0 Reactions

132 Views

RSS

emaher

(@emaher)

Posts: 71

Estimable Member

Topic starter

Our visit summary handout uses the DOCUMENT.SUMMARY symbol. If the visit summary is printed outside of an update, this causes MEL vomit (the error is something like "Invalid Row").

Is there a way for a handout to determine whether or not it is being printed from within an encounter? I haven't been able to find a way to do it.

-Eric

Posted : January 22, 2014 4:09 am

gibsonmi

(@gibsonmi)

Posts: 827

Prominent Member

Try ok(), like -

{if ok(DOCUMENT.SUMMARY) then DOCUMENT.SUMMARY else "" endif}

It checks for valid arguments, Im not sure if it will work but its my best guess

Posted : January 22, 2014 4:22 am

emaher

(@emaher)

Posts: 71

Estimable Member

Topic starter

A good idea, but it still throws the "Invalid Row" message.

"Ok" only seems to check whether a value is present. It can't handle other error conditions.

-Eric

Posted : January 23, 2014 4:01 am

gibsonmi

(@gibsonmi)

Posts: 827

Prominent Member

Eh, it was worth a try. Have you considered saving the document.summary to an observation term? Then it at least won't throw an error...

Posted : January 23, 2014 4:49 am

emaher

(@emaher)

Posts: 71

Estimable Member

Topic starter

Yeah, but it seems wasteful.

Posted : January 23, 2014 6:29 am

snichols

(@snichols)

Posts: 7

Active Member

No answer but, I am trying almost the identical thing on a handout. NEed to to bypass the error, INVALID ROW, when there is no data (which means there is no encounter).
If you find an answer please let me know. Thanks.

Posted : October 27, 2014 4:03 am

gibsonmi

(@gibsonmi)

Posts: 827

Prominent Member

I think there is an easy way -

getrowcount("Document")

returns 1 if there is an active document and 0 if there is not an active document, try

{if getrowcount("Document") == 1 then DOCUMENT.SUMMARY else “No Document” endif}

Posted : October 27, 2014 5:35 am

snichols

(@snichols)

Posts: 7

Active Member

The getrowcount worked perfectly for me (to find out if an encounter was open). Thanks so much!

Posted : October 28, 2014 3:35 am

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