FHIR to X12
Category: Healthcare Standards
Node id: fhir-to-x12
Standards: HIPAA, GDPR, SOC2
Converts FHIR resources (Claim, CoverageEligibilityRequest) to X12 EDI transaction formats (837P, 837I, 270)
What it does
- Converts FHIR Claim resources to X12 837P and 837I transactions
- Converts FHIR CoverageEligibilityRequest to X12 270 transactions
- ISA/GS/ST envelope generation with proper control numbers
- Diagnosis code mapping from FHIR CodeableConcept to HI segments
- Detailed field-level mapping report with unmapped field tracking
Use cases
- Generate X12 837 professional claims from FHIR Claim resources
- Submit eligibility inquiries to payers from FHIR coverage data
- Bridge FHIR-based clinical systems with X12-based billing clearinghouses
Runtime
- Performance tier:
fast
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
fhir_resource | json | Yes | FHIR resource to convert (Claim or CoverageEligibilityRequest) |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
result | json | No | Conversion result (x12_text, mapping_details, unmapped_fields, source_type, target_type) |
success | boolean | No | Whether the conversion succeeded |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Target Transaction Type | target_transaction_type | enum | No | 837P | 837P, 837I, 270 | X12 transaction type to generate |
Errors
| Code | Description |
|---|---|
RESOURCE_REQUIRED | fhir_resource input is missing |
UNSUPPORTED_MAPPING | Source FHIR resource type does not match the target X12 transaction |
INVALID_TRANSACTION_TYPE | target_transaction_type is not 837P, 837I, or 270 |
Runtime notes
- result.x12_text is the complete X12 EDI string with ISA/GS/ST envelopes — ready for clearinghouse submission
- result.mapping_details shows per-field mapping status; result.unmapped_fields lists FHIR fields that could not be mapped
- Supported mappings: Claim->837P, Claim->837I, CoverageEligibilityRequest->270
- Control numbers and timestamps are auto-generated — not suitable for production without customizing ISA/GS identifiers
See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.
Etwas unklar? Senden Sie Feedback zur Dokumentation per E-Mail..