HIPAA-Repository
The HIPAA-Repository approach represents the suggested overall HIPAA EDI processing strategic approach for the organization. While many approaches are "translator centric", the this 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.
English
Supported Technologies
OS/400,
Palm,
Windows CE,
MVS(OS/390),
Windows XP/2000/NT ,
HP/UX,
Solaris/Sun OS
ASP Hosted
Click on a technology to view similar products within this category.
Pricing
Users (# of seats), Server, System, Module
75,000 to 750,000
HIPAA@msc-inc.net
407-856-1691
Additional Product Information
The HIPAA-Repository approach represents the suggested overall HIPAA EDI processing strategic approach for the organization. While many approaches are "translator centric", the this 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 process 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 Organization 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 organization and places the responsibility and control of the data within the organization's systems environment and coding standards. Furthermore, by utilizing existing data structures and coding standards currently deployed within the organization'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.