eDoC+Workgroup+Charter

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

To view the esMD eDoC Workgroup Charter document please To view the esMD eDoC Workgroup Charter consensus page please Click Here

Announcements Thank you for your participation!! As of February 19th, 2013 the esMD eDoC (electronic Determination of Coverage) Workgroup Charter has been finalized. The document below as well as the text embedded within the Wiki reflects updates that were proposed and agreed upon during the formal Consensus Process. Please contact the Workgroup Lead or Support Lead if you have any remaining questions or concerns. =**Electronic Determination of Coverage (eDoC) Workgroup Charter **=

Challenge Statement
The Centers for Medicare and Medicaid Services (CMS) and other Health Plans/Payers need a standardized, implementable, machine-interoperable electronic solution to reduce the time, expense, and paper required to document patient conditions as part of current processing of benefit determination based on payer coverage rules. The key challenges to be addressed include the following: A. Define coverage determination documentation requirements as structured data sets and templates B. Determine standards to enable provider (or service supplier) capture of documentation based on payer rules C. Define decision support rules to facilitate provider decision making and preferred order management in light of payer standards D. Determine secure exchange of documentation between payers, providers, suppliers and beneficiaries E. Determine standards for digital signatures on transactions and documents F. Identify standards, data requirements and process to allow a payer to indicate when a procedure or service may require prior authorization –will be considered during phase 2 or later phases if time and resources permit

Purpose Statement
The purpose of eDoC Workgroup is to define data sets, templates and standards in providing guidance with decision support, enabling provider capture of required structured documentation, and securely exchanging for benefit determination based on Health Plan/Payer’s coverage and payment rules. This eDoC Workgroup will extend to have sub-work-groups to fulfill specific requirements for various use cases across Structured Data, Documentation Templates and Decision Support. This will include addressing the above mentioned key challenges by either leveraging the work that might have already been done or participating to work in conjunction with related S&I Framework initiative work groups such as Transitions of Care (Consolidated CDA), Provider Directories, Structured Data Capture, Health eDecisions, esMD Author of Record, Direct and Automate Blue Button Initiative.

Value Statement
The value of the esMD Initiative will be to provide consensus-based use cases, functional requirements, standards references and implementation specifications/guidance representing combined input from a broad range of stakeholders, including CMS, commercial Health Plans/Payers, Providers, and vendors. This will promote a nationally standardized approach to medical document request letters, claims attachments, and the proof of validity and authorship of medical documentation.

<span style="font-family: Arial,Helvetica,sans-serif;">Health Plans/Payers and Providers will benefit from this workgroup’s implementation guidance on electronic determination of coverage by moving away from current paper based or unstructured images of medical documentation for selected specific use cases pertaining to certain payment areas that are high in the list of interest to reduce improper payments and fraud. Additional benefits include: <span style="font-family: Arial,Helvetica,sans-serif;">A. Improved ability in determination of coverage with decision support guidance for providers <span style="font-family: Arial,Helvetica,sans-serif;">B. Standardized data sets, templates, structured data capture and secure exchange of required documentation as per payer coverage and payment rules <span style="font-family: Arial,Helvetica,sans-serif;">C. Saving time, money and resources for CMS, Commercial Health Plans/Payers, and Providers <span style="font-family: Arial,Helvetica,sans-serif;">D. Elimination of the paper or unstructured data processing and its associated labor and error rate <span style="font-family: Arial,Helvetica,sans-serif;">E. Guidance and recommendations on EHR Certification criteria for structured data capture <span style="font-family: Arial,Helvetica,sans-serif;">F. Improved accounts receivable cycle for Providers, so payments are received sooner <span style="font-family: Arial,Helvetica,sans-serif;">G. Reduced time for benefit determination and notification from Payer to Provider <span style="font-family: Arial,Helvetica,sans-serif;">H. Reduced staff time spent handling paper, printing, imaging and mailing

<span style="color: #0092d6; font-family: Arial,Helvetica,sans-serif; font-size: 1.3em; line-height: 1.5;">**Objective**

<span style="font-family: Arial,Helvetica,sans-serif;">The eDoC Workgroup will prepare to work on specific determination of coverage requirements conforming to the selected use case in defining the corresponding data set requirements, templates, structured data capture and decision support needs accordingly. The Workgroup will strive to reuse as much as possible from other S&I initiatives and work-groups and as well as from the completed use cases.

<span style="font-family: Arial,Helvetica,sans-serif;">Workgroup Scope
<span style="font-family: Arial,Helvetica,sans-serif;">This Workgroup will focus on defining the use case, user stories and requirements supporting a standards-based architecture. It will reuse existing S&I Initiative efforts where possible and create structured data capture templates and support exchange standards as needed. Power Mobility Devices will be the initial Use Case.

