PD+-+F2F+Sprint+Team+Meeting+Minutes+2011-06-15+-+Query+for+Electronic+Address+Use+Case

**Name** : //Provider Directories (PD)// Sprint Team F2F Meeting //- Query for Electronic Address Use Case Session//
 * Date:** //06/15/2011//

**Agenda/Objectives:**

 * **Topic** || **Time Allotted** ||
 * Query for Electronic Address || 1:30pm-4:30pm ||

Amram Ewoo, Galen Mulrooney, Michael Rossman, Nitin Jain, Robert Dieterle, Ryan Balsick, Sri Koka, Thompson H. Boyd, III, Veronica Yackuboskey, Vincent Lewis, Ken Pool, Melanie Combs-Dyer, Annamarie Saarinen, Lin Wan, Michael Nelson, Steve Rushing, Scott Chapin, Myung Choi, Stephen Witter, Tynisha Carter, Chris Andreou, Jonathan Tadese

Panelist Attendees:
Victoria Njoku, Virginia Riehl, Erik Pupo, Jitin Asnaani

Action Items:

 * **Date** || **Description** || **Status** || **Notes** ||
 * 6/16/2011 || Review and provide comments on sections completed i.e.
 * Scenarios
 * Base Flows
 * Use Case, Context, Activity, and Sequence Diagrams
 * Use Case Assumptions
 * Pre-conditions
 * Post-conditions
 * Actors and Roles
 * Functional Requirements
 * Information Exchange Requirements
 * System Requirements || OPEN ||  ||
 * 6/16/2011 || Review and provide comments on sections to complete during Friday PD Sprint Team meeting i.e.
 * Issues and Obstacles
 * Data Set Considerations
 * Overview and Scope (includes: In Scope, Out of Scope, Background, Policy Issues, Regulatory Issues, Communities of Interest sections)
 * Challenge Statement
 * Value Statement || OPEN ||  ||

**Key Discussion Points:**

 * Providers might need different indirect addresses
 * Provider or entity might have different addresses for different reasons
 * Concept of role(s) within an organization
 * Organizations have nodes. Nodes can be borrowed. Nodes can be either owed or borrowed.
 * The system will always query twice
 * There is a need for some means of trying to ensure that the correct endpoint/destination is identified (needs to be placed in issues and obstacles)
 * The query for Digital Certificate Use Case could query with electronic address and/ or UUID
 * The provider information consumer statement should be removed from the actors and roles section: this is an implementation statement
 * Update post conditions to reflect the changes made to Use Case 1 (bullets 1 and 2)
 * An Alternative flow will need to be included for line 2 in the post conditions section (10.3.1 base flow) and reference back to use case 1 to indicate that the consumer may query for a digital certificate in addition to the electronic address on a conditional basis.
 * Incorporating use case one into use case two by reference
 * Use case one can be enhanced later
 * Use case three can be the expanded version
 * We are solving the problem in Use Case 2
 * Queries to disambiguate the destination/intended recipient( information on the need to know bases)
 * Data set to be returned should be fixed and not variable i.e. the consumer will receive a fixed number of data elements following the query and not have option to determine which data elements to select from what is returned. The data elements returned will be at a minimum to address concerns for consumers that perform large volume queries e.g. CMS
 * Digital Certificate query is a conditional issue and not a fixed set issue
 * Data set elements work has rolled into Use Case 2 and will be addressed further in the next meetings

**Resolution(s):**

 * The following changes have been made to the User Story section:
 * Remove the statement “of the summary of care” from the first line
 * Remove “(either through their provider system or in a separate application) to locate the electronic address for the provider who is the intended recipient of the summary of care.”
 * Remove “provider” and replace with “destination”
 * Add the following
 * Change the word “correct” to “their”
 * Remove “If the query is initiated in a separate application, the provider directory returns the electronic address for the correct endpoint and the user enters this address manually in their provider system. The remainder of the user story is the same as in the User Story of the Query for Digital Certificate Use Case.”
 * Delete the word “correct” from the following statement “the electronic address for the correct endpoint and may return any required security information”
 * Delete “if the query is initiated through the provider system.”
 * Remove “the recipient uses the sender’s electronic address to access the certificate store to confirm the identity of the sending provider and confirms that the public certificate of the sender is signed by a trusted authority.”
 * Add “conditional” to the following statement may “conditionally” return any required security information- this is a conditional statement
 * The following changes have been made to the trigger section
 * Remove “provider” and replace with “sending entity”
 * Remove “another provider” and replace with “receiving entity”
 * Remove “health care organization”
 * The following changes have been made to the Activity diagram
 * Remove blocks 5,6,7,8
 * Step 3: change to “Select matching query”
 * Step 4: change “display” to “receives”
 * The following changes have been made to the base flow
 * Remove steps 3 and 4
 * The following changes have been made to functional requirements
 * Remove provider directory consumer system row
 * Remove provider information directory system row
 * The following changes have been made to system requirements
 * Remove provider Directory Consumer System row
 * Remove provider Information Directory System row
 * Remove provider Directory Consumer System row
 * The following changes have been made to Use Case assumptions
 * Remove “display” and replace with “receive”
 * Remove “public key information” and replace with “digital certificate information”
 * Remove “incorporate” and replace with “utilize”
 * Remove “into messages” from the following statement “provider systems will be able to incorporate public key information into messages”.
 * Change the same way as use case one (provider directories ensure that their data is accurate, timely, and complete)
 * Change bullet 11 to reflect changes made to use case 1
 * Change bullet 12 to reflect changes made to use case 1
 * The following changes have been made Post conditions
 * Remove “information” in the statement the provider’s system has the information required to electronically send information to the intended recipient and replace with “electronic”
 * The following changes have been made to actors and roles
 * The provider information consumer statement should be removed: this is an implementation statement
 * The use of UUID to query will not be pursued; therefore no changes will be made to the Query for Digital Certificate Use Case.