Query+Health+Charter+-+Call+for+Consensus

include component="page" wikiName="siframework" page="Query Health Header"



**__ Implementation Group __**** Call for Consensus (Round 3): Query Health Project Charter **

** DUE: **** 10/11/2011 **

Any references to the 'solutioning' of Query Health should be removed from the charter, as the architecture is defined during the design phase of the project. || 2. Move this statement up to challenge: "The Initiative will also build on existing investments, technology and thought leadership in distributed query". It is underspecified as a useful scoping statement, and too limiting (in that it apparently restricts us to use of existing investments). 3. The initiative will also __identify__ extensible ‘Query’ and ‘Return Results’ standards and __provide__ services 4. Requirements deadlines may still be unreasonable. 5. While architecture has been added as a deliverable, schedule (already noted to be aggressive) has not changed. 6. The charter states: "The Query Health Initiative will progress through an agile and iterative approach, with __**key milestones**__ and __deliverables__ to be defined by the Community through the initiative Workgroups". If the community does not have input into schedule (and thus far, they have not), then they are NOT defining the key milestones or deliverables. ||
 * **Organization** || **Individual Name** || **Endorsement (Yes or No)** || **If No, what can be changed to make it Yes?** ||
 * Alere Health ||  ||   ||   ||
 * All Healthcare Research and Resource Consulting ||  ||   ||   ||
 * Allscripts ||  || Yes ||   ||
 * American College of Physicians || Thomson Kuhn || Yes. || My previous concerns have been addressed in this new draft. There is a single mention of an "Appendix," but there is no further explanation. Please add or explain the referenced appendix. ||
 * American College of Rheumatology ||  ||   ||   ||
 * Angel eCare || Erin Fitzsimmons || Yes; with Comments || I would like to see the word 'may' be removed from the charter, especially in the scope section. The word 'may' implies that those attributes described in the charter "may or may not" be included in the project requirements, this "may or may not" situation is not measurable by the stakeholders, and the team will not be able to be crisp on satisfying the requirement as it is stated. The team should clarify those charter sentences, replacing the word 'may' with 'will' or 'shall'.
 * Anvita Health Inc. ||  ||   ||   ||
 * Arizona State University ||  ||   ||   ||
 * Biomedical Informatics Think Tank ||  ||   ||   ||
 * Bon Secours Health System ||  ||   ||   ||
 * Cal eConnect ||  ||   ||   ||
 * Cal2Cal Corp. ||  ||   ||   ||
 * Care Management Professionals ||  ||   ||   ||
 * CareEvolution, Inc ||  ||   ||   ||
 * Care Spark/Serendipity Health Consultant ||  ||   ||   ||
 * CDC || Barbara Massoudi, Kathleen Gallagher, Laura Conn, Peter Hicks, Robert Furberg, Taha Kass-Hout, Barry Rhodes, Genny B. Gallagher, Nikolay Lipskiy, James Buehler || Yes ||  ||
 * Center for Mental Health of SAMHSA ||  ||   ||   ||
 * Centra ||  ||   ||   ||
 * Cerner || David McCallie || Yes ||  ||
 * CGI Federal ||  ||   ||   ||
 * Children's Hospital of Philadelphia ||  ||   ||   ||
 * Coastal Connect HIE ||  ||   ||   ||
 * College of American Pathologists ||  ||   ||   ||
 * ConsentSolutions, Inc. ||  ||   ||   ||
 * Covisint ||  ||   ||   ||
 * Deborah B. O'Shea, Esq. (Independent) ||  ||   ||   ||
 * Delmar Family Medicine ||  ||   ||   ||
 * Discoverture Health Solutions ||  ||   ||   ||
 * Elekta, Inc ||  ||   ||   ||
 * Emergint Technologies, Inc. ||  ||   ||   ||
 * Epic ||  ||   ||   ||
 * FDA ||  ||   ||   ||
 * GE HEALTHCARE || Keith Boone || Yes || 1. I thought it had been previously agreed that the project is SELECTING rather DEFINING standards.
 * Georgia Tech ||  ||   ||   ||
 * Gorge Health Connect, Inc. || Brian Ahier || Yes ||  ||
 * Greenway Medical Technologies || Steve Felt || Yes ||  ||
 * Hahnemann University Hospital ||  ||   ||   ||
 * Harlow Group, LLC ||  ||   ||   ||
 * Healthcare Information Xchange of NY ||  ||   ||   ||
 * Health-ISP ||  ||   ||   ||
 * Healthcare Management Systems, INC. ||  ||   ||   ||
 * HealthyCircles, LLC ||  ||   ||   ||
 * Humedica ||  ||   ||   ||
 * Indian Health Service ||  ||   ||   ||
 * IntePro Solutions || John Donnelly || Yes || My previous concerns have been addressed in this new draft. ||
 * International Society for Disease Surveillance ||  ||   ||   ||
 * Lintech ||  ||   ||   ||
 * Lush Group, Inc ||  ||   ||   ||
 * McKesson/Relay Health ||  ||   ||   ||
 * Massachusetts eHealth Collaborative ||  ||   ||   ||
 * Mayo Clinic ||  ||   ||   ||
 * MedAllies/GSI Health ||  ||   ||   ||
 * Medical Arts Rehabilitation, Inc ||  ||   ||   ||
 * Medicity || Eric Heflin || Yes || I suggest that we add the following statement to the charter: "When gaps have been identified where existing standards don't address a topic area, we will 1) identify an appropriate solution and then 2) propose such a solution to the relevant standards body." ||
 * MedPlus || Scott Chapin || Yes ||  ||
 * Microsoft Health Solutions || Sean Nolan || Yes || Sean Nolan for Microsoft ||
 * MITRE || Andy Gregorowicz, Anne Kling, Arnon Rosenthal, Elizabeth C. Halley, Marc Hadley, Saul Kravitz || Yes ||  ||
 * Mount Auburn Cambridge, IPA ||  ||   ||   ||
 * Mountain Medical Technologies ||  ||   ||   ||
 * National Council for Prescription Drug Programs ||  ||   ||   ||
 * National Health Data Systems, Inc. || Steve Beller || Conditional Yes (see comment: updated 10/7) || My endorsement depends on agreement of the following:
 * 1) A node-to-node architecture is acceptable, in which the Agent (node) of the Requestor and the Agent (node) of the Responder exchange information directly between each other. That is, the Requestor agent/node sends the query and retrieves the results, while the Responder agent/node retrieves the query and sends the results.
 * 2) The data stores accessed by the Responder need not be a database, per se, but may also be delimited files of any sort that contain the data of one or more patients. Any suitable query language can be used to query those files.
 * 3) A query may be for a non-aggregated ("raw") data result, raw data values are returned by the Responder(s) to the Requestor. The Requestor (instead of the Responder) may then aggregate the returned data if desired. ||
 * National Partnership for Women & Families ||  ||   ||   ||
 * National Quality Forum ||  ||   ||   ||
 * New York eHealth Collaborative ||  ||   ||   ||
 * NextGen Healthcare ||  ||   ||   ||
 * New York City Department of Health & Mental Hygiene || Michael Buck || Yes ||  ||
 * Ohio Health Information Partnership ||  ||   ||   ||
 * OptumInsight ||  ||   ||   ||
 * Partners Health Care ||  ||   ||   ||
 * Pfizer ||  ||   ||   ||
 * Practice Communication, LLC ||  ||   ||   ||
 * Quality Health Network

