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 🙏

© 2024 – Pkg Stats / Ryan Hefner

nodengine-hl7

v4.1.8

Published

HL7 parser

Downloads

54

Readme

nodengine-hl7

Build Status Coverage Status

A hl7 parser

Installation

$ npm install --save nodengine-hl7

or install globally for the CLI tool

$ npm install -g nodengine-hl7
$ ne-hl7 --help
ne-hl7 - a streaming parser for hl7 messages

    usage: ne-hl7 [options]

    options:

      -h, --help                  show help and usage
      -l, --loglevel <level>      set log level
      -f, --file <file>           parse file
      -s, --segments              only show segment types
      -c, --count                 print message count
      -j, --json                  output in json
      -v, --version               show version

Unit Tests

To run tests:

$ npm test

NOTE: All hl7 test fixtures are samples taken from various places on the internet

API

Parser

Constructor


Message

Constructor

Params

| Name | Type(s) | Description | | ---- | ------- | ----------- | | segments | Array, Segment | A single Segment or an array of Segments |


Message.hasSegments()

Does this message have any segments?


Message.addSegment()

Adds the given segment to the message

Params

| Name | Type(s) | Description | | ---- | ------- | ----------- | | segment | Segment | The Segment to add to the message |


Message.getHeader()

Gets the header Segment of the Message


Message.delimiters()

Gets the delimiters for the given message. These are taken from the MSH


Segment

Constructor


Segment.parse()

Parses data as a hl7 segment

Params

| Name | Type(s) | Description | | ---- | ------- | ----------- | | data | Buffer, String | The segment |


utils.segmentIsHeader()

Is the given segment a header segment?

Params

| Name | Type(s) | Description | | ---- | ------- | ----------- | | segment | Segment | A Segment object |


utils.segmentTypeIsHeader()

Is the given segment type a header segment?

Params

| Name | Type(s) | Description | | ---- | ------- | ----------- | | type | String | The segment type |

License

MIT (See LICENSE for more info)