Presentation is loading. Please wait.

Presentation is loading. Please wait.

HData History 1 2009: Work on hData begins Mid-2011: ONC NwHIN team looks at hData and REST 2010: hData receives MIP funding.

Similar presentations


Presentation on theme: "HData History 1 2009: Work on hData begins Mid-2011: ONC NwHIN team looks at hData and REST 2010: hData receives MIP funding."— Presentation transcript:

1 hData History 1 2009: Work on hData begins Mid-2011: ONC NwHIN team looks at hData and REST 2010: hData receives MIP funding

2 hData Specifications  HL7 hData Record Format (HRF) –Currently DSTU  OMG hData RESTful Transport –Currently normative, v1.0 –Service behaviors 2 © 2012 The MITRE Corporation. All rights reserved. For internal MITRE use

3 hData Record Format (HRF)  One-year waiting period since DSTU (Dec 2011) has elapsed –DSTU status expires Feb 2014 –HRF is 3 rd most active DSTU (out of 31 proposed standards) –Approximately half-dozen “significant” comments so far –Most comments stem from implementation experience with Continua or misalignments with FHIR  Comments are currently being reviewed in weekly meetings with Finalization Task Force under SOA WG –Representation from HP, Deloitte, HL7, MITRE –SOA WG seeks one approach to RESTful services at HL7 –HRF focus session will be held at HL7 WG in 2 nd week of May  The next few slides provide background, then discuss some of the problems with the HRF 3 © 2012 The MITRE Corporation. All rights reserved. For internal MITRE use

4 hData Record Format: Root Files  HRF contains the recipe for creating “root” files –Root file is how an hData client discovers resources –Client retrieves the root file (HTTP) from known URL –Root lists URLs (sections) and resource types (extensions) 4 © 2012 The MITRE Corporation. All rights reserved. For internal MITRE use Root Id: string 1..1 version: integer 1..1 created: dateTime 1..1 lastModified: dateTime 1..1 Id: string 1..1 version: integer 1..1 created: dateTime 1..1 lastModified: dateTime 1..1 extension @extensionID: string 1..1 @contentType: string 1..1 (MIME type) extension: string 1..1 (definitional URL) @extensionID: string 1..1 @contentType: string 1..1 (MIME type) extension: string 1..1 (definitional URL) extensions 0..N section @path: string 1..1 @extensionID: string 1..1 @requirement: extension: string 1..1 @path: string 1..1 @extensionID: string 1..1 @requirement: extension: string 1..1 sections 0..N

5 hData Record Format: Content Profiles  HRF contains the recipe for creating Content Profiles –Content Profiles are the way that organizations standardize resource hiearchies –Root files may be composed out of one or more Content Profiles –Content Profile Documentation Package (required) includes schema definitions, business logic, use cases, and more 5 © 2012 The MITRE Corporation. All rights reserved. For internal MITRE use

6 Problems with HRF v1.0  Nothing in root file indicates which content profiles it implements –CP Definition Document doesn’t point to a CP Documentation Package, either –Needed for Continua  Sections should be able to use URL templates –Parameterized sections such as [base]/{patientID}/conditions –Enables one root file per service, rather than one per patient  Sections should be able to have their own root files –Enables modularity of multiple services (e.g. radiology, pharmacy, benefits)  Root doesn’t do enough to support search (URL query parameters) –Lack of search causes a problem with scalability (atom feed with many entries) –A search description should be associated with each section  Content profiles are difficult to understand; holding up adoption –Unclear what solution path may be (simplify? eliminate?)  Poorly-chosen terminology –“extension” means resource type, conflicts with FHIR –“section” means URL 6 © 2012 The MITRE Corporation. All rights reserved. For internal MITRE use

7 Overall vs Patient-Specific Service Endpoint 7 © 2012 The MITRE Corporation. All rights reserved. For internal MITRE use hData FHIR /resource Server Root @resourceID Configurable via root file Not configurable Not patient-centric FHIR Content Profile?

8 Goals of HRF Task Force  Resolve issues and produce for-comment draft by August  Support the ballot process in September  Normative ballot in January 8 © 2012 The MITRE Corporation. All rights reserved. For internal MITRE use


Download ppt "HData History 1 2009: Work on hData begins Mid-2011: ONC NwHIN team looks at hData and REST 2010: hData receives MIP funding."

Similar presentations


Ads by Google