Quantal Semantics, Inc. || Tracy Rue ||

Yes but needs clarifications. See notes ||

The project manager and their responsibility is usually named in a project charter. This sentence needs to be made clearer: "The Initiative will develop models for the technical and financial sustainability as well as best practices for organizations, management and coordination, data use, data sharing; giving consideration to privacy, security and consent requirements.It will also address methods for extensibility of the clinical information model; specifically those data elements, terminologies, and code sets that enable the queries and results expression." Why is this in scope? "The pilot/reference Implementation sites will be selected based on national priorities and existing research and health information management infrastructure." In Target Outcomes it appears that this initiative will be specifying standards. Can we be clearer about what standards we are specifying? Are we specifying existing terminology standards? Are we specifying specific data elements for query and recommending use of defined terminology standards? Do you really think you'll finish a first round of requirements in October as per this Roadmap? I think the middle of December might be more realistic? What is a HISP? This will be an assumption that will not be met: "Obtain, create and maintain consents, authorizations, audit logs and access lists required to support Query Health implementations." I'm guessing that Query Health will need to provide guidelines for consent management or access to data will be difficult. ||
 * Redwood MedNet || Will Ross || yes ||  ||
 * Scientific Technologies Corporation ||  ||   ||   ||
 * SCS ||  ||   ||   ||
 * Serendipity Health, LLC ||  ||   ||   ||
 * Seton Hospital ||  ||   ||   ||
 * Siemens ||  ||   ||   ||
 * Southeast Michigan Health Exchange ||  ||   ||   ||
 * STEMSOFT Software, Inc ||  ||   ||   ||
 * Techsant Technologies LLC || Sri Koka || Yes with Comments || I would like to see more clarity on where the TOC scope stops and where this initiative's scope begins.- Sri Koka ||
 * Texas State University ||  ||   ||   ||
 * University of California, Davis ||  ||   ||   ||
 * University of California San Francisco ||  ||   ||   ||
 * University of Ottawa Children's Hospital ||  ||   ||   ||
 * University of Tennessee Health Science Center ||  ||   ||   ||
 * Vanderbilt University ||  ||   ||   ||
 * Virginia Information Technologies Agency (VITA) ||  ||   ||   ||

1st Round of Consensus (Saved 9/20/2011): [[file:Query+Health+Charter+-+Call+for+Consensus.pdf]]

 * 2nd Round of Consensus (Saved 9/28/2011):**[|Query+Health+Charter+-+Call+for+Consensus_2011929.pdf]

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