Cross+Initiative+-+Use+Case+Simplification+Package+Consensus+Page


 * The Use Case Simplification package call for consensus will conclude on July 7th. Please follow the instructions below to leave your vote:**
 * 1) Click "Edit" in the top right corner of the page
 * 2) Scroll to your name in the table (table is organized in alphabetical order by organization)
 * 3) Cast your vote (Yes, Yes with Comments, or No)
 * 4) Indicate what changes you believe should be made to the Use Case Content (if applicable)
 * 5) Click "Save" on the right side of the toolbar

In the spirit of having everyone’s voice heard, the consensus page is organized to allow each participant to cast a vote and leave comments where applicable. However, only one vote per organization will be counted. Therefore, each organization is asked to designate one person to leave the final vote on behalf of the organization. This structure will allow for two people from the same organization to leave comments should there be specific opinions in changes that need to be addressed.

//NOTE//: //If you do not see your name within the table and you believe that it should be there, or if any of your information is incorrect, please contact your support leads.//

In the Core Matrix on the Common Data Elements worksheet, there is a Data Element Set name called "Person Information", but there is another 'person' listed as the Healthcare Provider on the same worksheet. Is "Person Information" specific to patients or is it common across all persons? If it is only for patients, then "Person Information" would be better described as "Patient Information". If it is common across all persons, then "Patient" needs to be listed as a common data element. || and appropriate use of term clinician in action entries || The LRI Use Case, section 2.1 includes multiple “states” of lab reports (“preliminary, final, appended, corrected, and/or amended”). Does the Scenario description of “[A.REC.1/2] Originate/Retain - Lab Results Report” need to be revised to clarify it includes all “states” of the lab result? Actor-“Laboratory System” - The LRI Use case Overview, User Story, Assumptions, Pre-Conditions, Actors and Roles, Functional Requirements, Activity Diagram etc. uses the term “Laboratory Information System”, suggest change “Laboratory System” to “Laboratory Information System” Actor Definition “Laboratory System” – suggest adding the following: A lab information system ("LIS") is a class of software that receives processes, and stores information generated by medical laboratory processes. These systems often must interface with instruments and other information systems such as hospital information systems (HIS). A LIS is a highly configurable application which is customized to facilitate a wide variety of laboratory workflow models. There are as many variations of LISs as there are types of lab work. Some vendors offer a full-service solution capable of handling a large hospital lab's needs; others specialize in specific modules. Disciplines of laboratory science supported by LISs include hematology, chemistry, immunology, blood bank (Donor and Transfusion Management), surgical pathology, anatomical pathology, flow cytometry and microbiology. Can you clarify the difference between “Provider – Individual” and “Clinician – Individual”? The definitions seem to overlap. -Suggest delete row 64 (LRI Data Element Sets (from HL7 v2 messaging) as the LRI elements/mapping are not included in the Work Sheet -Remove starting row 77 ||
 * **Name** || **Organization** || **Endorsement (Yes/Yes with Comments/No)** || **If no, what can be changed to make it yes?** ||
 * Michael Fitzmaurice || AHRQ || Yes, with comment || Looking for more specificity with respect to data elements and the standard(s) that specifies their use, and the vocabulary from which they come. Also looking for reuse of the same data element(s) across the use cases. For example, if HL7 V3 deft of person is used, defining the same data elements across all persons where they are applicable should be explicit. The simplification package is good and organizes our work to date. ||
 * Annamarie Saarinen || Ainsley Shea ||  ||   ||
 * Robert Dieterle || Cal eConnect ||  ||   ||
 * Cindy Vinion || NGIT || Yes with comments || In the Cover doc, slide 2, "constructs" listed as "Instantiable components". This needs more defintion or to be changed. Where can/should the constructs be instantiated: an exchange mechanism (CDA, HL7 message, etc), a database, user interface screens, paper forms, etc? These might be better described as "information constructs or components" or something more representative of what they are. For example, "address" is listed as one items in the DES but is is never (and should never) be instantiated as a single field, particulary in the electronic world (dbs, CDAs, messages, screens, etc).
 * Ronique Watkins || CDC ||  ||   ||
 * Elliott Sloan || CHIRP ||  ||   ||
 * Michael Glickman || Computer Network Architects, Inc. || YES with comment || Continued coordination to ensure consistency and simplicity. ||
 * Sandra Raup || Datuit || Yes ||  ||
 * Gordon Raup || Datuit || Yes, with Comment || The definition of “Provider EHR System” in cell C7 on the Common Actor Tab appears to refer to two different concepts: 1) the HR system maintained by individual provider organizations, and 2) the cumulative HR resulting from the integration of health data from multiple separate Provider EHR Systems. Innovative new solutions are being developed for the latter by multiple vendors. We should have different labels for these two different concepts. ||
 * Stephen Hufnagel || DoD, MHS ||  ||   ||
 * Kosta Makrodimitris,PhD || US-FDA,DHHS || Yes || some minor comments on the terms used in the presentation/deck and a need in the future to expand to a more detailed documentation and references ||
 * Jaime Estrada || Health Information Network of Arizona ||  ||   ||
 * Susan Nedza || HealthyCircles || Yes ||  ||
 * Audrey Dickerson || HIMSS ||  ||   ||
 * Gary Dickinson || CentriHealth || Yes ||  ||
 * Mayuri Patel || ICA || Yes ||  ||
 * Cyndalynn Tilley || Intermountain Healthcare ||  ||   ||
 * John Donnelly || IntePro Solutions || Yes with Comments || Completion of the definitional info re "provider"
 * Walter Suarez || Kaiser Permanente ||  ||   ||
 * Sandy Stuart || Kaiser Permanente ||  ||   ||
 * Andriy Selivonenko || Lockheed Martin ||  ||   ||
 * Amy Knopp || Mayo Clinic ||  ||   ||
 * Holly Miller, MD || Medallies ||  ||   ||
 * Luann Whittenburg || Medicomp Systems ||  ||   ||
 * Beth Halley || Mitre ||  ||   ||
 * Fred Buhr || Patient || Yes ||  ||
 * Rob Hunter || Providence Medical Group ||  ||   ||
 * Teresa Mota, BSN, RN || Quality Partners of Rhode Island || Yes ||  ||
 * Freida Hall || Quest Diagnostics || Yes with comments || **These comments are for the Core Matrix spreadsheet:** **Scenarios Worksheet:**
 * Common Actor Worksheet:**
 * Common Data Element Set Work Sheet:**
 * Doug Pratt || Siemens ||  ||   ||
 * Russell Leftwich, MD || State of Tennessee ||  ||   ||
 * Ollie Gray || TATRC ||  ||   ||
 * Kim Wolf ||  ||   ||   ||