MedMid conference call February 9, 2006

*Attendees*
Jack Buchanan, U. Tennessee - Memphis (Chair)
Paul Jolly, AAMC
Brendan Bellina, USC
Mike McGill, Internet2
Steve Olshansky, Internet2
Jessica Bibbee, Internet2 (scribe)

New *Action Items*
[AI] {Brendan} will draft a description of the challenges of updating a central identifier across multiple organizations for the use cases.
[AI] {Group} should send comments to the list or directly to {SteveO}, regarding the use cases.

Carryover *Action Items*
[AI] {Keith} will email the list with draft documents regarding the federa authentication program.
[AI] Anyone interested in testing the feasibility of inter-institutional collaboration on courseware via Shibboleth please contact Dave Damassa <david.damassa@tufts.edu>.
[AI] {All} should direct comments to list, regarding the VistA program, especially related to identity and access management middleware. (cf. SteveO's email 22-July-05 for related links).
[AI] {Keith} will post a note to the MACE list inquiring about MedMid related activities in Europe.

*Discussion*

{SteveO} has posted the AAMC identifier use cases under the Draft Documents on the MedMid WG site <http://middleware.internet2.edu/medmid/#Docs>. [AI] {Group} should send comments to the list or directly to {SteveO}, regarding the use cases.

{Paul} described 2 classes of applications, where: 1) the input is a set of other identifiers, and the output is the AAMC identifier, and 2) verifying by identifiers other than the AAMC, perhaps a SSN, graduation day, etc.

{Brendan} raised a concern that should be addressed by the use cases – Often times, an identifier is assigned, rather than being specifically related to the individual. So when the identifiers need to be changed, it presents a challenge in being able to retrieve the information that was once based on that identifier. This implies that a med school must have additional identifiers by which to query, else they would have no means to retrieve the new ID. There is a need to have a mechanism that is capable of notifying dependent systems when an ID changes, and would allow a system to query the old ID in return for the new ID, at a minimum. While some of these capabilities exist, they are not available across the board to outside users. [AI] {Brendan} will draft a description of the challenges of updating a central identifier across multiple organizations for the use cases.

{Paul} gave feedback on CAMP Med <http://www.aamc.org/meetings/specmtgs/campmed06/start.htm>. Much of the audience found the information on potential or standard tools helpful, as well as use cases. {Jack and Paul} commented that there is sufficient interest for an annual CAMP Med, but not necessarily more often.

The next MedMid WG conference call will be on Thursday, March 9, at 2pm ET.