npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

dcmregistry2js

v0.1.2

Published

Convert DICOM standard tag and UID registries to JSON format

Readme

dcmregistry2js

This project contains XSLT files to extract:

  • the attribute data dictionaries from DICOM part 6 and part 7, and
  • the UID registry from DICOM part 6 and to convert them to a JSON data dictionary format used by https://github.com/chafey/dicom2ion-js. (Alternatively an XML dictionary can be created.)

To use:

  • Get a copy of the DICOM part 6 and part 7 XML files from http://www.dicomstandard.org/current
    • Part 6 contains
      • Chapter 6. Registry of DICOM Data Elements
      • Chapter 7. Registry of DICOM File Meta Elements
      • Chapter 8. Registry of DICOM Directory Structuring Elements
      • Chapter 9. Registry of DICOM Dynamic RTP Payload Elements
      • Chapter A. Registry of DICOM Unique Identifiers
    • Part 7 contains
      • Chapter E. Command Dictionary including E.1. Registry of DICOM Command Elements and E.2 Retired Command Fields
  • Place the DICOM files part06.xml and part07.xml in the input directory.
  • There are 4 xslt tasks configured in the project:
    • Generate ./dist/tagsRegistry.json
    • Generate ./dist/tagsRegistry.xml
    • Generate ./dist/uidRegistry.json
    • Generate ./dist/uidRegistry.xml Run the desired extraction task.
  • Alternatively invoke the XSLT files (extractTags.xsl, extractUids.xsl) from your favourite tool or the commandline.
    • extractTags.xl uses the part06.xml file as the source, and takes the following parameters:
      • format=json,xml - specify the desired output format (optional; default: json)
      • +part07={path/to/part07.xml} - specify the part07.xml file. (required; the "+" indicates this is an xml document-node)
    • extractUids.xl uses the part06.xml file as the source, and takes the following parameters:
      • format=json,xml - specify the desired output format (optional; default: json)

To Do:

  • Improve the JSON output. The current output is a little ugly, but is compliant and funcitonal. The conversion is a combination of customized xslt and of some generic XML-to-JSON xslt. It may be possible to use the json namespace to craft something that will emit as nicer JSON.

To modify the xslt files, the VS Code extension XSLT Interactive Debugger may be useful.