Leadtools.Dicom Namespace > DicomNet Class : SendCGetResponse Method |
As an example, suppose an SCU requests an SCP to search all CT class instances for specific data. If the SCP has three CT class instances present, it must search all three instances for the required data. During the search, SendCGetResponse may be called multiple times. The table below gives examples of possible parameter values for the calls made to SendCGetResponse during the search:
Point within Search | status | remaining | completed | failed | warning |
---|---|---|---|---|---|
Finished 1st Instance | DicomCommandStatusType.Pending | 2 | 1 | 0 | 0 |
Finished 2nd Instance | DicomCommandStatusType.Pending | 1 | 2 | 1 | 1 |
Finished the Search | DicomCommandStatusType.Success | 0 | 3 | 1 | 1 |
After the first instance is searched, there are 2 remaining instances to search (remaining), there is 1 instance that has been completed (completed), no instances have failed the search (failed), and there are no warnings (warning).
After the second instance is searched, there is 1 remaining instance to search (remaining), there are 2 instances that have been completed (completed), 1 instance has failed the search (failed), and there is one warning (warning).
After the last instance has been searched, there are 0 remaining instances to search (remaining), there are 3 instances that have been completed (completed), 1 instance has failed the search (failed), and there is one warning (warning).
The instance that failed may have failed because one Data Element you were searching for was not in the instance. For example, you may have included "Patient Birth Date" in the elements to search for and one instance did not include "Patient Birth Date".
Information about the warning may be found in the Data Set that is returned.
Target Platforms: Windows 7, Windows Vista SP1 or later, Windows XP SP3, Windows Server 2008 (Server Core not supported), Windows Server 2008 R2 (Server Core supported with SP1 or later), Windows Server 2003 SP2