HIMSIG20080628

Liberty Alliance Project
SIG Health Identity Management
June 13, 2008
11:00-12:00 EST
Conference Call
Meeting Notes
Author: Kurt Kolok

Attendance:

Pete Palmer, Wells Fargo (Co-Chair)
Matt Madison, CORHIO
John Fraser, Mednet USA (Co-Chair)
Kumar ???, Sun
Bob Pinheiro, Individual Contributor
Tim Campbell, Sun
Rick Moore, eHealth Ohio
Steve ?,  ???

Brett McDowell, Liberty Staff
Eric Tiffany, Liberty Staff
Kurt Kolok, Liberty Staff

Agenda:

Sun Microsystems will discuss their open source offerings for healthcare. Rick Moore of eHealth Ohio will discuss the status of identity management and HITSP.

Kumar: Primary role: work with groups like this to drive the products they are working on.
Tim: Partner with Technology Enablement Solutions focusing on access management and federation.

Federation/access mgmt, Open Single Sign on—identical code base.

Review of presentation slides:

Row 15: Requires us to force the product (v7.0)—open source version is meant to build traction for building the internal version. V7.1 has been out for close to one year. Coming out with v8.0—a single product with the same code base. Sept. release date for fam8(???).

Row 16: Open SSO: You can get the open source version that does not come with support or you can purchase the commercially supported version.

Row 17: remerge into federation mgr 8.0. Added web services to this version. Metro is a web services stack (open source). Developers are different than SSO.

What are the web services standards that Metro supports? Metro is its own open source project, so we are not sure.

Row 18: renamed to ‘federated’ access manager to clarify the product. Federation was in the base product for Sun. The access management component would not be part of the foundation if you did not want to implement it. Virtual implementation, security token service, identity services are available as web services to increase interoperability. What you need to do to create a federation has been simplified.

Row 20: snapshots of the GUI
Row 21: comprehensive model config. Fedlit—you have configured the url, partner may not have. Can automatically build urls.

Daniel Raskin—blog.sun.com/raskin—by searching for ‘Fedlit’ you will find a video demonstrating this in action.

Row 23: serve as federation hub. Provide identity services as web services by SOAP or restful interfaces.

Implemented JSR196—an agent that snaps into WSP. They can have enforced stronger levels of security.

ACTION: Tim will answer the following questions via the mail list: What standards and which APIs? Which restful interface are you using? Which version of ID-WSF are being used?

Rows 25/26: mostly summary/review.
Row 27: new containers we’re certifying.
Row 28: time line: shift all items right one column.
Row 30: upgrade and compatibility to earlier versions.

Action: John will email Tim questions for the group.

Identity Assurance Framework (IAF) presentation (Rick Moore):

There were technical committee meetings for HITSP at the HIMMS National Tech week.
Slide 1: The hope is to harmonize standards in the industry and bring meaning to the madness. Looking at the general information document: people in membership and/or technical committees are given a certain percentage of value. There is a need across all areas of expertise to have individuals involved in standards bodies or have them engaged in the work of individual pieces in health identity management. HITSP is starting a series of seminars.

Harmonization framework focuses on interoperable specifications, transaction packages, transactions and components. It is focused on a transaction package (TP20) and component (C19). There is a national information technology meeting in DC which will be looking at setting up separate reviews and setting aside resolution for 2008 on TP20 and C19 (a policy attribute service). We need to make sure that we have a presence in these meetings and speak up/support the things that Liberty has been working on. Many players on HITSP are active in HL7, IHE, etc… The same players show up at all the different forums.

Liberty is working closely on a few issues with HITSP (PAS, PP20, P19); they plan on using IAF for guidance only. ID-Governance framework will play into access to attribute, privacy, etc…

The work we will be doing will be primarily through conference calls and email. If anyone is interested in helping staff committees to identify which issues are hot and which groups are focusing on identity management please contact Rick.

Meeting Adjourned