forked from projecthdata/projecthdata.github.com
-
Notifications
You must be signed in to change notification settings - Fork 0
/
standardization.html
67 lines (65 loc) · 4.05 KB
/
standardization.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
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
---
layout: master
title: hData Standardization
selected: standardization
---
<div id="content">
<div id="logo">
<a href="index.html"><img src="images/hData_logo.png" alt="hData Logo"></a>
</div>
<div class="projectDescription"><h2>Standardization</h2></div>
<div class="questionAnswer firstQuestion">
<div class="question">Standardization Status</div>
<p>
<table border="1">
<thead>
<td><b>Standard</b></td>
<td><b>Current Status</b></td>
<td><b>Next Step</b></td>
</thead>
<tr>
<td>HL7 hData Record Format</td>
<td>Passed DSTU ballot, awaiting final comment resolution</td>
<td>Publication as DSTU by HL7 (expected 10-2011)</td>
</tr>
<tr>
<td><a href="http://doc.omg.org/health/11-09-04/">hData RESTBinding for RLUS</a></td>
<td>RFC issued by OMG</td>
<td>Comment resolution and adoption (expected 12-2011)</td>
</tr>
</table>
</p>
</div>
<div class="questionAnswer">
<div class="question">Standardization History</div>
<p>
<a href="http://www.hl7.org">HL7</a> International is an ANSI accredited standards development organization (SDO) that has been active for over 25 years. It has more than 35 country affiliates across the globe.
hData was first presented to a wider audience within HL7 as the September 2009 meeting in Atlanta, GA. Since then, hData has first been evalauted as a HL7 research project within the HL7
<a href="http://wiki.hl7.org/index.php?title=ITS_WG">ITS working group</a>. The research project culminated in a "For Comment" ballot in January 2011. After a carefull analysis, HL7 decided to standardize the hData Record Format (which defines a unified packaging mechanism and metadata model) under the leadership of the HL7 <a href="http://wiki.hl7.org/index.php?title=Service_Oriented_Architecture">SOA working group</a>, while the hData RESTful Transport is being standardized through the <a href="http://hssp.wikispaces.com/">HSSP Collaboration</a> between HL7 and the <a href="http://www.omg.org/" >Object Management Group (OMG)</a> Healthcare Domain Task Force (DTF).
</p>
</div>
<div class="questionAnswer">
<div class="question">hData at HL7 and OMG</div>
<p>
The HL7 <a href="http://wiki.hl7.org/index.php?title=Architecture_Board">Architecture Board</a> decided that the SOA Working Group would be best suited to manage the hData projects at HL7. Other
interested parties include the ITS Working Group, <a href="http://wiki.hl7.org/index.php?title=Modelling_and_Methodology">Modeling and Methodology</a>, and the <a href="http://wiki.hl7.org/index.php?title=Security">
Security Working Group</a>. hData has its own <a href="http://wiki.hl7.org/index.php?title=HData">wiki page</a> on the HL7 wiki.
</p>
<p>Within OMG, the hData RESTful Transport specification has been submitted for consideration as an OMG specification using the (fast-track) RFC process.</p>
</div>
<div class="questionAnswer">
<div class="question">Relation to other HL7 and OMG activities</div>
<p>
The hData specifications can be seen as a realization of the HL7/OMG SOA RLUS model. Through the HCP mechanism, they interact also with the HL7 Clinical Domain Analysis Community, who need to determine what
content is appropriate to be included in a given hData Content Profile. The HCP also requires business justifications and behavioral modeling (where appropriate).
</p>
<p>
The following diagram illustrates the relationship between hData and other HL7 activities:
<img width="800" src="/images/Relationships among groups and artifacts - hData additions-v3.png" />
</p>
</div>
<div class="questionAnswer">
<div class="question">Schemas</div>
<p ><a href="http://github.com/projecthdata/hData/tree/master">Github project</a></p>
</div>
</div>