CDA Document ‘Executive’ Summary Section

Slides:



Advertisements
Similar presentations
CDM Registry Project Dr. Richard Lewanczuk Regional Medical Director Chronic Disease Management Capital Health.
Advertisements

Chapter 12 – Strategies for Effective Written Reports
S&I Data Provenance Initiative Presentation to the HITSC on Data Provenance September 10, 2014.
RECON: Interventions, Goals, Providers Brief Profile Proposal for 2014/15 presented to the Patient Care Coordination Planning Committee PCC Technical Committee.
IHE Radiology –2007What IHE Delivers 1 Christoph Dickmann IHE Technical Committee March 2007 Cross Domain Review PCC.
Patient Care Coordination Tone Southerland Greenway Medical Technologies Co-chair, IHE PCC Marcia Veenstra Senior Health Inc. Co-chair, IHE PCC Nursing.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
Dynamic Document Sharing Detailed Profile Proposal for 2010 presented to the IT Infrastructure Technical Committee Karen Witting November 10, 2009.
Standards Analysis Summary vMR –Pros Designed for computability Compact Wire Format Aligned with HeD Efforts –Cons Limited Vendor Adoption thus far Represents.
CISB 334 E-Business BUSINESS PLAN. What is Business Plan ?  A document that provides a framework for testing the business from conception through early.
Occupation Health Data Encoding Brief Profile Proposal for 2012/13 presented to the Patient Care Coordination (PCC) Planning Committee Lisa R. Nelson October,
Indian Health Service Suicide Reporting Form (SRF)
Dynamic Data Brief Profile Proposal for 2009/10 presented to the IT Infrastructure Planning Committee Karen Witting September 30, 2009.
HL7 SDWG Topic October 29, 2015 David Tao.  HL7 Success! C-CDA 2.1 is cited, and Care Plan is in 2015 Edition Certification Final Rule  Common Clinical.
S&I PAS SWG March 20, 2012 Consolidated CDA (C-CDA) Presentation 1.
1 THE REVIEW OF LITERATURE CHAPTER 2 PREPARED BY: MUKUNDA KUMAR.
Eschool documentation break out session
Health Management Information Systems Unit 8 Consumer Health Informatics.
Grant Proposal Writing
Electronic Submission of Medical Documentation (esMD) electronic Determination of Coverage (eDoC) PMD Discrete Data Definition October 30, 2013.
Patient View Visit Summary profile proposal George Cole, Allscripts Emma Jones, Allscripts.
AHIMA-IHE White Paper HIT Standards for HIM Practices 2015 Figures.
Dynamic/Deferred Document Sharing (D3S) Profile for 2010 presented to the IT Infrastructure Technical Committee Karen Witting February 1, 2010.
Use Case Model Use case description.
Abstract  An abstract is a concise summary of a larger project (a thesis, research report, performance, service project, etc.) that concisely describes.
Clinical Documentation Hearing Recommendations Meaningful Use and Certification and Adoption Workgroups Paul Tang, MU Workgroup Chair Larry Wolf, C&A Workgroup.
1 © 2007 Chapter 3 Strategic Planning for the EHR Migration Path.
1 Team Skill 3 Defining the System Part 1: Use Case Modeling Noureddine Abbadeni Al-Ain University of Science and Technology College of Engineering and.
HL7 C-CDA Survey and Implementation-A- Thon Final Report Summary Presentation to the HL7 Structured Documents Work Group on July 14, 2016.
Elements of Non Fiction
eHealth Standards and Profiles in Action for Europe and Beyond
1.10 Report Findings to Communicate Research Information to Others
MODULE 7 Creating the Facility Software Surveillance Plan (SSP)
Vital Registration and Care Coordination for Newborn Hearing Screening
AHIMA-IHE White Paper HIT Standards for HIM Practices 2015
OpenNotes: Expanding patient access to clinical notes
WP1: D 1.3 Standards Framework Status June 25, 2015
FHIR PlanDefinition for Care Planning
16 Personal Health Records.
Understanding Informational Text
HL7 WGM Madrid May 2017 Care Plan Standards Update
Business Plan Template
Perkins Annual Reports
Setting the Stage Health information exchanges (HIEs) are participating in quality measurement through the Qualified Clinical Data Registry (QCDR) program.
Telling Your SSIP Story
Patient Care Workgroup Care Plan Topic
Patient Care Coordination Dynamic Care Team Management Profile (DCTM)
Community Health Roundtable
an alliance among HL7, CEN and OpenEHR ?
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CP.1.6 Manage Immunization List aka DC in EHR-S FM R1.1
Case studies – a short guide to writing case studies
EDD/581 Action Research Proposal (insert your name)
Background Health information exchanges (HIEs) are becoming Qualified Clinical Data Registries (QCDRs) to measure and report quality performance Both.
Use Case Model Use case diagram – Part 2.
Semantic Interoperability
Understanding Informational Text
Training & Development
Chapter Four Engineering Communication
PowerChart Overview Tab New Feature for Physicians
Text Structure English 7 & 8.
, editor October 8, 2011 DRAFT-D
Letters, Envelopes, and Memos
Chapter Four Engineering Communication
Chapter Four Engineering Communication
EDD/581 Action Research Proposal (insert your name)
Text Structure English 7 & 8.
Formal reports are distinguished from informal letter and memo reports by their length and by their components. Though long reports can vary in format.
Basic Data Provenance April 22, 2019
US Core Data for Interoperability (USCDI): Data Provenance IG
Health Information Exchange for Eligible Clinicians 2019
Presentation transcript:

