cornerstonejs / dicomparser Goto Github PK

Could it be possible to use this library to anonymize certain tags of a dicom file?

I've tried to use the explicitDataSetToJS function, in order to locate and de-identificate the patient name, but once I have the new json object I don't know how to convert it into a dicom file again.

Thank you.

I feel like as long as the lookahead in readDicomElementImplicit.js remains, it feels like there's a snake in the grass in the code. While it works for the majority of time (I've never encountered it failing), it gives me this niggling feeling that at any time my code could fail, potentially silently which would be even scarier.

I'd like to implement a data dictionary, but I don't want to force it on everyone. Chris, what do you think about me putting it in a separate file that the user can choose to include if desired? I can add another grunt step so it will build in to the distribution seamlessly. I just wanted to solicit your thoughts before going forward with it.

I'm triying to anonymize dcm (dicom) files before uploading it to the server.

I want to do it on the client side using javascript. But I can't find more that dicom viewers.

I searched about the tags of dicom and I have found a lot of tools for remove metadata tags using python, java and ruby, but I don't know how to portrait it to javascript.

I have even decided what tags I would remove, but I'm not sure about how to do it.

Any ideas about?

Thanks for your time

I have several DICOM images that use encapsulated JPEG, but the pixel-element length is the actual length and not "4294967295". The following change to "dicomParser.readDicomElementExplicit" allows these to be read correctly:

        //if(element.length === 4294967295)
        //{
            if(element.tag === 'x7fe00010') {
                dicomParser.findEndOfEncapsulatedElement(byteStream, element, warnings);
                return element;
            }   else if(element.vr === 'UN') {
                dicomParser.findAndSetUNElementLength(byteStream, element);
                return element;
            } else if(element.length === 4294967295) {
                dicomParser.findItemDelimitationItemAndSetElementLength(byteStream, element);
                return element;
            }
        //}

Is this the best way to do this, and can we get this (or an equivalent change) accepted into the library?

Now dicmParser returns undefined, which leads to the result of no image showed in cornerstone.

I'm facing an issue file publishing my dotnet core Angular app
Error MSB3073 :

because of the following issue

which is at

this is the readTag method in the dicom-parser component which I am using to render dicom-images using cornerstone component.
this is my package.json

and webpack

Can any one put thoughts into it as it is from the dicom-parser
not be able to minified my UglifyJs which is causing the Issue.

This does not look quite right:

https://github.com/chafey/dicomParser/blob/d5c9300e6f35b595d958fdf13d0a521705cbb750/src/misc/header.js#L12

How can I get contour data in rtss dicomFile?
I'm using http to get a rtss file from server client and parse it by dicomParser.js, then I should get the contour data by tag '30060050', bind with ct image and show rtss image over ct image in browser;
however the result is string , which split by '', the '' is an escape character,is ignored,so I can't change it
into array and can not get the z position.

Thanks sincerely!

dicomParser.readFixedString = function (byteArray, position, length) {
if (length < 0) {
throw 'dicomParser.readFixedString - length cannot be less than 0';
}

        if (position + length > byteArray.length) {
            throw 'dicomParser.readFixedString: attempt to read past end of buffer';
        }

        var result = "";
        var byte;
        for (var i = 0; i < length; i++) {
            byte = byteArray[position + i];
            if (byte === 0) {
                position += length;
                return result;
            }
            result += String.fromCharCode(byte);
        }

        return result;
    };

