SDC+Kickoff+Q&A

include component="page" wikiName="siframework" page="Structured Data Capture Header"

Questions and answers from the SDC Kickoff meeting on January 23, 2013. Scroll to the bottom of the page to leave feedback.
> 1. **Question** from Keith Campbell: Re: Slide 10, SDC Success Metrics, how do we (A) standardize the semantics of Clinical Data Elements, and (B) deal with post-coordination of of the terminology standards. Are the these be part of the standard for the CDEs? Or additional standards? >> **Answer** from Kickoff: //This question will be addressed with the community. This would also allow us to discuss the pros and cons of LOINC and SNOMED.//

> 2. **Question** from Trish Whetzel: Is there a link to information on the underlying technology for the CDE portal? >> **Addressed** during Internal meeting: //This is a question for Lisa.//

> 3. **Question** from Stephen Beller: Is it likely that there may be CDEs that EHRs do not currently capture? If so, then would there be need for EHRs modules or middleware to help manage those supplemental data. >> **Answer** from Kickoff: //There are many CDEs that EHRs are not capturing. We want to enable a standard that will point to the CDE regardless of what system you are using or organization you are in. Ideally and ultimately, EHRs would be certified to do this.//

> 4. **Question** from Prableen Singh: Do CDEs follow a particular research information model? >> **Addressed** during Internal meeting: //This is a question for Lisa/Amy/community.//

> 5. **Question** from Samantha Spencer: In the Q&A, could you please speak to the clinical utility of creating the CDE data sets vs. using SNOMED and other existing standardized terminologies? Are CDEs just meant to be a collection of what is used in practice, to then map to these standardized terminologies? >> **Answer** from Kickoff: //CDEs are not in opposition to SNOMED, but rather they are an opportunity to use SNOMED or other standards to express constructs and patient assessment instruments that can be exchanged electronically. Research communities like Traumatic Brain Injury and Parkinson’s Disease have been at the forefront of identifying CDEs for their research; they have also identified important elements for the purposes of data sharing and data quality.//

> 6. **Question** from Keith Campbell: Is there a candidate starting point for the CDE standard? >> //Not addressed during Kickoff. **(11-179?)**//

> 7. **Question** from J. Michael Fitzmaurice (AHRQ): Will the powerpoint versions of all these slides be made available to today's participants? >> **Answer** in chat during Kickoff: //Jenny Brush: Yes, the slides will be available on the wiki after the meeting on the Meeting Artifacts page.//

> 8. **Question** from William Riley: Is this "common formats" for patient safety event reporting related in any way to the Common Terminology Criteria for Adverse Events? >> **Answer** from Kickoff: //The common formats are broad and can capture information about any type of adverse event, so there may be overlap. This is something we can explore further on the wiki.//

> 9. **Question** from Nikolay Lipskiy: The Surveillance Case report Form has been developed by the ONC S&I PH Reporting Initiative. How the CDS scope will be different regarding the PHRI task and scope for PH reporting Forms? >> **Addressed** during Internal meeting: //Evelyn will address with Doug/Jim/CDC team on 1/25/13.//

> 10. **Question** from J. Michael Fitzmaurice (AHRQ): At which of these 7 steps will the SIF initiative choose the data element name, definition, representation, base standard source, and other metadata needed for national reference? >> **Answer** from Kickoff: //The intent is for the two content workgroups is to tackle this particular question.//

> 11. **Question** from Stephen Beller: Is there willingness to look beyond XML to other useful data structures. >> **Answer** from Kickoff: //Yes, we hope to identify additional data structures during the community meetings.//

> 12. **Question** from Ken Pool: The process flow described prescribes that the EHR will pre-populate the form as opposed to having the form manager (using RFD terms) perform the pre-population. That seems that this approach will push us back to depending on development pace for EHRs. >> **Answer** from Kickoff: //The conceptual workflow is merely conceptual, and it is not intending to increase the burden or changing the workflow. This will be discussed, especially as we walk through Use Case development.//

> 13. **Question** from	Betty Tai: CDEs, in the end, will be those that are experts-consensused data or only those validated instruments and data or include both? even validated tool and data has its conditions to apply. How to determine CDEs in terms of validation process? >> **Addressed** during Internal meeting: //This will be addressed in the WG.//

> 14. **Question** from Victor Beraja: How will this apply to pre-populating insurance forms in prior authorizations? >> **Addressed** during Internal meeting: //This will be addressed in the WG.//

> 15. **Question** from Daniel Rubin: How realistic is it to expect physicians to do structured data entry? The mockup shown looked like it would disrupt the workflow, and physicians are already not big fans of EMRs. >> **Addressed** during Internal meeting: //This will be addressed in the WG.//

> 16. **Question** from Trent Rosenbloom: Research around the needs, value and utility of structured clinical entry versus narrative entry is lacking, and the presence of improving text processing methods and tools are constantly changing the balance between the two. It is unclear to me the degree to which this project will encourage all clinical documentation be entered via structured methods versus only certain high-value clinical elements. Can you speak to this? >> **Addressed** during Internal meeting: //This will be addressed in the WG, and is a question of scope—not everything can be structured.//

media type="custom" key="22014970" Note: Comments may take a minute to appear. media type="custom" key="22014982"

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