How to Test a Transaction
Test a transaction, without filing a complaint!
The ASETT system allows testing transaction files for HIPAA compliance, with or without filing a complaint. Once you register as a user for the ASETT system, your password may be retained for future use.
Please see below information about the steps to follow for testing a transaction:
- Click the “Register” link on the ASETT Homepage to create a new user account. *All registration steps must be completed prior to accessing the Transaction Testing Tool*.
- After successfully registering, select the “Test HIPAA Transactions” button towards the bottom of the screen.
- Enroll in the Testing Tool by selecting the Onboarding, Testing, and Cloud Services (OTCS) link.
- Follow the system prompts.
- View or print the results.
Review our ASETT User Manual (PDF) for a step-by-step guide.
What file types are acceptable when testing transactions? When testing transactions, acceptable file types are: .dat, .txt, or .edi file formats.
Validate transactions across various formats including the following:
- ASC X12 5010
- NCPDP D.0
*OTCS will not validate diagnostic (ICD-10) or procedure codes (CPT or HCPCS), or validate TIN or EIN in a transaction, but will point out if a code is the wrong length or in the wrong position within the transaction segments.*
Learn more about ASETT with these resources:
How to Test Electronic Health Care Transactions for HIPAA Compliance (PDF)
Provides an overview and step-by-step instructions of how to test transactions in ASETT.
ASETT Demonstration Video (Video)
This demonstration video walks users through how to register for ASETT, how to use it to file complaints against HIPAA covered entities for noncompliance with Administrative Simplification standards for electronic health care transactions, and how to test their electronic health care transactions, as well as their trading partners' transactions for potential noncompliance.