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

POCT Form

Trading Post

Last Post by Anonymous 1 second ago

8 Posts

4 Users

0 Reactions

74 Views

RSS

ljburnham

(@ljburnham)

Posts: 331

Reputable Member

Topic starter

Since I am so new at this I am looking to fellow chuggers for help. We have POCT form for in office testing, we are now being told that we need to have the reference ranges show in the note beside the result. I am pretty sure I need to do an "if then" statement, but not 100%. Any help would be apprecietd. This is a screen shot of the form and some mel language from my error. Confused

POCT

Posted : October 17, 2013 11:21 pm

gibsonmi

(@gibsonmi)

Posts: 827

Prominent Member

in each field you probably have something that looks like this in the text translation

{CFMT(OBSNOW("Color"),"","Color: ","B","

")}

The last two parenthesis are the post text (higlighted red) you can use those to put text after the field, and it will show up only if the field, in this case OBSNOW("Color"), is not blank.

{CFMT(OBSNOW("Color"),"","Color: ","B","\tReference Range: Yellow

")}

That will do the same thing but add a tab space, the text "Reference Range: Yellow" before starting a new line.

Posted : October 17, 2013 11:57 pm

ljburnham

(@ljburnham)

Posts: 331

Reputable Member

Topic starter

gibsonmi said:

in each field you probably have something that looks like this in the text translation

{CFMT(OBSNOW("Color"),"","Color: ","B","

")}

The last two parenthesis are the post text (higlighted red) you can use those to put text after the field, and it will show up only if the field, in this case OBSNOW("Color"), is not blank.

{CFMT(OBSNOW("Color"),"","Color: ","B","\tReference Range: Yellow

")}

That will do the same thing but add a tab space, the text "Reference Range: Yellow" before starting a new line.

Thanks, it was the \t that I was missing. Your help is much appreciated.

Laurie

Posted : October 18, 2013 12:36 am

ljburnham

(@ljburnham)

Posts: 331

Reputable Member

Topic starter

Adding Reference Range to each field made the form too busy. So I made a heading of Reference range, and put the range in the chart translation., but everything is on the right side of the page. Is there a way to make it look like it is on the form:

POCT 2ND IMAGE

Posted : October 18, 2013 1:50 am

gibsonmi

(@gibsonmi)

Posts: 827

Prominent Member

Yes but it gets really complex.

First the form needs to be in a fixed-width font, like courier new

Then you need a spacing function, like the one I included, then text translations needs to be like this -

{CFMT(OBSNOW("Color"),"","Color: ","B",AddSpace("Color: " + OBSNOW("Color"),50) + "Yellow

")}

So, how it works. The var field includes all of the text from the observation and the label, it starts the reference range "column" at 50 characters over from the left. It adds spaces to whatever var is to get to 50 so you need to make sure you include the label and observtaion correctly where it says var. The 50 can be adjusted to whatever you think is appropriate.

{fn AddSpace(var,total){

local howmuch = total - size(var)

if howmuch < 0 then return "" endif

local rslt = ""

for i = 1,i<=howmuch, i = i + 1 do

rslt =rslt + " "

endfor

return rslt

}}

I hope that all makes sense

Posted : October 18, 2013 2:01 am

ljburnham

(@ljburnham)

Posts: 331

Reputable Member

Topic starter

gibsonmi said:

Yes but it gets really complex.

First the form needs to be in a fixed-width font, like courier new

Then you need a spacing function, like the one I included, then text translations needs to be like this -

{CFMT(OBSNOW("Color"),"","Color: ","B",AddSpace("Color: " + OBSNOW("Color"),50) + "Yellow

")}

So, how it works. The var field includes all of the text from the observation and the label, it starts the reference range "column" at 50 characters over from the left. It adds spaces to whatever var is to get to 50 so you need to make sure you include the label and observtaion correctly where it says var. The 50 can be adjusted to whatever you think is appropriate.

{fn AddSpace(var,total){

local howmuch = total - size(var)

if howmuch < 0 then return "" endif

local rslt = ""

for i = 1,i<=howmuch, i = i + 1 do

rslt =rslt + " "

endfor

return rslt

}}

I hope that all makes sense

It does, but it is over my head. Time to get out my MEL book.

Thanks

Laurie