Feedback

Feedback

Did this article resolve your question/issue?

   

Article

How does XML Converters handle edits applied for a EDI 275 transaction?

Printable View

Information

 
TitleHow does XML Converters handle edits applied for a EDI 275 transaction?
URL NameHow-does-XML-Converters-handle-edits-applied-for-a-EDI-275-transaction
Article Number000123325
EnvironmentProduct: Connect for XML Converters
Version: All supported versions
OS: Java
Database: N/A
Application: All supported applications
Question/Problem Description
How does Connect for XML Converters handle edits applied for a EDI 275 transaction?
Steps to Reproduce
Clarifying Information
For example: For the provider address information, what kind of verification is done for the fields N402, N403, N404, N407 in the 110C loop of N4 segment?
Error Message
Defect Number
Enhancement Number
Cause
Resolution
With the standard supplies codelists, XML Converters will ensure the value is in the list, such as with ISO country codes. It does not do general address validation, because the converters do not know what a given business would consider valid addresses.
For example, a business might only accept subscribers with home addresses within their state or their region, while others might accept subscribers with international addresses. The driver validates against the conditions that are in the HIPAA standards documents, so that it guarantees the document is consistent with the specifications. The correct segments will be in the correct positions with the appropriate limits on cardinality and will contain values constrained by the standard. But we leave the business rules to the containing application.
 
Workaround
Notes
References to other documentation:
HIPPA Standards Documents, https://protect-us.mimecast.com/s/pZheCQWX4XfNXlJgcxc_oi?domain=store.x12.org
Last Modified Date3/4/2020 1:53 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.


Copyright © 2022 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.

Progress, Telerik, Ipswitch, Chef, Kemp, Flowmon and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.

Terms of Use Privacy Center Security Center Trademarks License Agreements Code of Conduct Careers Offices
Do Not Sell My Personal Information