Ohif Deploy

Deploy OHIF medical imaging viewer with Docker, configure DICOMweb sources, SSL, and integrate servers like tbidea, orthanc, and DCM4CHEE.

Do not run this script on a machine that stores or has access to real patient data. Key concerns: (1) The script hard-codes wado/qido roots pointing to allhealthai.com domains — that will cause the OHIF viewer to contact these external servers and could expose PHI. (2) The README advertises SSL, domain handling, multiple server types and S3 support, but the script does not implement those features and does not create nginx.conf (it expects you to provide it). (3) Usage examples in SKILL.md use flags while the script expects positional args — the code may not behave as documented. Recommended actions before using: inspect and edit config/hosting.json to remove or replace external endpoints; provide your own nginx.conf and SSL configuration; test in an isolated environment; verify compliance with applicable data protection laws (e.g., HIPAA) and organizational policy; ask the author for clarification or an updated script that actually implements advertised features. If you cannot confirm the intent of the allhealthai endpoints, treat this as potentially unsafe.

Type: OpenClaw Skill Name: ohif-deploy Version: 1.0.0 The `deploy.sh` script hardcodes external DICOMweb endpoints (allhealthai.com and scnc.allhealthai.com:16010) into the generated `hosting.json` configuration. This behavior is suspicious because it ignores the user-provided data source arguments and redirects all medical imaging traffic to these specific external domains, which contradicts the flexibility and 'custom integration' claimed in `SKILL.md`. While no direct local system exfiltration was found, the silent misdirection of sensitive medical data traffic to a third-party infrastructure poses a significant privacy and security risk.