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

Issue with Quick text pulling in a Text Component

General Discussion

Last Post by willadams805 9 years ago

8 Posts

4 Users

0 Reactions

59 Views

RSS

Sirna

(@sirna)

Posts: 384

Honorable Member

Topic starter

Currently I have a provider that has multiple text components. I have gone ahead and created a quick text for each one with the {INSERT_TEXT_COMP()} option and making sure the the path is correct as well as the naming on the text component. I am able to get this to work within the open body of the chart note. However my problem is that the quick texts do not work when trying to drop into any of the update forms: HPI, CPOE, Patient instructions etc. I keep receiving: [MLI_TEXT:1634807686306770] in place of the text component. Does anyone have any ideas why these would work within the body of the update, but not dropping onto the forms?? Any help would be greatly appreciated!

Posted : October 26, 2012 3:07 am

Sam

(@sam)

Posts: 371

Honorable Member

Can you post your programming language up so we can see it?

Posted : November 5, 2012 12:39 am

Sirna

(@sirna)

Posts: 384

Honorable Member

Topic starter

So this is the set up for the quick text:

{INSERT_TEXT_COMP("Enterprise\Franklin","Abuse")}

I am pulling from the enterprise and the from the specific folder and then the named Text component. It is working within the plain body of the update, just not working within any of the update forms..... I hope this is what you were asking for!

Posted : November 5, 2012 12:44 am

Sirna

(@sirna)

Posts: 384

Honorable Member

Topic starter

And I only get the above MLI Error code when trying to drop these into a form.

Posted : November 5, 2012 12:45 am

jjordet

(@jjordet)

Posts: 545

Honorable Member

I don't think you can insert a text component into a form field. You can insert text, but not from a text component, so you're limited to 512 characters.

Posted : November 5, 2012 1:34 am

Sirna

(@sirna)

Posts: 384

Honorable Member

Topic starter

So we have been able to drop in the text component directly into the form, but pulling it in from a quick text is not working. I am just wondering what the disconnect is....

Posted : November 5, 2012 1:40 am

Sam

(@sam)

Posts: 371

Honorable Member

jjordet is correct. You are not allowed to use QuickTexts that pull Text Components into Forms. This is for the same reason that you are not able to use QuickTexts in edit fields in forms--only in multi-line edit fields. This prevents the user from thinking a full body of text has been entered without being able to visually verify it. It's a built-in Centricity safeguard.

Posted : November 5, 2012 4:31 am

willadams805

(@willadams805)

Posts: 2

New Member

I am having the exact same issue. My logic is as follows:

{INSERT_TEXT_COMP("Enterprise\Mulcahy","EGD")}

The output is:

[MLI_TEXT:1771838806658110]

It does not work in any form. I have to use switch from form entry to text entry to make it pull data. This will not work with our physicians. Is this the way it was designed? If so, it's a terrible design and GE should really think about why they even have this variable in place.

I work with many practices and ALL physicians use their forms to enter data. The point of forms is to organize the data in a fashion that make it easy for doctors to enter PHI and keep it consistent across all patients. Don't even get me started on the meaningful use aspect of entering data through the text fields. It does not work.

Has anyone found a way to make this work in forms?

Posted : February 23, 2016 8:25 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