HIPAA transaction processing, built for the cloud.
transSend Core is AXIOM's cloud-native transaction platform, running on AWS. Files begin processing the moment they arrive, every file and every transaction inside it is tracked through to completion, and each client runs in a fully isolated environment of their own.
Every transaction has a known state.
A trading partner delivers a file and processing begins immediately. The platform unpacks the envelope, issues acknowledgements, splits the file into individual transactions, validates each one, and exports what passes, recording where every item stands at each step.
Because state is tracked per transaction rather than per batch, a handful of failures don't hold up everything behind them. The rest of the file continues, and the exceptions are identified individually for your team to work.
Your data lives in your own account.
Each client's production environment is a separate AWS account with its own database, storage and processing, separated at the infrastructure level rather than by application logic, so isolation doesn't depend on getting a permission check right.
Separate accounts per client
Every client runs in a dedicated AWS account with its own database, message broker, storage and processing. There is no shared state between clients.
Encrypted throughout
Data is encrypted at rest across databases, volumes and file storage, and in transit using TLS for connections, HTTPS for the web interface and encrypted SFTP for file delivery.
Audit trail by design
The processing record for every file and transaction, with timestamps and error detail, is a product of how the platform works rather than a report bolted on afterwards.
Scoped access
Each service holds only the permissions it needs, credentials are held in a managed secret store rather than in code or configuration, and access to the interface is role-based.
Capacity follows the work.
Open enrollment and month-end are not the same workload as a quiet Tuesday, and the platform sizes itself accordingly.
Near-infinitely scalable
Capacity is added across the processing pipeline as volume grows. Nothing to size in advance, no upgrade cycle to plan around, and no practical ceiling to design for.
Responds to actual demand
Capacity is driven by the work waiting to be done. A large file arriving triggers scale-out where the work actually is, and a quiet system consumes very little.
Room to add transactions
transSend Core processes 834, 837 and 275 today. The architecture is built so that additional transaction types, rules and integrations extend the platform rather than rework it.
See it while it's happening.
Insights is the browser-based interface to the platform. Watch batches progress, drill into an individual claim or member, and see the validation detail behind an exception with the context needed to act on it.
Tell us your volumes and we'll tell you what fits.
transSend Core is rolling out and we're deliberate about which environments it suits today. A short conversation will establish whether transSend Core, TransSend Classic, or a combination is the right answer for your plan.
Talk to our team →Let's talk about your HIPAA transactions.
Thirty years in healthcare EDI, on both sides of the claim. Tell us what you're running and we'll tell you honestly whether we fit.
Software for healthcare payers and the providers who bill them, since 1996. Simplifying HIPAA eCommerce.
Frederick, MD 21701
(301) 815-5220