forked from projecthdata/projecthdata.github.com
-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
43 lines (43 loc) · 3.54 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
---
layout: master
title: Project hData - Simple and Scalable Clinical Information Exchange.
selected: index
---
<div id="splitContent">
<div id="leftColumn">
<div id="logo">
<a href="index.html"><img src="images/hData_logo.png" alt="hData Logo" /></a>
<a href="http://groups.google.com/group/hdata-general/subscribe" target="_external"><img src="images/button_announcements.png" alt="Join Announcement List" /></a>
</div>
<div class="projectDescription"><h2>What is hData?</h2></div>
<p>hData is a specification for exchanging electronic health data.</p>
<div class="projectDescription"><h2>What is the objective of hData?</h2></div>
<p>Current electronic health data standards are complex, hard to implement, and difficult to manage, especially for web centric and mobile developers. hData is a simple, flexible framework that addresses these issues and lays the foundation for efficient health IT technologies.</p>
<p>The hData specifications have been submitted to <a href="http://www.hl7.org/" >Health Layer 7 (HL7)</a> and and the <a href="http://www.omg.org/">Object Management Group (OMG)</a> for standadization. The hData Record Format is on the normative track at HL7 and has recently passed the DSTU ballot. More information can be found in the <a href="/standardization.html">Standardization</a> page. </p>
<div class="projectDescription"><h2>What is the hData design philosophy?</h2></div>
<img src="/images/hData-specs.png" width="300px" style="float:right" />
<p>hData is designed for ease of implementation and improved efficiency by reducing the size of the data set, implementing a single way to represent data, and using standard web best practices. Crucial to achieving these design goals is a clear separation of content and exchange specifications. For this, the HL7 hData Record Format defines the concept of a hData Content Profile (HCP), which allows the specification for a detailed content model (including syntax, semantics, and behavioral models) for a given business use case. <p>
<div id="feedback">
<div id="feedbackLink">For more information, contact us at: <a href="mailto:hdata-general@googlegroups.com">hdata-general@googlegroups.com</a></div>
</div>
</div>
</div>
<div id="sidebar">
<table class="milestonesList">
<caption><h2>Milestones</h2></caption>
<!-- there is a known bug in IE 6 regarding sibling selectors
since we want the second column to look different than the first
we are going to work around this bug by inserting a class on every other td-->
<!--thead>
<tr><th>Date</th><th>Event</th></tr>
</thead-->
<tbody>
<tr><td class="milestoneDate">Dec 2012</td><td class="milestoneSubject">OMG hData FTF delivers Finalization Report to AB and DTC</td></tr>
<tr><td class="milestoneDate">Dec 2012</td><td class="milestoneSubject">RHEx <a href="/rddls/rhex">RDDLs</a> and <a href="/schemas/rhex">schemas</a> available from projecthdata.org</td></tr>
<tr><td class="milestoneDate">Sep 2012</td><td class="milestoneSubject">"HL7 V3 Medication Statement Service Profile Using hData, Release 1" on DSTU ballot</td></tr>
<tr><td class="milestoneDate">Jul 2012</td><td class="milestoneSubject">IHE ITI TC Health uses hData as foundation for IHE MHD</td></tr>
<tr><td class="milestoneDate">Dec 2011</td><td class="milestoneSubject">OMG TC Meeting - hData adopted as Beta Specification</td></tr>
<tr><td class="milestoneDate">Sep 2011</td><td class="milestoneSubject">HL7 hData Record Format passes HL7 DSTU ballot</a></td></tr>
</tbody>
</table>
</div>