Load X12 and HL7 directly into your database
Move data between HIPAA X12, HL7, XML, and relational databases as part of the conversion itself. Load inbound transactions into tables, and generate outbound X12 from database queries, with no intermediate files.
- ODBC connectivity
- Native Oracle and SQL Server APIs
- Two-way
- Stored procedures
Connect through ODBC or native APIs
Native API connections to Oracle and SQL Server avoid the generic ODBC layer; actual throughput depends on your schema, volumes, and hardware.
SQL inside the map, no custom code
- Define the database interfaceDescribe it in the output definition (OFD) using standard SQL syntax.
- Embed the statementsINSERT, UPDATE, DELETE, or SELECT; use views or stored procedures for complex logic.
- Run the mapThe engine handles connectivity and transaction management during the conversion.
Where teams use it
EDI to database
Load incoming HIPAA X12, HL7, or XML messages into relational tables for processing and analytics.
Database to EDI
Generate outbound transactions such as 837, 834, or 270 directly from database queries.
Analytics and reporting
Query EDI data in your own database for reporting, dashboards, and business intelligence.
RMap data store
Keep RMap-formatted HIPAA data in your database as the system of record, with pre-built maps for the HIPAA transaction types.
Point-and-click database mapping
With the HIPAA Package, the Database Module adds database mapping to the GUI Mapper.
Drag-and-drop mapping
Map between message trees and database tables visually.
Self-mapping
Build a new database schema and its matching map in one step.
Automatic OFD generation
Generate ready-to-run output definitions with the SQL statements included.
Ready for SQL Server and Oracle
With the RMap Module, the Database Module includes pre-built maps for SQL Server and Oracle, as starting points to configure and verify against your schema:
- 270/271 Eligibility
- 276/277 Claim status
- 278 request and response
- 820 Premium payment
- 834 Enrollment
- 835 Claim remittance
- 837P Professional
- 837I Institutional
- 837D Dental
Try the database tools on synthetic data
Use the hosted synthetic samples, with no local installation; demo access and registration rules apply. Request an evaluation key to test your own files. Do not upload PHI.
How the module is licensed
AnyToAny Engine
Required. The core engine: single-pass processing, IFD/OFD definitions, and the runtime.
Database Module
This module. ODBC and native API connectivity, embedded SQL in output definitions, stored procedures, and transaction management.
RMap Module
Recommended. Adds the pre-built HIPAA database maps and RMap as your data store.
The AnyToAny Engine is required for every conversion; each module is licensed separately.
Put your EDI where your reporting lives
Tell us your database, schema, and transactions. We show a working load or extract on a de-identified sample.