The CSV side of HL7 and X12 healthcare files, validated and mapped.
The Healthcare HL7 Pack ships flat CSV layouts and mappings. Your HL7 interface engine or clearinghouse converts between the wire format and these files, and DataBridge validates, maps and moves the CSV.
Healthcare data moves as HL7 messages and X12 claims, and downstream systems usually want tidy tables. Someone has to check the codes and reshape the files between the two.
Modules. Any paid module opens the Marketplace. Add Transfer to move files.
Edition. DataBridge Server or Desktop for the file work.
How DataBridge does it.
Each step names the feature as it appears in the product.
- Step 1
Your engine
A tool such as an HL7 interface engine or a clearinghouse converts between pipe-delimited HL7 or X12 and CSV. That step is outside DataBridge.
- Step 2
File templates
HL7 v2.x layouts for ADT, ORM, ORU (one row per observation), DFT and SIU, and HIPAA X12 layouts for 837 Professional and Institutional, 835, 270, 271, 276 and 277.
- Step 3
Validate File
Coded columns such as patient gender, order control and result status carry allowed-value checks, so a bad code is flagged by row and column.
- Step 4
Field mappings
Mappings turn HL7 ADT into Patient Demographics, ORU into Lab Results, ORM into Orders, Healthcare Claims into an 837 claim export, and an 835 remittance into Claim Payments.
- Step 5
Transfer
Move the CSV files between systems over SFTP, a shared folder or cloud storage.
What this does not do.
- DataBridge does not read or write HL7 pipe-delimited messages or X12 envelopes, and it does not listen for HL7 over a network connection. You need your own interface engine or clearinghouse.
- These files contain protected health information. Keep them on storage covered by your own safeguards. DataBridge does not make a file compliant.
Marketplace packs used: Healthcare HL7 Pack. See the Marketplace.
Related pages.
Try the parts that are free today.
The free browser edition needs no sign-in and never uploads your files.