ROIContourSequence :
Item #0 xfffee000
ContourSequence :
Item #0 xfffee000
ContourData : "-225.05-124.07-122.44-222.9-124.73-122.44-220.75-124.98-122.44-218.6-125.06-122.44-216.46-125.12-122.44-214.31-125.17-122.44-212.16-125.17-122.44-210.01-125.12-122.44-207.86-125.12-122.44-205.71-125.12-122.44-203.56-125.06-122.44-201.42-125.12-122.44-199.27-125.12-122.44-197.12-125.12-122.44-194.97-125.17-122.44-192.82-125.17-122.44-190.67-125.07-122.44-188.53-124.87-122.44-186.38-124.18-122.44-185.87-123.85-122.44-184.23-121.91-122.44-184.13-121.7-122.44-183.77-119.56-122.44-183.79-117.41-122.44-184.03-115.26-122.44-184.23-114.58-122.44-184.77-113.11-122.44-186.38-111.1-122.44-186.57-110.96-122.44-188.53-110.04-122.44-190.67-109.59-122.44-192.82-109.4-122.44-194.97-109.34-122.44-197.12-109.33-122.44-199.27-109.33-122.44-201.42-109.33-122.44-203.56-109.28-122.44-205.71-109.24-122.44-207.86-109.18-122.44-210.01-109.14-122.44-212.16-109.09-122.44-214.31-109.09-122.44-216.46-109.08-122.44-218.6-109.09-122.44-220.75-109.1-122.44-222.9-109.27-122.44-225.05-109.77-122.44-227.2-110.86-122.44-227.32-110.96-122.44-228.84-113.11-122.44-229.35-114.9-122.44-229.43-115.26-122.44-229.49-117.41-122.44-229.35-118.3-122.44-229.12-119.56-122.44-228.05-121.7-122.44-227.2-122.66-122.44-225.47-123.85-122.44"
NumberOfContourPoints : "464"
ContourGeometricType : "CLOSED_PLANAR"
ContourImageSequence :
Item #0 xfffee000
ReferencedSOPInstanceUID : "2.16.840.1.113662.2.12.0.3057.1241703565.529"
ReferencedSOPClassUID : "1.2.840.10008.5.1.4.1.1.2" [ CT Image Storage ]

Right now we have:

            catch(e) {
                var ex = {
                    exception: e,
                    dataSet: dataSet
                };
                throw ex;
            }

which leave this in the console:

dicomParser.js:157 Uncaught [object Object]

see: http://eslint.org/docs/rules/no-throw-literal

Is there any way to use dicomParser in node.js? The documentation doesn't mention it. On a related note, it would be great to publish the package on npm, which I'd be happy to help if needed.

(cc @juanprietob)

I ran into an issue where I have a DICOM file with an empty Sequence and the dicomParser is returning and incomplete data set.

In the case of an empty sequence the findItemDelimitationItemAndSetElementLength function will never find the ItemDelimitationItem and reads until the end of the stream.

I wonder if we can modify the code to stop reading if it finds a SequenceDelimitationItem and move on to other elements. Let me know if you think that makes sense or if I have some misunderstanding about how DICOM works in this case.

Thanks so much,

Henry Q. Dineen

This may be intended behavior, but
var studyInstanceUid = dataSet.string('x0020000D'); will result in undefined whereas:
var studyInstanceUid = dataSet.string('x0020000d'); will store the tag value as expected.

And perhaps throw an exception if invalid (perhaps by flag). Some examples of bad dates that this function should guard against:

dicomParser.parseDA('20150001'); // 00 is invalid month
dicomParser.parseDA('20150100'); // 00 is invalid day
dicomParser.parseDA('201500AA'); // AA is invalid day, returns NaN

Hi Chris,

In #6 you mention you're working with jap1968 on the design for big endian support. I'm interested in that feature and willing to implement it or help implement it. What can I do to help get that in the code base?

Thanks,
Bryan

I found a strange behavior in the case of a single fragment and a new Uint8Array is crated as a view of the dicom object byteStream: the new array is misaligned from the source buffer.
In my case the new array is two bytes ahead: fragments[0].dataOffset is 2056, the new array starts at byte 2054 of the byteStream. Length is correct.
I found this behavior using Safari on Mac OS X, Chrome and Firefox on Ubuntu Linux x64, Chrome on Windows 7 x64. Could be a dword alignment? but 2056 is at dword boundaries!
The work around I applied is to comment the if( fragments.lenght === 1) condition.

https://github.com/chafey/dicomParser/blob/34c02a7cec6b71a68ae21856029a8f5d957e900e/src/readSequenceElementExplicit.js

