PDMP+&+HITI+Use+Case+Consensus

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

The PDMP & HITI Use Case achieved consensus on March 25, 2014.
The consented Use Case Document (with track changes) and consensus votes/dispositions are below:


 * [[file:Prescription Drug Monitoring Program & Health IT Integration_Consented Use Case_3.25.2014.pdf|PDMP & HITI Final Consented Use Case with Privacy Appendix]] - posted 4/24/2014
 * [|PDMP & HITI Consented Use Case (with track changes)] - posted 3/25/2014
 * [[file:PDMPHITI Consensus Votes and Dispositions.pdf|PDMP & HITI Consensus Votes and Dispositions]]

Instructions on the Consensus process can be found below; after you have reviewed the final Use Case document, you can begin casting your vote. If you would like to add any additional comments to your ballot, remember to provide actionable comments where applicable/necessary. **Note:** Only “one” vote per committed organization will be counted; please make sure to reconcile your votes with your colleagues.

Only Committed Members will be able to cast a vote. If you have any questions about your commitment level, please contact Ali.Khan@esacinc.com. =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. Each Initiative Member will provide one of the following votes during the Consensus process: . ..
 * **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)."**

media type="custom" key="25458722"