Basic process
Problems with Current System
- Largely mainframe-based (PPS, UCSF Individual Identifier System (IID), and Campus Locator System (CLS)
- IID runs mainframe-based Identity Match code and Person Database
- Service oriented integration with downstream applications is difficult (would not be worth investment in service interfaces to PPS or IID given that systems are going away)
- User confusion around updating profile data: Multiple units on campus allow individuals to update their basic profile data (address, phone, etc) creating confusion about where to go; Profile updates for non Med-Center staff require manual processing by departmental delegated admin; (Please note: A campus-wide Steering Committee just endorsed a new plan that calls for a campus-wide "identity portal" where main updates to person data can take place and get pushed in realtime to other apps that wish to integrate)
Rough Diagram of Current Design
Thoughts on Future Design
- Need to replace all mainframe-based services
- Would like a rational approach to self-service profile data updates
- Would like to design a campus-wide person data model and repository with standard interfaces that can be used to provision user data to campus and cloud-based apps and for a variety of realtime queries (LDAP, WS, message-based, etc)