HL7v2 Reference Lookup
Look up HL7v2 definitions using the reference script:
bun scripts/hl7v2-ref-lookup.ts <code> [--version <version>]
<code>: the HL7v2 identifier to look up. Must be one of:
- Message:
ORU_R01, ADT_A01
- Segment:
PID, OBX
- Field:
PID.3, OBX.2
- Component:
PID.3.1, CWE.1
- Table:
0001, 0203
- Datatype:
CWE, ST, ID
--version: HL7v2 version (default 2.8.2). Supported: 2.5, 2.8.2
Version rules
This project has reference data for two HL7v2 versions: v2.5 and v2.8.2.
- When answering user questions (no version specified): look up both versions in parallel and present results. Highlight differences (optionality, cardinality, field presence, data types, table values). If identical, say so briefly.
- When coding (writing/modifying converters, parsers, builders): use v2.8.2 as the primary reference — this is the project's target version. Check v2.5 if dealing with backward-compatibility concerns or if the code explicitly references v2.5.
- When user specifies a version: use only that version.
When to use
- Answering questions: User asks about HL7v2 fields, datatypes, or message structures
- Design/architecture: Need to understand what fields a segment contains, what values a table allows, or how a message is structured
- Coding: Building or parsing HL7v2 segments — look up field positions, datatypes, optionality, cardinality, and valid table values
- Code review: Verify that field mappings, datatypes, and table values are correct
Do NOT skip this skill and rely on codebase exploration or memory for HL7v2 specifications. The reference data is the authoritative source.
When looking up multiple codes, make separate Bash tool calls in the same response — do NOT use shell & or && to chain commands. The script is allowlisted individually (bun scripts/hl7v2-ref-lookup.ts:*), and chained shell commands bypass the allowlist and trigger permission prompts. Show the full script output to the user without modification.
1---2name: hl7v2-info3description: Look up segment fields, datatypes, components, tables, and message structures. MUST use this skill for writing HL7v2↔FHIR converters, mapping HL7v2 fields, checking field positions/optionality, verifying HL7v2 compliance or answering questions about hl7v2.4---5
6# HL7v2 Reference Lookup
7
8Look up HL7v2 definitions using the reference script:
9
10```bash
11bun scripts/hl7v2-ref-lookup.ts <code> [--version <version>]
12```
13
14- `<code>`: the HL7v2 identifier to look up. Must be one of:
15 - Message: `ORU_R01`, `ADT_A01`
16 - Segment: `PID`, `OBX`
17 - Field: `PID.3`, `OBX.2`
18 - Component: `PID.3.1`, `CWE.1`
19 - Table: `0001`, `0203`
20 - Datatype: `CWE`, `ST`, `ID`
21- `--version`: HL7v2 version (default `2.8.2`). Supported: `2.5`, `2.8.2`
22
23## Version rules
24
25This project has reference data for **two HL7v2 versions**: v2.5 and v2.8.2.
26
27- **When answering user questions** (no version specified): look up **both versions in parallel** and present results. Highlight differences (optionality, cardinality, field presence, data types, table values). If identical, say so briefly.
28- **When coding** (writing/modifying converters, parsers, builders): use **v2.8.2** as the primary reference — this is the project's target version. Check v2.5 if dealing with backward-compatibility concerns or if the code explicitly references v2.5.
29- **When user specifies a version**: use only that version.
30
31## When to use
32
33- **Answering questions**: User asks about HL7v2 fields, datatypes, or message structures
34- **Design/architecture**: Need to understand what fields a segment contains, what values a table allows, or how a message is structured
35- **Coding**: Building or parsing HL7v2 segments — look up field positions, datatypes, optionality, cardinality, and valid table values
36- **Code review**: Verify that field mappings, datatypes, and table values are correct
37
38Do NOT skip this skill and rely on codebase exploration or memory for HL7v2 specifications. The reference data is the authoritative source.
39
40When looking up multiple codes, make **separate Bash tool calls** in the same response — do NOT use shell `&` or `&&` to chain commands. The script is allowlisted individually (`bun scripts/hl7v2-ref-lookup.ts:*`), and chained shell commands bypass the allowlist and trigger permission prompts. Show the full script output to the user without modification.
majiayu000