CDA Document ‘Executive’ Summary Section Presented by Emma Jones, Daniel Venton, George Dixon - Allscripts

The Problem(s) Current CDA content profiles do not capture a concise synopsis about the document that the author need to communicate to the reader (e.g. provider to provider and/or to the patient). Some CDA documents contain elements with linkages to other elements that is often not represented in a way that effectively portrays the clinical picture. CDA documents often contains large amounts of information that makes it difficult to identify pertinent information in an efficient way.

Use Case 1 ‘Synopsis’ Section – Provide a brief cover note that one provider writes to the next provider. This provides a place for the document author to explain the purpose of the document, what should be done, what portions or items in the document should get special attention, etc.

Use Case 2 Care Plan Nesting Summarization – Consolidated CDA Care Plan document provides the ability to link entry templates together to tell the care planning story. IHE PCC Patient Care Plan Profile provides the ability to nest sections within sections Providing an easy view of how care plan components are linked and nested, without forcing the traversing across various sections, will be very helpful to the user. User is still able to view the entire document if needed.

Standards & Systems Standards Systems EHR PHR Patient Portal HIE CDA R2 IHE PCC Medical Document Consolidated CDA FHIR HTML Rendering??? Systems EHR PHR Patient Portal HIE

Discussion Provide a concise view of a document based on a summary of specific user expectations can be time saving for a provider. Provide a way to reflect what the patient need to see so that the large amount of information in the CDA document is provided but at the same time not become overwhelming. Depending on use case, a Summary Section can be added to a document, summarizing pertinent information populated by some of the data in the various sections to create a composite, single Summary section. A summary section can also be used for the author of the document to describe pertinent information about the document Further exploration and discussion needed.

New Optional CDA Summary Section CDA Document Care Plan Executive Summary (with nested elements) New Optional CDA Summary Section CDA Document Sections Health Concern Section Goals Section Interventions Section Outcomes Section

Questions? Could this be something that can go in xds description? How is this going to succeed with existing efforts for similar profiles? e.g. Cardiology procedure note (document summary section – concise narrative). Proposal captures multiple problems – should we treat as multiple work items? Need to determine how to structure this. Describe each problem separately.