BlueButton+Plus+-+Content+Sub+Workgroup

include component="page" wikiName="siframework" page="ABBI Header" =Announcements= =Workgroup Artifacts= Meeting materials and presentations are available on the Automate Blue Button Meeting Artifacts page. =Reference Materials= Mapping from the Blue Button text file label to a value expressed in the CCD (via a full XPath): =Content Sub-workgroup Project Charter=
 * **Workgroup activities are complete.**
 * Thank you to every member of the Clinical Content SWG for all of your hard work! With help from you, we now have an ABBI IG - Content Format for Health Records.
 * Clinical Content Implementation Guide:** ABBI IG - Content Format for Health Records
 * Content: A Blue Button file must be both machine-readable and human-readable.**
 * In Scope**
 * Content needs to connect to meaningful information to explain what it means.
 * Leverage work done by the ToC S&I Initiative
 * Leverage work done by HL7 and Consolidated CDA
 * Leverage work done by VA in the Current Blue Button Format (version 12)


 * Requirements**
 * 1) File must be both human-readable on multiple platforms: PC, Mac, iOS, and Android.
 * 2) File must be printable.
 * 3) File must be machine-readable.


 * Use Cases**
 * Use Case 1 (UC1) - A patient can download a copy of his/her records and is able to read and print it out.
 * Use Case 2 (UC2) - A patient can point a software or web application to their Blue Button file and it can parse it.

- Consolidated CDA (HL7) - XML File - .JSON
 * Health IT Systems and Developers**

- Text File - Consolidated CDA (HL7) - XML File and XSLT Stylesheet - HTML File - PDF
 * Patient-Centered**

- X12 - Extensions on CDA - Simple .JSON
 * Claims**

Feedback or comments? Use the discussion form below. 

media type="custom" key="20826840"

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