So I have been doing tests for parsing 1000+ files and I keep running into a memory leak/ inefficient garbage collection happening with these functions. It is making out my heap and causing the parsing to crawl waiting for garbage collection to finish. I was wondering if anyone else ran into this problem. Also I think I may be able to fix the underlying issue but I might need to talk it through with @chafey

I have had a look at some functions in your code. In particular, since you have some comments (something like: "I am sure there is a better way than this but this should be safe") in your functions dicomParser.readFloat() and dicomParser.readDouble(), I was thinking that it was possible to get some performance gain in these functions.

Before submitting any proposal of changes, I have done some tests using the jsperf website. My intention was to suggest using the subarray method available on the typed arrays instead of copying every single byte. The goal of doing previously these tests was not to make the same mistake as I did when I decided to use the DataView class on my code (more information here)

Here you can have a look at the results: http://jsperf.com/readfloat

In short: right now, copying bytes seems to be the best solution.

We are using this in our node project but version 1.0.1 on npm doesn't have the fix from PR #15.

Can you re-publish to npm or publish a new version?

Thanks in advance.

Sometimes, the UL fields contains 2 numbers (or more!) to be parsed.

(0020,9157) UL 1\60                                     #   8, 2 DimensionIndexValues

dicomParser's uint32 only returns the first one.

Test datasets available at: http://www.insight-journal.org/midas/collection/view/194

Hi,
how can i retrieve the pixel data in the x7fe00010 tag with your parser?

I compiled the last version with webpack and there is many warnings (no-throw-literal, vars-on-top, func-style, init-declarations, no-param-reassign, ...).

Is it normal ? Are we dropping ESLint checking ?

Today I swapped the metaHeaderDataSet and instanceDataSet parameters in mergeDataSets() in an attempt to put the P10 header before the rest of the instance. This did work, but it caused one of the big endian tests to fail. On further investigation, it appears that instance items were in the metaHeaderDataSet with incorrect values (thus swapping them caused the test to fail). I don't know if the issue is with the test or the big endian parser itself

The dicomParser doesn't seem to exported

PatientName: "ÎâÎÀÉú"

Hello
I have used you library for a project and now I want to add P10 parsing and modifying.
I have found some instruction you gave to another user ( #12 ) but I have not managed to do it.
Do you have any further instruction or this is the only steps?
Thanks in advance
Dimtiris

Raises error "Unhandled Promise Rejection: TypeError: undefined is not an object (evaluating 'pixelDataElement.encapsulatedPixelData')" If DICOM file is of 1.2.840.10008.5.1.4.1.1.104.1 SOP class (encapsulated PDF) because such files have encapsulated data stream in tag x00420011 while dicomParser checks for data only in tags x7fe00010 and x7fe00008 (getPixelData.js, function getPixelData).

I use create-react-app and run build, then the error oppeared, i don't know how to solve it, is anyone have saw the problem?

Hello. If I try to view images from Siemens Avanto and Skyra cornerstone give error. dicomParser:parseDicomDataSetExplicit: buffer overrun

Would it make sense to add a "defaultTransferSyntax" as an option?

The use case it that some custom made DICOM files do not contain this required field so DicomParser just returns an error.

Having an option would let the user "help" dicomParser to do the work:
https://github.com/chafey/dicomParser/blob/master/src/parseDicom.js#L26

if(metaHeaderDataSet.elements.x00020010 === undefined && !this.option && !this.options.defaultTransferSyntax)

Please let me know if that makes sense and I'll submit a pull request.

Does it have any other implications that I am missing?

I was wondering in particular how to make use of the following Key Features:

• Each element exposes the offset and length of its data in the underlying byte stream
• Supports reading incomplete/partial byte streams
  • By specifying a tag to stop reading at

This code will get me just the values:

var dicom = dicomParser.parseDicom(byteArray);
var patientName = dicom.string('x00100010');
var patientId = dicom.string('x00100020');

But how do I get the positions of those elements in the byte stream?

I found this method dicomParser.readDicomElementImplicit = function(byteStream, untilTag) in your source but the comments say that it's an "Internal helper functions for for parsing DICOM elements" and I can't really figure out how to construct the required dicomParser.ByteStream = function(byteArrayParser, byteArray, position) object because there is no helper function to determine the correct object to instantiate for the byteArrayParser argument.

Please help? :)

