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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@rethinkhealth/hl7v2-annotate-message-structure

v0.4.2

Published

Unified plugin to infer HL7v2 message structure from message code and trigger event

Readme

@rethinkhealth/hl7v2-annotate-message-structure

unified plugin to infer HL7v2 message structure when MSH-9.3 is missing.

Contents

What is this?

This package is a unified plugin that infers the message structure (MSH-9.3) from message code (MSH-9.1) and trigger event (MSH-9.2) when the structure field is not present in the HL7v2 message.

Real-world HL7v2 messages often omit MSH-9.3, especially in older versions. This plugin automatically infers the structure using the convention: {messageCode}_{triggerEvent}.

When should I use this?

Use this plugin when:

  • Processing HL7v2 messages that may not include MSH-9.3
  • You want to normalize message metadata for downstream processing
  • You need to ensure all messages have a message structure for routing or validation

Note: This plugin requires @rethinkhealth/hl7v2-annotate-message to run first to extract message metadata.

Install

npm install @rethinkhealth/hl7v2-annotate-message-structure

Use

import { unified } from 'unified';
import { hl7v2Parser } from '@rethinkhealth/hl7v2-parser';
import { hl7v2AnnotateMessage } from '@rethinkhealth/hl7v2-annotate-message';
import { hl7v2AnnotateMessageStructure } from '@rethinkhealth/hl7v2-annotate-message-structure';

const processor = unified()
  .use(hl7v2Parser)
  .use(hl7v2AnnotateMessage)
  .use(hl7v2AnnotateMessageStructure);

// Message without MSH-9.3
const message = 'MSH|^~\\&|SENDER||RECEIVER||20241201||ADT^A01|MSG123|P|2.5';

const tree = processor.parse(message);
await processor.run(tree);

console.log(tree.data.messageInfo);
// {
//   version: "2.5",
//   messageCode: "ADT",
//   triggerEvent: "A01",
//   messageStructure: "ADT_A01"  // ← Inferred!
// }

API

This package exports the identifier hl7v2AnnotateMessageStructure. There is no default export.

unified().use(hl7v2AnnotateMessageStructure)

Infer message structure from message code and trigger event.

This plugin:

  1. Checks if tree.data.messageInfo.messageStructure is already set
  2. If missing, checks for messageCode and triggerEvent
  3. If both present, infers structure as {messageCode}_{triggerEvent}
  4. Updates tree.data.messageInfo.messageStructure with inferred value
Parameters
  • None
Returns

Transformer (function (Root) => Root)

Examples

Basic Inference

import { unified } from 'unified';
import { hl7v2Parser } from '@rethinkhealth/hl7v2-parser';
import { hl7v2AnnotateMessage } from '@rethinkhealth/hl7v2-annotate-message';
import { hl7v2AnnotateMessageStructure } from '@rethinkhealth/hl7v2-annotate-message-structure';

const processor = unified()
  .use(hl7v2Parser)
  .use(hl7v2AnnotateMessage)
  .use(hl7v2AnnotateMessageStructure);

// MSH-9.3 is missing
const message = 'MSH|^~\\&|||||||VXU^V04|MSG001|P|2.5.1';
const tree = processor.parse(message);
await processor.run(tree);

console.log(tree.data.messageInfo.messageStructure); // "VXU_V04"

Non-Destructive Behavior

// If MSH-9.3 is already present, it won't be overwritten
const messageWithStructure = 
  'MSH|^~\\&|||||||ADT^A01^ADT_A01_CUSTOM|MSG001|P|2.5';

const tree = processor.parse(messageWithStructure);
await processor.run(tree);

console.log(tree.data.messageInfo.messageStructure); 
// "ADT_A01_CUSTOM" (original value preserved)

Combined with Linting

import { hl7v2LintMessageStructure } from '@rethinkhealth/hl7v2-lint-message-structure';

// Infer structure and warn about missing source values
const processor = unified()
  .use(hl7v2Parser)
  .use(hl7v2AnnotateMessage)
  .use(hl7v2AnnotateMessageStructure)  // Fix missing structure
  .use(hl7v2LintMessageStructure);     // Warn about missing source

const result = await processor.process(message);
// Will have messageStructure populated, but may have warnings

Behavior

When Structure is Inferred

  • Both messageCode (MSH-9.1) and triggerEvent (MSH-9.2) must be present
  • Structure is inferred as: {messageCode}_{triggerEvent}
  • Examples:
    • ADT + A01ADT_A01
    • ORU + R01ORU_R01
    • VXU + V04VXU_V04

When Structure is NOT Inferred

  • Message structure already exists (won't override)
  • Message code is missing or empty
  • Trigger event is missing or empty
  • No messageInfo exists in tree data

Compatibility

  • Node.js: 18+
  • TypeScript: 5.0+
  • unified: 11.0+

Related

Contributing

We welcome contributions! Please see our Contributing Guide for more details.

  1. Fork the repository
  2. Create your feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes (git commit -m 'Add some amazing feature')
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Open a Pull Request

Code of Conduct

To ensure a welcoming and positive environment, we have a Code of Conduct that all contributors and participants are expected to adhere to.

License

Copyright 2025 Rethink Health, SUARL. All rights reserved.

This program is licensed to you under the terms of the MIT License. This program is distributed WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the LICENSE file for details.