Elvasoft PACS — Public Issue & Support Hub

This repository is a public discussion and tracking space for all current and future issues related to Elvasoft PACS.
The source code remains private. Use this repo to report problems, share sanitized logs, document workarounds, and coordinate L1/L2 triage with the internal team.

---

Who this repo is for

• Elvasoft support team handling user-facing tickets
• Internal engineering/ops collaborating on triage and fixes

---

How we use this repo

Use Issues when it’s actionable

• Bugs, incidents, outages, regressions
• Tasks with a clear owner and “Done” state
• Items that belong on a project/kanban board

Tip: Include steps to reproduce, expected vs actual, and logs (sanitized).

Use Discussions for conversation

• Q&A, clarifications, hypotheses
• Gathering context from L1/L2 before a formal issue

You can convert a Discussion into an Issue once a clear action emerges.

---

Before you post (redaction checklist)

• Anonymize any patient/user data (names, MRNs, phone/email, DOB)
• Trim logs to relevant excerpts and time windows

⚠️ Do not attach proprietary source code or raw database dumps.

---

How to file a good Issue

Title: concise summary (e.g., DICOM C-STORE intermittently times out on large studies)
Body (suggested outline):

1. Impact/Severity: S0 (critical) · S1 (high) · S2 (medium) · S3 (low)
2. What happened: clear description
3. Expected vs actual
4. Steps to reproduce: numbered, exact commands/screens
5. Artifacts: sanitized logs, screenshots, timestamps, request IDs
6. Scope: where seen (module/workflow), frequency, first-seen date
7. Workarounds: if any
8. Notes: hypotheses, related tickets

Labels (suggested):

• severity/S0 severity/S1 severity/S2 severity/S3
• area/ris area/pacs area/dicom area/storage area/viewer …
• type/bug type/incident type/question type/workaround
• status/triage status/investigating status/waiting-info status/resolved

---

L1/L2 workflow (suggested)

1. Discussion (optional): start here for clarifications or to gather context.
2. Issue: create when it’s actionable; add severity + area labels.
3. Assign & track: tag maintainers and update status labels.
4. Close with resolution: add “Root cause,” “Fix,” and “Prevention” notes.

---

Triage & response

Maintainers: @JeremyMic @Darfito @iannn07 @fangelineap @thossb

---

Security notes

If you suspect a security vulnerability, please do not open a public Issue or Discussion.
Instead, contact the maintainers via internal channels (chat/email) for private handling.

---

What’s out of scope

• Requests for access to the private codebase
• Unrelated feature requests (unless they arise from an issue)
• Sensitive data, proprietary configurations, or vendor contracts

---

FAQ

Why is this repo public if the audience is internal/L1/L2?
To allow easy linking, screenshots, and broad visibility without exposing code. Content must be sanitized.

Do we need environment matrices right now?
Not required. Add as needed per issue.