Datawarehouse architect

Hello, Hope you are doing good. Position: Data Architect (Data Warehousing) Location: Remote Duration: Long Term Client: State of Vermont Job Description: SCOPE OF WORK PURPOSE BACKGROUND The Vermont Department of Health (VDH) is seeking a Data Architect to perform analysis and produce recommendations to inform the vision for development of a data warehouse that combines data from across multiple VDH programs. The scope of this work is limited to design and planning. The primary products to be produced via this effort include a VDH Data Warehouse Strategy Report, technical architecture, data model, data flow, and data architecture models as outlined in the deliverables section of this document. These products will inform a future project to build and implement a warehouse. EXISTING TECHNOLOGY ENVIRONMENT The Vermont Department of Health currently maintains multiple independent data systems. While many of these are integrated to facilitate data sharing and reporting the Department does not currently have a central data warehouse. The systems include very large databases such as the Shared Public Health Information Exchange (SPHINX) which houses State vital records (births and deaths) along with the State's immunization registry, vaccine inventory and multiple childhood health screening registries; and systems that support the State's public health laboratory. In addition, there are multiple smaller systems both internally developed and vendor hosted which contain data anticipated to be included in the VDH Data Warehouse. The VDH is a Department within the State's Agency of Human Services (AHS). The AHS has defined a vision for a Unified Data Health Space (UDHS) that includes data from VDH and the other Departments within the Agency. A critical element of this is the Medicaid Data Warehouse and Analytics Solution (MDWAS). This context must be considered in determining the model and architecture for the VDH Warehouse. The VDH warehouse is independent, but consideration should be given in design to potential future integration with MDWAS . The State of Vermont Agency of Digital Services (ADS) defines standards for data modeling, architectural vision, roadmap and standards for governing, modeling storing and delivering data within the enterprise. Parallel to the work to be performed under this contract ADS is engaged in efforts to update and define these standards. The work under this contract must include engagement with those developing these standards to assure alignment of deliverables to the current standard. The technology platforms that support VDH systems are primarily arenaflex. The data in State of Vermont developed systems is primarily hosted in SQL databases on or planned to migrate to Azure virtual machines. The current enterprise tool for integration is Mulesoft. It is anticipated Verato will be used for establishing a Master Person Index. Data in vendor hosted SaaS solutions, may be supported by different technology. Core data systems include Electronic Birth Registration System (EBRS) Electronic Death Registration System (EDRS) Vermont Immunization Registry (IMR) Universal Developmental Screening Registry (UDS) Vermont Early Hearing Detection & Intervention Program (VTEHDI) Healthy Homes and Lead Poisoning Surveillance System (HHLPSS) National Electronic Disease Surveillance System (NEDSS) Base System (NBS) Vermont Cancer Registry (VCR) Statewide Incident Reporting Network (SIREN) Vermont Advance Directives Registry (VADR) Enhanced HIV/AIDS Reporting System (eHARS) Vermont Prescription Monitoring System (VPMS) StarLIMS WIC Management Information System (Ceres) Vermont Newborn Screening Program REQUIREMENTS: For this particular request, knowledge requirements include: Proficiency in data modeling and design Expert knowledgeable of data quality and governance processes, such as data profiling, data cleansing, data validation, data lineage, data security, data privacy, and data compliance Expertise in the principles and components of master data management including master person index. Knowledge of the Verato master data management platform preferred Experience in SQL development and database administration Proficiency in Visio (for creation of all models) Knowledge of use of MuleSoft for integration. Experience working with legal context governing sharing of public health data including HIPAA, 42 CRF Part 2 is preferred. Experience in Data warehouse design and ETL including expert knowledge of appropriate tools, technologies and strategies employed in data warehouse development, such as ETL (extract, transform, load) tools, databases, data marts, data lakes, data warehouses as a service, and business intelligence tools. ADDITIONAL ATTACHMENTS/ASSURANCES For this particular request, the current versions of AHS Attachments E (BAA) and F (AHS Customary Terms) as attached to this SOW-RFP, shall be incorporated into the resulting SOW Agreement. For this particular request, the following additional assurances required by federal or state law, shall be incorporated into the resulting SOW Agreement: Attachment G: STATE OF a VERMONT- FEDERAL TERMS SUPPLEMENT The Data Architect will use tools provided by the State of Vermont. These tools are: a state-issued desktop, laptop computer or virtual desktop, arenaflex Office applications, arenaflex Visio, Azure DevOps, office space in either the State Office Complex, Waterbury or The Enterprise Architecture Office, Montpelier. PROJECT DELIVERABLES DELIVERABLE REQUIREMENTS: Workplan This plan must outline high level tasks for completing the analysis and drafting of the report and other documentation to be delivered under this agreement. This must include a timeline with start/end dates and dependencies. This plan will be updated weekly to reflect progress and SOV approval of significant changes in scope of work. Weekly Work Status Reports These reports must include: The status of the progress on all items outlined in the work plan. A risks/issues log highlighting any barriers to progress and recommended strategies to mitigate or address these items. In addition, to inclusion in this report, it is expected that any issues that are active blockers to work are also raised via direct communication (e-mail, or meeting) as soon as they are identified. Proposal of any new tasks or scope of analysis not included in the Workplan that would be of high value to production of the deliverables. This includes requests for approval of significant updates to the workplan as well as requests for information about data or the VDH context that may not have been identified as relevant in the initial plan. The contractor must be available to meet to weekly to review reports and upon request of the SOV. VDH Data Warehouse Strategy Report. An outline and draft report must be delivered to VDH and ADS for approval prior to submission of final. This deliverable must include at a minimum. Accurate inventory of specific data elements identified for sharing including Definition of data element key business rules, specifications and governance applicable to these data elements. Indication of data that must be redacted or obfuscated when presented or never included in the warehouse. Governance and procedures to ensure and monitor ongoing data quality Data architecture framework including security and master data management. Data model for the warehouse. This must include a visual representation using Visio showing necessary relationships which allows analysts and developers to see connections between data Model for flow of all data in and out of warehouse. This must be a visual representation using Visio. Data mapping of all data sources to the data warehouse. Recommended transformations or mapping of data to standard values for data common across multiple systems. Anticipated stakeholders who will access the data warehouse. Recommended methods of access for all stakeholders Technical architecture including identification of anticipated programming interfaces (APIs). Recommendations for building the data warehouse including specific technology and design. Recommended roadmap of action steps to implement the warehouse including recommended order and estimates of time for completion based upon experience in similar settings. Analysis of the proposed solution comparative to established Public Health Data warehouses in University of Massachusetts, Michigan, Ohio and Washington State. This includes outlining the pros and cons of the implemented design. Original Data Inventory and Mapping Documents - all data inventory mapping documents must be delivered in the original Excel or other approved template. Original Visio documents of all diagrams and models included in Summary report. At a minimum this includes: Data architecture framework Warehouse Data Model (relational data model) Data Flow Diagram Technical Architecture Thanks Manikanta.yerra@my3tech.com Apply tot his job

