In-app bug & feature reporting
Report a bug or request a feature from inside the app, with attachments, without leaking PHI.
Problem
You hit a defect mid-session, or you want to request an enhancement, and you want to report it without leaving the application or filing a ticket elsewhere. The catch: dcmage handles DICOM data, and the feedback backend is not covered by a HIPAA Business Associate Agreement. The channel therefore has to make it hard to leak Protected Health Information — in attachments, in the description, or in raw .dcm files — while still being quick to use.
Steps
Open the dialog
-
Trigger feedback from any of four entry points: the ✉ control in the top bar, the command palette (“Report a bug” / “Request a feature”), the ⌘/Ctrl+Shift+F shortcut, or the Report this error button on the crash screen (which seeds the bug tab with a PHI-scrubbed stack).
-
The dialog opens on the matching tab. A magenta banner pinned at the top warns: do not include patient information.
Fill and gate
-
Enter a title and description. Bug reports add steps / expected / actual / severity; feature requests add priority and a use-case field.
-
Acknowledge the “no PHI included” checkbox — the Send feedback button stays disabled until the title, description, and this acknowledgement are all set.
Attachments (PHI-safe)
-
Drop or pick screenshots, text, JSON, or logs. Each file is validated against the media-type allowlist and the 5-file / 25 MB caps; raster images have their embedded metadata stripped before upload.
-
A
.dcmfile is never accepted directly: an automated PHI pre-scan runs, lists any identifying metadata tags and burned-in text it finds, and only then reveals a second, separate confirmation checkbox. A scan that cannot complete offers no override.
Submit
- Send — each attachment is uploaded straight to object storage via a presigned URL, then the report is posted with the resulting keys. On success the dialog closes and a “Feedback sent” notice appears; on failure the dialog stays open and shows the returned error.
Result
Bugs and feature requests reach the maintainers from inside the app, with optional (PHI-scrubbed) diagnostic context and validated attachments. Every layer — the warning, the required acknowledgement, the .dcm pre-scan gate, image-metadata stripping, and context scrubbing — works to keep patient data from leaving the operator’s control on a non-BAA channel.