Re: Mark's note below, I would suggest that in some cases User Acceptance Testing will include beta/trading partner testing.
Scenario: 1) A hospital that uses third party software to submit its claims to a clearinghouse 2) The third party software gets a feed from a recently updated HIS (updated to capture new data per the 837 requirement) 3) The clearninghouse that takes the third party software files (often determined by the third party software vendor) puts the billing software data feed into 837 format and submits claims to health plans "in bulk" Wouldn't the billing software vendor's hospital client want to include testing with its largest specific trading partners as part of its User Acceptance Test for the billing software? If not, how will the hospital know that its not-so-generic situations have been properly accounted for by the billing software vendor, and the HIS/billing software vendor interface? Re: MEDICARE-related User Acceptance Testing, I'd be surprised if the definition of what that's supposed to be wasn't documented within CMS, uh, documentation (:^>). My two cents... Cynthia Korman, Principal Strategic System Solutions, LLC 973 394-9529 [EMAIL PROTECTED] www.healthcare-systems.com ----- Original Message ----- From: "Mark A Lott" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, February 18, 2002 11:33 AM Subject: Transmittal : AB-02-020 - Change Request - 2039 > Greetings, > > User acceptance testing is widely known as "requirements based" testing from > an end-user perspective. This phase occurs after system testing and before > beta or trading partner testing. It is used to verify that all business > requirements are functioning correctly in accordance with design, this would > include executing the entire internal system and relevant interfaces to > ensure that the new EDI transactions and code sets are compliant with the > implementation guides and that a regression test is also successful > (regression meaning that any previous functionality was not inadvertently > impacted by HIPAA system changes). > > In terms of the 837, you should ensure your system can accept 837 test files > and process them programmatically through your remediated system. By doing > this step you will ensure that your beta testing phase will flow more > smoothly. Hope this helps... > > Mark A Lott > CIO > HIPAA Testing, Inc. > 480-946-7200 > > "Automating HIPAA Compliance" > > > > CONFIDENTIALITY NOTICE: This e-mail message, including any > attachments, is for the sole use of the intended recipient's) and may > contain confidential and/or privileged information. Any unauthorized > review, use, disclosure or distribution is prohibited. If you are not the > intended recipient, please contact the sender by reply e-mail and > destroy all copies of the original message. > > > > ********************************************************************** > To be removed from this list, send a message to: [EMAIL PROTECTED] > Please note that it may take up to 72 hours to process your request. > ********************************************************************** To be removed from this list, send a message to: [EMAIL PROTECTED] Please note that it may take up to 72 hours to process your request.
