You do not need an imaging archive to begin.
DICOM is the format and communication standard behind medical imaging. EASI JS gives JavaScript applications a fluent way to read that data, extract what matters, and produce an output they can use.
The same pipeline pattern carries from a small metadata example to native DICOM files, HTTP responses, and Node.js DIMSE connections. Start with a concrete result, then change one stage at a time.
Node.js 22 or 24, npm, and a JavaScript editor. All sample identifiers and metadata are synthetic. You can run the first three guides without a server.
Four steps, one pipeline model.
Your first pipeline
Install the library and read synthetic imaging metadata. No PACS, patient files, or optional codecs required.
02 · Core concepts · Inputs and outputsChoose your output
Keep a full DICOM instance, select a few attributes, or serialize bytes. Understand what your application retains.
03 · Integration · Identity and aggregationBridge DICOM and FHIR
Turn instance metadata into FHIR R4 ImagingStudy resources, with deliberate subject references and study counts.
04 · Networking · A configured DICOM peerConnect to a PACS
Use Node.js to verify an archive, query studies, and plan GET or MOVE retrieval with explicit limits.
Reading a local file? Begin with steps one and two. Connecting imaging metadata to an existing FHIR system? Continue to step three. Working with a traditional DICOM archive? Step four covers the network prerequisites.
Keep the reference close.
These guides explain the decisions behind a workflow. The v1.0.0 README covers public imports, browser setup, custom mappings, writing chunks, codec configuration, and troubleshooting.
The API documentation describes individual classes and extension points. You can inspect the source when you need to understand a parser or transport contract.
Before adding EASI JS to a product, review the community and commercial licensing options.