DEV DEPENDENCIES

• grunt-contrib-qunit
  Requested: ^0.4.0 | Latest: 0.7.0
  OUTDATED INSECURE
  semver Regular Expression Denial of Service
  Found in sub-dependency: grunt-contrib-qunit (0.4.0) → grunt-lib-phantomjs (0.5.0) → semver (1.0.14)
• grunt-contrib-watch
  Requested: ^0.6.1 | Latest: 0.6.1
  INSECURE
  qs Denial-of-Service Extended Event Loop Blocking
  Found in sub-dependency: grunt-contrib-watch (0.6.1) → tiny-lr-fork (0.0.5) → qs (0.5.6)
  qs Denial-of-Service Memory Exhaustion
  Found in sub-dependency: grunt-contrib-watch (0.6.1) → tiny-lr-fork (0.0.5) → qs (0.5.6)
• load-grunt-tasks
  Requested: ^0.2.1 | Latest: 3.2.0
  OUTDATED
• grunt-contrib-concat
  Requested: ^0.3.0 | Latest: 0.5.1
  OUTDATED
• grunt-contrib-clean
  Requested: ^0.5.0 | Latest: 0.6.0
  OUTDATED
• grunt-contrib-copy
  Requested: 0.4.x | Latest: 0.8.0
  OUTDATED
• grunt-contrib-jshint
  Requested: ^0.8.0 | Latest: 0.11.2
  OUTDATED
• grunt-contrib-uglify
  Requested: ^0.4.0 | Latest: 0.9.1
  OUTDATED

mainly used for pixelData 7fe0,0010 but could be used for others. Result should indicate if the tag exists or not in dataset

The node package is broken. I get :

ReferenceError: window is not defined

