Jan+4,+2012+Agenda+and+Meeting+Minutes

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


 * Date: January 4, 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 ||
 * Action Item Review - John Stinn ||= 4:05 - 4:10 ||
 * User Story Domain Update
 * Communicable Diseases - Nikolay Lipskiy
 * Adverse Events - Lise Stevens
 * Child Health - Anna Orlova
 * Chronic Disease - Riki Merrick
 * Infrastructure/Quality/Research - Anna Orlova / Lise Stevens ||= 4:10 - 4:25 ||
 * Identified Issues / Clarification - Lise Stevens
 * Workflow items
 * Stakeholder requirements agreements
 * Open Decision Points: Scope (lab reporting, billing) ||= 4:25 - 4:35 ||
 * PHRI Use Case Schedule - John Stinn ||= 4:35 - 4:40 ||
 * Other Open Items
 * Definitions Sub-Working Group - Riki Merrick
 * Standardization Framework Narrative - Anna Orlova ||= 4:40 - 4:50 ||
 * Action Items / Next Steps - John Stinn ||= 4:50 - 5:00 ||
 * Adjourn ||= 5:00 ||

**Meeting Minutes**

 * __Welcome__**
 * Reviewed the agenda and roll call for those on the phone.
 * Recap of current progress
 * Working on a consolidated use case based on the content provided by the working groups in the tool sheets and templates.
 * Consolidated use case will be shared with members for review in the next couple of weeks (end of January 2012)


 * __Use Case / User Story Domain Updates__**
 * Communicable Disease - Nikolay Lipskiy
 * Received 10 user stories
 * Two places for initiation of report: EHRs and Laboratory systems, therefore, two consolidated user stories were developed
 * Shared the flow of events, pre-conditions, post-conditions, and actors for both consolidated stories
 * There are some outstanding questions about Healthcare Acquired Infections - these will be discussed later and should not affect the current process
 * Data modeling will start soon - except communication about classes and data elements for data flow, description and vocabulary
 * Adverse Events - Lise Stevens
 * Reviewed the template and highlighted that issues will be discussed later in the agenda
 * Involves reporting from EHR and hospital incident reporting systems
 * Timing will vary - timing of adverse events is when the event is discovered, there may be interim steps that take place before it is sent
 * Will need to circle back with the workgroup on this template to discuss data categories
 * General comment: There can be automated response from EHR and lab reporting (not linked to EHR). If the hospital doesn't require approval for PH Reporting process, auto-reporting will work well; but, that may not always be the case and this review step should be addressed in the workflow (discussion of manual v. automated processes).
 * Discussion
 * David highlighted the HAI concern (and various sources)
 * Anna commented that billing systems are usually run separately; the user story for administrative data calls for billing data. There is a similar issue with quality measures for hearing screening. Should these issues be sub-processes or an expanded scope?
 * Will suggested that we document the recommendation(s), and as we move into functional requirements and modeling we can look for opportunities to harmonize.
 * Child Health - Anna Orlova
 * No additions to what the workgroup reported out on the last call
 * Discussion about the data category column
 * May need a better title/label, but like it's inclusion in the template
 * Riki suggested "data artifacts" as not everything listed is a data category
 * How can this be linked to information modeling?
 * This is something that can be discussed further and is being considered. Should expect some recommendations/resolution in the near future.
 * Chronic Disease - Riki Merrick
 * No additions to what the workgroup reported out on the last call
 * Next steps - user story submitters to group data elements based on existing models (no completion date assigned yet)
 * Chronic deals with three systems - may consider a single system in the future
 * Infrastructure/Quality/Research
 * No comments

During the call, questions were raised about how to post comments to the wiki about consolidated user stories. The support team will send additional details/instructions for doing this. Additionally, we can find time in future calls to demo wiki functionality.

At this point in time, all consolidated user stories that have been developed have been posted to the appropriate wiki page (to navigate to domain pages, click on "User Stories" then the appropriate domain).


 * __Identified Issues / Clarification__**
 * Workflow items
 * Example: Immunization is performed and is sent to a PH agency. If a patient has an adverse event later, that could be considered 'follow-up' information to the PH Agency, but for the Adverse Event it is considered the initial report. Initial report is in scope, but follow-up is not. Suspect this will create similar issues for communicable disease and laboratory reporting.
 * Need to consider this when we get to functional requirements
 * Stakeholder Requirements Agreements
 * There are different statutory requirements for institutions. Therefore process flow and information used to populate the report may vary.
 * Open Decision Points - Scope (lab, billing)
 * Several systems interfacing and data resides in multiple instances. Need to be mindful of reconciling data and the flow between systems. Also, need to consider that some providers are paper based. If we're looking to automate the workflow, what subsets of data go to modules to populate the report.
 * Follow-up report discussion
 * Follow up reports may be very different and mor detailed (including additional interfaces) and were considered out of scope for this endeavor. Need to discuss how to consider the actor, fields, and records. The content needs to be very specific and should be considered in the data modeling phase. Need to remember why the initial report is sent - to initiate a PH activity. The determination of "Follow-up" may differ based on the system used to define the term (e.g., "follow-up" from EHR is an additional report for any patient, whereas "follow-up" for PH Agency is a report for the same case with additional information). Should we be considering "reporting", rather than initial/follow-up.
 * Need to have a follow-up discussion about these reports and how the details will be addressed in modeling and functional requirements.

January 25 (appx) - share PHRI consolidated use case with members for review/comment February 8 (appx) - finalize PHRI consolidated use case
 * __Schedule Items__**


 * __Discussion__**
 * There will be a call about Definition review next week (Jan 11, 2012). Direct questions to Riki Merrick.
 * Anna Orlova mentioned that there will be meetings coming up in the next few weeks (e.g., HL7) that may be good opportunities to present on this work. Need to prepare a presentation for such events, even if we are not on the agenda. Will work with others to determine if a presentation can be put together for HL7.
 * Nikolay Lipskiy mentioned that data modeling discussions will begin soon.

Powerpoint Slides


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