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

Visibility field using BP criteria

MEL, SQL, Oracle

Last Post by Anonymous 1 second ago

3 Posts

3 Users

0 Reactions

94 Views

RSS

dubsterne

(@dubsterne)

Posts: 55

Trusted Member

Topic starter

I'm working on using BP readings to open visibility fields and I've got this working well, with the exception of one small issue. I have the "normal" to open the field using

{OBSANY("BP SYSTOLIC") =>1 AND OBSANY("BP SYSTOLIC")=<120 OR OBSANY("BP DIASTOLIC") =<80 }

And the "Elevated" using

{OBSNOW("BP SYSTOLIC") => 121 or OBSNOW("BP DIASTOLIC")=> 81}

The problem comes up, if the BP result is something that crosses both - such as 122/78 - then both visibility fields open. Any suggestions on how to resolve this issue?

Posted : April 7, 2015 4:00 am

Lee

(@lee-cooper)

Posts: 348

Reputable Member

You want to break it up into its parts. One 'visibility set' for systolic and one 'visibility set' for diastolic. Using that approach will permit better control. If you want to use just one 'visibility set', you would need to group the values and have more visibility layers.

(sysbp >= value and sysbp <= value) and (diabp >= value and diabp <= value)

Posted : April 7, 2015 4:21 am

Scott Forest

(@sforest)

Posts: 527

Honorable Member

Agreed with Lee. Also, don't be afraid to make multiple visibility regions with similar code.

one for sys AND dia high
one for sys high AND dia normal
one for dia high AND sys normal
one for sys AND dia normal
etc etc etc

Posted : April 7, 2015 5:34 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