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.

Slides:



Advertisements
Similar presentations
Electronic Submission of Medical Documentation (esMD) eDoC Administrative Documents Templates for HL7 Orders October 25, 2013.
Advertisements

Functional Requirements and Health IT Standards Considerations for STAGE 3 Meaningful Use for Long-Term and Post-Acute Care (LTPAC) Update to the HITPC.
2014 Edition Test Scenarios January Contents Purpose of Test Scenarios3 Completed Work4 Current Work5 Using a Narrative Test Case Scenario to Develop.
Participation Requirements for a Patient Representative.
2014 Edition Release 2 EHR Certification Criteria Final Rule.
Longitudinal Coordination of Care (LCC) Workgroup (WG)
C-CDA Constraints FACA - Strategy Discussion June 23, 2014 Mark Roche, MD.
HITPC - Information Exchange Work Group Meaningful Use Stage 3 Subgroup 2: Care Coordination and Patient and Family Engagement Co-Chairs: Jeff Donnell.
Summary of Comments on the ONC Voluntary 2015 Edition Proposed Rule Implementation Workgroup Liz Johnson, co-chair Cris Ross, co-chair April 24, 2014.
Transitions of Care Initiative Consolidated CDA’s alignment with Meaningful Use Stage 2 NPRMs and ToC Recommendations 1.
2015 Edition Proposed Rule Modifications to the ONC Health IT Certification Program and 2015 Edition Health IT Certification Criteria.
Companion Guide to HL7 Consolidated CDA for Meaningful Use Stage 2
Overview of Longitudinal Coordination of Care (LCC) Presentation to HIT Steering Committee May 24, 2012.
Supporting Meaningful Use Stage 2 Transition of Care Requirements
Interoperability and Health Information Exchange Workgroup April 17, 2015 Micky Tripathi, chair Chris Lehmann, co-chair.
Proposed Meaningful Use Criteria for Stage 2 and 3 John D. Halamka.
Foundation of Nursing Documentation in nursing
Discussion of 2015 Ed. NPRM Certification/Adoption Workgroup HIT Policy Committee April 2, 2014.
Understanding and Leveraging MU2 Optional Transports Paul M. Tuten, PhD Senior Consultant, ONC Leader, Implementation Geographies Workgroup, Direct Project.
Meaningful Use Personal Pace Education Module: Transitions of Care.
Harmonization Opportunities Russell Leftwich. Past Harmonization Efforts Consolidated CDA (C-CDA) – IHE, Health Story, HITSP 32, HL7 – 3,000 ballot comments.
NWH TRANSITION OF CARE DOCUMENT FOR MU STAGE 2 JUNE 6, 2014.
Authentication, Access Control, and Authorization (1 of 2) 0 NPRM Request (for 2017) ONC is requesting comment on two-factor authentication in reference.
CMS Proposed Changes for Meaningful Use in Mark Segal, Vice President, Government and Industry Affairs, GE Healthcare IT May 1, 2015.
The Key to Writing Policies and Procedures Updated: February 2012 Public Health Nursing & Professional Development Unit Eunice Inman, RN Gay Welsh, RN.
Transitions of Care Initiative Companion Guide to Consolidated CDA for Meaningful Use.
Standards Analysis Summary vMR – Pros Designed for computability Compact Wire Format Aligned with HeD Efforts – Cons Limited Vendor Adoption thus far Represents.
LCC -Proposal for Next Steps August 28, Discussion Points Recap of Whitepaper Recommendations Critical milestones and activities driving LCC activities.
March 27, 2012 Standards and Interoperability Framework update.
HITPC Meaningful Use Stage 3 RFC Comments March 1, 2013 Information Exchange Workgroup Micky Tripathi.
Longitudinal Coordination of Care LCP SWG Monday, August 12, 2013.
Longitudinal Coordination of Care LCP SWG Thursday July 18, 2013.
10/27/111 Longitudinal Care Work Group (LCWG) Proposal to Re-Scope and Re-Name the LTPAC WG.
HL7 Child Health Work Group Update HL7 EHR-Public Health Task Force Andy Spooner, MD CMIO, Cincinnati Children’s Hospital & Medical Center Co Chair, HL7.
1 DICOM SR and CDA Rel SIR SIR is extract of Imaging Report Summary Imaging Report (SIR)  Patient Personal Record  Back to Referring Physician.
© 2015 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International.
HIT Standards Committee S&I and CDA – Update and Discussion November 16 th, 2011 Doug Fridsma, MD, PhD.
Provider Data Migration and Patient Portability NwHIN Power Team August 28, /28/141.
Mandatory Payload = MU2 Consolidated CDA. Qualifier: "leniency" (allowance for null or alternative codes) should be allowed in the following areas of structured.
Larry Wolf, chair Marc Probst, co-chair Certification / Adoption Workgroup March 6, 2014.
Standards Analysis Summary vMR –Pros Designed for computability Compact Wire Format Aligned with HeD Efforts –Cons Limited Vendor Adoption thus far Represents.
Longitudinal Coordination of Care. Agenda Confirm Community Work Streams Use Case and Policy Whitepaper Approach Recommendation for Use Case scoping.
Larry Wolf Certification / Adoption Workgroup May 13th, 2014.
MATT REID JULY 28, 2014 CCDA Usability and Interoperability.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
Nursing Process: The Foundation for Safe and Effective Care Chapter 5.
S&I PAS SWG March 20, 2012 Consolidated CDA (C-CDA) Presentation 1.
1 October, 2015 HL 7 Working Group Meeting. FDA UDI Rule – 9/24/2013 Unique device identifier (UDI) means an identifier that adequately identifies a device.
© 2012 Lantana Consulting Group, 1 Analysis Process.
HITPC Meaningful Use Stage 3 RFC Comments July 22, 2013 Information Exchange Workgroup Micky Tripathi.
Standards Analysis Summary vMR – Pros Designed for computability Compact Wire Format Aligned with HeD Efforts – Cons Limited Vendor Adoption thus far Represents.
360Exchange (360X) Project 12/06/12. Reminders / announcements 360X Update CEHRT 2014 / MU2 Transition of Care Requirements 1 Agenda.
© 2015 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International.
Longitudinal Coordination of Care Use Case Scoping Discussion 3/19/2011.
Longitudinal Coordination of Care LCP SWG Thursday, July 11, 2013.
Interoperability Measurement for the MACRA Section 106(b) ONC Briefing for HIT Policy and Standards Committee April 19, 2016.
Health Management Information Systems Unit 3 Electronic Health Records Component 6/Unit31 Health IT Workforce Curriculum Version 1.0/Fall 2010.
Clinical Documentation Hearing Recommendations Meaningful Use and Certification and Adoption Workgroups Paul Tang, MU Workgroup Chair Larry Wolf, C&A Workgroup.
HL7 C-CDA Survey and Implementation-A- Thon Final Report Summary Presentation to the HL7 Structured Documents Work Group on July 14, 2016.
Nutrition in HL7 Standards
Nutrition in HL7 Standards
HL7 Consolidated CDA “Relevant and Pertinent” Project
Setting the Stage Health information exchanges (HIEs) are participating in quality measurement through the Qualified Clinical Data Registry (QCDR) program.
HL7 WGM Madrid May 2017 Care Plan Standards Update
An Overview of Meaningful Use Proposed Rules in 2015
Nutrition Care Plan: Stakeholder Call
Relevant and Pertinent Findings and Recommendations
HL7 Consolidated CDA “Relevant and Pertinent” Project
Health Information Exchange for Eligible Clinicians 2019
Presentation transcript:

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 Data Set (CCDS) has been expanded with specific C-CDA sections related to Care Plan  CCDS is required in Transition of Care (ToC) exchanges  The net effect looks like a conflation of ToC documents and parts of Care Plan ◦ Will this be what clinicians want? ◦ Will developers know what they should do?

 ToC objective in MU2 is being met by summary documents such as CCD, Consultation Note, Discharge Summary…  ToC document in 2015 edition is not significantly different, except for expanded CCDS. Most vendors will probably want to continue producing the same doc types  Care Plan document is brand new in 2015 edition, and follows C-CDA as intended

