esMD+PPA+UC1+Harmonization+Meeting+Minutes+3-28-2012





Introduction

 * Reviewed the F2F registration and hotel reservation dates

Data Model Development

 * Added two objects to the Data Model Object tab.
 * ‘Individual Name’
 * ‘Address’
 * Two elements within the ‘Address’ object are gray and have a cardinality of zero (not required), but we keep them to stay aligned with the objects in the PD data model.
 * To avoid confusion, added a comment that, “elements below are not required in the esMD data model”.
 * Decision to move ‘Address Line 2’ back into the optional esMD ‘Address’ Objects.
 * Decision to leave “Prefix’ within the ‘Individual Name’ object
 * If someone had a prefix, you force it into one of the other elements, which could create problems in how people store/collect data.
 * Decision to reuse PD codesets in standard format/vocab column for ‘Individual Prefix’ and ‘Individual Suffix’.
 * Discussion about people that only have one name (e.g. Prince, Cher). Decided to change the cardinality of ‘Individual First Name’ to (0,1) to address this.
 * Added comment to indicate that the ‘Telephone Number’ is, “area code plus traditional seven digits and extension if necessary”.
 * Added comment under ‘Individual Provider’ Object’s ‘Public Digital Certificate’ that “for CMS, certificates MUST be issued by authorities cross certified by the Federal Bridge”. For ‘Provider Organization’ Object’s ‘Public Digital Certificate’, made it “certificates MAY be issued…”

Action Items
> Action Item – Support staff will schedule a harmonization meeting to focus on security requirements
 * Action Item – Support staff will change the cardinality comments to sit within the cardinality column, and include text to “see comment”.
 * Action Item – Support staff will review PD data model for a Prefix and Suffix codeset.