PD+Sprint+Meeting+Session+9+Meeting+Minutes+2011-07-29


 * Date:** 7/29/2011
 * Name**: Provider Directories (PD) Initiative Sprint Team Meeting 9

**Agenda/Objectives:**

 * **Topic** || **Time Allotted** ||
 * Initiative Updates and Announcements || 10 minutes ||
 * Query for Electronic Service Information including Electronic Address Use Case || 100 minutes ||
 * Sprint Team Logistics/ Next Steps and Questions || 10 minutes ||

Attendees:
Erik Pupo, Craig Klassy, Ernest Grove, Margaret Weiker, Ron Sawdey, Dave Shevlin, Ken Pool, Chris Andreou, lin wan, Tynisha Carter, Rita Torkzadeh, Emily Mitchell, Charlene Harven, rao parvatam, JOHN MOEHRKE, Jeff Ice, Scott Chapin, Teresa Strickland, Walter Suarez, Debra Rouse, Noam Arzt, Robert Dieterle, Erin Cornell, John McLamb, peter bachman, Karen Witting, Michael Nelson, Lester Keepper, Rick Marolt, Aleena Dhar, Ed Larsen, Heather Stevens __Panelists:__ Victoria Njoku, Virginia Riehl

Action Items:

 * **Date** || **Description** || **Status** || **Notes** ||
 * 8/1/2011 || Address comment about definition of Electronic Address in Return data elements table of Use Case || CLOSED || Support Leads to work offline with Co-Leads ||
 * 8/1/2011 || Present completed //Query for Electronic Service Information// //including Electronic Address// //Use Case// for consensus || CLOSED ||  ||
 * 8/1/2011 || Cast vote on Use Case || OPEN || Committed Members ||
 * 8/1/2011 || Provide Comment on Use Case || OPEN || Non-Committed Members ||
 * 8/1/2011 || Review posted Meeting Minutes for Sprint Team and SWG meetings and provide any corrections || OPEN || SWG Members ||

__**Query for Electronic Service Information including Electronic Address Use Case:**__

 * Key Discussion Points:**
 * The discussion for comments related to additional requirements proposed by SWG to the Functional Requirements section focused on the following:
 * Workgroup members examined the statement “The Provider Directory returns Electronic Service Information (including electronic address and security information)”
 * The proposed statement is redundant; it reflects what is already stated in section 10.4.2 System requirements
 * Workgroup members examined the statement “Provider Directory systems have controls to ensure that destination information is maintained in a secure manner and that information is shared only with authorized users”
 * Statement was revised and added to the System Requirements section (10.4.2)
 * Both Provider Information Directory and Electronic Service Information Consumer System have to be capable for this exchange
 * Business actors are assigned to their systems
 * This is a system to system communication
 * A request was made to add a reference to information interchange requirement name section including “using query data elements (Table 8)” to the following statement “query for destination information”
 * A request was made to revise the Information Interchange Requirement for the Provider Information Directory System to “List of destinations query data elements (Table 9) matching query”
 * Workgroup members examined the statement “Provider Directories can support a relying party agreement which may address accurate, timely, and complete data, legal and governance policies, data access authorizations, data ownership, and data use”
 * Statement was revised and added to the System requirements section (10.4.2)
 * Workgroup members examined the statement “A Provider Directory will provide at least one secured and guaranteed delivery transport mechanism”
 * Statement was revised and added to the System requirements section (10.4.2)
 * A request was made to revise the following statement “receives list of destination that match query parameters along with their electronic service information” to the following “Receives list of destination data elements (table 9) that match query parameters”
 * A suggestion was made to insert the following statement in the functional requirements section of the Use Case “it is the role of the consuming system to validate that the information is still current”
 * A suggestion was made to add the following verbiage to section 10.4.2 (system requirements). System “Electronic Service Information Consumer System”; System Requirement “Consumer systems shall support validation of current information if caching occurs”
 * Workgroup decided that this is a good implementation strategy but is not necessary in the Use Case.
 * Workgroup also decided that this is out of scope
 * The discussion for the Issues, Obstacles, and potential risk focused on the following:
 * A request was made to add the following risk “Potential for expired information if consumer system caches destination and electronic service information”
 * A request was made to add “electronic service information” to the following bullet “Providers are not broadly experienced in acquiring and using provider information from Provider Directories
 * Other issues/risks/obstacles from the //Query for Digital Certificate for Direct Project Use Case// did not seem appropriate to include in this Use Case
 * The discussion for the Data Set Considerations focused on the following
 * A request was made to remove “practice organization” from the individual level
 * A suggestion to change the statement to the following “name of practice organization” instead of removing the bullet
 * The statement “name of practice” at the individual level violates the object hierarchy.
 * “Practice organization” was deleted
 * A suggestion was made to add another level Organization – Organization relationship to the dataset consideration for return message
 * Definition of Electronic Address under the Electronic Service Information data section will best described with the definition already noted in the glossary section

Resolution(s):

 * Revisions Functional Requirement section are as follows:
 * Statements in section 10.4.1 (Information interchange requirement name) have been changed to the following
 * “Query for destination information using query data elements (Table 8) for the Electronic Service Information Consumer System
 * “List of Destinations query data elements (table 9) matching query” for the Provider Information Directory System
 * “Have controls to ensure that destination information is maintained in a secure manner and that information is shared only with authorized users” was added to the System Requirements section (10.4.2) for the Provider Information Directory System
 * “Receives list of destination data elements (Table 9) that match query parameters” was added to the System Requirements section (10.4.2) for the Electronic Service Information Consumer System
 * “Can support a relying party agreement which may address accurate, timely, and complete data, legal and governance policies, data access authorizations, data ownership, and data use” was added to the System Requirements section (10.4.2) for the Provider Information Directory System
 * “Will provide at least one secured and guaranteed delivery transport mechanism” was added to the System Requirements section (10.4.2) for the Provider Information Directory System
 * Revision to the Issues, Obstacles, and Potential risk section are as follows:
 * The following statement was added “Potential for expired information if consumer system caches destination and electronic service information”
 * “Provider Information” was replaced with “Electronic Service Information” in the previous statement “Providers are not broadly experienced in acquiring and using provider information from Provider Directories”
 * Revisions to the Data set considerations section are as follows
 * “Practice Organization” was removed from the individual data section of the return table
 * Organization – Organization relationship was added to the dataset consideration for return message.
 * Relationship (Unique Reference for related organization, Type of Relationship, Description) was removed from the organization data section of the return table
 * The following data elements were captured under this section: “Unique Reference for from Organization,” “Unique Reference for to Organization,” “Status,” “Description,” and “Type of Relationship”
 * Definition of Electronic Address under the Electronic Service Information data section of the return table will be revised offline to align with definition in the glossary

Key Discussion Points:

 * Next Certificate Discovery SWG Meeting rescheduled for Monday August 1, 2:30-4:00PM ET
 * Next Electronic Service Information Discovery SWG Meeting scheduled for Thursday August 4, 12:00-1:30PM ET)
 * Next Sprint Team Meeting scheduled for Friday August 5, 2011 3:00-5:00PM ET
 * Review posted Meeting Minutes for Sprint Team and SWG meetings and provide any corrections
 * Present completed //Query for Electronic Service Information// //including Electronic Address// //Use Case//for consensus
 * Committed Members requested to review Use Case and cast votes during consensus
 * Continue Harmonization work for Certificate Discovery for Direct Project work stream