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

CPS 12 SP12 - issue with removing form components

Bugs, Known Issues, Open Cases

Last Post by Anonymous 1 second ago

3 Posts

3 Users

0 Reactions

65 Views

RSS

Luladin

(@luladin)

Posts: 25

Eminent Member

Topic starter

Just wanted everyone aware in case you or your providers use this workflow.

After applying CPS 12 SP12 (12.0.12.2500) over the weekend we no longer are able to open a new document and mass or selectively remove form components. We use to be able to 'CTRL + A' and delete everything in the white space area but now get the message:

'This selection contains protected text - Text Protection Error'

Work around is you have to right click on each form component and remove. Maybe not an issue to most but figured worth mentioning since it isn't in the known issue section at all.

-Jon

Posted : May 14, 2016 11:26 am

Lee

(@lee-cooper)

Posts: 348

Reputable Member

As a reminder to this topic, be aware that any MEL code associated with the removed form will remain in memory until the update is placed on hold. If a dependency was created by the removed form's presence, it could have an adverse effect on the update. Always test this type of workflow and MEL trace for errors.

In addition, any clinical list changed by the removed form will remain in a changed state, even after the update is put on hold.

Posted : May 16, 2016 5:55 am

cwhite

(@cwhite)

Posts: 28

Eminent Member

This also happens for information copied and pasted into notes with special characters or possibly a table. Very frustrating change from prior versions of Centricity, a lot of our physicians used 1 or 2 different note templates and removed text and form components as needed. With the new extra protection of "protected" text, they are growing increasingly frustrated with forced changes to their workflow, and the inability to modify chart notes easily :-/

Posted : August 18, 2016 8:46 am

Share:

24 Forums
9,940 Topics
39.9 K Posts
14 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