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

@fhir-dsl/terminology

v1.2.2

Published

Compile-time FHIR terminology resolver for ValueSets and CodeSystems

Downloads

395

Readme

@fhir-dsl/terminology

Compile-time FHIR terminology resolver. Loads pre-expanded ValueSets and CodeSystems from a FHIR spec or Implementation Guide, resolves bindings (required / extensible / preferred / example) by strength, and walks CodeSystem hierarchies (is-a, descendent-of, regex filters with transitive subsumption).

This is the engine behind @fhir-dsl/cli generate --expand-valuesets / --resolve-codesystems. Most users never import it directly — install standalone only when you need the same resolver outside the generator (e.g. a custom binding-strength linter or an offline validate-code runner).

Install

npm install @fhir-dsl/terminology

Usage

Resolve a ValueSet from a parsed bundle

import {
  TerminologyRegistry,
  parseCodeSystem,
  parseExpansionsBundle,
  resolveValueSet,
} from "@fhir-dsl/terminology";

const registry = new TerminologyRegistry();
parseExpansionsBundle(expansionsBundleJson, registry);
parseCodeSystem(codeSystemJson, registry);

const vs = resolveValueSet(
  "http://hl7.org/fhir/ValueSet/administrative-gender",
  registry,
);
// vs?.codes: ResolvedCode[] — { code, display?, system, definition? }

Walk a CodeSystem hierarchy

TerminologyRegistry exposes the parsed CodeSystem graph for transitive subsumption (is-a + descendent-of filters). The generator uses it to expand compose.include[].filter against in-house concept trees without needing a live terminology server.

import { resolveCompose } from "@fhir-dsl/terminology";

// resolveCompose handles the full ValueSet.compose grammar:
// - include.system + include.concept[]
// - include.system + include.filter[].op (= "is-a" | "descendent-of" | "regex" | "in" | "not-in" | "exists")
// - include.valueSet[]
// - exclude.* (subtracts from the union)
const codes = resolveCompose(compose, registry);

Coverage

  • Bindings by strengthrequired, extensible, preferred, example. The generator narrows enums for required (and extensible under --strict-extensible); preferred / example keep the open string type.
  • CodeSystem filtersis-a and descendent-of walk transitive concept.concept[] hierarchies; regex matches code against the supplied pattern; in / not-in membership checks; exists against concept.property[].
  • Pre-expanded ValueSets — when a ValueSet ships an expansion.contains[] block, that wins over compose (matches the FHIR spec's hint that pre-expansion is authoritative).

What's not in scope

  • Live $expand / $validate-code against a remote server — that lives in @fhir-dsl/core (client.terminology.*). This package is purely offline.
  • SNOMED post-coordination, LOINC parts — out of scope; treat them as opaque codes.

License

MIT