Payer+Charter+Vote+and+Use+Case+Prioritization

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

Homework
Payer WG Members: Your homework is to prioritize the Payer Use Cases. Instruction are here.

Voting on the Payer WG Charter is CLOSED
Thank you to everyone who voted and commented on the Charter. =Payer Workgroup - WG Charter and Straw Man=

Synopsis
The aim of the ABBI Payer Content workgroup is to identify a practical human-readable and machine-readable content standard for Blue Button data, capable of conveying __both clinical and non-clinical health data__ offered by existing payers today, either by Blue Button or in EOB (Explanation of Benefits) documents today. **The goal is to arrive at a data & interoperability platform, feasible for payers & PBMs and attractive to developers to innovative apps & to create personally-controlled solutions that target clinical quality, affordability, access and the experience of care itself.**

In Scope

 * Leverage existing elements defined by public & private payers
 * Leverage existing standards if possible e.g. MyMedicare.gov ASCII, X12, HL7, cCDA extension, HealthVault EOB data model
 * Produce implementation guidance
 * Payor-generated Health Financial data and Clinical Claims Data
 * Solutions themselves are out-of-scope; HOWEVER, the data standards & interoperability in-scope, and pre-requisite for 3rd-parties to create solutions.
 * Examples of relevant data : Explanations of Benefit (EOBs) -- with noted concern about proprietary network discounting information
 * Self-reported and unstructured data initially out of scope for Version 1, but nice to have as optional

Requirements
1. File content standard must allow for common data elements in payor & PBM-generated Blue Button ASCII files today, e.g. those generated by MyMedicare.gov. Elements that the standard should support include:
 * Eligibility Dates
 * Provider Identifiers
 * Diagnosis Codes
 * Procedure Codes
 * Rx Codes
 * Financial Information related to transactions/encounters (e.g. billed, allowed, paid & patient-responsible amounts)

media type="custom" key="21396186"

media type="custom" key="21244560"

 Our goal is to prioritize the list of Use Cases for the Payer Content Workgroup in order to focus our activities in the coming months. To make this easier, each workgroup member is allotted 10 total votes. You may distribute your 10 votes among the use cases in any way you like. For example, if you only like Use Case 1 and Use Case 7, you may give 5 votes to Use Case 1, and 5 votes to Use Case 7 and leave the rest of the use case fields blank. Alternatively, if you think all 10 use cases are equally important, you may give each use case 1 of your votes. You may distribute your 10 'votes' among the use cases in any way you like.
 * 2. Prioritize the Payer Use Cases**

media type="custom" key="21244446" media type="custom" key="21244590" include component="page" wikiName="siframework" page="ABBI Initiative Contacts" include component="page" wikiName="siframework" page="space.template.inc_contentleft_end"