fhir-hl7-validator

Original：🇺🇸 English

Translated

This skill should be used when the user asks to "validate FHIR resources", "check HL7 messages", "validate healthcare data format", "parse FHIR", "HL7 v2 messages", "FHIR R5 validation", "CDA documents", "healthcare data interchange", "FHIR resource schema", "HL7 specifications", or mentions FHIR validation, HL7 message parsing, CDA validation, healthcare data format compliance, or Fast Healthcare Interoperability Resources standards.

2installs

Source1mangesh1/dev-skills

Added on2026-03-12

NPX Install

npx skill4agent add 1mangesh1/dev-skills fhir-hl7-validator

SKILL.md Content

View Translation Comparison →

FHIR & HL7 Validator

Healthcare data format validation skill for AI agents. Validates FHIR R5 resources, HL7 v2 messages, and CDA clinical documents. Ensures healthcare data interchange compliance with HL7 standards and identifies schema violations, missing required fields, and interoperability issues.

Capabilities

FHIR Validation - Validate FHIR R5 resources against official schemas
HL7 Message Parsing - Parse and validate HL7 v2.x messages (ADT, ORU, OBX, RXO)
CDA Document Validation - Validate Clinical Document Architecture (CDA) R2 documents
Schema Compliance - Check resources against FHIR specification and UK Core
Data Type Validation - Verify FHIR data types (Identifier, CodeableConcept, Reference, etc.)
Reference Resolution - Validate internal and external references
Cardinality Checking - Ensure required vs. optional field compliance
Terminology Validation - Check value sets and coding systems (SNOMED CT, LOINC, ICD-10)
Interoperability Analysis - Identify implementation guide adherence
Error Reporting - Generate detailed validation error reports with remediation

Usage

/fhir-hl7-validator [command] [target] [options]

Commands

```
validate-fhir <file>
```
- Validate FHIR JSON/XML resource
```
validate-hl7 <file>
```
- Validate HL7 v2 message
```
validate-cda <file>
```
- Validate CDA clinical document
```
parse-fhir <file>
```
- Parse and display FHIR resource structure
```
parse-hl7 <file>
```
- Parse and display HL7 segments
```
check-references <file>
```
- Validate all resource references
```
check-terminology <file>
```
- Validate coding systems and value sets
```
bulk-validate <directory>
```
- Validate multiple files
```
report <output-format>
```
- Generate validation report (JSON, markdown, HTML)

Options

```
--version <ver>
```
- FHIR version (default: R5; also 4.0, 3.0)
```
--variant <name>
```
- Implementation guide (e.g., uk-core, us-core)
```
--strict
```
- Enforce must-support constraints
```
--terminology-check
```
- Validate coding systems (enables online lookup)
```
--output <file>
```
- Write report to file
```
--format <type>
```
- Output format: json, markdown, html, xml

Workflow

Follow this workflow when invoked:

Step 1: Identify Healthcare Data Type

Ask user to specify:

Data format (FHIR, HL7 v2, CDA)
FHIR version or HL7 dialect
Implementation guide/profile (if applicable)
Data source (EHR, lab system, imaging system)

Step 2: Validate Structure

Check:

JSON/XML well-formedness
Required elements present
Data type conformance
Cardinality compliance (min/max occurrences)
Pattern and regex validation

Step 3: Semantic Validation

Verify:

Code system membership (SNOMED CT, LOINC, ICD-10, etc.)
Reference consistency (local vs. external)
Identifier uniqueness and format
Date/time format accuracy (ISO 8601)
Quantity unit validity

Step 4: Interoperability Check

Ensure compliance with:

FHIR implementation guides
US Core or UK Core profiles
HL7 message specifications
Clinical data interchange standards

Step 5: Generate Report

Provide:

List of validation errors with line numbers
Severity level (error, warning, info)
Remediation guidance
Reference to relevant standards

FHIR Resource Examples

Patient Resource

json

{
  "resourceType": "Patient",
  "id": "example",
  "identifier": [
    {
      "system": "http://example.org/medical-record",
      "value": "12345"
    }
  ],
  "name": [
    {
      "use": "official",
      "given": ["Jane"],
      "family": "Doe"
    }
  ],
  "birthDate": "1990-01-15",
  "address": [
    {
      "use": "home",
      "line": ["123 Main St"],
      "city": "Springfield",
      "state": "IL",
      "postalCode": "62701"
    }
  ]
}

Observation Resource