Bugs in file parsing deserves special attention, but the article is quite sensationalist. Many other similar problems (algorithms crashing, hanging, leaking memory if receiving incorrect or unusual input) are getting fixed in medical image computing libraries without being ever reported to vulnerability databases - probably because in this field it is just not common practice to use these tools.
That said, GDCM has many open issues (several of them referring to vulnerability databases), which should be fixed. I hope medical device companies that use GDCM take note and help out @mathieu.malaterre.
Yes, I would expect (hope?) that critical medical systems are not importing DICOM files of unknown origin.
For this particular issue it does not appear that a “public” issue was created. Perhaps only e-mail was sent to the project developer where not response was received. I am not sure creating an article and issue like this is the best way for security individuals to interact with open source communities to get issues addressed.
Agreed, I think GDCM is in need of more resources and effort.