[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Minutes of April 1, 2011 XSPA TC Conference Call
Friday, April 1, 2011 Minutes XSPA Conference Call Dial in info: +1 800 767 1750 Access code 97728 [i.e. XSPA T(C)] 1. Roll Call & Agenda Review Voting Members: John Moehrke, GE John Davis, Veterans Health Administration Duane DeCouteau, Veterans Health Administration David Staggs, Veterans Health Administration Non-Voting
Members: Chris Garza, Jericho
Systems Corporation Quorum achieved
(4/6 voting members) 2. Minutes of
Friday, March 4, 2011 are approved. 3. Future demonstrations were discussed. Mike suggested contacting Gartner to inquire
if they would want to host a demonstration of the XSPA profiles at the upcoming
Gartner/Burton conference. The
conference date is 26-29 July 2011.
David has called and sent e-mails to the Gartner representatives and has
not received a response. 4. Discussion on the creation of an OASIS reference model of XSPA. Duane showed material describing the VA reference
model. Mike told the group that the
VA is building a reference model on top of the XSPA model. The VA reference model will have web
services, schemas, and working code examples. Mike stated the VA model goes
beyond what the XSPA TC might want to host at the OASIS site. John stated that the VA work was a not a
reference model, instead it seems it is an instantiation of a reference model
with a specific vocabulary. Mike took an action item to find out if the VA
model could be released to the general public. Duane suggested the OASIS reference model would encompass the
functionality that could validate or generate an XSPA message. Mike saw this as
a reference implementation instead of a reference model and that Duane was
suggesting creation of a test harness.
Duane took an action item to define the SAML validation functionality of
the test harness an when that might be offered to OASIS. 5. General discussion included how the Nation Wide Health
Information Network (NwHIN) Connect might be using
XSPA attributes compared to the work being done in NwHIN
Direct. John stated XDR will be
recognized as “NwHIN Direct-compliant” John
distinguished end-to-end distribution of health related information within an
enterprise vs. communications between enterprises which require SMIME for
compliance in NwHIN Direct. The comparison of Direct
with Exchange is informational only; XSPA is aimed at web service communications. Regards, David David Staggs, JD, CISSP
(SAIC) |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]