Facility Readiness

Article, How To, Internal, Microsoft, R&D, Security, Software, Uncategorized

For hospital IT and security teams

  • Facility readiness and security exceptions checklist (what to allow, where to look) – use our intake form if you need to document exceptions.
  • CrowdStrike Falcon exclusions for PathCam – minimal, scoped allow strategy using Device Control (VID/PID) and targeted exclusions.

Associated Links:
Support intake form |
CrowdStrike exclusions guide

Facility Readiness and Security Exceptions (Windows – PathCam)

Audience – hospital IT, biomed, partner engineers
Goal – confirm the host PC and environment are ready for PathCam and document any required policy exceptions before install or go-live. Uses guidance text instead of screenshots.

1) Host and OS readiness

  • Windows edition and build recorded.
    How to find: Press Win+R -> type winver -> Enter. Or go to Settings -> System -> About and copy Windows specifications.

  • Recent Windows updates reviewed (last 30 days KBs).
    How to find: Settings -> Windows Update -> Update history.

  • Admin rights available for install and updates.

  • User who runs PathCam can launch the app after install.

2) Camera and USB hardware

  • Canon camera model and serial recorded.

  • USB cable is data-capable and undamaged, length appropriate.

  • Connection path is direct to PC port or a powered USB hub (5 V or higher recommended).

  • Prefer desktop rear I/O; laptops/docks may provide less power.

3) Device enumeration and Windows policies

  • Windows Devices lists Canon EOS under Settings -> Bluetooth and devices -> Devices.

  • Device Manager shows the camera under Portable Devices.
    Tip: If it appears as a generic MTP device and fails, uninstall the device, unplug, and reconnect to re-enumerate.

  • Windows camera privacy allows desktop apps.
    How to find: Settings -> Privacy and security -> Camera. Turn on “Camera access” and “Let desktop apps access your camera.”

4) Endpoint security and whitelisting

  • Endpoint security vendor/version recorded (e.g., CrowdStrike, Defender, Carbon Black, Trellix, Symantec).

  • If security blocks camera or media writes, follow a minimal, scoped allow strategy.
    See the CrowdStrike guide for allow rules by VID/PID and targeted exclusions.

5) Conflicting software

  • Canon EOS Utility or EOS Webcam Utility is not auto-launching. If conflicts persist and it’s not inconvenient, uninstall.

  • Close video apps during acquisition (Teams, Zoom, browsers using webcam).

6) PathCam application and licensing

  • PathCam version/build recorded (PathCam STUDIO -> Help -> About).

  • License mode confirmed – bound to camera serial or short unbound trial. Record unbound expiration if used.

  • Default camera dial is Program (P). For older PathCam versions, users may adjust the dial in the grossing sink hood if needed, subject to site policy.

7) Storage and network

  • Working directory allows writes for the signed-in user.

  • Network share paths used by PathCam allow writes and are not DLP-blocked.

  • If writes are restricted, provide an approved alternate location.

8) Remote support and maintenance window

  • Remote support approval status recorded (Yes, No, or Requires change approval).

  • Onsite IT contact captured (name, email).

  • Preferred maintenance windows (with time zone) captured.

Exceptions log (for change control)

Track any non-standard policies and how they were approved:

  • Policy/control and rule ID

  • Current setting

  • Requested exception (scope and duration)

  • Approval owner

  • Effective dates

Whats Next?

  • If all items pass, proceed to installation or upgrade.

  • If security blocks device access, use the CrowdStrike article for a least-privilege allow path.

  • If issues persist, open a ticket at /pathcam-support-intake and include the requested details.

 

Facility Readiness Form – Conversation Version