HIPAA Package FAQ.
Common questions about the Redix HIPAA Package — included components, supported transaction sets, X12 versions, NPI support, and licensing.
What does the Redix HIPAA Package include?
The Redix HIPAA Package bundles everything you need to build, test, and deploy HIPAA-compliant data exchanges:
- Redix AnyToAny Format Converter Engine — high-performance runtime engine for versatile data transformations across formats
- GUI Mapper with EDI Authoring Tools — point-and-click map designer and tester for intuitive EDI mapping
- HIPAA database — all essential HIPAA EDI transaction sets, ensuring full HIPAA compliance
Which HIPAA transaction sets are supported?
- 270/271 — Health Care Eligibility/Benefit Inquiry and Information Response
- 276/277 — Claim Status Request and Response
- 278 — Health-care Service Review – Request for Review and Response
- 834 — Benefit Enrollment and Maintenance
- 835 — Claim Payment/Advice (EDI 835 remittance)
- 837 — Claim (Institutional, Professional, Dental)
What is the difference between HIPAA_A1_837_Prof and HIPAA_A1_837_Prof_Outbound messages?
HIPAA_A1_837_Prof is the generic 837 professional definition defined in X12 4010. HIPAA_A1_837_Prof_Outbound is a specific form based on HIPAA usage, with rigorously defined segments and loops that eliminate vagueness in HIPAA data exchange.
It is highly recommended to use _Outbound as the target message definition when generating a HIPAA 837 message. Conversely, use _Prof as the source message definition when converting an incoming HIPAA 837 file.
What X12 versions does the HIPAA Package support?
The engine supports all X12 transactions across versions:
- 3040
- 4010, 4020, 4030
- 5010, 5020, 5030, 5040, 5050
The HIPAA-specific maps use 5010A1 NPI editions for all supported transaction sets.
Can the HIPAA Package be licensed as a standalone product?
The HIPAA Package is a bundled product that includes the AnyToAny Format Converter Engine, GUI Mapper, and HIPAA database together. The engine is the core runtime component required for all conversions.
Does the HIPAA Package support NPI (National Provider Identifier)?
Yes. All HIPAA maps use the 5010A1 NPI editions. This includes NPI-enabled maps for all supported transactions: 270, 271, 276, 277, 278, 820, 834, 835, 837 Professional, 837 Institutional, and 837 Dental.
Does the HIPAA Package include predefined maps?
Yes. The package includes predefined maps for all supported HIPAA transaction sets. When combined with the RMAP module, additional maps are available for converting between HIPAA X12 and Redix's simplified CSV (RMAP) format in both directions.
How does the HIPAA Package relate to the RMAP and Database modules?
The RMAP module provides simplified CSV formats that preserve all HIPAA-mandated data, with bidirectional maps (HIPAA to RMAP and RMAP to HIPAA) for all supported transactions.
The Database module enables loading RMAP or HIPAA data directly to/from SQL Server, Oracle, and other databases. Both are separately licensed add-ons to the AnyToAny Engine.
Still have questions? Contact us or try our AI Chat for instant answers.