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

Workstation ID has patient locked

General Discussion

Last Post by chaddix 8 years ago

5 Posts

5 Users

0 Reactions

64 Views

RSS

jessicaw

(@jessicaw)

Posts: 434

Prominent Member

Topic starter

I have a ticket in with GE but maybe someone here knows the solution.

Recently registration staff has been seeing an alert pop up that states "Workstation ID 6107 currently has this patient locked. Your Workstation ID is: 6103. Julie Fox".

It is occurring when they make changes within a patients registration screen and go to save those changes. They click OK and it allows them to continue with their work.

Julie Fox is one of our receptionists and it is odd that her name is attached to these alerts because the patients it is occurring on are patients that have not been accessed by her.

Any ideas??

Posted : November 18, 2016 10:33 am

mcwilson

(@mcwilson)

Posts: 92

Estimable Member

I always assumed these kinds of things were just annoyances when a rare thing like the person's Centricity crashes and files are not closed correctly.

We usually wait 5-10 minutes and the lock gets released by the system and things are back to normal. In rare cases we have had to get GE involved to go in to the database to correct the issue.

Mike

Posted : November 21, 2016 7:28 am

virtualHITman

(@virtualhitman)

Posts: 319

Reputable Member

When locking issues are reported in error (i.e. it says a user has the patient locked when that user is not in the chart), you can try this to expedite the process:

Go to the computer that is reporting the error message AND the computer workstation that supposedly has the patient locked. Exit CPS and then go to All Programs on your Start menu and find the Centricity Practice Solution program group. Run the "Reset CPS Process" (see figure) on both computers. This will often fix the problem; otherwise you simply have to wait several minutes as Mike suggested before Centricity realizes the user is no longer accessing the patient chart. We have discovered that the way Centricity monitors record locking is not very efficient and is problematic in environments where you have multiple users in and out of the same chart on a regular basis (i.e. pretty much any medical practice).

Posted : November 22, 2016 4:07 am

gpincomb

(@gpincomb)

Posts: 278

Reputable Member

We simply use the following SQL script:

delete ll2
from LOGLOCKS ll2
where ll2.WSID = xxxx;

Where the "xxxx" is the actual Workstation ID reported in the pop up.

Posted : November 22, 2016 7:44 am

chaddix

(@chaddix)

Posts: 177

Estimable Member

If you have not downloaded the Centricity Admin Toolbox, I would start there. In instances where there is a document lock issue, the Toolbox can solve most of them.

For all other lock issues, my process is as follows:

1. SELECT * FROM LOGLOCKS

2. Copy to Excel

3. Search for the patient's PID in the Excel workbook. Once you find it, this is most likely the culprit. Write down the LogLocksId for this row.

4. DELETE FROM LOGLOCKS WHERE LogLocksId = [LogLocksId Identified in Step 3]

Posted : November 22, 2016 8:20 am

Share:

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