fo-dicom | Fellow Oak DICOM for NET, NET Core, Universal Windows, Android, iOS, Mono and Unity

You can just skip the first 128 bytes of the file and read the next 4 bytes and compare them with the ASCII codes for "DICM", for example:

When building a DICOMDIR with fo-dicom by iterative calling AddFile for each file, then you will get a DICOMDIR with all the required DicomTags. But of course there are a lot of tags that are optional and you can add them yourself. The method AddFile returns an instance of type DicomDirectoryEntry, which gives you a reference to the patient record entry, the study record entry, the series record entry and the instance record entry. There you can add as many additional optional data that you wish. In your case it would look like

It's very easy to do. A WorklistQuery is a Dataset, that contains some DicomTags that are queried. Some of those DicomTags may contain values, then the Worklist Server has to use those values as filters.

So basically a WorklistQuery is a normal DicomDataset, that you can extend and manipulate. The helper-methods DicomCFindRequest.CreateWorklistQuery() is a helper-method that creates common used datasets. But you can then update/change this DicomDataset before sending to the server.

The solution was to fully read the stream when opening the DICOM file.

In case someone else runs into this problem, the issue was the original code was in .NET Framework, but the new code was in .NET Core. In Core, the ImageManager does not use the WindowsImageManager by default, so you need to set it manually.

I solved the problem by installing the Azure CLI and logging in as described here: https://docs.microsoft.com/cli/azure/install-azure-cli-windows?tabs=azure-cli

First of all:

• The Referenced SOP Class/Instance UID are always items of a sequence, and the sequence defines the meaning of the reference.
• The Referenced Image Sequence does not refer to Modality Worklist, it refers to images and other objects only.

The sequence is intended to accommodate other objects which are relevant for the interpretation of a given image. In DICOM: "A Sequence that references other images significantly related to this image."

These may be:

• other images which are related to the current image (e.g. the ID of the other plane in a Bi-Plane acquisition)

• other images on which the calculation of the current image is based

• the second image in case the current image is part of a stereo pair

Any particular meaning of the reference may be constrained or enforced by the particular type of image you are creating. This information can be obtained by following the references in the IOD (Information Object Definition as defined in DICOM Part 3).

For most images, the referenced image sequence is an optional (Type 3) or "may-be empty" (Type 2) attribute which means that if there is no significant relation to other images, it may be omitted.

You can control this behavior on ASSOCIATION level. Validate the Abstract Syntax proposed before sending ASSOCIATE_ACCEPT.