Home » Archived » OHF » Draft Plan for 2006
| Draft Plan for 2006 [message #567546] |
Thu, 09 March 2006 22:28 |
 Grahame Grieve
Messages: 76
Registered: July 2009 |
Member |
|
|
This is a multi-part message in MIME format.
--------------090109070106050603020606
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Hi All
I have attached the Draft plan for 2006 for OHF to this
message. It will be finalized at the face to face meeting
at Eclipse Con on Thurs 23 Mar.
You are welcome to comment here on the plan.
Grahame
--------------090109070106050603020606
Content-Type: text/html;
name="plan2006.html"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="plan2006.html"
<html>
<head>
<title>Draft Eclipse OHF Plan for 2006</title>
</head>
<body>
<h1>Draft Eclipse OHF Plan for 2006</h1>
<h2>Overview</h2>
<p>The 2006 OHF plan represents a first step towards the goals outlined in the 2006
Eclipse Roadmap, which says:</p>
<blockquote>
<p>A future growth area for Eclipse is to extend our projects to provide open
source application frameworks and exemplary tools targeted at standards</p>
</blockquote>
<p>The long term goal of the OHF project is to meet these goals. For the year 2006,
the OHF project will be focusing on selected low hanging fruit. Generally, the selection
of the work we propose to complete this year is based on one or more of 3 factors:</p>
<ul>
<li>Availability of resources (both technical and business)</li>
<li>identification of a need in the industry</li>
<li>readiness of the appropriate standards</li>
</ul>
<p>In the future, higher priority will be given to focusing on a coherent and complete
framework to support the development of healthcare applications. For This reason,
it is likely that none of the items in the plan will be regarded as fully released
as we will reserve the right to rework the interfaces for consistency during 2007.</p>
<p>The 2006 plan is divided up by the project, generally following the projects
proposed at the face to face meeting in Washington, October 2005.</p>
<p><i>This document is a draft; it will be finalised at the OHF FTF meeting at Eclipse
Con 2006 (Thurs afternoon Mar 23).</i></p>
<h2>IHE Profiles</h2>
<p>OHF will begin publishing a exemplary implementation of a number of IHE profiles.
Theis year, we will release preliminary implementations of the following IHE profiles:</p>
<ul>
<li>IHE XDS Source & Consumer Actors (+XDS-I)</li>
<li>PIX client</li>
<li>Consistent Time</li>
<li>Document Digitial Signature</li>
<li>ATNA (client side)</li>
<li>Document Availability Notification</li>
<li>Cross Enterprise User Authentication</li>
</ul>
<p>These IHE profiles which will be contributed by several different members. We
will plan to work towards a more consistent interface and paradigm in the future.</p>
<h2>HIMSS IHE/HL7 Demo</h2>
<p>Eclipse OHF will investigate involvement in the HIMSS demo for 2007, either outright
in a collaborative form with OHF member vendors.</p>
<p>Several OHF technology pieces are candidates for HIMSS involvement, most obviously
the IHE profile implementations (especially server side using OSGi/Server), the
H3ET tools, and CTS.</p>
<h2>H3ET (HL7 V3 Eclipse Tools)</h2>
<p>During 2006, we plan to release underlying V3 infrastructure, specifically java
class representations of HL7's MIF and message formats along with the supporting
code for persistence and validation. In addition, we will formalise our relationship
with HL7.</p>
<p>In addition, as an adjunct to the V3 tools, we will also release a set of V2
tools, that will support:</p>
<ul>
<li>a run-time framework for handling HL7 V2 messages and models</li>
<li>editing V2 Conformance profiles in Eclipse</li>
<li>code generation from the conformance profiles to use the run-time framework</li>
</ul>
<h2>CTS component</h2>
<p>We will commit all the code that Mayo Clinic is donating for CTS, LexGrid and
the LexGrid editor to the Eclipse cvs. We will create an Eclipse package for CTS
consumers (i.e. clients) to allow CTS consumers to delegate CTS provision to run-time
configuration. We will investigate CTS involvement in the HL7 HIMSS demo for 2007,
and we will publish a plan for the longer term development of CTS.</p>
<H2>Core Framework</H2>
<p>Define the OHF Core Framework architecture including APIs and
write a supportive “OHF Application Developer's Guide”.
In support of other OHF projects scheduled for 2006, Core priorities
will be as follows: </p>
<ul>
<li><b>Security</b>: Basic framework with an IHE ATNA-compatible reference
implementation and support for username/password and smart card authentication.
Most OHF applications and plug-ins will be required to extend this plug-in.</li>
<li><b>Resource Manager</b>: Provides a consistent service invocation interface
to applications and other Core components. Several OHF projects planned for
2006, including CTS, Consistent Time, and Document Digital Signature, would
extend this plug-in.</li>
<li><b>Messaging</b>: Message Exchange Patterns and Semantics. This module would
provide integrated support for exchanging messages with integrated security and
delivery features based on emerging standards, and would use underlying transport
mechanisms from other resources, such as Web Services and SMTP and file-based
transport of SOAP messages. Applications or components interacting with servers
or web-hosted services can use this framework and its services by extension.
Proposed 2006 projects requiring messaging services include the IHE XDS, XUA,
Notification and PIX actors.</li>
<li><b>HDM Processing</b>: Build an early consensus on what a
Healthcare Document/Message (HDM) processing framework API should
include. Presenting an OHF application with an HDM “factory”
has significant advantages.</li>
</ul>
<P>During the year 2006, we will hold regular teleconferences, along
with supporting email discussion. These telecons will lead to the
publication of a comprehensive architecture for an integrated core
framework that healthcare applications can be built upon. This OHF
Core architecture will be integrated with other Eclipse initiatives.</P>
<h2>OSGi/Server</h2>
<p>In collaboration with the Equiox and ECF projects, a Web/Servlet Container that
hosts an OSGi environment will be released.</p>
<p>OHF will implement the XDS plug-ins in this container as an exemplary test case,
which will result in the XDS functionality being available as a web service.</p>
<h2>DiCOM</h2>
<p>A plugin representing a simple WADO client will be released, and will serve as
a basis for preparing an extensible architecture for a standard WADO client.</p>
<h2>Organisational</h2>
<p>We will hold at least 3 FTF (face-to-face) meetings. The meetings will be held
in conjunction with healthcare standards meetings or industry conferences. Ongoing
discussion for the time and place of these meetings will be held on news:eclipse.technology.ohf.</p>
<p>In addition, we will update the web site, and thereafter keep it current. We
will keep records of OHF FTF meetings on the OHF web site.</p>
<p>Finally, we will define our Milestone releases for this year, in accordance with
this plan, at the FTF meeting on Mar 23 and publish these on our website and newsgroup.</p>
</body>
</html>
--------------090109070106050603020606--
|
|
|
Goto Forum:
Current Time: Wed Apr 24 23:08:29 GMT 2024
Powered by FUDForum. Page generated in 0.02908 seconds |
] 
Search
Help
Register
Login
Home
