Onboard a payer, sponsor, or TPA from the file they already have. Map their columns once, teach the fields how to clean themselves, and turn a raw HR export into standards-clean X12 — no re-keying, no custom code per client.
What It Does
Every client sends a different layout with its own quirks. Instead of a one-off importer for each one, operators build a reusable configuration in a visual studio — and the same engine backs it in every HIPAAsuite master.
The workflow
Proof point
A Menonita Oracle-HR extract came in as a flat CSV: full names in one cell, coverage described in prose, blank genders, a marital code that didn't match X12. Mapped once with a handful of field rules, it produced a fully SNIP-validated 834 covering every member — no manual fixes.
The import studio lives in the shared platform layer, so every HIPAAsuite master inherits the same mapping, scripting, and validation — no per-product rebuild.
