1. © 2012 The MITRE Corporation. All rights reserved. For internal MITRE use 11 July 2013 Meeting #6 hData Record Format Task Force 1 © 2012 The MITRE Corporation. All rights reserved. For internal MITRE use

2. Attendees  Mark Kramer  Asim  Sam  Paul  David 2 © 2012 The MITRE Corporation. All rights reserved. For internal MITRE use

3. Agenda  Schedule & Process Review  Atom feed alignment w/ FHIR  Metadata alignment  JSON support (Root file and Atom feed) 3 © 2012 The MITRE Corporation. All rights reserved. For internal MITRE use

4. HL7 Ballot Schedule 4 © 2012 The MITRE Corporation. All rights reserved. For internal MITRE use #5: Notice of intent to Ballot – July 1 - COMPLETE #4: Next deadline : JULY 14 – Initial content due

5. Ballot Submission Information  What goes into a ballot submission package?  Guidelines? –HL7 Ballot Charts (HL7.org>Resources>Work Groups>Balloting)HL7 Ballot Charts –Publishing Committee WikiPublishing Committee Wiki 5 © 2012 The MITRE Corporation. All rights reserved. For internal MITRE use

6. Pre-Ballot Votes?  Not clear what votes are required prior to ballot submission  Votes that might be needed: –DSTU Comment Resolution  By this committee  By SOA WG –Vote on Submission Package  By this committee  By SOA WG  July 22: proposed date for SOA WG Vote to move forward  See: SOA WG Decision PracticesSOA WG Decision Practices 6 © 2012 The MITRE Corporation. All rights reserved. For internal MITRE use

7. HRF 2.0 Document Status  Welcoming your feedback  Updated copy distributed 10 July –Major revisions to Atom Feed section for FHIR compatibility –Major changes to simplify Optional Metadata –Minor changes to root schema  Changed ID attribute to element for JSON compatibility  Changed “Content Type” to “Representation” based on last week’s discussion  Made resource prefix a boolean (@ or nothing) –Added “Nomenclature Changes” section  TO DOs: –JSON examples and conversion rules –Examples –Schemas –Update Fig. 1 (add FHIR) & Fig. 2 (nomenclature) –Pseudo-XML and UML for Optional Metadata (not essential) 7 © 2012 The MITRE Corporation. All rights reserved. For internal MITRE use

8. Atom Feed  FHIR Alignment –Aligned Atom feed with FHIR definitions of elements –Only a few changes required  Title changed from URL to description  Clarified use of link element  JSON conversion –Propose to follow FHIR rules of thumb and examples  FHIR’s JSON conversion can’t handle elements with both attributes and text values  We have a suggestion to handle this; may submit comment to FHIR –Side note: Root schema had @id and child elements with text contents, so changed id to child element to facilitate JSON conversion 8 © 2012 The MITRE Corporation. All rights reserved. For internal MITRE use

9. Atom Feed: Metadata  DSTU required metadata on Atom to represent pedigree, confidentiality –Styled after CDA header information –Was crazy complicated!  Summarized issue in email and received feedback from Paul, David and Sam  Consensus: –Resources often represent their own pedigree internally; therefore any metadata should be OPTIONAL –Where resources don’t keep their own metadata (pdf, jpg), hData can provide a simple metadata model 9 © 2012 The MITRE Corporation. All rights reserved. For internal MITRE use

10. Metadata Simplification  Modeled on FHIR Provenance resource  Server can add new a pedigree element in response to significant lifecycle events affecting the resource represented by the  Note that Pedigree is NOT a resource, just metadata on atom  Need feedback particularly on recommended value sets for party.type and party.role 10 © 2012 The MITRE Corporation. All rights reserved. For internal MITRE use

11. FHIR Provenance Resource  Rolled “Activity” into 11 © 2012 The MITRE Corporation. All rights reserved. For internal MITRE use

12. Next Steps  Prepare “Initial Content” for July 14 deadline (Mark)  JSON examples and conversion rules (Sam & Mark)  Update Fig. 1 (add FHIR) & Fig. 2 (nomenclature) (Mark)  Pseudo-XML and UML for Optional Metadata (Mark)  Examples  Normative Schemas – once Root, metadata have settled  Content Profile for FHIR  Comment tracking 12 © 2012 The MITRE Corporation. All rights reserved. For internal MITRE use

13. Actions  Change Pedigree to Provenance –Check the dictionary and practical use of terms  Add root flag for metadata support, suggested by Sam  Check updated tag definition in Atom feed for consistency with FHIR  Forward Monday 22 July info to team 13 © 2012 The MITRE Corporation. All rights reserved. For internal MITRE use

14. Action Items (from last time)  David H. –Will look at harmonizing Atom feeds between hData and FHIR –NO - Can we use FHIR build tool to generate XSD and JSON examples for Root resource? (not realistic in time frame)  Mark K. –Can Root.xml equally support for JSON? –In accord on changing “contentType” to “representation”  Reason: content suggests something that is contained; contentType is HTTP jargon it is synonymous with media type  Sam –Take a look at excluded characters for resourcePrefix, or why not just use “@”? 14 © 2012 The MITRE Corporation. All rights reserved. For internal MITRE use