You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: index.html
+50-28Lines changed: 50 additions & 28 deletions
Original file line number
Diff line number
Diff line change
@@ -71,25 +71,32 @@ <h3>Modules!</h3>
71
71
<h2>Architecture</h2>
72
72
<p>
73
73
The C3-PRO toolchain is made up of various software modules living in three areas: embedded into your <i>mobile app</i>, server pieces that live in the <i>www</i>, aka, “wild wild web”, and modules living <i>behind a firewall</i> with access to your backend.
74
+
Since data exchange happens via FHIR Resources (or encrypted versions thereof), you can easily substitute each component with your own solution.
The diagram above illustrates the traditional data flow in a C3-PRO environment.
81
+
On the mobile side, the iOS and Android <i>mobile frameworks</i> facilitate working with ResearchKit and ResearchStack, respectively, sending encrypted data to (and retrieving data from) the <i>receiver server</i> living on the open web.
82
+
Secure systems, capable of decrypting incoming data, are running behind the institution’s firewall and store data into an <i>i2b2 research backend</i>.
83
+
<p>
84
+
<p>
85
+
From the list <ahref="#modules">below</a> you can pick the modules that best suit your needs to design a custom data flow.
0 commit comments