Back to blog
Ads

Common Interview Questions And Answers

1. HOW DO YOU PLAN YOUR DAY?

This is what this question poses: When do you focus and start working seriously? What are the hours you work optimally? Are you a night owl? A morning bird? Remote teams can be made up of people working on different shifts and around the world, so you won't necessarily be stuck in the 9-5 schedule if it's not for you...

2. HOW DO YOU USE THE DIFFERENT COMMUNICATION TOOLS IN DIFFERENT SITUATIONS?

When you're working on a remote team, there's no way to chat in the hallway between meetings or catch up on the latest project during an office carpool. Therefore, virtual communication will be absolutely essential to get your work done...

3. WHAT IS "WORKING REMOTE" REALLY FOR YOU?

Many people want to work remotely because of the flexibility it allows. You can work anywhere and at any time of the day...

4. WHAT DO YOU NEED IN YOUR PHYSICAL WORKSPACE TO SUCCEED IN YOUR WORK?

With this question, companies are looking to see what equipment they may need to provide you with and to verify how aware you are of what remote working could mean for you physically and logistically...

5. HOW DO YOU PROCESS INFORMATION?

Several years ago, I was working in a team to plan a big event. My supervisor made us all work as a team before the big day. One of our activities has been to find out how each of us processes information...

6. HOW DO YOU MANAGE THE CALENDAR AND THE PROGRAM? WHICH APPLICATIONS / SYSTEM DO YOU USE?

Or you may receive even more specific questions, such as: What's on your calendar? Do you plan blocks of time to do certain types of work? Do you have an open calendar that everyone can see?...

7. HOW DO YOU ORGANIZE FILES, LINKS, AND TABS ON YOUR COMPUTER?

Just like your schedule, how you track files and other information is very important. After all, everything is digital!...

8. HOW TO PRIORITIZE WORK?

The day I watched Marie Forleo's film separating the important from the urgent, my life changed. Not all remote jobs start fast, but most of them are...

9. HOW DO YOU PREPARE FOR A MEETING AND PREPARE A MEETING? WHAT DO YOU SEE HAPPENING DURING THE MEETING?

Just as communication is essential when working remotely, so is organization. Because you won't have those opportunities in the elevator or a casual conversation in the lunchroom, you should take advantage of the little time you have in a video or phone conference...

10. HOW DO YOU USE TECHNOLOGY ON A DAILY BASIS, IN YOUR WORK AND FOR YOUR PLEASURE?

This is a great question because it shows your comfort level with technology, which is very important for a remote worker because you will be working with technology over time...