fhir-hl7-validator_skill

Overview

This skill validates healthcare data formats and enforces HL7 and FHIR standards for interoperability and compliance. It supports FHIR R5 (and earlier versions), HL7 v2 messages, and CDA R2 documents, producing actionable error reports and remediation guidance. Use it to detect schema violations, missing required elements, broken references, and terminology issues.

How this skill works

The validator parses the provided artifact (FHIR JSON/XML, HL7 v2 text, or CDA XML), checks well-formedness, and runs structural validation against the selected FHIR version or HL7 dialect. It performs semantic checks: cardinality enforcement, data type conformance, reference resolution, and terminology membership (SNOMED CT, LOINC, ICD-10). Results are returned as a structured report with severity, line/element context, and remediation steps.

When to use it

• Validating FHIR resources before EHR ingestion or API exchange
• Checking HL7 v2 messages from interfaced systems (ADT, ORU, RXO)
• Validating CDA clinical documents for health information exchange
• Auditing data for implementation guide compliance (US Core, UK Core)
• Running bulk validation across a directory of clinical artifacts

Best practices

• Specify exact format and FHIR version to avoid false positives
• Enable terminology checks when online access to value sets is available
• Use --strict or must-support enforcement during pre-production validation
• Resolve broken references by validating bundled or referenced resources together
• Include sample failing artifacts when requesting remediation guidance

Example use cases

• Validate a Patient or Observation FHIR resource before submitting to an HIE
• Parse and validate incoming ADT messages to catch missing PID fields
• Run a bulk-validate pass on exported clinical documents prior to migration
• Check coding systems in lab results for LOINC/SNOMED conformance
• Generate a remediation report highlighting required-field fixes and code corrections