Package Exports

@glion/annotate-profile-fields

Readme

@glion/annotate-profile-fields

unified plugin to annotate HL7v2 field nodes with profile metadata.

What is this?
When should I use this?
Install
Use
API
Examples
Compatibility
Related

What is this?

This package is a unified plugin that enriches Field AST nodes with metadata from HL7v2 profile definitions. After running this plugin, each field carries its profile information directly on field.data — making the AST self-describing.

The plugin reads the message version from MSH-12, loads the corresponding field definitions from @glion/profiles, and spreads the profile properties onto each field node. Unknown segments (Z-segments) and unsupported versions are silently skipped.

When should I use this?

Use this plugin when:

You want to inspect a parsed AST and see field names, datatypes, and constraints without loading profiles yourself
Building tools (serializers, debuggers, IDE integrations) that need field-level metadata
Creating custom processors that need to know which fields are required, repeatable, or coded

Install

npm install @glion/annotate-profile-fields

Use

import { unified } from "unified";
import { hl7v2Parser } from "@glion/parser";
import { hl7v2AnnotateProfileFields } from "@glion/annotate-profile-fields";

const processor = unified().use(hl7v2Parser).use(hl7v2AnnotateProfileFields);

const message =
  "MSH|^~\\&|SENDER||RECEIVER||20241201||ADT^A01^ADT_A01|MSG123|P|2.5\rPID|1||12345||Doe^John";

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

// Field nodes now carry profile metadata on field.data
// e.g., PID-3: { id: "PID-3", name: "Patient Identifier List", required: true, repeatable: true, datatype: "CX", ... }

API

This package exports the identifier hl7v2AnnotateProfileFields. The default export is hl7v2AnnotateProfileFields.

`unified().use(hl7v2AnnotateProfileFields)`

Annotate Field nodes with profile metadata.

This plugin:

Reads the HL7v2 version from MSH-12
Loads field definitions for all segments in the message
Visits each Field node and spreads the matching profile properties onto field.data

Returns

Async transformer (async function (Root) => Root)

Augmented `FieldData`

Importing this package augments the FieldData interface from @glion/ast:

Property	Type	Description
`id`	`string`	Field identifier (e.g., `"MSH-9"`, `"PID-3"`)
`name`	`string`	Human-readable field name (e.g., `"Patient Name"`)
`required`	`boolean`	Whether this field is required in the segment
`repeatable`	`boolean`	Whether this field supports repetition
`datatype`	`string`	Datatype ID (e.g., `"XPN"`, `"ST"`, `"CWE"`)
`maxLength`	`number`	Maximum allowed length (when defined in the profile)
`table`	`string`	Table reference for coded fields (e.g., `"HL70001"`)
`item`	`string`	HL7 specification item number

All properties are optional (undefined when not available in the profile).

Examples

Accessing field metadata

import { visit } from "@glion/util-visit";

// After running the annotator...
visit(tree, "field", (node, ancestors, info) => {
  if (node.data?.required && node.data?.name) {
    console.log(`Required field: ${node.data.id} (${node.data.name})`);
  }
});

Finding coded fields

visit(tree, "field", (node) => {
  if (node.data?.table) {
    console.log(`${node.data.id} uses table ${node.data.table}`);
  }
});

Compatibility

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

@glion/annotate-profile-datatypes — Annotate components with datatype metadata
@glion/annotate-profile-code-systems — Annotate coded values with UTG display names
@glion/preset-annotate-profile-recommended — Preset bundling all profile annotators
@glion/profiles — Profile data source

Contributing

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

Fork the repository
Create your feature branch (git checkout -b feature/amazing-feature)
Commit your changes (git commit -m 'Add some amazing feature')
Push to the branch (git push origin feature/amazing-feature)
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

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.

JSPM