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

Windows 10 / Web Cam / Failed to Acquire Image from Device

CPS, C-EMR, PM

Last Post by Anonymous 1 second ago

3 Posts

3 Users

0 Reactions

139 Views

RSS

[email protected]

(@mmageesignaturehealth-net)

Posts: 6

Active Member

Topic starter

For some time we have been experiencing camera issues with our Windows 10 machines. We've tried several different web cams but cant get seem to get anything to work. We keep getting the old "failed to acquire image from device" message.

Recently we found a company named Terminal Works" that has a piece of software called Unitwain that will capture images from any web camera directly into CPS. There is no need to take the picture locally first and then attach it. It works like a champ. They have a 15 day trial for testing purposes.

https://www.terminalworks.com/unitwain

Posted : July 12, 2018 9:55 am

hinks2000

(@hinks2000)

Posts: 50

Trusted Member

We found that CPS (12.3.1 on Windows 10 in our testing) is writing a file to the root of c: drive called capture.avi when capturing a patient profile picture from webcam. If we create a blank file with that name using a computer startup script and give users full control of that file, it seems we have no issues with both UAC or file rights. Not sure if you tried this and it's still flaky? Might save a nickel if you have to purchase additional software to work around. This is in a fat client scenario.

Note: If you create the capture.avi with a GPO, you'll run into trouble with some integrity levels (above my head). Here are some links to better explain this:
https://msdn.microsoft.com/en-us/library/bb625963.aspx
https://docs.microsoft.com/en-us/windows/desktop/secauthz/mandatory-integrity-control
Basically GPO creates files in the root of C with High integrity and CPS runs with Medium Integrity causing a rights issue. We got past this with a startup script to create the file.

We have not attempted image capture in a RDP connection yet, but TSWebCam by Terminal Works might be an avenue to try if necessary.

Jake

Posted : July 18, 2018 6:39 am

kegeorge

(@kegeorge)

Posts: 1

New Member

Adding onto Jeff's comment I was able to get this working by manually creating C:\capture.avi and running the command "icacls C:\capture.avi /setintegritylevel M". This sets the integrity level to medium where CPS runs. After that non-administrator accounts in Windows 10 were able to capture photos using the webcam.

Kenny

Posted : August 10, 2018 6:46 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