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

[SOLVED] - Is there a way to stop the new HTML Prescription form from generating the text component that documents LISTRXNEWFULL

CPS, C-EMR, PM

Last Post by Anonymous 1 second ago

7 Posts

4 Users

0 Reactions

70 Views

RSS

Adam Daniel

(@adaniel)

Posts: 524

Prominent Member

Topic starter

Our issue is that new Rx's will not document unless that Prescription form is open and the text component is generated.

Manually inserting the text component into the document template works unless someone clicks the Prescription form thus generating another text component causing duplicate text translation.

Is there a way to turn the automatic generation of that text component off from the prescription form or does anyone else have a better idea on how to handle this?

Under the current circumstance obviously the answer is to have the one prescribing launch the prescription form and then launch the update medications module from within but getting everyone onboard with those extra clicks has been a task.

Posted : January 24, 2019 3:39 am

gibsonmi

(@gibsonmi)

Posts: 827

Prominent Member

You could either modify the RxRefill form or the text component it is inserting. I think either will require maintaining the change with every update. To edit the form, go to jboss server and to the Encounters folder \\[jboss-server]\c$\Program Files\Centricity Practice Solution\jboss\standalone\deployments\[database].ear\CentricityPracticeWS.war\\EncounterForms\rxrefill\controllers\rxrefill-controller.js. Find the line that contains ADD_TEXT_COMP and comment it out with two forward slashes (for me its line 69).

You could just edit the referenced text component as well, for me that is 'Enterprise\Medicalogic\Rx Refill 2016' and remove the text translation.

Posted : January 24, 2019 3:55 am

Adam Daniel

(@adaniel)

Posts: 524

Prominent Member

Topic starter

Thanks, figured there was jboss option didn't think about your 2nd option there, the simplest one haha.

Posted : January 24, 2019 4:06 am

Adam Daniel

(@adaniel)

Posts: 524

Prominent Member

Topic starter

Is there a document template for the Rx Refil button anymore?

EDIT: found it, it is the Encounter Type "RxRefill" with with Document Template "RxRefill".

This seems to be a canned default from Centricity one that cannot be re-selected or found in Document Templates. We now pointed ours to a custom template and remove the translation from the text component that is auto generated adding a custom text component to exist so it will always document.

Posted : January 24, 2019 4:18 am

jessicaw

(@jessicaw)

Posts: 434

Prominent Member

Remove this entire statement??

$scope.InitializeForm = function () {
if ($scope.currentFormId > 0) {
emrApiAccessService.evalMel("{ADD_TEXT_COMP('Enterprise\\Medicalogic', 'Rx Refill 2016', 'AFTER_CURRENT', 1)}", false);
}
}

Posted : January 29, 2019 9:30 am

gibsonmi

(@gibsonmi)

Posts: 827

Prominent Member

I would leave the function definition its probably called somewhere, you can gut it though.

$scope.InitializeForm = function () {

}

Posted : January 29, 2019 12:21 pm

JClarkLRGH

(@jclarklrgh)

Posts: 31

Eminent Member

"Gutting" the function, but leaving it intact is exactly what we did and it's been working fine for the better part of a year. No issues.

Posted : March 11, 2019 7:30 am

Share:

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

Powered by wpForo Powered by wpForo version 2.4.0