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

Special Characters Text Translation

MEL, SQL, Oracle

Last Post by Anonymous 1 second ago

11 Posts

3 Users

0 Reactions

78 Views

RSS

csimmons

(@csimmons)

Posts: 61

Estimable Member

Topic starter

I have text that in Form View looks correct, however when it is views in Text View, it has some added characters. Any thoughts as to how to correct this? See below for sample - with added characters underlined by me here - not in either view. It seems to dislike special characters. I've searched the forums and haven't found anything yet...

Form View:

Each area was infiltrated with up to 3 cc of 1% lidocaine using a 27G x 1¼” needle.

Text View:

Each area was infiltrated with up to 3 cc of 1% lidocaine using a 27G x 'b'94 needle.

Form View:

After 3 minutes, radiofrequency ablation was initiated at 80°C for 1 minute.

Text View:

After 3 minutes, radiofrequency ablation was initiated at 8'b0C for 1 minute.

Posted : August 27, 2018 5:02 am

joeg1962

(@joeg1962)

Posts: 843

Noble Member

well,

1) superscript 1 (one) is in the ascii chart at b9 (B nine).

2) the degree symbol is in the ascii chart at b0 (B zero).

Typically, computer software does not operate with characters at the upper end of the ascii definition (above 7f). So not sure how the items are being stored.

May be related to your font choices. Whatever font you are using to read the entry, try to make sure that is the same font in your other view.

Posted : August 27, 2018 5:19 am

gibsonmi

(@gibsonmi)

Posts: 827

Prominent Member

Use this source -

https://www.ascii-code.com/

The left column is the code you use for the symbol in the 5th column.

In conjunction with this function (listed twice for your two examples)

numtoascii(186)

numtoascii(188)

Posted : August 27, 2018 6:28 am

csimmons

(@csimmons)

Posts: 61

Estimable Member

Topic starter

As far as I can tell, the font is the same - Arial.

Posted : August 27, 2018 7:54 am

csimmons

(@csimmons)

Posts: 61

Estimable Member

Topic starter

I'm not sure what to do with the ASCII. I tried entering that directly into the Chart Note but it just shows through into the Text View as plain text, so it ends up looking like:

Each area was infiltrated with up to 3 cc of 1% lidocaine using a 27G x 1&#188'94 needle.

Posted : August 27, 2018 8:01 am

csimmons

(@csimmons)

Posts: 61

Estimable Member

Topic starter

Can anyone assist me in determining where/how to set these functions in VFE? I've got other functions (on the right-hand side of VFE) that are working but no matter how I try to add these, I get MEL code showing in the form.

Here's what I see (it seems to be regardless of how I try to format this):

fn numtoascii(186 <-COMPILER ERROR NEARBY: Expect IDENTIFIER NAME. Instead had LONG after LEFT PAREN

I've tried entering just numtoascii(186) and numtoascii(188) (on the same line and on separate lines), I've tried adding them with curly brackets "{}" around them, I've tried with curly brackets and fn in front - like this {fn numtoascii(186)}.

Posted : August 29, 2018 5:17 am

gibsonmi

(@gibsonmi)

Posts: 827

Prominent Member

Sorry I missed your first response. You don't need the fn out front, that is causing the issue. The fn is used to declare or define a function. For example this function will multiply a number by two.

{fn newFunction(variable){

return variable*2

}}

You can call it like this

{newFunction(3)}

and it will return 6.

or more useful you can do -

{DOCUMENT.FIELD = newFunction(3)}

will set the document variable with name 'Field' equal to 6.

So for your case to display it in a chart note use {numtoascii(186)}, or something like

{CFMT(DOCUMENT.FIELD,"","This is your label: ","B",numtoascii(186) + "

")}

Posted : August 29, 2018 5:32 am

csimmons

(@csimmons)

Posts: 61

Estimable Member

Topic starter

I'm pretty sure I tried the first one: {numtoascii(186)} but will try again as well as playing around with the second option. Thank you for the assist.

Posted : August 29, 2018 5:47 am

csimmons

(@csimmons)

Posts: 61

Estimable Member

Topic starter

So, placing {numtoascii(186)} over in the white space where my functions are defined doesn't produce MEL Code, hoever the Text View of the form still shows the ASCII characters. I thought that perhaps I needed numtoascii instead but I ended up with the same results. Moving onto trying this via the Chart Note.

Posted : August 29, 2018 5:54 am

csimmons

(@csimmons)

Posts: 61

Estimable Member

Topic starter

And, in the Translation tab for the edit field in question, I now have this:

{CFMT(DOCUMENT.PROCEDURE_TEXT, "", "", "B",numtoascii(186) + "
")} and it produces the following error:

CFMT(DOCUMENT.PROCEDURE_TEXT_5990153556158049890, "", "", "B",numtoascii(186) + "
")) ENDIF <-FUNCTION DEFINITION IS NOT EXECUTABLE

Posted : August 29, 2018 5:59 am

csimmons

(@csimmons)

Posts: 61

Estimable Member

Topic starter

I still can't figure out where to place the {numtoascii(186)} but have (hopefully) uploaded my .dlg. The RF Cervical is one that shows the incorrect text. This is my first time trying to attach a file in the forum so I don't know yet if it will work or not... 53

Posted : September 5, 2018 10:36 am

24 Forums
9,940 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