You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Organizations  as Subjects

Elizabeth Salley, University of Michigan

Note: needs more editing as of July 6, 2009

Sponsor system

Managing affiliates

Homegrown system

Recently roled it out to our campus

Units around campus define person who is an authority

That authority can delegeate to one or more person in their area to renew and extent a person in their area.

Designed a Human user interface.

They are an individual person.

Must be a current regular U-M employee to be an admin. Must have completed our admin access and cojpliance training and must attest to be a good steward of the system. The med center has their own very robust IdM system. Needed to get data and not tie it to person in health system.

Didn't want problem if person who wrote the code left the university.
When moved from human home grown into web services, needed to think thru requirements again.

Think thru when to move to non human interfaces.

Q: So a trust relationship had to be established with the Medical Center to do this. Did you have to build a policy infrastructure?

A: Yes, our deveopers of this web service designed a very complicated way of enforcing this trust relationship
We said we will only have 3 of these.  So short term solution was just a singed agreement
Between the 2 organizations.

Tried to keep it simple. Will have more of these and will try to do a better way ofencoding this into system for future partnership

Q: TomB:  So ? acts as med centerin this application
A: coder is u-M employee.  Didn't want it to look as if Joe was taking this action.

It was Medical Center who removed this sponsorship.

Q: So med center is responsible for auditing changes?

A: We track that medical center made this change. We assume that med center captures more details to the level required for them.

Q: What kind of workflows are used and how are they customized?
A: It's a new system and in terms of workflows...  when ? about to expire then a notification goes out and ? have 2 weeks to decide.  We are not that sophisticated but we would like to be.  Should be easy to manage the data.

  • No labels