PD+Electronic+Service+Information+SWG+Meeting+Session+14

**Time:** 12:00PM - 1:30PM EDT **Dial-in:**1-408-600-3600 | **Passcode:** 668 071 497
 * Electronic Service Information Discovery Workgroup Call **
 * Date: **09/22/2011

Tynisha Carter, Virginia Riehl, Sam Dechario, Shay Paintal, William Ryan, Robert Dieterle, Sally Love Connally, Zeshan Rajput, SI Framework, Gail Kocher, Terri Skalabrin, Mike Woodcock, John Moehrke, Richard Eshbach, Karen Witting
 * Attendance: **


 * Action Items:**
 * Action Item – need to determine the code sets for Organization Specialty offline.
 * Action Item – support team filter change to “Individual name” down to the workstreams.
 * Action Item – support team will discuss use of codesets that need to be purchased with the ONC.
 * Action Item - review Implementation Guide for Use Case 1 and comment on the layout that has been suggested.

Create list number 9: usage under the digital certificate object.
 * Minutes:**
 * There was a list under HPD, so we will start with that and add to it.
 * Starting List
 * S-mime
 * Signing
 * User
 * John suggests that a Usage element is unnecessary. A digital certificate contains a usage tag and the provider directory should not try to change or redefine that usage.

Discuss Service Address: billing, mailing, and legal address:
 * Those were the types of addresses that were represented under the usage.
 * In X12 call, we determined that we would want to return any or all of those addresses, whereas you should be able to query using any of them.
 * These are “types” of service addresses. Each type allows multiples.
 * We need to clearly define each type, because provider data people will define it differently. “Billing address” could entail the place where bills are sent as opposed to payments.
 * Four types: practice location, mailing, legal, payment.

Response Data Set Individual-Organization Relationship
 * Removed status, type, relation. (this was done on one of the work stream calls and is being applied to the entire use case).

Action Item – Need to offline determine the code sets for Organization Specialty.
 * List 3:
 * “Direct secure email” has been switched to “Direct Project email”.
 * “Unsecure service email” and “unsecure personal email” switched to “other email”.
 * Individual Name Object
 * Someone could have multiple names. For example, when they get married, their name may change and someone querying may not know that. We have added an element to the response data set.
 * “Individual name” has been broken into two categories: “Primary individual name” (single) and “Alternate individual name” (multiple).
 * Action Item – filter this change down to the workstreams.

Karen and Bob are meeting at 9am Tuesday. Agenda for their call: 1. Electronic Service information Object section. 2. Query/Response definitions.
 * ONC is receptive to a work group creating their own code sets.
 * They want a proposal made.
 * What if we find a codified set of data that comes with IP and purchasing issues?
 * Action item – support team will draft an email to Bob, Ken, and Gail about creating a proposal/question to ONC about what happens if we encounter a code set that we would need to purchase.

Please review Implementation Guide for Use Case 1 and comment on the layout that has been suggested. Action Item – Put Jitin’s reason about why MicroData has been removed as a workstream into writing (support team).