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.
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.
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
--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
{"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"}]}
MSH|^~\&|SendingApp|SendingFac|ReceivingApp|ReceivingFac|202502071350||ADT^A01|123456|P|2.5
PID^^^12345||JaneDoe||19900115|F|||123 Main St^^Springfield^IL^62701|||||||S
PV1||I|ICU^FL2^BED01|||||||||||||||||||||||||||
Common Validation Errors
Error
Cause
Solution
Missing required element
Element marked cardinality: 1..1 not present
Add the required element
Invalid data type
Value doesn't match specified type
Convert to correct type (e.g., date to YYYY-MM-DD)
Unknown code system
Code not in specified value set
Use code from official code system (SNOMED CT, LOINC)
