Minutes+October+12,+2011

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

Call in number: 866-842-6975 with pass code: 218840# Web Conference: []
 * Date: 10//12/2011**
 * Time: 4PM - 5PM EDT**
 * Dial in:**

Files for use during this call:
 * Meeting Agenda:**
 * **Time** || **Topic** ||
 *  4:00-4:05 || Welcome & Intro, John Stinn ||
 * 4:05-4:10 || Update from ONC, Riki Merrick ||
 * 4:10-4:35 || PH Reporting Standardization Framework presentation, Anna Orlova ||
 * 4:35-4:50 || Update on Tasks from 10/5, Riki Merrick ||
 * 4:50-4:55 || Proposed Project Tasks/Timeline, John Stinn ||
 * 4:55-5:00 || Review of Action Items, Lise Stevens ||

Attendance
Anand Ambrose, Anna Orlova, Art Davidson, Barbara Walker, Bill Brand, Cindy Vinion, DB, Erik Pupo, Genny Barkocy-Gallagher, Hwa-Gan Chang, Jim Kirkwood, Joel Greenspan, John Abellera, John Loonsk, John Roberts, John Stinn, Kathy Walsh, Kevin Stevens, Kim Gadsen-Knowles, Laura Conn, Lei Zhang, Les Westberg, Lisa Ferland, Lise Stevens, Lynn Giljahn, Mark Marostica, Mike Colleta, Nedra Garrett, Nikolay Lipskiy, Noam Arzt, Riki Merrick, Roniqua Watkins, Seth Foldy, Shu McGarvey, Starla Ledbetter, Steve Modesitt, Sundak Gansesan, Wendy Blumenthal, Wendy Scharber, Xidong Deng

Action Items
(see: http://wiki.siframework.org/file/view/PH%20ReportingStandardizationFramework-10-12-11.ppt) || ALL || open || 10/21/2011 ||  ||
 * **#** || **Date Initiated** || **Action** || **Owner** || **Status** || **Due Date** || **Date Closed** ||
 * 1 || 10/12/2011 || Comments on Standardization Framework concept, including review of the business processes
 * 2 || 10/05/2011 || Prioritizing the list of terms for defintions (see: http://wiki.siframework.org/file/view/S%26I_PHReporting_Definitions20111010.xlsx) || ALL || open || 10/14/2011 ||  ||
 * 3 || 10/05/2011 || Adding definitions we can adopt – suggest forming a subgroup – possibly vocab to provide this strawman || Vocab WG/ALL || open || 10/26/2011 ||  ||
 * 4 || 10/12/2011 || Post documents related to minimum data sets and the HL7 CDA guide || Leads || open || 10/14/2012 ||  ||
 * 5 || 10/12/2011 || Start consensus vote on user story selection criteria document || ALL || open || 10/19/2011 ||  ||

Meeting Notes
Riki started the call @ 4:03 PM. Introduced Mr. John Stinn, (Deloitte) as the facilitator. John provided an overview of his role as a facilitator (wiki updates/logistics) and his background in supporting other S&I initiatives.

ONC Update (Riki): Provided an overview of our teleconference with ONC reps Jitin Asnaani and Merideth Vida. There is some interest from ONC; however, there is a need to crystallize our immediate goals, especially the need to break down the work such that there are measureable deliverables due in 6-9 months. The first deliverable is an implementation guide that can be used to cover reporting for a variety of use cases, focusing on the core set of data elements that can be best applied across one use case with multiple user stories.

Questions/Discussion:

Seth: Is there a substantial difference in what we conveyed in our charter versus the expectations/terms used by ONC? There are no major differences in the overall approach or deliverables, but we are using different terms.

Genny requested to consider capturing occupation across all use cases as one of those core elements.

Art Davidson: What is the difference between the one guide and multiple PH program areas versus one use case and multiple stories? Does this mean we would get only one of the PH program areas listed on the slide?

Riki: The difference is the terminology – the one guide should capture core elements for all those bullets listed below

John Loonsk: There is one guide for ELR, Immunizations and Syndromic Surveillance. There is a concern about how to we could combine the requirements for multiple PH use cases when the trend has been to create separate guides. The HL7 CDA R2 document with multiple templates could be a potential way to support the requirement.

Les Westberg: During the recent ONC Policy Committee meeting there was a reference to one IG, but not sure what this relates to.

Seth: I am not aware of a single standard, although the ONC Standards Committee did suggest to go to just a single version for MU stage2, which will be v2.5.1. I want to make clear that we are not seeking a single guide for ALL of PH reporting; however, we are seeking a common domain set of requirements that can be used to help create a base for PH reporting.

Les has had a role in NHIN architecture group and development of model driven architectures and creation of open health tools that can build templates on top of CDA documents once the model is created. We may want to consider this as an option for creating the guide.

We discussed the need to be sure we include the International Society for Disease Surveillance (ISDS) minimum data set (that was part of a presentation by John Halamaka to the Policy Committee) in our work.

Lise: The CDA guides published for Hospital Acquired Infection and Immunization reporting used a common CDA construct for capturing data elements and supports the additional layer or template that is unique for each program.

Wendy Blumenthal: In Cancer we did not use that CDA document as our reference construct, but instead created “children” of the CCD sections in our document. We also have compared how well this aligns with other similar approaches.

Action item : Need to research the HL7 CDA for public health reporting, including other guides, and all relevant documents and post to the wiki as reference material for this initiative. The goal is to review this material and determine how/if we can leverage this body of work to inform our approach for meeting ONC’s request to create an implementation guide that can be “broadly” applied across several PH reporting use cases.

Anna’s presentation began at 4:25P

Questions/Discussion

Does the generalizable set of language (as reflected as common business processes) imply that the underlying architecture is also generalizable? Yes we think so.

Les: Making a single guide for all of PH in 9-12 month will not work. Concentrate on the 32 data elements identified as the minimum set in ISDS would need to be included.

Anna: Hoping to not only use the 3 domains that contributed to the data set in MU stage 1 but expand beyond those use cases.

Action item: Consider the business processes described in the presentation and provide comments about whether they accurately describe the breadth of scope of PH reporting activities and if they should be considered as part of our scoping exercise for selecting use cases and development of the consolidated guide. Comments due 10/21

Action Items from previous meetings: Riki

Terms and definitions used in Anna’s presentation: Riki consolidated some of the terms with others that were started last week. A spreadsheet has been created and posted to the wiki. We should establish a sub-group to begin working on a straw-man document that the larger group can begin to work with. First pass of terms due 10/14 – indicating prioritization of those terms where we need to create our own definitions vs. adopting definitions from other initiatives.

Definitions are due 10/21. Added the terms “implementation guide” and “optionality” as suggested by John Loonsk. Anna suggested we also add “use case” during the call. There was a concern about how to manage different versions of the document. Nikolay and Riki will manage the versions of the document.

Need to add new topic regarding the core set ISDS elements to draw from.

We will initiate the formal voting process for use case selection criteria at our next scheduled meeting. Since there is an S&I Framework meeting scheduled next week, we agreed that our next meeting will be held 10/26 4-6PM EST

Next Meeting
Web Conference: []
 * Date:10/26/2011**
 * Time: 4PM - 6PM EDT**
 * Dial in:** 866-842-6975 with pass code: 218840#

Reference Materials

 * Note: This template serves as a base layout for capturing and structuring meeting minutes. Please recognize that the structure may change to meet individual WG needs.

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