Attendees

Agenda

1. Introductions/Roll Call
2. Action Items Review from last meeting.
   1. Bob will fold in the header from Ben's document into his page from a format perspective.
   2. Add affiliate requirement to the enrollment / registration section - Steven.
   3. Review and make notes in the document with regard to changes / additions / questions - All
   4. Need a "general bag of requirements" (notifications, reporting etc.). Change notifications to General Enterprise Requirements - (I think Renee did this) - Steven will add some stuff here.
   5. Consolidate requirements in one page by next Friday then start reviewing gaps. - All

Follow-up from previous action items on adding requirements to deliverables page

• Missing some sections - lifecycle and IEP requirements - Bob and Renee
• Benn's registration section - needs to roll into the main page
• Missing assurance requirements - Bob and Renee
• Still need to add affiliate requirements to the enrollment/registration section
  • Steve - have some notes but need to type them in
• Aaron - i made a few notes in the registry

1. Need to add information into requirements for registry regarding HR data, at least the core set
2. Should add some simple definition of terms at the top of the document, especially for terms that might be ambiguous
3. Need to add "calendar-driven" lifeycycle to the requirements list
4. Add mention in requirements of non-person entities and that there needs to be a flat namespace across person and non-person entities
5. Add a requirement to be able to store "test" users in the registry
   • needs to be some way to distinguish them from the rest of the population
   • need to not be considered in the reconciliation process
6. Add explicit requirements about the ability to create entries in the registry for these people who "self-register" (i.e. via federated or other processes)
7. Do we need to add any mention to the document about tools that might be needed as part of the whole package? workflow and rules engines?