<span style="font-family: Arial,Helvetica,sans-serif;">Structured Data
<span style="font-family: Arial,Helvetica,sans-serif;">A. Determine documentation requirements <span style="font-family: Arial,Helvetica,sans-serif; font-size: 1em; line-height: 1.5;">B. Evaluate appropriate clinical elements <span style="font-family: Arial,Helvetica,sans-serif; font-size: 1em; line-height: 1.5;">C. Evaluate appropriate Clinical Vocabularies <span style="font-family: Arial,Helvetica,sans-serif; font-size: 1em; line-height: 1.5;">D. Define Consolidated CDA (CCDA) template

<span style="font-family: Arial,Helvetica,sans-serif;">Documentation Templates
<span style="font-family: Arial,Helvetica,sans-serif;">A. Define template requirements <span style="font-family: Arial,Helvetica,sans-serif;">B. Define template workflow <span style="font-family: Arial,Helvetica,sans-serif;">C. Define EHR data capture requirements <span style="font-family: Arial,Helvetica,sans-serif;">D. Specify storage requirements

<span style="font-family: Arial,Helvetica,sans-serif;">Decision Support
<span style="font-family: Arial,Helvetica,sans-serif;">A. Define rules to guide documentation <span style="font-family: Arial,Helvetica,sans-serif;">B. Define rules to present covered alternatives <span style="font-family: Arial,Helvetica,sans-serif;">C. Determine workflow issues

<span style="font-family: Arial,Helvetica,sans-serif;">Targeted Goal & Outcome
<span style="font-family: Arial,Helvetica,sans-serif;">A. Goal – Achieve provider/supplier documentation required for the electronic determination of coverage by payer’s rules in an efficient manner for payers and providers <span style="font-family: Arial,Helvetica,sans-serif;">B. Outcome <span style="font-family: Arial,Helvetica,sans-serif;">a. Successful pilot of templates, decision support, information exchange standards over standard secure transactions for the purpose of determining coverage <span style="font-family: Arial,Helvetica,sans-serif;">b. Validation with initial use case for Power Mobility Devices

<span style="font-family: Arial,Helvetica,sans-serif;">Timeline
<span style="font-family: Arial,Helvetica,sans-serif;">The Workgroup will use an incremental approach to address Structured Data Capture Templates and Decision Support that will build on the foundation of Structured Data defined in Phase 1 of the initial Use Case for Power Mobility Devices. It will coordinate the Discovery, Implementation and Pilot phases for completing both the PMD phases as per the proposed timeline below.

<span style="font-family: 'Times New Roman',serif; font-size: 14pt;">

<span style="font-family: Arial,Helvetica,sans-serif;">Relevant Policies
<span style="font-family: Arial,Helvetica,sans-serif;">A. CMS National Coverage Determination (NCD) <span style="font-family: Arial,Helvetica,sans-serif;">B. CMS Local Coverage Determination (LCD) <span style="font-family: Arial,Helvetica,sans-serif;">C. Health Insurance Portability and Accountability Act of 1996 (HIPAA) Privacy and Security Rules <span style="font-family: Arial,Helvetica,sans-serif;">D. Applicable State regulations and laws <span style="font-family: Arial,Helvetica,sans-serif;">E. Applicable Federal regulations and laws <span style="font-family: Arial,Helvetica,sans-serif;">F. Specific Medicaid and Commercial Payer coverage guidelines
 * <span style="color: #4f81bd; font-family: Cambria,serif;">(List is exemplary and will be expanded during Use Case development) **

<span style="color: #0092d6; font-family: Arial,Helvetica,sans-serif; font-size: 1.3em; line-height: 1.5;">**Potential Standards for Consideration**

<span style="font-family: Arial,Helvetica,sans-serif;">Related S&I Framework Initiatives <span style="font-family: Arial,Helvetica,sans-serif; font-size: 1em; line-height: 1.5;">A. Transitions of Care (Consolidated CDA) <span style="font-family: Arial,Helvetica,sans-serif; font-size: 1em; line-height: 1.5;">B. Provider Directories <span style="font-family: Arial,Helvetica,sans-serif; font-size: 1em; line-height: 1.5;">C. Structured Data Capture (SDC) <span style="font-family: Arial,Helvetica,sans-serif; font-size: 1em; line-height: 1.5;">D. Health eDecisions (HeD) <span style="font-family: Arial,Helvetica,sans-serif; font-size: 1em; line-height: 1.5;">E. Longitudinal Coordination of Care (LCC) <span style="font-family: Arial,Helvetica,sans-serif; font-size: 1em; line-height: 1.5;">F. esMD Author of Record <span style="font-family: Arial,Helvetica,sans-serif; font-size: 1em; line-height: 1.5;">G. Direct <span style="font-family: Arial,Helvetica,sans-serif; font-size: 1em; line-height: 1.5;">H. Automate Blue Button Initiative (ABBI)
 * <span style="color: #4f81bd; font-family: Cambria,serif;">(List is exemplary and will be expanded during Use Case development) **

