Electronic+Service+Information+Discovery+-+Data+Model


 * ANNOUNCEMENTS:**
 * **Electronic Service Information Discovery Data Model is open for consensus voting. Voting will be open from 11/18 to 12/2. Please vote here.**

**Data Model Overview**
The initial step within the harmonization approach for the Query for Electronic Service Information Use Case is to further detail the data elements listed in Section 12 of the use case document. Details within the data model would include:
 * Description of the data element - a clear definition that everyone understands and everyone can "map" standards to.
 * Possible datatypes - to help in mapping to standards, possible datatypes will need to be considered (in what format would the data element be stored in a provider directory). This is an optional step.
 * Cardinality - cardinality at this time assumes that either zero, 1, or more than 1 value can be used in each data element. This assumption can be changed by the workgroup if they feel cardinality needs to be adjusted for each individual data element or all the data elements.

What is NOT in scope for the data model:

 * While valuable to know (and which can be captured in Notes), it is not important at this time to know exactly where the data might come from. For example, it is assumed that policy information is accessible and could be stored in a provider directory in some format.
 * Not in scope to discuss the validity of each data element in the use case. Each data element must be considered regardless of whether it can be mapped to a standard or not and we will NOT be discussing their validity.

Data Model - Provider Query Result
The following figure shows a logical data model for the Provider Query Result data elements. It is important to note assumptions in this data model:
 * The Provider Directory Query Result entity is conceptual and is just meant to show how all the data elements coalesce into a query. This is why it has no data elements inside.
 * Initial datatype mappings have been provided. Where "default" is used, this indicates an area where the workgroup will need to provide more clarity on the data element and how it might be stored.

Provider Directory Data Elements - Data Dictionary
The following table outlines each of the data elements listed:

Click [|here] to make edits media type="custom" key="11055952"

Harmonization Notes for Data Elements
The following notes were captured in the Query for Electronic Service Information Use Case and will need to be reviewed within harmonization:
 * For recipient name under Direct Address, this depends on the data model and will be addressed during harmonization phase.
 * All data elements captured under Dataset Considerations (Section 12.0) may have zero, one, or many values
 * There may be a need to enhance search capabilities through a nickname, vanity cities, and first and middle name reversals
 * The inclusion of “recipient name” under Electronic Address as captured in the query message table of the Dataset Considerations (Section 12.0) depends on the data model

Use Case Reference
media type="custom" key="10268905"