Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HL7 / IAN Notification Rules : Enable additional Trigger Types #4684

Open
vrindanayak opened this issue Mar 14, 2025 · 0 comments
Open

HL7 / IAN Notification Rules : Enable additional Trigger Types #4684

vrindanayak opened this issue Mar 14, 2025 · 0 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@vrindanayak
Copy link
Member

vrindanayak commented Mar 14, 2025

Related #4682, #4683

Rationale : In some customer setups, additional trigger types are required to send out notifications to external clients, including (but not limited to) the following :

  • First IMAGE of study received
  • Study AVAILABLE in archive
  • Study UNAVAILABLE in archive, caused by deletion / rejection
  • FIRST_SOP : Send when the system receives the first image of the study, before any archiving activity begins.
  • ARCHIVE : Send when the system initially archives a study
  • LOGICAL_DELETE : Send when user logically deletes a study via the system UI Interface.
  • PHYSICAL_DELETE : Send when a user physically deletes a study via the system UI Interface, or if the study is deleted via automated lifecycle activities.
  • RESTORE : Send when a user restores a study via the system UI Interface that had been logically deleted.

Note : More clarification required on trigger types

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants