esMD+Use+Case+1+Implementation+Guide+Consensus+Page

include component="page" wikiName="siframework" page="esMD Header"

=Announcements= toc =Works Approved Through Consensus= =Consensus Process= The goal is unanimous consent, which is obtained by carefully considering and addressing significant input from the Community of Interest. Where unanimity is not possible, a group SHOULD strive to make consensus decisions where there is significant support and few abstentions. Any significant deliverable of the Initiative Charter will be approved through a formal Consensus process. Each Initiative Member will provide one of the following votes during the Consensus process:
 * **__ Thank you for your participation!! __** As of February 1st, 2013, the esMD Use Case 1 Implementation Guide has been finalized and Consensus-approved. The document below reflect updates that were proposed and agreed upon during the formal Consensus Process. Please contact the Workgroup Lead or Support Lead if you have any remaining questions or concerns.
 * Click here to access the PPA Harmonization (Use Case 1) Workgroup page.
 * **Date** || **Artifact Name** || **Artifact Links** ||
 * 2/1/2013 || esMD Use Case 1 Implementation Guide || * [[file:esMD Use Case 1 Implementation Guide Final v1.0.docx|Document link]]
 * S&I Framework Repository Link ||
 * **Yes**
 * A Yes vote does not necessarily mean that the deliverable is the ideal one from the perspective of the Initiative Member, but that it is better to move forward than to block the deliverable
 * **Yes with comments**
 * If a Consensus Process attracts significant comments (through Yes with comment votes), it is expected that the comments be addressed in a future revision of the deliverable.
 * **Formal Objection**- with comments indicating a path to address the objection in a way that meets the known concerns of other members of the Community of Interest. "Formal Objection" vote without such comments will be considered Abstain votes.
 * A Formal Objection means that the objector cannot proceed with the project unless the objections are met. It is acceptable and expected to use a Formal Objection in a first consensus round to communicate a point of view or process issue that has not been addressed in the drafting of the initial deliverable.
 * Should a Consensus Process attract even one "Formal Objection" vote with comments from an Initiative Member, the deliverable must be revised to address the "Formal Objection" vote (unless an exceptional process is declared).
 * **Abstain** (decline to vote)


 * Note: If you have comments on multiple sections please submit a new entry for each comment. Only one vote will be counted per committed organization and each comment from members of a single organization must contain the same type of vote.**
 * **E.g. - If one member of ACME Corp. votes "Yes (with comment)" another member from ACME Corp. cannot vote "Object (with comment)." In such cases votes will be considered an "Abstain" vote. Alternatively, if one member of ACME Corp. votes "Objection (with comment)" on one section of the document but has comments regarding another section of the document, they are welcome to provide additional comments but their vote for the new comment must still be "Objection (with comment)."**

For Implementation Guide specific questions, contact Sweta Ladwa (esMD Project Manager) - sweta.ladwa@esacinc.com If you have questions or technical difficulties, contact: Apurva Dharia (S&I Administrative Lead) - apurva.dharia@esacinc.com

media type="custom" key="22041616"

include component="page" wikiName="siframework" page="esMD Contacts" include component="page" wikiName="siframework" page="space.template.inc_contentleft_end"