<span style="font-family: Arial,Helvetica,sans-serif;">Specific Standards Development Organizations and Operating Rules Authoring Entities <span style="font-family: Arial,Helvetica,sans-serif;">A. ASC X12 <span style="font-family: Arial,Helvetica,sans-serif;">B. CAQH CORE <span style="font-family: Arial,Helvetica,sans-serif;">C. HL7 <span style="font-family: Arial,Helvetica,sans-serif;">D. IHE <span style="font-family: Arial,Helvetica,sans-serif;">E. OASIS <span style="font-family: Arial,Helvetica,sans-serif;">F. IETF <span style="font-family: Arial,Helvetica,sans-serif;">G. W3C <span style="font-family: Arial,Helvetica,sans-serif;">H. ISO <span style="font-family: Arial,Helvetica,sans-serif;">I. NCPDP <span style="font-family: Arial,Helvetica,sans-serif;">J. DICOM

<span style="font-family: Arial,Helvetica,sans-serif;">Potential Stakeholders

 * <span style="color: #4f81bd; font-family: Cambria,serif;">(List is exemplary and will be expanded during Use Case development) **

<span style="font-family: Arial,Helvetica,sans-serif;">A. Medicare, Medicaid, and Commercial Payers <span style="font-family: Arial,Helvetica,sans-serif;">B. Providers, Provider Organizations <span style="font-family: Arial,Helvetica,sans-serif;">C. Service suppliers (e.g. DMEs) <span style="font-family: Arial,Helvetica,sans-serif;">D. Health Information Handlers (HIHs) <span style="font-family: Arial,Helvetica,sans-serif;">E. HIT/EHR Vendors and Vendor Associations <span style="font-family: Arial,Helvetica,sans-serif;">F. State HIEs, HIE Vendors <span style="font-family: Arial,Helvetica,sans-serif;">G. SDOs <span style="font-family: Arial,Helvetica,sans-serif;">H. CAQH CORE

<span style="font-family: Arial,Helvetica,sans-serif;">Dependencies
<span style="font-family: Arial,Helvetica,sans-serif;">A. Current standards and policies on determination of coverage set by CMS and Commercial Health Plans/Payers <span style="font-family: Arial,Helvetica,sans-serif;">B. EHR Technologies <span style="font-family: Arial,Helvetica,sans-serif;">C. Payer and contractor technologies <span style="font-family: Arial,Helvetica,sans-serif;">D. State and/or local regulations and laws <span style="font-family: Arial,Helvetica,sans-serif;">E. Federal regulations and laws

<span style="font-family: Arial,Helvetica,sans-serif;">Potential Risks
<span style="font-family: Arial,Helvetica,sans-serif;">A. Ensuring secure, trustable communications between Health Plans/Payers, Providers and their respective intermediaries, agents and business associates <span style="font-family: Arial,Helvetica,sans-serif;">B. Compliance with FISMA in sending PHI from Health Plans/Payers to Providers <span style="font-family: Arial,Helvetica,sans-serif;">C. Establishing policy regarding signatures or proof of content authorship Identifying implementable solutions to prove authorship that minimize burden to both Providers and Health Plans/Payers <span style="font-family: Arial,Helvetica,sans-serif;">D. Dependencies on schedule of and deliverables from other S&I initiatives <span style="font-family: Arial,Helvetica,sans-serif;">E. Lack of vendor (PMD and EMR) engagement in process


 * [[image:/i/c.gif width="10" height="21"]] ||  || [[image:/i/c.gif width="23" height="21"]] ||>   || [[image:/i/c.gif width="10" height="21"]] ||


 * || Bold || Italic || Underline || Style Text ||  ||   || Format - Normal Normal || ▼ ||   ||   || Numbered List || Bulleted List || Insert Horizontal Rule ||   || Link Insert Link || File Insert Images and Files || Widget Embed Widget || Table Insert Table || Comment Add Comment ||   || Undo || Redo ||   || Preview Preview || Continue Editing Continue Editing || Cancel Cancel ||   || Save Save ||   ||   ||   ||

&amp;lt;h2&amp;gt;Javascript Required&amp;lt;/h2&amp;gt; &amp;lt;p&amp;gt;You need to enable Javascript in your browser to edit pages.&amp;lt;/p&amp;gt; help on how to format text


 * [[image:/i/c.gif width="10" height="21"]] ||  || [[image:/i/c.gif width="23" height="21"]] ||>   || [[image:/i/c.gif width="10" height="21"]] ||


 * || Bold || Italic || Underline || Style Text ||  ||   || Format - Normal Normal || ▼ ||   ||   || Numbered List || Bulleted List || Insert Horizontal Rule ||   || Link Insert Link || File Insert Images and Files || Widget Embed Widget || Table Insert Table || Comment Add Comment ||   || Undo || Redo ||   || Preview Preview || Continue Editing Continue Editing || Cancel Cancel ||   || Save Save ||   ||   ||   ||

&amp;lt;h2&amp;gt;Javascript Required&amp;lt;/h2&amp;gt; &amp;lt;p&amp;gt;You need to enable Javascript in your browser to edit pages.&amp;lt;/p&amp;gt; help on how to format text