Provider+Directories+(PD)+Initiative+Electronic+Address+Discovery+SWG+Meeting+Session+6

Date: July 21, 2011 12:00-1:30PM EDT Name: Provider Directories (PD) Initiative – Electronic Address Discovery SWG Meeting Session 6

Agenda/Objectives:

 * **Topic** || **Time Allotted** ||
 * Dataset Considerations of Query for Electronic Address Use Case || 30 minutes ||
 * Revisions to Introductory Sections of Query for Electronic Address Use Case || 25 minutes ||
 * Revisions to Other Sections of Query for Electronic Address Use Case || 30 minutes ||
 * Sprint Team Logistics /Next Steps || 5 minutes ||

Ken Pool; Andriy Selivonenko; Ernest Grove; Rao Parvatam; Erik Pupo; Ananya Gupta; Dan Kearney; Aleena Dhar; Peter Bachman; Bob Yencha; Jonathan Tadese; lin wan; Dan Huber; Kelly Conlin; Bob Lutolf; Lester Keepper; Noam Arzt; Don Jorgenson
 * Attendees:**

__Panelist Attendees:__ Bob Dieterle, Virginia Riehl, Victoria Njoku


 * Action Items:**
 * **Date** || **Description** || **Status** || **Notes** ||
 * 7/21/11 || Draft definition for Electronic Service Information for review || OPEN || Bob Dieterle ||
 * 7/21/11 || Inform Initiative Coordinator about SWG proposal to change scope of current Use Case to Electronic Service Information Discovery and report feedback/direction back to Sprint Team || In Progress || Use Case Support Leads ||
 * 7/21/11 || Review updated Use Case and provide comment on Wiki (if any) to be addressed during 7/22 Sprint Team meeting || OPEN || SWG and Sprint Members ||

//Key Discussion Points://
 * Dataset Considerations**
 * **Dataset Considerations:**
 * In the query message table, the option to change the “Direct Address (...)” broadly to “Electronic Address” was accepted
 * In order to indicate a parent-child relationship within organizations in the return message table, two options were presented:
 * An organization-organization relationship added as an additional section
 * An additional data element within the Organization section called “Relationship (Unique Reference for related organization, Type of Relationship, Description)
 * The group preferred this option
 * The element “Status” may need further clarification to an external reader, hence a note was included to indicate that it refers to whether the organization or relationship is active or inactive
 * One member emphasized allowing the Provider Directory to return policy information following the query. The group did not see this as out of scope or something to address later and introduced a data element “Policy Information” to the organization section where it was only necessary. A definition was also included in the notes section
 * The section “Electronic Service Information” and its corresponding data elements which includes “Electronic Address” raised discussion about changing the scope of the Use Case to discovering electronic service information
 * Initially, the use of “Electronic Address Information” was considered to replace “Electronic Service Information” but external readers could potentially be confused between the use of Electronic Address as what is being sought and the group of data elements called “Electronic Address Information”
 * Alternatively, the use of “Electronic Service Information” would practically change the Use Case since other elements associated with an electronic service such as service type may be returned from the query
 * The group determined that the electronic address would be part of the electronic service information along with other items, such as, service type, message type, recipient name, and security information (e.g. digital certificate).
 * Based on this discussion, the group concluded that the query was intended to retrieve the more comprehensive set of electronic service information.
 * Several members of the group proposed changing the name of the Use Case to “Query for Electronic Service Information” instead of the current “Query for Electronic Address Use Case” and requested ONC feedback
 * A question was raised about whether and how requirements are translated downstream including the harmonization phase. A response will be provided by the harmonization team during the next Sprint Team meeting
 * Overview and Scope:
 * Given the proposal to change the Use Case, the group made revisions to replace electronic address and security information with “Electronic Service Information” and provide a definition in the glossary section
 * Bob Dieterle agreed to draft a definition for “Electronic Service Information”
 * In order to clarify that Direct Project users can also use the Provider Directory to discover Direct Addresses and digital certificates, an additional outcome was included
 * In response to a comment about removing the in scope statement “Exchanges dealing with sending one message to one recipient,” it was agreed that the Use Case supports health information exchange in general including sending one message to one recipient

//Resolution(s)://


 * “Relationship (Unique Reference for related organization, Type of Relationship, Description) was added as an additional data element within the Organization section of the return message
 * A note was included to indicate that “Status” refers to whether the organization or relationship is active or inactive
 * “Policy Information” was included as a new data element to the organization section in the return table and a definition was also included in the notes section
 * Electronic address and security information was replaced with “Electronic Service Information” throughout the Use Case
 * Bob Dieterle agreed to draft a definition for “Electronic Service Information” and will include in the glossary section
 * A fourth outcome was included to indicate that “Users of Direct Project implementations may use the Provider Directory to discover Direct Addresses and digital certificates”


 * Logistics and next steps:**

- Bob Dieterle will draft a definition for Electronic Service Information - Use Case Support Leads will inform Initiative Coordinator about proposal to change scope of Use Case to Electronic Service Information Discovery and report feedback/direction back to Sprint Team - Review full Use Case and provide comment on Wiki (if any) to be addressed during 7/22 Sprint Team meeting - Recurring SWG Meetings occur every Thursday 12:00-1:30PM ET. - Next Sprint Team Meeting scheduled for July 22, 2011 3:00-5:00PM ET - Next SWG Meeting scheduled for July 28, 2011 12:00-1:30PM ET