Validation & Profiles

Overview

InteropSuite provides comprehensive validation at two stages: preflight validation of source messages and FHIR validation of generated bundles. All validation runs 100% offline with no network calls required.

Offline Validation

InteropSuite embeds all validation resources locally:

US Core 6.1.0 Profiles

All FHIR resources are validated against appropriate US Core profiles:

Clinical Resources

Diagnostic Resources

Administrative Resources

Vital Signs Profiles

Vital sign observations are automatically profiled based on LOINC code:

CMS-0057-F Profiles

InteropSuite transforms X12 5010 transactions to FHIR R4 bundles validated against CMS-0057-F profiles. When using OutputFormat.Cms0057F, profiles are automatically selected based on transaction type:

CARIN Blue Button 2.1.0

Used for 835 (Remittance) and 837 (Claims) transactions:

Da Vinci PAS 2.0.1

Used for 278 (Prior Authorization) transactions:

PDex 2.1.0 Provenance

All CMS-0057-F bundles include PDex Provenance with source format tracking:

Preflight Validation

Before transformation, source messages undergo preflight validation:

HL7 v2.x Preflight

• Message structure validation (MSH segment present)
• Required segment checks (PID for patient messages)
• Field format validation (dates, identifiers)
• Code system validation (optional)

X12 Preflight

• Envelope validation (ISA/GS/ST structure)
• Delimiter consistency
• Loop structure validation
• NPI checksum validation

C-CDA Preflight

• XML well-formedness
• ClinicalDocument root element
• HL7 v3 namespace presence
• Required header elements

Severity Levels

Handling Warnings

Warnings indicate non-blocking issues that may affect data quality:

var result = await Interop.HL7ToFhirAsync(message);

// Transformation succeeds even with warnings
if (result.Success)
{
    // Process the bundle
    SaveBundle(result.FhirBundle);

    // Log warnings for review
    if (result.Warnings.Any())
    {
        foreach (var warning in result.Warnings)
        {
            _logger.LogWarning("Transformation warning: {Warning}", warning);
        }

        // Optionally flag for manual review
        FlagForReview(result.FhirBundle, result.Warnings);
    }
}

Common Warning Types