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

How to remove an unsigned order entered during same encounter

MEL, SQL, Oracle

Last Post by Anonymous 1 second ago

4 Posts

4 Users

0 Reactions

61 Views

RSS

wle

(@wle)

Posts: 2

Active Member

Topic starter

Hi all,

I have a VFE form that enters an order based on certain criteria when the user clicks a button. When the button is clicked again, it reevaluates all of the criteria and does not add another order if it's already entered. However, the order would still be there even if the criteria have changed. Is it possible to remove an unsigned order? If not, what could I do to work around this?

Posted : January 10, 2017 11:28 am

jfitzmd

(@jfitzmd)

Posts: 419

Reputable Member

There is no MEL command to remove an order. Go into the Order window and manually delete the unsigned order.

Posted : January 10, 2017 12:10 pm

Scott Forest

(@sforest)

Posts: 527

Honorable Member

unfortunately John is correct. No other way around it.

Posted : January 11, 2017 1:44 am

Lee

(@lee-cooper)

Posts: 348

Reputable Member

Within your logic, isolate the section that adds the order. Reverse the logic so that the code checks for the presence of the order and evaluates if the criteria is applicable. From there, you can fashion a pop-up reminding the user that the order was placed, the criteria has changed, and now should be removed.

This is an unfortunate side-effect of 'automating' data entry. Orders, medications, problems, even obsterm values must be coded as if they are a 'two way street', otherwise erroneous data will be captured and become a permanent part of the record. O_o

Posted : January 11, 2017 9:12 am

Share:

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