ethercis-old.github.io/index.html at master · ethercis/ethercis-old.github.io · GitHub

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
<!doctype html>
<html>
  <head>
    <meta charset="utf-8">
    <meta http-equiv="X-UA-Compatible" content="chrome=1">
    <title>EtherCIS by ethercis</title>

    <link rel="stylesheet" href="stylesheets/styles.css">
    <link rel="stylesheet" href="stylesheets/github-light.css">
    <script src="javascripts/scale.fix.js"></script>
    <meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no">
    <!--[if lt IE 9]>
    <script src="//html5shiv.googlecode.com/svn/trunk/html5.js"></script>
    <![endif]-->
  </head>
  <body>
    <div class="wrapper">
      <header>
        <h1 class="header">EtherCIS</h1>
        <p class="header">an open source openEHR server</p>


        <ul>
          <li><a class="buttons github" href="https://github.com/ethercis">GitHub Profile</a></li>
        </ul>

      </header>
      <section>
        <p></p><h2 id="65746865726369732c20616e206f70656e20736f75726365206f70656e65687220736572766572">
<a id="ethercis-is-a-development-in-progress-and-is-currently-in-a-beta-mode-code-will--hopefully--be-updated-frequently-interested-users-or-testers-can-post-support-request-and-issues-at-ethercis-support" class="anchor" href="#ethercis-is-a-development-in-progress-and-is-currently-in-a-beta-mode-code-will--hopefully--be-updated-frequently-interested-users-or-testers-can-post-support-request-and-issues-at-ethercis-support" aria-hidden="true"><span class="octicon octicon-link"></span></a>
Ethercis is a development in progress and is currently in a BETA mode. Code will -hopefully- be updated frequently. Interested users or testers can post support request and issues at: <a href="https://www.assembla.com/spaces/ethercis-support">ethercis support</a>
</h2><p>EtherCIS (<i>Ethereal Clinical Information System</i>) is an Open Source platform compatible with the <a href="http://openehr.org/">openEHR </a>standard. It is design to allow simple interactions with clients using<a href="https://ehrscape.com/index.html"> </a><a href="http://en.wikipedia.org/wiki/Representational_state_transfer">RESTful </a>API and persist clinical data in a separate DB engine. Clinical data are exchanged using different formats:</p><ul>
<li>FLAT JSON: which is a flatten representation of access path along with the corresponding field value</li>
<li>Canonical XML: representing an openEHR composition in standard XML</li>
</ul><p>For more details on data representation in openEHR see this <a href="https://github.com/handihealth/c4h_sits/blob/master/docs/general/openehr_intro.md">page</a></p><p></p><p>The core component of the architecture is
a persistence engine that leverage new capabilities introduced recently
in several RDBMS in particular the support of relational and NoSQL.
datatypes in the single table structures. Although EtherCIS is flexible
in term of choice of DB, in this implementation, we use <a href="http://www.postgresql.org/docs/9.4/static/release-9-4.html">PostgreSQL 9.4</a> and <a href="http://www.postgresql.org/docs/9.4/static/datatype-json.html">JSONB </a>datatype.
This is key feature since clinical data can be used with standard data
query/mining tools in the context of clinical studies for instance. The persistence layer is using extensively<a href="http://www.jooq.org/"> jOOQ 3.5</a>.
This library supports various RDBMS and allows very neat SQL coding in
Java. It allows to migrate the persistence layers to suit a target
production environment, for example to deploy with Oracle or DB2.</p><p>Clinical records are automatically versioned by the platform following an update or a delete. To retrieve a specific version, the request adds a version number to a record id (in openEHR terms, this is done by appending a version number to a composition Id).  <br></p><p>Security is an important feature of the platform and compliance with ISO18308 and most national medico-legal regulations
(HIPAA, ASIP etc.) has been a key driver of this system design. Patient data
privacy, security and controls of accesses as well as auditing user activities
are built-in functions of the platform.. We use a flexible framework provided by <a href="http://shiro.apache.org/">Apache Shiro</a>
supporting environment specific policies. Depending on the
requirements, fine grained security accesses can be implemented to
support for example a patent's informed consent. <br></p>EtherCIS
implement a service model based on a component architecture allowing
simple system modification and fine grained runtime administration via
JMX. The platform can be scaled to larger settings as various mechanisms
can be used to allow distributed caches to support session tokens
across multiple instances, database clustering, foreign data
integration, clinical model caching etc.
      </section>
      <footer>
        <p><small>Hosted on <a href="https://pages.github.com">GitHub Pages</a> using the Dinky theme</small></p>
      </footer>
    </div>
    <!--[if !IE]><script>fixScale(document);</script><![endif]-->

  </body>
</html>