HealthImaging Warning Codes
HealthImaging attempts to import all your medical imaging data. If data non-conformances or
unrecognized data elements are encountered during imports, HealthImaging will add one of the following
warnings to the warning.ndjson file. A warning associated with an imported
instance will also be searchable via the SearchDICOMInstances action with the
WarningReason element. Instances imported with a warning may have reduced support via
HealthImaging APIs, as described below.
| Warning Reason (Hexadecimal) | Warning Reason (Decimal) | Warning Type (Enum) | Warning Details | Resulting Behavior |
|---|---|---|---|---|
| DICOM Standard Warning Reasons | ||||
| 0xB000 | 45056 | COERCION_OF_DATA_ELEMENTS | The ingestion modified one or more data elements during storage of the instance. See Section 6.6.1.3 |
n/a |
| 0xB006 | 45062 | ELEMENTS_DISCARDED | The ingestion discarded some data elements during storage of the instance. See Section 6.6.1.3 |
n/a |
| 0xB007 | 45063 | SOP_CLASS_DATA_MISMATCH | The StoreDICOM action observed that the Data Set did not match the constraints of the SOP Class during storage of the instance. |
n/a |
| AWS HealthImaging Warning Reasons | ||||
| 0xB100 | 45312 | TRANSCODING_EXCEPTION | This warning occurs when HealthImaging cannot transcode the instance PixelData to HTJ2K (default storage format), or if the PixelData cannot be transcoded for another reason (i.e. failed validations, wrong pixel data attributes, etc). In this case, the pixel data will be stored as a blob. | Pixel data may still be retrievable as a single blob if required, passing wildcard "*" as the transfer-syntax in Accept header will return it in the stored format. |
| 0xB110 | 45328 | FRAMES_EXTRACTION_FAILURE | This warning occurs when there is an issue parsing individual frames from the PixelData based on the given DICOM metadata. | Pixel data was malformed and cannot be retrieved, use GetDICOMInstance to retrieve the entire instance |
| 0xB111 | 45329 | FRAME_NUMBER_MISMATCH | This warning occurs when the "NumberOfFrames" DICOM element does not match the actual number of image "fragments" in the input DICOM file. | Pixel data was malformed and cannot be retrieved, use GetDICOMInstance to retrieve the entire instance |
| 0xB112 | 45330 | INVALID_OFFSET_TABLE | This warning occurs when the offset table in the fragments of the input DICOM file do not match up with the actual frame length and could result in malformed frames depending on the severity. | Pixel data was malformed and cannot be retrieved, use GetDICOMInstance to retrieve the entire instance |
| 0xB120 | 45344 | UNSUPPORTED_TRANSFER_SYNTAX | This warning occurs when HealthImaging encounters an unrecognized or unsupported transfer syntax. When this happens, HealthImaging will store the pixel data as a blob. | Pixel data may still be retrievable as a single blob if required, passing wildcard "*" as the transfer-syntax in Accept header will return it in the stored format. |
| 0xB201 | 45570 | INVALID_UID_FORMAT | This warning occurs when one or more UID elements violate the DICOM Value Represention (e.g. 1.2.3..4) |
n/a |
| 0xB202 | 45571 | INVALID_DICOM_VALUE_LENGTH | This warning occurs when a DICOM element has a length longer than that supported by the DICOM Value Representation, potentially introducing invalid behaviors for search/retrieve actions. | Some fields may not be parseable and therefore cannot be searched on (i.e. StudyDate or StudyTime) |
| 0xBFFF | 47513 | OTHER | This warning occurs when there an uncaught warning that HealthImaging does not capture as a specific warning code. | Pixel data was malformed and cannot be retrieved, use GetDICOMInstance to retrieve the entire instance |
