skills.rest
Aidbox
AidboxOFFICIAL
Explore all skills by this author →
WebsiteGitHub

hl7v2-info

Look up HL7v2 definitions for messages, segments, fields, components, tables, and datatypes.

7|3|Updated Dec 9, 2025
Search Tags:#reference#converter#mapping#lookup#datatypes#hl7v2#hl7v2-to-fhir
One-click install
npx skills add https://github.com/Aidbox/aidbox-hl7v2-example --skill hl7v2-info
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hl7v2-info
Source: https://github.com/Aidbox/aidbox-hl7v2-example/tree/main/.claude/skills/hl7v2-info
Command: npx skills add https://github.com/Aidbox/aidbox-hl7v2-example --skill hl7v2-info

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides fast lookup of HL7v2 definitions (messages, segments, fields, components, tables, and datatypes) to support HL7v2↔FHIR converters, mappings, and validation tasks.

Core Features & Use Cases

  • HL7v2 reference lookup across two versions (v2.5 and v2.8.2) for messages, segments, fields, components, tables, and datatypes.
  • Version-aware comparisons to highlight differences in optionality, cardinality, and data types.
  • Guided assistance for designing, implementing, and validating HL7v2 to FHIR converters, mappings, and compliance checks.

Quick Start

Run a quick lookup for a specific HL7v2 code using the reference script.

Frequently Asked Questions about hl7v2-info

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I look up HL7v2 segment and field definitions for building a FHIR converter?▼

This Skill provides instant HL7v2 reference lookups for messages, segments, fields, components, tables, and datatypes across versions 2.5 and 2.8.2. It filters by code type to return precise optionality and datatype details required for building accurate converters.

Can I compare HL7v2 datatype differences between version 2.5 and 2.8.2?▼

Yes, the reference script supports version-aware comparisons between HL7v2 v2.5 and v2.8.2, highlighting differences in optionality, cardinality, and data types. This ensures your mappings remain compliant across both standard versions.

What is the best way to validate HL7v2 message structure before mapping it to FHIR?▼

The best way to validate HL7v2 message structure before mapping to FHIR is to query the reference script for message, segment, and component definitions. This verifies structural compliance against version-specific optionality and datatype rules before conversion.

Does the HL7v2 reference support filtering by code types like Segment, Field, and Datatype?▼

Yes, HL7v2 reference lookups support code-type filtering for Message, Segment, Field, Component, Table, and Datatype categories. This narrows results to the exact structural element needed for your specific mapping or validation task.

Why do I need an HL7v2 reference lookup tool for FHIR mapping tasks?▼

You need an HL7v2 reference lookup tool to accurately resolve message structures, field optionality, and datatype constraints during FHIR mapping. Without precise version-specific definitions, converters risk dropping required data or mapping fields incorrectly.

Related Skills

Explore More Software Engineering Skills→
CJCreator-NewCJCreator-New

hims-fhir-specialist

Map and validate FHIR R4/R5 resources for HIMS interoperability with ABDM.

Community
Advanced
mark64oswaldmark64oswald
1

healthsim-patientsim

Generate synthetic clinical data in FHIR R4 or HL7v2 formats.

Community
Advanced
aks-buildsaks-builds
1

terminology-services

Provides healthcare code system validation, FHIR terminology operations, mapping, and reference guidance for engineers.

Community
Advanced
nahisahonahisaho
3

scientific-clinical-standards

Map clinical terminology codes across LOINC, ICD-10/ICD-11, and FHIR.

Community
Advanced