EDW & EWS Data Changes Coming to Support Northwest Hospital (NWH) and UW Physicians (UWP)

October 28, 2019

This is a heads up on upcoming changes to both the Enterprise Data Warehouse (EDW) and Enterprise Web Services (EWS).

 

As you may be aware, UW Medicine is currently in the process of consolidating activities across two of its major entities: 

  1. Northwest Hospital (NWH) will become a second campus of the University of Washington Medical Center (UWMC)
  2. UW Physicians (UWP) staff will become part of the UW Medicine Health System (UWMHS) supervisory org structure in Workday and part of the School of Medicine otherwise

A major component of this consolidation effort includes integration of ~2600 NWH and UWP employees into Workday and UW-IT systems. A dedicated project is in progress to support this transition. The project has successfully completed design, configuration, and 2 rounds of end-to-end testing. The final round of end-to-end testing is now in progress. The cutover and data migration activities are planned for the last two weeks of December 2019, with the final cutover planned for January 1, 2020.

We do not think the changes impact you.

However, we want to make sure you aware of what is happening. Over the last few months both EDW & EWS teams worked very hard to evaluate, adapt, and test the changes. The goal is to ensure a smooth transition for NWH and UWP units while minimizing impact on the rest of campus.

Existing fields are not changing as part of this work. There are no new data elements. So what are the changes?

New values will appear in existing fields. The new values will start showing up in mid-December with a final implementation date of January 1, 2020.

The new values fall into two categories: 1) data additions that could happen at any time, and 2) changes that are unique to this project.

1. Data additions that could happen any time

We’re communicating them here because they are being added as part of the NWH/UWP project:

  • Supervisory orgs
  • Cost centers
  • Locations
  • Job profiles
  • Job classifications (absence related)
  • Compensation grades
  • Bargaining units/unions
  • Job families, related to unions

2. Changes that are unique to this project

  • New employee sub type (worker type):
    • This new type of employee (worker) was added to support paying some NWH hourly employees the actual hours they work
    • This new type of employee (worker) is for positions known as “regular, hourly”
    • Currently, only relevant to a subset of the NWH population
    • “Regular, hourly” subtype will function the same as the subtype “regular”
    • The assumption can no longer be made that an hourly employee is temporary
    • Hourly employees can be temporary or regular, depending on their job profile
  • New pay component code (earning code):
    • Associated with the new employee subtype
    • The new value is RGH
    • RGH is typically treated like regular earnings, REG, except the pay type is hourly
    • RGH is treated as “REG Equivalent” 

 

How can you tell if you are impacted by #1 or #2’s new values?

  • Consider how you filter or query on these concepts. If a new value shows up, will that impact your results?
  • If you do any filtering or querying around “regular earnings”, based on what you are trying to accomplish, you may need to include “RGH” in the long list of codes that are treated like “REG”.

 

We will continue to update this page with new information related to the NWH/UWP Implementation Project based on your questions and as new information emerges.

If you have any questions about these changes, as always, we’re here to help you. So are our partners with the NWH/UWP Implementation Project. The best way to reach us is: