webMethods is pleased to introduce the 6.0.2 version of the webMethods HIPAA Module. Version 6.0.2 of the Module is a special minor release that provides customer-driven enhancements to a subset of HIPAA transactions -- 820, 834, 835 and 837-Institutional.
For the 820, 834, 835 and 837-Institutional transactions, the transaction validation services have been modularized to give users more granular control over the types of HIPAA validation (Types 1-5) that they want to implement for a specific partner and transaction.
For the 820, 834, 835 and 837-Institutional transactions , the modularized validation services enable users to implement EDI Large File Handling (according to guidelines), thereby allowing users to process large, multi-megabyte EDI files.
For the 820, 834, 835 and 837-Institutional transactions , validation services for the included transactions support the Addendum to the WEDI HIPAA Implementation Guidelines released in February 2003.
For the 820, 834, 835 and 837-Institutional transactions , in addition to the standard included Validation Reports, validation errors now generate a robust set of error codes that can be used for more complex, customized Validation Reports.
Based on the new design, users should expect an improvement in performance for the HIPAA validation services for the 820, 834, 835 and 837-Institutional transactions.
Customers who want to deploy all HIPAA transactions together at this time should consider using Version 6.0.1. Version 6.0.1 and 6.0.2 employ different architectures and should not be implemented in the same instance of webMethods Integration Server.
Use Version 6.0.2 when:
Use Version 6.0.1 when:
For information about previous releases of webMethods HIPAA Module 6.0.1, see the release notes for those releases, below.
webMethods is pleased to
introduce the release of the webMethods HIPAA Module, version 6.0.1.
Built on top of the
webMethods Integration Platform and the webMethods EDI Module, the HIPAA Module
enables employers, payers, providers and clearinghouses to engage in processing
medical claims transactions according to the HIPAA standard. It also allows HIPAA implementations to easily make use of
the robust and comprehensive feature sets of the entire webMethods Integration
Platform, including business process modeling, human workflow elements, and
monitoring.
Full support for all 11 HIPAA transactions:
Using Trading Networks, users can manage and use unique identifiers for providers, plans, employers and individuals as theses identifiers become mandatory.
The webMethods HIPAA Module
fully supports HIPAA-defined success/failure notification of envelope errors via
TA-1 technical acknowledgments. 997 functional acknowledgments also
are supported to communicate syntax errors in HIPAA documents. In addition to
these, detailed error reports are generated and sent to your HIPAA Administrator
via e-mail.
Through our development partner, Softima, webMethods has successfully validated transactions 270, 271, 276, 277, 835, and all three versions of 837 (Institutional, Professional, Dental) through Claredi.
Claredi certification provides out-of-the-box support validation to Level 5, as defined by the WEDI-SNIP structured certification process. The webMethods HIPAA Module will be certified for every transaction supported by Claredi certification software.
Through the addition of
code sets and validation customization, the webMethods HIPAA Module also is
capable of Level 6 and 7 validation, as defined by WEDI-SNIP certification
guidelines.
webMethods Administrator, webMethods Broker, webMethods Developer, webMethods Installer, webMethods Integration Server, webMethods Mainframe, webMethods Manager, webMethods Modeler, webMethods Monitor, webMethods Trading Networks, webMethods Workflow and the webMethods logo are trademarks of webMethods, Inc. "webMethods" is a registered trademark of webMethods, Inc.
All other marks are the property of their respective owners.
Copyright (c) 2003 by webMethods, Inc. All rights reserved, including the right of reproduction in whole or in part in any form.