| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
| <html xmlns="http://www.w3.org/TR/REC-html40"> |
| <head> |
| <title>Eclipse Open Healthcare Framework Project</title> |
| <link rel="stylesheet" href="/proposals/eclipse-webtools/templates/eclipse/eclipse.css"></head> |
| <body text="#000000" bgcolor="#ffffff" link="#0000ee" vlink="#551a8b" alink="#ff0000"> |
| <TABLE cellSpacing=5 cellPadding=2 width="100%" border=0> |
| <TBODY> |
| <TR> |
| <TD align=left width="60%"><FONT class=indextop>Open Healthcare Framework</FONT> |
| <BR><FONT class=indexsub>A Technology Project Proposal |
| </FONT></TD> |
| <TD width="40%"> |
| <IMG height=86 hspace=50 src="/images/Idea.jpg" |
| width=120 align=center></TD></TR></TBODY></TABLE> |
| <TABLE cellSpacing=5 cellPadding=2 width="100%" border=0> |
| <TBODY> |
| <TR> |
| <TD vAlign=top align=left bgColor=#0080c0 colSpan=2><B><FONT |
| face=Arial,Helvetica color=#ffffff>Introduction</FONT></B></TD></TR> |
| <TR> |
| <TD> <P>The Eclipse Open Healthcare Framework Project is a proposed open source |
| project under the <a href="/technology/">Eclipse Technology Project</a>. </P> |
| <p>This proposal is in the Project Proposal Phase (as defined in the <a href="/projects/dev_process/">Eclipse |
| Development Process document</a>) and is written to declare its intent |
| and scope. This proposal is written to solicit additional participation |
| and input from the Eclipse community. You are invited to comment on |
| and/or join the project. Please send all feedback to the <a href="http://www.eclipse.org/newsportal/thread.php?group=eclipse.technology.ohf">http://www.eclipse.org/newsportal/thread.php?group=eclipse.technology.ohf</a> newsgroup.<br> |
| </p> |
| </TD></TR></TBODY></TABLE> |
| <TABLE cellSpacing=5 cellPadding=2 width="100%" border=0> |
| <TBODY> |
| <tr> |
| <TD vAlign=top align=left bgColor=#0080c0><b> |
| <font face="Arial,Helvetica" color="#FFFFFF">Overview</font></b></TD> |
| </tr> |
| <tr> |
| <TD> |
| <P>The goal of the Open Healthcare Framework (OHF) is to build an |
| interoperable, extensible, open-source healthcare framework on top of the |
| Eclipse Platform, and to demonstrate that extensibility with a set of |
| exemplary tools. OHF will enable software providers to create specialized, |
| differentiated offerings for the healthcare industry, offerings which |
| comply with government regulations and industry standards. OHF will |
| produce frameworks that address the needs of the healthcare industry, |
| government regulators, patients and insurance providers.<br> |
| </P> |
| </TD> |
| </tr> |
| <TR> |
| <TD vAlign=top align=left bgColor=#0080c0><B><FONT |
| face=Arial,Helvetica><FONT |
| color=#ffffff>Background</FONT></FONT></B></TD></TR> |
| <TR> |
| <TD> <P>Healthcare in the United States has been characterized as a $1.7 |
| trillion cottage industry. It is highly fragmented, labor intensive, |
| barely connected, extremely competitive, with many different vendors and |
| solutions that are all proprietary. Against this backdrop, the U.S. |
| Department of Health and Human Service issued regulations to require that |
| healthcare organizations establish administrative, physical and technical |
| infrastructure to safeguard sensitive health information as well as to |
| implement standards to improve efficiency in healthcare delivery. The US |
| government estimates dramatic cost savings at more than $250 billion |
| annually if the healthcare industries can be automated. Healthcare systems |
| throughout the world face similar challenges and opportunities. At the |
| same time, the amount of detailed healthcare information is overwhelming. |
| The ability to generate the information has outstripped its usability. |
| Commercial and proprietary solutions and systems have generated multiple |
| environments without the basic interoperability of systems or information. |
| Healthcare information systems encompass vastly different types of |
| information tracking from pre-natal to post-mortem. Industry standards and |
| specifications are broad, complex and lack implementations. Industry has |
| suffered from proliferation of new technologies which have yielded more |
| complexities rather than collaborative solutions. Privacy, security and |
| accuracy are of critical concern.<br> |
| </P> |
| </TD></TR></TBODY></TABLE> |
| <TABLE cellSpacing=5 cellPadding=2 width="100%" border=0> |
| <TBODY> |
| <tr> |
| <TD vAlign=top align=left bgColor=#0080c0><b> |
| <font face="Arial,Helvetica" color="#FFFFFF">Scope</font></b></TD> |
| </tr> |
| <tr> |
| <TD> |
| <P>The project will provide a common, vendor-neutral framework that |
| includes a set of local infrastructure-level services and exemplary tools |
| that support interaction with distributed Electronic Health Records (eHRs), |
| common resources on the <a href="http://www.os.dhhs.gov/healthit">National Health Information Network</a> (e.g. patient |
| directories, provider directories, locator services, credential services) |
| and other network-based services required by locally executing healthcare |
| processes and workflows.<br> |
| <br> |
| Unlike existing eHR systems and healthcare applications, the next |
| generation of eHR systems are being designed as distributed, |
| loosely-coupled systems that comply with emerging standards for eHR |
| document structure and eHR system functional requirements defined by |
| <a href="http://www.hl7.org/ehr">HL7</a>, |
| <a href="http://www.astm.org/cgi-bin/SoftCart.exe/COMMIT/COMMITTEE/E31.htm?L+mystore+isym5396+1112774053">ASTM</a> and other healthcare standards bodies. An eHR is a collection of |
| documents containing a patient's healthcare information that are created in compliance with standard specifications that define |
| document structure, datatypes, terminology/vocabulary and essential |
| processing requirements. We implement industry standard requirements that |
| assure an authors semantic intent is captured in a manner that can later |
| be recovered by a different person or machine at a later time and place. |
| <br> |
| <br> |
| The OHF will be able to take standards-compliant eHR documents, as well as |
| other structured healthcare documents/messages, and process them as |
| required to recover semantic content for presentation according to the OHF |
| users role and perspective. <br> |
| <br> |
| The OHF will provide framework users (such as healthcare application |
| vendors) with the interoperability tools that provide near-transparent |
| transport layers that handle regulation-imposed security and privacy |
| requirements.<br> |
| <br> |
| The exchange of formatted data with legacy systems, especially in support |
| of migration of existing systems to emerging eHR standardized systems, |
| will be |
| facilitated by pluggable adapters. <br> |
| </P> |
| </TD> |
| </tr> |
| <TR> |
| <TD vAlign=top align=left bgColor=#0080c0><B><FONT |
| face=Arial,Helvetica><FONT |
| color=#ffffff>Description</FONT></FONT></B></TD></TR> |
| <TR> |
| <TD> |
| <P>The following is a high level schematic visual of the proposed OHF |
| project. <br> |
| <br> |
| <img border="0" src="image002.jpg" width="510" height="377"><br> |
| <br> |
| The OHF encompasses a common foundation of services for creating, |
| managing, storing and retrieving an Electronic Health Record (eHR), which |
| conforms to the industry standards. In addition, the OHF preserves and |
| protects the privacy, security and identity of individuals and systems. |
| Finally, the OHF adapts the industrys legacy environments, including |
| data, applications and workflow processes. For each of these functional |
| areas, the OHF provides frameworks with well-defined extension points |
| (plug-ins). Upon these frameworks, the OHF builds exemplary and extensible |
| tools.<br> |
| <br> |
| The proposed framework can be considered to be an enabling infrastructure |
| for the higher-level healthcare applications. The availability of this |
| framework is intended to allow application developers to focus on |
| innovation and delivery of core value rather than repetition and |
| reinvention. <br> |
| <br> |
| <b>Industry Standards Implementation</b><br> |
| This solution builds a framework that consists of a comprehensive, |
| standards-based information model coupled with a set of integrated |
| services for data exchange, identity management and business process |
| workflow management. It implements industry standards that support |
| electronic healthcare records (eHRs), HIPAA compliance and process |
| automation. The model supports document/message creation, compilation, |
| transport, translation, storage and presentationall while maintaining an |
| environment that assures document/message integrity, confidentiality and |
| interoperability. It provides comprehensive support for HL7 protocol |
| specification standards based upon the HL7 Version 3 Reference Information |
| Model, which includes data structures for such diverse purposes as patient |
| administration, laboratory billing, imaging and pharmacy order |
| management. In addition, the OHF Project will support the joint OMG-HL7 |
| healthcare IT systems interoperability standards based on the Model-Driven |
| Architecture (MDA). <br> |
| </P> |
| </TD> |
| </TR></TBODY></TABLE> |
| <TABLE cellSpacing=5 cellPadding=2 width="100%" border=0> |
| <TBODY> |
| <tr> |
| <TD vAlign=top align=left bgColor=#0080c0><B><FONT color="#FFFFFF" |
| face=Arial,Helvetica>Interested Parties</FONT></B></TD> |
| </tr> |
| <tr> |
| <TD valign="top"><P>The following organizations have expressed interest in |
| implementing these service:</P> |
| <ul> |
| <li>Department of Defense (Health Affairs)</li> |
| <li>Veterans Health Administration</li> |
| <li>SerAPI (Finland)</li> |
| <li>MedicAlert Foundation</li> |
| <li>Kaiser-Permanente</li> |
| <li>InterMountain Health</li> |
| <li>Kaiser-Permanente Submission</li> |
| </ul> |
| </TD> |
| </tr> |
| <tr> |
| <TD vAlign=top align=left bgColor=#0080c0><b> |
| <font face="Arial,Helvetica" color="#FFFFFF">Project Principles</font></b></TD> |
| </tr> |
| <tr> |
| <TD valign="top"> |
| <P>A large part of the audience for this project is not experienced with |
| the concepts of Eclipse open source development. Therefore, this section of |
| the proposal elaborates on the spirit of open-source, community-driven |
| principles guiding eclipse.org itself. This project will concentrate on |
| several key ideals: <br> |
| <br> |
| <b>Vendor neutrality</b><br> |
| We implement healthcare management frameworks and tools not biased toward |
| any vendor. Our intention is that OHF be leveraged to provide the Eclipse |
| community with the widest range of healthcare management choices possible. |
| To this end, we seek community involvement in formulating key framework |
| interfaces, so that the largest possible constituency is represented.<br> |
| <br> |
| <b>Extensibility</b><br> |
| We recognize both the common need for the stable healthcare infrastructure |
| and the desire to extend the offerings in new and innovative ways. To |
| support these efforts, our components will be designed for, and make good |
| use of, extensibility mechanisms supported by Eclipse. <br> |
| <br> |
| <b>Community Involvement<br> |
| </b>Success for OHF, as with other Eclipse projects, is |
| as much a factor of community involvement as the technical merit of its |
| components. We strongly believe that OHF will achieve its full potential |
| only as the result of deep and broad cooperation with the Eclipse |
| membership-at-large. Thus, we make every effort to accommodate |
| collaboration, reach acceptable compromises and provide a project |
| management infrastructure that includes all contributors, regardless of |
| their affiliation, location, interests or level of involvement. Regular |
| meetings covering all aspects of OHF, open communication channels and |
| equal access to process will be key areas in driving successful community |
| involvement.<br> |
| <br> |
| <b>Transparency</b><br> |
| As with all projects under the eclipse.org banner, key |
| information and discussions at every level such as requirements, design, |
| implementation, and testing will be easily accessible to the Eclipse |
| membership-at-large. <br> |
| <br> |
| <b>Agile Development</b><br> |
| We will strive to incorporate into our planning process |
| innovations that arise once a project is underway, and the feedback from |
| our user community on our achievements to date. We think an agile planning |
| and development process, in which progress is incremental, near-term |
| deliverables are focused and long-term planning is flexible will be the |
| best way to achieve this. <br> |
| <br> |
| <b>Development Process</b><br> |
| This proposal is in the Project Proposal Phase (as defined in the Eclipse |
| Development Process document). The OHF Project will follow the spirit, |
| intent and processes as defined in the Eclipse Development Process |
| document.<br> |
| <br> |
| <b>Licensing</b><br> |
| OHF and all contributions to Projects under this Sub-Project must adhere |
| to the Eclipse Foundation Intellectual Property Policy.<br> |
| </P> |
| </TD> |
| </tr> |
| <TR> |
| <TD vAlign=top align=left bgColor=#0080c0><b> |
| <font face="Arial,Helvetica" color="#FFFFFF">Organization</font></b></TD> |
| </TR> |
| <TR> |
| <TD valign="top"> |
| <p><strong>Initial Committers</strong></p> |
| |
| <table border="0" cellpadding="0" cellspacing="0" bordercolor="#111111" width="504" id="AutoNumber2"> |
| <tr> |
| |
| <td width="111"> <span style="color: windowtext; text-decoration: none">Dmitry |
| Bakuntsev</span></td> |
| |
| <td width="164"> <a href="http://www.intertechnogroup.com/" target="_blank">ITG</a></td> |
| |
| <td width="229"> DBakuntsev (at) intertechnogroup.com</td> |
| </tr> |
| <tr> |
| |
| <td width="111"> <span style="color: windowtext; text-decoration: none">Igor |
| Yasno</span></td> |
| |
| <td width="164"> <a href="http://www.intertechnogroup.com/" target="_blank"> |
| ITG</a></td> |
| <td width="229"> iyasno(at) intertechnogroup.com</td> |
| </tr> |
| <tr> |
| |
| <td width="111"> <span style="color: windowtext; text-decoration: none">Kim |
| Clohessy</span></td> |
| |
| <td width="164"> <a href="http://www.IBM.com/" target="_blank"> IBM</a></td> |
| <td width="229"> kim(at)diamondtrail.com</td> |
| </tr> |
| <tr> |
| |
| <td width="111"> <span style="color: windowtext; text-decoration: none">Marc |
| Erickson</span></td> |
| |
| <td width="164"> <a href="http://www.inpriva.com/" target="_blank"> |
| Inpriva</a></td> |
| <td width="229"> cma(at)wimpzilla.com</td> |
| </tr> |
| <tr> |
| |
| <td width="111"> <span style="color: windowtext; text-decoration: none">Don |
| Jorgenson</span></td> |
| |
| <td width="164"> <a href="http://www.inpriva.com/" target="_blank"> |
| Inpriva</a></td> |
| <td width="229"> djorgenson(at)inpriva.com</td> |
| </tr> |
| <tr> |
| |
| <td width="111"> <span style="color: windowtext; text-decoration: none">Paul |
| Trevithick</span></td> |
| |
| <td width="164"> <a href="http://www.socialphysics.org/" target="_blank"> |
| Social Physics</a></td> |
| <td width="229"> paul(at)parityinc.net</td> |
| </tr> |
| <tr> |
| |
| <td width="111"> <span style="color: windowtext; text-decoration: none">Joel |
| West</span></td> |
| |
| <td width="164"> <a href="http://www.sjsu.edu/" target="_blank"> San |
| Jose State University</a></td> |
| <td width="229"> Joel.West(at)sjsu.edu</td> |
| </tr> |
| <tr> |
| |
| <td width="111"> <span style="color: windowtext; text-decoration: none">Grahame |
| Grieve</span></td> |
| |
| <td width="164"> Jiva eHealth Solutions</td> |
| <td width="229"> grahame(at)kestral.com.au</td> |
| </tr> |
| </table> |
| <p> </p><p><b>Contact</b><br> |
| Mr. Igor Yasno<br> |
| Chief Operating Officer<br> |
| International Technology Group<br> |
| 7608 Aston Court, Los Angeles, CA 91304<br> |
| Telephone: +1 818 206 4598 x. 711<br> |
| Facsimile: +1 818 206 4598<br> |
| E-Mail: |
| <a href="mailto:iyasno@intertechnogroup.com" style="color: blue; text-decoration: underline; text-underline: single"> |
| <span style="color: windowtext; text-decoration: none"> |
| iyasno@intertechnogroup.com</span></a><br> |
| Web: <a href="http://www.intertechnogroup.com/" style="color: blue; text-decoration: underline; text-underline: single">www.intertechnogroup.com</a><br> |
| </p> |
| </TD> |
| </TR> |
| <TR> |
| <TD valign="top"> </TD> |
| </TR> |
| </TBODY> |
| </TABLE> |
| </body> |
| </html> |