(function webpackUniversalModuleDefinition(root, factory) {
	if(typeof exports === 'object' && typeof module === 'object')
		module.exports = factory();
	else if(typeof define === 'function' && define.amd)
		define("dicom-parser", [], factory);
	else if(typeof exports === 'object')
		exports["dicom-parser"] = factory();
	else
		root["dicomParser"] = factory();
})(window, function() {   // <==== HERE
return /******/ (function(modules) { // webpackBootstrap
/******/ 	// The module cache
/******/ 	var installedModules = {};

I suppose this is probably due to the change to webpack 4? At least one node test case should probably be included..

Hi, I just started using dicomParser with the dicom dump example. I'm working with a derivative standard that has additional tags, and I'm wondering whether the tags not known to DICOM would still show up as elements in the dataset. I'm new to both DICOM and the derivative standard, so I don't know the additional tags yet, and the dump shows elements with tags known only to DICOM. This is also true when console logging the dataset. It's possible that the image I uploaded doesn't include any unknown tags, but I wanted to be sure whether they would show up or not if included.

Thanks.

Hi Chris, the following commit is breaking my code:

https://github.com/yagni/dicomParser/blob/a512e23b6d0cf83fafcbde96cae7df0d2087d282/dist/dicomParser.js

It throws this exception on all the files I've test:

dicomParser.readSequenceItem: item tag (FFFE,E000) not found at offset 61502

As I understand it checks for FFFE,E000 after every "SQ", but I'm not sure if this is correct. For example, please see this dump:

# Dicom-Data-Set
# Used TransferSyntax: JPEG Lossless, Non-hierarchical, 1st Order Prediction
(0008,0005) CS [ISO_IR 100]                             #  10, 1 SpecificCharacterSet
(0008,0008) CS [DERIVED\PRIMARY]                        #  16, 2 ImageType
(0008,0016) UI =DigitalXRayImageStorageForPresentation  #  28, 1 SOPClassUID
(0008,0018) UI [40.113845.11.1000000001951524609.20160323200435.3393292.3.54811] #  64, 1 SOPInstanceUID
(0008,0020) DA [20160323]                               #   8, 1 StudyDate
(0008,0023) DA [20160323]                               #   8, 1 ContentDate
(0008,0030) TM [201546]                                 #   6, 1 StudyTime
(0008,0033) TM [201703]                                 #   6, 1 ContentTime
(0008,0050) SH [290235.13]                              #  10, 1 AccessionNumber
(0008,0060) CS [CR]                                     #   2, 1 Modality
(0008,0068) CS [FOR PRESENTATION]                       #  16, 1 PresentationIntentType
(0008,0070) LO [Sirona]                                 #   6, 1 Manufacturer
(0008,0080) LO [Institution]                       #  16, 1 InstitutionName
(0008,0090) PN [.]                                      #   2, 1 ReferringPhysicianName
(0008,1010) SH [Puestoortophan]                         #  14, 1 StationName
(0008,1030) LO [CONDILOGRAFIA]                          #  14, 1 StudyDescription
(0008,1070) PN (no value available)                     #   0, 0 OperatorsName
(0008,1090) LO [ORTHOPHOS XG]                           #  12, 1 ManufacturerModelName
(0008,1120) SQ (Sequence with explicit length #=0)      #   0, 1 ReferencedPatientSequence
(fffe,e0dd) na (SequenceDelimitationItem for re-encod.) #   0, 0 SequenceDelimitationItem
(0008,2111) ST [Lossless JPEG compression, selection value 1, point transform 0, c... #  90, 1 DerivationDescription
(0008,2218) SQ (Sequence with explicit length #=1)      #  48, 1 AnatomicRegionSequence
  (fffe,e000) na (Item with explicit length #=3)          #  40, 1 Item
    (0008,0100) SH [T-D1100]                                #   8, 1 CodeValue
    (0008,0102) SH [SNM3]                                   #   4, 1 CodingSchemeDesignator
    (0008,0104) LO [Head]                                   #   4, 1 CodeMeaning
  (fffe,e00d) na (ItemDelimitationItem for re-encoding)   #   0, 0 ItemDelimitationItem
(fffe,e0dd) na (SequenceDelimitationItem for re-encod.) #   0, 0 SequenceDelimitationItem

As you can see, there are some tags (0008,1120 for example) that are sequences with length=0, so, no FFFE,E000 after them, but in all cases, SQ values end with an FFFE,E0DD tag.

Correct me if I'm wrong but I think the right behavior should be this:

(0008,1120)
    # here can be an FFFE,E000 finished with FFFE,E00D or nothing (0.."n" multiplicity) 
(fffe,e0dd)

So, the line 2211 I think should be replaced by:

if ( (element.tag !== 'xfffee000') && (element.tag !== 'xfffee0dd') )

What do you think?.

The while loop is using byteStream.length instead of byteStream.byteArray.length for the readFragmentsUntil function which causes JPEG2000 images to fail :

function readFragmentsUntil(byteStream, endOfFrame) {
        // Read fragments until we reach endOfFrame
        var fragments = [];
        var bufferSize = 0;
        // Use byteStream.byteArray.length instead of byteStream.length to avoid exception / blowing up
        while (byteStream.position < endOfFrame && byteStream.position < byteStream.byteArray.length) {
            var fragment = dicomParser.readSequenceItem(byteStream);
            // Omitted for brevity

(I did not want to make a pull request for just a single line of code. Maybe you can address on your next update.)

I'm trying to implement DICOM manipulation and was wondering if there was any interest in making dicomParser capable of manipulating the data and storing to a buffer.

DicomParser should be declared as a browser global object in the case where it's used as a node module. ElectronJS uses both node modules and bower components, therefore dicomParser should be declared as a global

/*! dicom-parser - v1.6.1 - 2016-05-24 | (c) 2014 Chris Hafey | https://github.com/chafey/dicomParser */
(function (root, factory) {

    // node.js
    if (typeof module !== 'undefined' && module.exports) {
        module.exports = factory();
        dicomParser = factory();
    }
....

Since we have the vrCallback now, would it make sense to add vr to the element within readDicomElementImplicit with the return value from the vrCallback (if provided)? I can do this.

just an fyi

Problem is that I know this is a vaild dicom file since it can be parsed online using the data dump. I'm using the script directly and not by npm. I suspect there might be a bug there because if I use npm and bundle the final project with browserify it works too.

A side not, parcel does not seem to work with this library either. And why all the extra dependencies in the npm download?

I'm trying to use the simple example to read in a dicom file and display it on the page using cornerstone and the cornerstoneWADOImageLoader libraries. I have this working fine using regular files and the wado fileuri loader, but I'm trying to get it working with byte arrays so I can do work with it with server-processed data. The simple example is throwing an error based on an incorrect Uint16Array length, I believe. Does anyone see anything wrong with this code?

const reader = new FileReader();
reader.addEventListener('load', (e) => {
    let pixelData = self.loadP10Data(reader.result);
    dicomImageData['example://1'] = pixelData;
    self.loadAndViewP10Image('example://1');
}, false);

reader.readAsArrayBuffer(file);

loadP10Data(readerResult) {
    const self = this;
    try
    {
        let byteArray = new Uint8Array(readerResult);

        // Parse the byte array to get a DataSet object that has the parsed contents
        var dataSet = dicomParser.parseDicom(byteArray/*, options */);

        // get the pixel data element (contains the offset and length of the data)
        var pixelDataElement = dataSet.elements.x7fe00010;

        // create a typed array on the pixel data (this example assumes 16 bit unsigned data)
        // FAILS HERE:
        var pixelData = new Uint16Array(dataSet.byteArray.buffer, pixelDataElement.dataOffset, pixelDataElement.length);

        return pixelData;
    }
    catch(ex)
    {
        console.log('Error parsing byte stream', ex);
    }
    return '';
}

Error:

Got pixel data {tag: "x7fe00010", vr: "OW", length: 89456, dataOffset: 2098, hadUndefinedLength: true, …}
app.js:56571 LENGTH 89456
app.js:56577 Error parsing byte stream RangeError: Invalid typed array length: 89456
at typedArrayConstructByArrayBuffer ()
at new Uint16Array (native)
at StringBase64DicomFile.loadP10Data (http://localhost:3000/app.js:56573:29)
at FileReader.reader.addEventListener (http://localhost:3000/app.js:56539:26)

Thanks for this great package.

Some DICOM doesn't have 128 byte 00H preamble and DCIM string, see
http://nipy.org/nibabel/dicom/spm_dicom.html

Now parseDicom simply judges this file as non-DICOM and throws exception, but it is convenient if parseDicom accepts truncated DICOM.

The implementation is very easy, just seeking back to the file head and setting the transfer syntax to default (1.2.840.10008.1.2).
More eager check may be preferable though.

I've already implemented (without eager check though).
If you think parseDicom should be able to handle truncated DICOM, I'll send a pull request.

Hi Chris,

First of all thanks for the great library -

I am trying to read encapsulated pixelData in order to decompress it but it seems is is not exposed in the uglified dicomParser.js:

var compressedPixelData = dicomParser.readEncapsulatedPixelData(
    this._dataSet,
    this._dataSet.elements.x7fe00010,
    frameIndex);

returns:

'undefined' is not a function

How are we supposed readEncapsulatedPixelData with dicomParser? I was following what is done in the cornerstone WADO loader.

Also, as a related question, why do we have to provide the frameIndex to decompress the pixelData? Does it automatically return the frame of interest if we have a muti-frame dataset?

Is it possible to extract all the pixelData at once, in the case of a multi-frame dataset, and split it later if needed, or is it not recommended?

Thanks
Nicolas

ParseTM parses out the fractional portion of the time stamp using a straight parseInt, causing '.5' and '.000005' to result in the same value of 5 microseconds. TM allows anywhere from 1 to 6 digits to be provided so parseTM needs to consider the actual number of digits present in the fractional component and multiply by the appropriate power of 10. Could also zero right-pad then parse but that would probably be the most expensive/wasteful option.

I have an issue with a dicom file that has an unknown tag before Pixel Data. dicomParser tries to determine the length of this unknown tag and checks only ItemDelimitationItem (fffe, e00d), not SequenceDelimitationItem (fffe, e0dd), so it can not determine its length and sets its length to the end of the buffer, so skips Pixel Data.

My quick fix is that i check SequenceDelimitationItem in findItemDelimitationItemAndSetElementLength, but not sure if that is a good fix.

if(elementNumber === 0xe00d || elementNumber === 0xe0dd) { ... }

This is the end of its dicom dump which shows the unknown tag and Pixel Data:

(0507,1001) SQ (Sequence with undefined length #=1) # u/l, 1 Unknown Tag & Data
(fffe,e000) na (Item with explicit length #=8) # 74, 1 Item
(0507,0000) UL 62 # 4, 1 PrivateGroupLength
(0507,1002) ?? (no value available) # 0, 1 Unknown Tag & Data
(0507,1003) ?? (no value available) # 0, 1 Unknown Tag & Data
(0507,1004) ?? (no value available) # 0, 1 Unknown Tag & Data
(0507,1005) ?? 30\20 # 2, 1 Unknown Tag & Data
(0507,1006) ?? 30\20 # 2, 1 Unknown Tag & Data
(0507,1007) ?? (no value available) # 0, 1 Unknown Tag & Data
(0507,1008) ?? 30\20 # 2, 1 Unknown Tag & Data
(fffe,e00d) na (ItemDelimitationItem for re-encoding) # 0, 0 ItemDelimitationItem
(fffe,e0dd) na (SequenceDelimitationItem) # 0, 0 SequenceDelimitationItem
(7fe0,0010) OB (PixelSequence #=2) # u/l, 1 PixelData
(fffe,e000) pi (no value available) # 0, 1 Item
(fffe,e000) pi ff\d8\ff\c3\00\0b\10\06\01\03\04\01\00\11\00\ff\c4\00\24\00\00\00... # 1250014, 1 Item
(fffe,e0dd) na (SequenceDelimitationItem) # 0, 0 SequenceDelimitationItem

I can not share the file, because anonymization tools remove that unknown tag.

I am getting:

dicomParser.readEncapsulatedPixelData: non zero frame specified for single frame encapsulated pixel data

for a file even tough I know it has more than 1 frame.

In fact, if I look at (0028, 0008) Number of Frames, I see 240 (also seen above in fragments).

c.intString('x00280008') // 240

I see this issue on v1.5.0

So I am having problems parsing a dicom file, it is possible that the anonymization before it was sent to me is causing the issue but I can't figure out why the parser is failing. I have used some other dicomParsing and they are able to be viewed fine. I get a Uncaught # and the error is getting thrown here. I have zipped the file so you can replicate, all patient data is bogus.

image_0001.dcm.zip

function readDataSet(metaHeaderDataSet)
    {
        var transferSyntax = readTransferSyntax(metaHeaderDataSet);
        var explicit = isExplicit(transferSyntax);
        var dataSetByteStream = getDataSetByteStream(transferSyntax, metaHeaderDataSet.position);

        var elements = {};
        var dataSet = new dicomParser.DataSet(dataSetByteStream.byteArrayParser, dataSetByteStream.byteArray, elements);
        dataSet.warnings = dataSetByteStream.warnings;

        try{
            if(explicit) {
                dicomParser.parseDicomDataSetExplicit(dataSet, dataSetByteStream, dataSetByteStream.byteArray.length, options);
            }
            else
            {
                dicomParser.parseDicomDataSetImplicit(dataSet, dataSetByteStream, dataSetByteStream.byteArray.length, options);
            }
        }
        catch(e) {
            var ex = {
                exception: e,
                dataSet: dataSet
            };
            throw ex;
        }
        return dataSet;
    }