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

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


 * Date: May 2, 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 ||
 * Use Case - John Stinn
 * Review of public comment
 * Final version posted to wiki ||= 4:05 - 4:15 ||
 * Data Mapping Update - Nikolay Lipskiy ||= 4:15 - 4:25 ||
 * Functional Requirements Update - Anna Orlova / Lise Stevens ||= 4:25 - 4:35 ||
 * Communications Update - Mike Coletta / Therese Hoyle ||= 4:35 - 4:40 ||
 * Stage 3 Meaningful Use Deployment Update - Seth Foldy
 * Self Assessment Tool ||= 4:40 - 4:50 ||
 * Virtual Meeting - John Stinn ||= 4:50 - 4:55 ||
 * Adjourn ||= 5:00 ||

**Meeting Minutes**

 * Use Case (John Stinn)
 * Public comment period is now closed; have received several sets of feedback; some were accepted without need for discussion
 * Worked with each respondent one-on-one to understand feedback/concerns and try to accommodate the suggestions in the document
 * Offered opportunity for those who submitted feedback to comment on the call
 * Kevin McAloon asked about coding and analytics around ICD10 (diagnostic codes) in the future; Seth Foldy mentioned an HHS group regarding ICD10 implementation
 * In relation to NY State communications, current document focuses on the exchange, which is an architecture component; as we move into pilot and demonstrated, the workflows from both clinical and public health settings will need to be elaborated and tested; this isn’t limited to just NY State, this comment probably applies to others
 * Feedback included working towards consistency in terminology, clarification on actors, flow
 * Final version of the Use Case has been posted to the wiki
 * Data Mapping Update
 * Data Harmonization Timeline – data harmonization within domains and core electronic elements will be complete this week; validating the elements in the harmonized spreadsheets with the community and user story submitters; working to identify gaps with clinical care
 * In May, will work on document to capture final data elements and mappings as well as gaps and clarifications – this will be an input to existing models such as Federal Health Information Model (such as FHIM)
 * Functional Requirements (Anna Orlova / Lise Stevens)
 * Co-leads reviewing documents for functional requirements analysis and standards selection
 * May need an additional document to describe this work
 * Information system functional and nonfunctional requirements, triggers, actors, schema across actors, data harmonization profile as a reference, as well as standards that may be relevant to the use case
 * Outline should be ready to be shared next week; will ask for input on this document and request input to the focus group for writing and standard selection (May – June); this document may inform implementation guide and technical specifications
 * Kevin McAloon – need to define users of the documents because use cases and functional requirements may vary based on these users
 * A report traveling through this exchange may travel to several different systems; these end (receiving) systems have different needs – our job is not to design those systems (do need to understand the needs), but to focus on the //__message__// coming in and the interface handoff; we recognize limits due to changes; we are not getting into receiver requirements – any considerations of these are in what was originally submitted
 * Surveillance for action may be a future step/ phase
 * Functional requirement types:
 * Collect, manage, analyze, integrate and use data
 * Need a further discussion on terminology: triggers, functional requirements, etc
 * Triggers become functional criteria (triggers can be send or receiving criteria – we are not working on the pull from EHR here
 * Need to continue to work with submitters to make sure the trigger criteria are defined correctly
 * Communications Update
 * Published an FAQ last week – some of the scope discussion on the call today is addressed there
 * Future publications will relate to harmonization to translate these more technical documents for other audiences
 * Stage 3 Meaningful Use Deployment (Seth Foldy)
 * Deploying a self-assessment tool for user story submitters/stewards to complete
 * A harmonized set of elements, standards, value sets, etc is valuable
 * Would also like a specification for some type of public health reports in time for consideration for adoption in Stage 3 of meaningful use (decisions will be made in about 20 years)
 * Working towards identifying user stories with a high degree of consensus that is ready for specification and pilot (including senders and receivers) and users that are ready – this tool is working towards to gathering this information
 * __Asking for completion of the forms in the next three weeks (May 23)__
 * We do believe there will be further specifications and future phases, so even if you aren’t ready now, do still consider this.
 * Send completed tool and/or questions to John Stinn (jstinn@cdc.gov) and Lindsay Brown (lrbrown@cdc.gov)
 * Virtual Meeting
 * Expect a placeholder for a 2-hour block of time in May

Presentation


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