Convert, organize, and prepare claims for printing, on your own machines
One operator interface for the work that follows conversion. The Workbench batch-converts 837 claim files, keeps every claim with its original EDI in a searchable archive, and prints CMS-1500 claims onto preprinted forms or blank paper. Where the 835 map is installed, remittances become readable remittance reports too.
- 837P → CMS-1500
- 835 remittance reports
- Windows application
- Original EDI retained
- Local archive
More than an online converter. A local workflow for the work after conversion, built on the Redix engine that US healthcare organizations have run in production for more than a decade. Production claim data does not need to leave machines you control.
Finding the right claim years later
An auditor asks for the images of specific claims and their remittances. The claims were adjudicated years ago. The 837 and 835 files still exist somewhere, on a share or in a backup, but which file holds the claim, which remittance goes with it, who has used the archive since, and can you show which file today's image was produced from?
A PDF converter answers only the smallest part of that: it makes a file readable. It does not tell you where the claim is, show what it came from, record who looked, or hand the auditor a package whose files they can check. The Workbench adds retrieval, provenance, an access record, and an evidence package, locally. Provenance shows which source file a PDF was made from; it does not prove that a newly generated PDF matches a paper claim submitted years ago.
From one file to a local workflow
The online converter shows what the engine produces from a single 837 or 835 file; it is a demonstration for sample or de-identified files, not for production PHI. The Workbench is for the work that follows, run by your own staff.
- Select and convertChoose claim files or a whole folder and convert them in one run.
- Review resultsSearch the archive; open each claim with its PDF, its original EDI, and where it came from.
- Resolve reported issuesA claim the Workbench cannot print as it stands is listed with the reason, so it can be fixed before printing.
- ArchiveEvery run is kept locally with its original EDI; export audit-support packages when needed.
- PrintCMS-1500 claims, through the Workbench print queue, onto preprinted forms or blank paper.
Everything between the 837 file and the printed or archived claim
| Function | What it does |
|---|---|
| Batch conversion | 837P to CMS-1500, whole folders at a time. Where the 835 map is installed, 835 to a remittance-report PDF for review and archiving (not a claim form, and not printed as a claim). |
| Archive search | Find a claim by claim number, member, payer, provider/NPI, transaction type, status, filename, or service or payment date. |
| Original EDI retention | The source 837/835 is kept and linked to every generated PDF, with provenance per claim (source file, ISA13/GS06, SHA-256 fingerprint). |
| Hash-chained access log | Conversions, record views, file opens and downloads, exports, printing, settings changes, and sign-ins made through the Workbench are recorded in a hash-chained log. Its integrity check can reveal a past entry that was altered, reordered, or removed from within the chain; it cannot by itself show that no entries were removed from the end of the log, so keep the log in your backups. |
| Audit evidence package | One-step export of the PDFs, the original EDI, and a manifest of content hashes with a cover sheet, so the recipient can check that the files are the ones listed. |
| Method 2: claim-data-only PDF | The claim information without the form artwork, positioned for printing onto preprinted CMS-1500 forms. Still a PDF, archived like any other output. |
| Method 1: full-form PDF | Form artwork and claim information together: for review, sharing, and archiving, and printable on blank paper. |
| Printer calibration | A saved whole-page adjustment per printer, its settings, method, and form. It moves everything on the page together. |
| Check before printing | For supported layouts, checks claim-data placement before printing and holds a job when a required check detects overflow or cannot complete. A held job states the reason and, where available, the box and the source of its value; nothing is shrunk or abbreviated automatically. |
| Roles and access | Local accounts with role-based access controls, including least-privilege retrieval access. |
Each run writes a per-run record that the Workbench does not rewrite; a rebuildable index over those records powers search. The record is the source of truth; the index can be dropped and rebuilt from it.
Two output methods, checked before they print
Both methods produce a PDF for each CMS-1500 claim, archived with the original EDI, and both print through the Workbench print queue.
Method 2: claim-data-only PDF
The claim information without the form artwork, for printing onto preprinted forms loaded in your printer.
Method 1: full-form PDF
Form artwork and claim information together, for review, sharing, and archiving, and printable on blank paper.
Checked before it prints
For supported layouts, placement is checked and a job is held when a required check detects overflow or cannot complete, with the reason and, where available, the box and the source of its value.
Whole-page calibration
A measured shift of the entire page for one printer in one configuration. Saved per printer, settings, method, and form, and not applied if the printer's settings change.
Individual field positioning
Field Configuration changes where one field prints, as a new, previewed layout version that is put into use separately and can be rolled back.
Printing outside the Workbench
A downloaded PDF printed from another program keeps Field Configuration changes, because they are part of the PDF, but not the printer calibration or the checks before printing.
Set up with Redix. We set up printing with you: your printers, your forms, and the requirements of the payers you send paper claims to. Printer alignment and payer-specific requirements must be verified during setup for your printers and intended payer workflow.
Claims and remittances are PHI, so the archive lives where the data already is
On-premises
Runs on a desktop or an internal server. There is no Redix-hosted service in the data path; in the current design, claim data is processed locally and is not transmitted to Redix or third parties.
No production PHI in the demo
Real claim archives are processed on machines you control. The public online converter is a separate demonstration tool for sample or de-identified files.
Customer-managed controls
Storage encryption, TLS on the server lane, and backup remain yours to manage. The Workbench provides the archive, access control, and the access log; a Security & Deployment Brief is available on request.
Built for claims operators. The Workbench converts, finds, prints, and packages claim documents for audit. It renders 837 and 835 files to PDF; it does not submit claims to payers or replace your billing system.
An add-on to the Redix V9 engine
Desktop lane
A Windows application for a single workstation, with a guided Setup. For pilots and individual operators; it serves only the local machine.
Internal server lane
The same application as an internal service for multiple named users behind your own TLS reverse proxy: one shared archive, central backup, central access log. It can suit production and multi-year retention, depending on the agreed deployment and a validated workload.
Engine and license, separate
The Redix V9 engine and its license are installed first, and the license enables the PDF module. Map packages are supplied separately and determine which forms, transactions, and output methods are available.
See it on your own claims
The Workbench is available to Redix Claims-to-PDF customers: a Redix V9 engine with the PDF Module and your claim or remittance maps. Ask for a demonstration with your own sample files and forms.