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

@br-health-kit/fhir

v1.0.0

Published

Terminologia e perfis FHIR brasileiros da RNDS, com as URIs canonicas oficiais

Readme

@br-health-kit/fhir

Brazilian FHIR R4 terminology and profiles, extracted from the official RNDS implementation guide.

npm install @br-health-kit/fhir
import { fhir } from '@br-health-kit/fhir'

fhir.coding('cid10', 'J45', 'Asma')
// { system: 'https://rnds-fhir.saude.gov.br/CodeSystem/BRCID10',
//   code: 'J45', display: 'Asma' }

fhir.identifier('cns', '700000000000000')
// { system: 'http://rnds.saude.gov.br/fhir/r4/NamingSystem/cns', value: '...' }

fhir.systemUri('tuss')   // resolves the alias to the canonical URI

The value is in the canonical URIs

A FHIR resource coding a CID-10 diagnosis is only interoperable if it names the system exactly as the RNDS does. A URI off by one character produces a resource nobody can interpret, and no validator will tell you which character.

Every URI in this package comes from the official guide's package.tgz, with checksum and version. None was transcribed from documentation or from memory.

Nobody remembers that TUSS is BRCBHPMTUSS in the RNDS guide. The aliases (cid10, cbo, tuss, ciap2, cns, cpf, cnes) handle that; the URI that comes out is the canonical one.

It is the bridge between the kit and FHIR

import { cid10 } from '@br-health-kit/cid10'
import { fhir } from '@br-health-kit/fhir'

const asthma = cid10.find('J45')
fhir.codeableConcept('cid10', asthma.code, asthma.description)

@br-health-kit/cid10 knows the codes; this package knows how to say them in FHIR.

An unknown system is not a guess

fhir.systemUri('doesNotExist')     // null
fhir.coding('doesNotExist', 'X')   // throws UnknownSystemError

And identifiers are separated from code systems by construction: emitting a patient's CNS under a code-system URI would be silently wrong, so fhir.identifier() only accepts the three identifier systems the RNDS declares (CNS, CPF, CNES).

What the dataset contains

| Table | Contents | | --- | --- | | codeSystems | 28 systems, with their concepts | | namingSystems | 54 canonical URIs, 3 of them identifiers | | valueSets | 25 sets and the systems they reference | | profiles | 27 Brazilian profiles and extensions |

Limit

This package provides terminology and the profile URIs. It does not validate a FHIR resource against a StructureDefinition. For that, use a real FHIR validator, pointed at the profiles whose URLs are here.

Environment

Node 20+ through the default entry. For a client bundle use @br-health-kit/fhir/web. See docs/browser.md.

Provenance

The public RNDS implementation guide, redistributed without content modification. Code under MIT.