Over the span of my career, I have led or been involved in numerous system installations and conversions. It seems like each project involves an out of date or unsupported primary/legacy system that needs to be replaced, which means that a new and exciting system is waiting out there to improve the client’s productivity.
As Director of Product Integration at HCIM, it is one of my primary job functions to implement new product installations and conversions, but I also get to lead and consult on projects for existing and new clients on core system conversions. About five years ago I was a primary influence in the conversion of providers, contracts, claims, auths, and members for a large client that was converting from Amisys C/S to Facets. I was involved in the data conversion mapping for all major modules and directly mapped much of the data myself. This included both the field level mapping from and to the legacy and new systems as well as conditional field and lookup table designs. I was a key member of the team, deciding what fields could be carried directly from system to system and what needed to be mapped to new values, in addition to what couldn’t be converted due to system limitations, changed workflow, or configuration design and needed to be fully recreated from scratch.
I recently led two historical data conversion projects for clients converting to ikaSystems’ ikaClaims and other ikaEnterprise modules. My team and I worked together to design a proprietary platform that imports legacy data, maps or converts it to the new database import schema, and validates each data field against individual field types, relational lookup values, industry standards, and system requirements. This process produced a clean file in the ikaSystems’ standard format. ikaSystems’ platform is flexible enough to allow for customization to accommodate each individual client’s business rules and policies so the converted data is both technically accurate and operationally functional for historical reference.
For the ikaSystems conversion we were called upon to convert historical system data for the member, provider, authorization, claims, payment, benefit plans, and accumulators. The task demanded a thorough understanding of business processes, system functionality, and technical rules to successfully accomplish an undertaking of this magnitude. It also required a good team and LOTS of communication in all directions.
Contact me if your organization is due for a new claims system and is looking for help selecting a new core claims transaction system or needs assistance with the historical data conversion or data clean up (i.e. duplicate provider or vendor records). I look forward to hearing from you.
Greg Merica
Director of Product Integration
HealthCare Information Management, Inc.