*Attendees*
Nadim El-Khoury, UNC
Kirke Lawton - AAMC
Keith Hazelton, U. Wisconsin
Renee Frost, Internet2
Mary Kratz, Internet2
Steve Olshansky, Internet2
Jeanette Fielden, Internet2

*Discussion*
Use of the AAMC identifier in conjunction with the U. Cincinnati pilot was discussed. Kirke indicated that AAMC is interested though there are concerns over what would be involved, how to support it, and timing to ensure that AAMC can effectively support their level of involvement.

From the pilot side the desire is simply for a user to be able to look up their AAMC identifier and then be able to copy and paste it into a U. Cincinnati pilot form. If they don't have an AAMC identifier they get a "Sorry you're not registered" message. AAMC would not need to generate a new identifier on the spot for a user. All that would be needed for the pilot is a web interface where someone could look up his/her identifier. No system-to-system communication is needed. There is willingness to simplify and clarify any requirements to aid AAMC in participating.

The interest in using AAMC identifiers stems from the fact it's unique and could help resolve potential name conflicts. While mistaken ids are not a big concern they do happen, and AAMC has an internal process to track when an identifier changes or multiple ids have been issued to the same person. They don't have front-end wrappers for the system. A note can be inserted in so if a user checks an id and it's changed they're aware of what's been done so unnecessary help calls to the AAMC will be minimized.

Nadim El-Khoury is the chair of the VidMid VC group and will be participating in the MedMid group. One of the next items the VC group is going to work on is how to do security for video conferencing, which includes data encryption and identity authentication. They want to ensure that what they work on to handle security and privacy incorporates the medical point of view and avoids duplicating/overlapping other efforts.

H.350 is a set of LDAP object classes and attributes that have been standardized through ITU-T. The attributes represent how to put the data into LDAP. This was developed because every vendor stores attributes in a proprietary way even though they all talk to LDAP. If you decide to change vendors you don't want to reenter all the data into the gatekeepers or proxies. The attributes described are for H.323, SIP, and H.320. There are also attributes described for H.235, which encompasses security for H.323 and the entire H. series type of applications. Links to H.350 can be found on the VidMid VC web page: http://middleware.internet2.edu/video/.

Mary asked if the electronic health record initiative was discussed at the Internet2 Fall Member Meeting. There was a brief update of current events at the meeting. The next meeting of the electronic health record group will be in January. They are interested in working with Internet2. Mary will forward information as it becomes available.