Difference between revisions of "HData"
| Line 9: | Line 9: | ||
hData requires strong separation of the technical representation and transport technology on the one side, and the clinical content of an electronic health record on the other side. To this end, hData has the concept of hData Content Profiles (HCP), which define what kind of content is represented and transport through hData. | hData requires strong separation of the technical representation and transport technology on the one side, and the clinical content of an electronic health record on the other side. To this end, hData has the concept of hData Content Profiles (HCP), which define what kind of content is represented and transport through hData. | ||
| − | [[Micro ITS]] and hData are complimentary. Conceptually, Micro ITS provides a generalized mechanism for defining Domain Specific Markup Languages (DSML) to represent RIM content models. | + | [[Micro ITS]] and hData are complimentary. Conceptually, Micro ITS provides a generalized mechanism for defining Domain Specific Markup Languages (DSML) to represent RIM content models. The following diagram illustrates the integration pattern: |
| + | |||
| + | <center> | ||
| + | [[Image:HData-HL7 Layer Cake.png]] | ||
| + | </center> | ||
== Documentation == | == Documentation == | ||
Revision as of 20:39, 22 June 2010
Contents
Overview
hData is a set of specifications that have been developed with ease-of-implementation in mind. This page is a placeholder for a more comprehensive introduction to hData and its relationship to Micro ITS and greenCDA.
hData requires strong separation of the technical representation and transport technology on the one side, and the clinical content of an electronic health record on the other side. To this end, hData has the concept of hData Content Profiles (HCP), which define what kind of content is represented and transport through hData.
Micro ITS and hData are complimentary. Conceptually, Micro ITS provides a generalized mechanism for defining Domain Specific Markup Languages (DSML) to represent RIM content models. The following diagram illustrates the integration pattern:
Documentation
Strawman Draft Specifications
- The basic hData Record Format (HRF) specification describes the overall data organization.
- The hData RESTful API specification describes the RESTful API defined of an hData record and a simple messaging interface.
Requirements Document
- The hData Security Requirements paper outlines the concepts and requirements for securing RESTful hData exchanges.
Structured Document Template Design Pilot
hData is part of the Structured Document Template Design Pilot, progress can be tracked on the HData Template Sub Project page.
Presentation Material
Links
Project hData was started by MITRE and is currently hosted on http://projecthdata.org/
Code
Sample code and XML schemas capturing the HITSP/C32 profile of the HL7 CCD can be found on http://github.com/projecthdata