A couple of commenters expressed concern regarding whether this proposal aligned with the C-CDA standard… A few commenters noted that we should clarify the intent of the “Goals Section” and “Health Concerns Section.” These commenters noted that the “Goals Section” and “Health Concerns Section” of the C- CDA Care Plan document template provide more structure and were originally designed to be used with the Care Plan document template. However, other C- CDA document templates, like CCD, allow for health concerns and goals to be included as a narrative within the “Assessment Section (V2),” “Plan of Treatment Section (V2),” or “Assessment and Plan Section (V2).”

We have reviewed the CCDA 2.1 standard and believe there is no misalignment…Therefore we have adopted the specific data elements as proposed (i.e., “Assessment Section (v2)” and “Plan of Treatment Section (v2)” or “Assessment and Plan Section (v2);” Goals Section;” and “Health Concerns Section”). We clarify that we will certify Health IT Modules to the “Goals Section” and the “Health Concerns Section” from the Care Plan document template for the purposes of meeting the Common Clinical Data Set definition. Thus, other C-CDA document templates such as CCD, Referral Note, and Discharge Summary would need to be able to exchange the structured “Goals Section” and “Health Concerns Section” in order to meet the “Common Clinical Data Set definition.”

 Care Plan document SHALL contain Health Concerns and Goals sections  CP SHOULD contain Interventions and Health Status Evaluation & Outcomes sections (note: Cert Rule requires these in Care Plan doc)  ALL of these sections are only specified in a Care Plan document  Care Plan SHALL NOT contain a Plan of Treatment Section (V2) (CONF: )

 PoT (known as “Plan of Care” section in CCDA 1.1) was renamed in CCDA 2.x.  PoT is required in Discharge Summary, optional in other document types, but prohibited in Care Plan  PoT section includes narrative and may include structured entries such as “planned x” where x can be act, encounter, immunization, medication, observation, procedure, or supply. May also include Goal observation, handoff communication participants, instruction, nutrition.  Most EHRs probably don’t create structured PoT section; if structured, there was little or no guidance. Care Plan document attempted to provide a better structure  “Assessment” + “PoT” sections are logically equivalent to the single “Assessment and Plan Section”

 First Impression: the Rule introduces issues ◦ Internal Redundancy because Assessment and PoT section(s), Health Concerns and Goals sections must now be in the same document ◦ Overlap between ToC and Care Plan certification criteria ◦ Increased size of ToC document ◦ Potential Confusion:  Developer: which data goes in which sections and entries?  Provider: where do I find the Plan? Is it in one place or several? ◦ Care Plan document is co-opted by ToC document. If produced, much of it is redundant with ToC doc. (Note: Care Plan is a certification requirement, but not a MU3 requirement)  Is this a major problem, or not a problem, or something in between that can be clarified by guidance?

 Clarify how to implement ToC such that it is relevant and pertinent to clinicians, right-sized, easily readable, internally consistent, non-redundant, not “choppy”  Clarify Range of Care Plan Info: longitudinal patient- centered vs provider/encounter-specific? If both, what goes where?  Expand Care Plan diagram, showing relationships among sections and entries beyond the original CP document (Lisa’s PACP diagrams are an example). For example, should PoT Section be a shell that points to other sections?  Dual-compliant ToC/CP document that adds remaining Care Plan sections (Interventions, Health Status Evaluation). At least that would be holistic, rather than having “half a Care Plan”  Ideas?