Difference between revisions of "HData"
| Line 7: | Line 7: | ||
</center> | </center> | ||
| − | 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. It should be note that conceptually CDA and hData are similar in their approach to representing data points in a hierarchical way. |
[[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: | [[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: | ||
| Line 20: | Line 20: | ||
* The basic [[hData Record Format]] (HRF) specification describes the overall data organization. | * The basic [[hData Record Format]] (HRF) specification describes the overall data organization. | ||
| − | ** An [http://github.com/projecthdata/lab-content-profile/tree/master/hdata-examples/simple/ example hData Record], capturing a lab order and result. | + | ** An [http://github.com/projecthdata/lab-content-profile/tree/master/hdata-examples/simple/ example hData Record], capturing a lab order and result. Again, for this example it is important to note that the content of the structure is independent of its structure. |
* The [[hData RESTful API]] specification describes the RESTful API defined of an hData record and a simple messaging interface. | * The [[hData RESTful API]] specification describes the RESTful API defined of an hData record and a simple messaging interface. | ||
| Line 29: | Line 29: | ||
=== Structured Document Template Design Pilot === | === 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. | + | hData is part of the [[Structured Document Template Design Pilot]], progress can be tracked on the [[HData Template Sub Project]] page. Within this pilot it is demonstrated that hData can be made conceptually equivalent to a CDA based approach: the content of an CDA document and an hData record following the rules of the HRF specification are isomorphic, as long as an hData Content Profile is used that supports all features used in the CDA instance. |
=== Presentation Material === | === Presentation Material === | ||
Revision as of 20:30, 24 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. It should be note that conceptually CDA and hData are similar in their approach to representing data points in a hierarchical way.
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.
- An example hData Record, capturing a lab order and result. Again, for this example it is important to note that the content of the structure is independent of its structure.
- 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. Within this pilot it is demonstrated that hData can be made conceptually equivalent to a CDA based approach: the content of an CDA document and an hData record following the rules of the HRF specification are isomorphic, as long as an hData Content Profile is used that supports all features used in the CDA instance.
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
