SUMMARY:

• Data Management professional with skills centralized in Healthcare augmented by Banking and Financial industry experience.
• Developed standards for naming and entity definitions.
• Created data element abbreviation standards.
• Designed data models for OLTP and OLAP environments.
• Generated STTMs and technical specifications documents for developers.
• Evaluated tools; communicated technical information to non - technical users.
• Led JAD sessions and participated in others to elicit business requirements from users.
• Collaborated with vendors to resolve software issues.
• Gathered and centralized meta-data sources for end-user.
• Excellent communication skills.

TECHNICAL SKILLS:

• DB2
• Oracle
• SQL Server 2000/2005
• SQL Developer
• ER Studio
• ERwin
• PowerDesigner
• MS Office
• LDM
• Dimensional Modeling
• SharePoint
• DB EXCEL
• Overview level understanding of Hadoop and NoSQL

PROFESSIONAL EXPERIENCE:

Confidential

Data Analyst

Environment: Agile; Oracle 11g; SQL Developer, Aginity Workbench for Confidential ; PDM; STTM; Informatica; MS Office

Responsibilities:

• Working mainly remotely created STTMs for Lab Results subject area. Approach was target-driven and involved:
• Meeting with SMEs to understand business process
• Understanding the data model
• Determining natural Ids and gaps between target and sources
• Becoming proficient in Aginity Workbench for Confidential so its use would not be a critical success factor
• Profiling source data using built-in Confidential functionality and scripts generated as needed
• Creating multiple STTM documents, conducting business and technical reviews and lobbying stakeholders for sign-off.

Confidential

Data Modeler/Architect

Environment: Oracle 11g; SQL Developer, PL/SQL; Teradata; Master Data Management; PDM; ER Studio; Informatica; MS Office; SharePoint

Responsibilities:

• Compared ER Studio structures with those in production and updated ER Studio by reverse engineering missing models into it.
• Reviewed business requirements designing tables and generating DDL to: land data from external source.
• Collaborated with SDLC SMEs on supplementing SDLC with a Data Modeling SDLC, including deliverables, to standardize modeling process. Also analyzed current on-boarding process for new data modelers and data architects streamlining the process for them to be functional sooner.

Confidential, NJ

Sr. Data Architect

Environment: Oracle 11g; SQL Developer, PL/SQL; PDM; STTM; ER Studio; MS Office; SharePoint

Responsibilities:

• Generated PL SQL scripts to gather data from operational system in support of workarounds to meet updated business requirements.

Confidential

Data Modeler/Architect

Environment: Agile; DB2; DB Visualizer; Oracle 11g; SQL Developer; PL/SQL; Teradata; Master Data Management; LDM; PDM; STTM; Dimensional Modeling; ER Studio; Informatica; MS Office; SharePoint

Responsibilities:

• Developed data model to support functionality for PCMH pilots using Agile methodology. Worked with business analyst to confirm requirements then produced data model; meet with developers, analysts and developers to review model and ensure it supported requirements.
• Provided data modeling support for bringing data from two related Health Care Reform projects into EDW. First was Enrollment and second Claims Submission.
• Architected different solution for importing 3rd Party Rx Claims into EDW. Utilized a single CRF table capable of housing accounts with different layouts from same Pharmacy Benefit Manager, (PBM). List partitioning supported the different accounts. Solution included landing the data, mapping to Common Record Format (CRF), and moving into existing unified schema. Architecture and accompanying processes resulted in significant savings in cost and time to activate a new account.
• Developed project data models to support several areas of business functionality. Worked with architects to carve out sub models from CRF and with business analysts to map data and create models for PBM projects.
• Brainstormed on guidelines, policies and procedures for streamlining the work of data modelers within EDW team. Including were recommendations for artifact definitions; when and how to move models to SharePoint and work flow changes to ensure early involvement of modelers in SDLC.
• Mentored junior team members including providing assignments, reviewing DDL and monitoring reviews with developers.

Confidential

Data Architect

Environment: included: DB2; SQL Developer; SQL; ERwin; LDM; PDM; STTM; MS Office; SharePoint

Responsibilities:

• Performed gap analysis for Eligibility area of Benefits system and mapped data requirements using as source data brought into environment in earlier project. Created data model to support the requirements and generated DDL using ERwin. Profiled source data to identify LOVs; worked with SME from source system to identify data gaps; met extensively with technical and business experts to close gaps, escalating issues as appropriate; resolved how to uniquely identify records for ETL team.
• Analyzed Eligibility source data including COBOL structures and created data models then DDL using ERwin. Produced STTMs for developers. System was successfully implemented.
• Collaborated with stakeholders to create requirements document for state-mandated changes to existing functionality on how OON providers should be paid. Provided feedback. Identified data needs then conducted gap analysis to determine need for new structures. Created summary data matrix for use by various areas impacted by planned changes. Using cost benefit analysis, management decided on manual solution.

Confidential

Data Architect

Environment: included: Oracle; SQL Developer, PL/SQL; PDM; ER Studio; MS Office; SharePoint

Responsibilities:

• Reverse engineered vendor’s OLTP system scheduled for implementation to create a model for analyzing the source system to identify data needed to support current and future reporting requirements.
• Provided definitions to over 200 tables in the model created with the aid of multiple meta data sources.

Confidential, CA

Sr. Data Architect

Environment: included: SQL Server 2000/2005; T-SQL; ERwin; ER Studio; Informatica; LDM; PDM; STTM; Dimensional Modeling; SharePoint; MS Office

Responsibilities:

• As part of successful implementation of data mart for e-ICU: reverse engineered vendor’s clinical application analyzed model’s complexity advising management on availability of data and its ease of use in answering patient-care questions de-normalized vendor data-mart to create one flat file with over 200 columns, many simple repeating groups utilized the structure to provide source-to-target mapping document for ETL developer developed test plan and an appropriate reconciliation process with vendor since vendor’s architecture did not support multiple installations of the software feeding into data mart and therefore vendor’s built-in reconciliation was inadequate conducted end-user training using Access, the end-users’ reporting tool.
• Introduced T-SQL scripts to do field by field content comparisons during migration from SQL Server 2000 to SQL Server 2005. This widened thoroughness of data validation. Use of such scripts became the standard for such testing.
• Assisted in designing test cases to validate data in Audit and Stage during re-architecture of data warehouse from Kimball to Inmon methodology; was responsible for creating the technical specs and mapping between 3NF tables in Base and the Data Mart Fact and Dimension target tables.

Confidential

Data Architect

Environment: DB2; DB2 Command Center; SQL; ERwin; Informatica; Dimensional Modeling; STTM; Data Vault, PowerDesigner; MS Office; SharePoint

Responsibilities:

• Designed Capitation Subject Area using then new Data Vault architecture and Star Schema Dimensional Modeling. Tasks involved collaborating with business analyst to identify source systems and data needed; developing dimensional model and mapping it and data to EDM; generating DDL including indexes and constraints for table creations; creating project documentation. Used PowerDesigner and DB2 Command Center for data profiling.