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

C-STORE SCU: Optionally nullify Accession Number in retrieved/exported Composite Objects dependent on Issuer of Accession Number #2958

Open
gunterze opened this issue Jan 11, 2021 · 0 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@gunterze
Copy link
Member

gunterze commented Jan 11, 2021

Meets the requirement:

  • J.2.7: Expected Actions for Retrieval Request

    If there is a preconfigured default Accession Number Assigning Authority for the C-MOVE Destination Application Entity then the Image Manager shall only specify an Accession Number value from this Assigning Authority in the SOP Instances sent to the C-MOVE Destination Application Entity. If there is no Accession Number value defined for this preconfigured default Assigning Authority then the Accession Number value shall be left blank.

for Image Managers supporting the Multiple Identity Resolution option of the Scheduled Workflow Integration Profile.

@gunterze gunterze added the enhancement New feature or request label Jan 11, 2021
@gunterze gunterze added this to the 5.23.1 milestone Jan 11, 2021
@gunterze gunterze self-assigned this Jan 11, 2021
@gunterze gunterze changed the title C-STORE SCU: Optionally nullify Accession Number in retrieved/exported Composite Objects dependent on Issuer of Accession Numbe C-STORE SCU: Optionally nullify Accession Number in retrieved/exported Composite Objects dependent on Issuer of Accession Number Jan 11, 2021
@gunterze gunterze modified the milestones: 5.23.1, 5.24.0 Feb 10, 2021
@gunterze gunterze modified the milestones: 5.23.2, 5.24.0 Mar 24, 2021
@gunterze gunterze modified the milestones: 5.23.3, 5.24.0 May 18, 2021
@gunterze gunterze modified the milestones: 5.24.0, 5.24.1 Aug 6, 2021
@gunterze gunterze modified the milestones: 5.24.1, 5.24.2 Sep 15, 2021
@gunterze gunterze modified the milestones: 5.24.2, 5.25.0 Oct 1, 2021
@gunterze gunterze modified the milestones: 5.25.0, 5.26.0 Dec 15, 2021
@gunterze gunterze modified the milestones: 5.25.1, 5.26.0 Dec 28, 2021
@gunterze gunterze modified the milestones: 5.25.2, 5.26.0 Feb 14, 2022
@gunterze gunterze modified the milestones: 5.26.0, 5.26.1 Mar 23, 2022
@gunterze gunterze modified the milestones: 5.26.1, 5.26.2 Jun 9, 2022
@gunterze gunterze modified the milestones: 5.27.0, 5.27.1 Jul 27, 2022
@gunterze gunterze modified the milestones: 5.28.0, 5.28.1 Sep 13, 2022
@gunterze gunterze modified the milestones: 5.29.0, 5.29.1 Oct 19, 2022
@gunterze gunterze modified the milestones: 5.29.1, 5.29.2 Dec 22, 2022
@gunterze gunterze modified the milestones: 5.29.2, 5.29.3 Feb 27, 2023
@gunterze gunterze modified the milestones: 5.30.0, 5.31.0 Jun 6, 2023
@gunterze gunterze modified the milestones: 5.31.0, 5.31.1 Aug 23, 2023
@gunterze gunterze modified the milestones: 5.31.1, 5.31.2 Nov 3, 2023
@gunterze gunterze modified the milestones: 5.31.2, 5.31.3 Dec 21, 2023
@gunterze gunterze modified the milestones: 5.32.0, 5.32.1 Apr 19, 2024
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

1 participant