| Management Systems Consulting, Inc. |
Excellence in Computing
Honesty ~ Integrity ~ Loyalty ~ Respect |
|
Glossary of Computer Terms (5C) ****************************
**************************** *********************** Visit IQ-Home for your housing design needs:
*********************** Updated:03/08/2008 Copyright © 1996-2008 Management Systems Consulting, Inc. |
HIPAA MMIS Enhancement ProjectEDI Translation Concept Overview HIPAA Repository Configuration ConfigurationThis schematic represents the suggested overall HIPAA EDI processing strategic approach for the State. While many approaches are ‘translator centric’, the above depicted approach limits the dependency on the translator product and emphasizes the translation process. The difference is more than semantic, it can dramatically reduce dependency on a limited resource availability product represented by the translator. Many/most EDI translator products on the market are configured with their own proprietary language and scripting features. While enabling sophisticated data manipulation, their proprietary nature and technical specificity limit the resource pool for maintaining the code sets after implementation. Utilizing these internal tools, increase dependency on a vendor product and technology that at this time is in a state of evolution. As technology approaches become more sophisticated in the area of electronic data interchange (EDI), utilizing new technologies like XML/EDI and ebXML, dependency on a single translator product may restrict or impede future flexibility to meet new State requirements. The approach represented here is directed to take control of the inbound data as soon as possible and maintain control of the outbound data (represented by EDI transactions) as long as possible. This increased span of control for the State and places the responsibility and control of the data within the State’s systems environment and coding standards. Furthermore, by utilizing existing data structures and coding standards currently deployed within the State’s infrastructure, the labor pool available to maintain the data and control structures is broadened. Reducing the dependency on ‘intelligence’ on behalf of a translator product and locating it within the existing infrastructure provides for more control and maintainability of the final HIPAA EDI translation solution. ProcessThe process represented reflects both inbound and outbound HIPAA compliant EDI formatted data. The EDI Data Translator is depicted as residing between two communications gateways. The first ‘Communications Exchange’ represents external data to/from the State’s EDI Server transported through a secured firewall tunneling protocol. The second ‘Communications Interface represents a secured communications network bridge from the EDI Server to the HIPAA Repository over the existing network bridge. The HIPAA Data Repository is defined as a set of data base tables governed by business rules for data handling, validation and extraction. Inbound data will be ‘mapped’ into these data base tables from inbound EDI data from the EDI Server and translator program. Outbound data (from MMIS) will be written to and mapped from this data repository. Business rules enforced by DB2 rules, SQL scripts and program code will provide the means to transport transactions into and out from the MMIS Systems. In addition, by utilizing the HIPAA Data Repository as the gateway into and out from the MMIS system, the functional data and operational structures will be in place to add future capabilities of input/output processing from web or Internet based applications. Instead of inbound/outbound EDI transactions, web based (possibly XML driven) transactions can be implemented into and out from the Data Repository. The common interface developed during the HIPAA EDI implementation phase will likewise be able to process the transactions from the data repository regardless of their origination source or destination. BenefitsThe following benefits may be realized from this approach: · Reduced dependency on an outside vendor. · Broadened use of existing open data structures and coding standards. · Limit use of specialized expertise in proprietary/closed language and scripting. · Faster time to deployment of the EDI translation process. · Simplification of the overall translation process. · Future flexibility by broadening the access points into and out from the MMIS system. · Open systems accessibility to the gateway enabling easier Internet or web based application integration in the future. View Slide Show Presentation |
Send mail to the Webmaster with questions or comments about this web site. |
