BlueButton+Plus+-+Project+Charter

include component="page" wikiName="siframework" page="ABBI Header" media type="custom" key="20312646" =Blue Button Plus Overview= Blue Button Plus gives consumers the ability to obtain their health care records in both human-readable and machine-readable format, and to send them where they choose. This enables a consumer to do everything from printing a physical copy to sharing it with a third party application.

Through the S&I Framework, the Blue Button Plus initiative advanced the implementation standards, tools, and services associated with the Blue Button to provide consumers with automated updates to their health information in a human readable and machine readable format. For the Push Scenario, we have successfully demonstrated the automation of the private and secure transmission of personal health data to a specific location of the consumer’s choosing. For the Pull Scenario, we are in the process of allowing a third party application of the consumer’s choosing to privately and securely access personal health data on demand.

=Vision= =Challenge= The White House, the VA, and HHS have challenged us: How can we – through the S&I Framework – advance the implementation standards, tools, and services associated with the Blue Button to provide consumers with automated updates to their health information in a human readable and machine readable format? =Goals= =Scope Statement= =Success Metrics= //Consider outcome measures for all viewpoints as project progresses. Note that these are example metrics to be re-considered as the project progresses.//
 * **Blue Button Plus Push Implementation Guidance** || [] ||
 * **Blue Button Plus Pull API Guidance** || [] ||
 * Consumers want to be empowered to be more engaged in their health and healthcare.
 * Through the Blue Button, consumers want the ability to exercise more access to and portability of their health care information. With the right privacy and security assurances, they want to be able to:
 * Better understand their health and make more informed decisions
 * Help to make sure that they and all of their care team members are on the same page
 * Improve the accuracy and completeness of the information
 * Plug it into apps and tools that promise to make information truly available, when and where it’s needed
 * PUSH:** Automating the private and secure transmission of personal health data to a specific location of the consumer’s choosing.
 * PULL:** Allowing a third party application of the consumer’s choosing to privately and securely access personal health data on demand.
 * Identify, define, and harmonize implementation standards, tools and services that facilitate the automated PUSH and automated PULL of patient information
 * Identify, define and harmonize content structures and specifications so that information downloaded is machine readable and human readable
 * Identify, define, and harmonize protocols around identification and credentialing, and protocols around access and authorization, that facilitate the automated PUSH and automated PULL of patient information

=Driving Milestones= //Reconsider when workgroup charters are complete.// =Expected Deliverables= =Relevant Standards and Stakeholders=
 * For Dataholders**
 * Number of existing Blue Button dataholders that implement ABBI
 * Number of records being shared (with/to the patient)
 * Percent of available data made available to the patient
 * Number of new dataholders that take the pledge and implement ABBI
 * Number of dataholders using ABBI for Stage II Meaningful Use
 * For Patients**
 * Number of patients that access their data using ABBI
 * Number of patients that use new features of ABBI (both push and pull)
 * For Third-parties**
 * Number of application developers parsing consuming/utilizing ABBI data
 * Number of patients using applications that are powered by ABBI
 * Number of third-parties that take the pledge and implement ABBI
 * Pilot Push implementation by November 22, 2012
 * Pilot Pull implementation by March 3, 2013
 * Workgroup Charters (Push, Pull, Content)
 * Use Case(s) and Functional Requirements
 * Standards for Blue Button
 * Implementation Guidance for Blue Button
 * Tool development to support Blue Button
 * Pilots and results
 * Patients and/or their representatives
 * **DIRECT:** A set of transport standards, services, and use cases that any data holder or receiver can implement, to package and send/receive electronic health information in a private and secure fashion.
 * **[|HL7:]** work to create and encourage adoption of a new CCD to Blue Button “Transform tool” (to support OPM request)
 * **FHIR**: Fast Healthcare Interoperability Resources draft specification
 * **[|IHE:]** Mobile Health Documents (MHD) Profile: a RESTful transport for document exchange.
 * **LRI:** (Lab Results Interface initiative) Content recommendations on document structures for Lab Interfaces to electronic health records.
 * **[|Markle Foundation:]** recommendations for Blue Button (including privacy and security specifications)
 * **[|NSTIC:]** (National Strategy for Trusted Identities in Cyberspace) public-private initiative to create stronger, more consistent cyber identification policies and services.
 * **[|OAuth & OpenID:]** Community-developed, industry-standardized protocols for authentication and authorization. (Note: The FHA is currently developing a RESTful approach to information exchange that leverages OAuth and OpenID.)
 * **[|OSEHRA:]** an open, collaborative community of users, developers, and companies engaged in advancing electronic health record software and health information technology.
 * **RHEx:** Working on security standards (OpenID and OAuth) and content standards (working now) for applying a RESTful design approach to exchanging health information.
 * **ToC:** Content recommendations on document structures to fulfill Meaningful Use Stage 2 Transitions of Care requirements (consolidated CDA).
 * Work underway to specify use cases for using EHRs and DIRECT to transmit updated summaries of care to a patient as they become available.

Please note that the PUSH Project Scope has been moved to the PUSH Discussion and will be consensus voted on when the Push Workgroup Charter is complete. Please note that the PULL Project Scope has been move to the PULL Discussion and will be consensus voted on when the Pull Workgroup Charter is complete. =Project Charter Consensus:= media type="custom" key="20747280" =Members:= New member requests may take up to 1 business day to process. Please check back later to view your updated information media type="custom" key="20621709"
 * Announcement: The voting period for the Automate Blue Button Initiative Project Charter has officially closed. **

include component="page" wikiName="siframework" page="BlueButton Plus - Initiative Contacts" include component="page" wikiName="siframework" page="space.template.inc_contentleft_end"