ToC+Standards+Analysis+WG+Meeting+2011-07-06

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

Standard Analysis WG Meeting Minutes

 * Date:** 07-06-2011
 * Time:** 1:00-2:00pm EDT
 * Dial in:** 1-408-600-3600 **Passcode**: 669 491 394
 * Meeting Agenda: Click here for the agenda!**

Attendance
Robin Barnes, Amy Brantley, Mark Braunstein, Bob DeAnna, John Donnelly, Patty Grimes, Emma Jones, John King, Russell Leftwich, Patricia MacTaggart, Erik Pupo, Sandy Stuart, Cyndalynn Tilley, Steven Waldren, Bob Yencha

Action Items

 * **#** || **Date Initiated** || **Action** || **Owner** || **Status** || **Date Closed** ||
 * 1 || 07-06-2011 || Begin working on Data Element Sets that need to be exchanged in Content Module Index and show correlation || John Donnelly || Open ||  ||
 * 2 || 07-06-2011 || Provide feedback on how Nursing Documentation as it relates to Standard Analysis, TOC and CDA document exchange work || All || Open ||  ||
 * 3 || 07-06-2011 || Develop a statement and provide feedback on Standard Selection Process focusing on baseline standards for Reference Implementation || All || Open ||  ||

Agenda Items

 * 1) Welcome and Announcements (Meredith Lewis)
 * 2) Review Content Module Index (John Donnelly)
 * 3) Next Steps (John Donnelly; Meredith Lewis)

Meeting Notes

 * Content Module Index** (Reviewed by John Donnelly)

Data Elements Set Tab/Section Consolidation-Category Nursing Documentation topic: Shows expression of Data Element Sets from use case simplification work, Nursing Documentation is a part of clinical events and needs to be included in Transitions of care


 * Patty Greim question**- Why is this WG specifying nursing language in Standards Interoperability, SNOMED CT is the chosen language? Why are we covering same ground in another format?
 * Patty Greim comment**- SNOMED can increase content and then there is no need for any ancillary vocabularies.


 * Bob Yencha comment**- We have a need to account for nursing documentation at this point the nursing communication has number of terms and no distinction on which one is used. The end target is SNOMED if specific use case with the same information and SNOMED may not have codes maybe a selection of another terminology. If there was a code gap the coding would be SNOMED but the value would be an alternative.


 * Russell Leftwich comment**- The Care Planning WG did not create this deliverable


 * Bob Yencha comment**- Remove nursing documentation from main view and focus on work core constituents have agreed upon.


 * John Donnelly comment**- Nursing documentation is mentioned in to tab of the Content Module Index in the Data Element Sets/Section Consolidation-Category tabs. What is correct representation of nursing documentation in the Content Module Index artifact?


 * Patty Greim comment**- The text included in the CIM document states “Any nursing vocabulary that maintains a integration with SNOMED CT is a candidate for the spreadsheet” because SNOMED CT is recommended for interoperability in an exchange.


 * Standard Selection Process** (Reference Implementation)
 * Put together a statement (use as a guidance to transformation- Use work completed by CDA Consolidation WG for each section HL7 HITSP and IT work to come away with a solution)
 * Reach consensus on reference implementation baseline standards
 * Build around CDA documentation work. Will use this process to comply with requirements in use case and express the exchange

Next Meeting

 * Date:** 07-13-2011
 * Time:**1:00-2:00pm EDT
 * Dial in:** 1-408-600-3600 **Passcode**: 667 035 388

Reference Materials

 * 1) ToC Content Module Index

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