May+30,+2012+Agenda+and+Meeting+Minutes

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


 * Date: May 30, 2012**
 * Name:** Public Health Reporting Initiative Web Conference

Live Meeting: []
 * Location:** Conference Call: 1-866-842-6975; passcode: 218840#

**Agenda/Objectives:**

 * **Topic** ||= **Time Allotted** ||
 * Welcome / Agenda Overview - John Stinn ||= 4:00 - 4:05 ||
 * Functional Requirements - Lise Stevens / Anna Orlova
 * Activity Flow
 * Draft Document ||= 4:05 - 4:30 ||
 * Data Mapping - Nikolay Lipskiy ||= 4:30 - 4:40 ||
 * Stage 3 Readiness Self-Assessment - Seth Foldy ||= 4:40 - 4:50 ||
 * Discussion / Action Items ||= 4:50 - 5:00 ||
 * Adjourn ||= 5:00 ||

**Meeting Minutes**
__Functional Requirements__ __Data Mapping__ __Stage 3 Readiness__
 * Wiki page includes outline for functional requirements document, draft activity flow diagrams, and resources/references
 * Link to page is posted in the announcements section of home page or you can navigate to "Workgroup Pages" then "Functional Requirements Harmonization Workgroup"
 * Activity Flow Diagrams
 * Outline the actions involved in public health reporting
 * Draft has been posted to the wiki for review – use the discussion boards or email lrbrown@cdc.gov . Provide comments by COB on Friday, June 8, 2012
 * Activity Diagram illustrates what is in scope, out of scope, and important implementation considerations. It was a major topic of discussion during the working session 5/23/12 and was revised according to member feedback.
 * Also organized along ‘swimlines’ to clearly call out the actors and roles of those actors
 * Included a table to capture additional detail and specifications
 * Ask for membership:
 * Please review both diagrams if possible. If you only have time for one, the ‘activity flow diagram’ (the first diagram) is the most important for you to review
 * Also review the table to make sure we have captured with specific clarity the functions associated with each actor
 * Draft Document
 * Aim to post document by the end of the week for review and comment
 * Meeting June 8, 2012 to verify data elements that have been collected/compiled and begin identifying ‘core’ public health reporting data elements
 * Next steps
 * Will post data element spreadsheets and data element document for public comment
 * Will continue to work towards data modeling
 * Reconcile functional requirements with data mapping work
 * Once data elements and functional requirements are complete, we will go through a more formal consensus process to ensure our documents and work is eligible for inclusion in the S&I Document Repository
 * 11 self-assessments received
 * If you plan to send one, please let us know by emailing lrbrown@cdc.gov. It would also be helpful to know why you did not submit one, if you chose not to do so.
 * Key features
 * Differentiation between a highly bi-directional process or the provider-initiated submission of a report
 * Immunization information system – provider sending a request to receive an immunization summary about the individual. Will follow up to determine if this user story is fully in scope for our user story. (Remember the scope of our user story is the provider-initiated system)
 * Tobacco quitlines – outgoing message with a clear expectation for subsequent sharing of information from the quitline to the provider
 * Early hearing screening – 3 messages; 2 are provider-initiated documents to public health, but the third is shared from the public health program to the provider. The third document doesn’t quite fit into the current scope of the initiative – will follow up to determine if we can focus on the messages from healthcare to the hearing registry. (John Eichwald – this makes sense in terms of this initiative)
 * Variances in the extent to which there is consensus around the data elements and value sets by this October – several user stories indicated that there would not be consensus
 * These stories may not be ready for stage 3 implementation
 * HL7 2.5.1 (2.x messages) – many user stories indicated that their data exchange standard for message/document may fit in either 2.5.1 or CDA
 * Next steps – would like to meet with those stories that identify themselves as ‘stage 3 ready’ to determine
 * If these stories would like to be included in a harmonized approach from our initiative, or move towards stage 3 separate from the initiative.
 * If we should focus on HL7 2.5.1 or CDA or both
 * Need to discuss availability and willingness to move rapidly towards creating an implementation guide for those stories that would like to move forward in a harmonized approach

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