<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Helios Software - Medium]]></title>
        <description><![CDATA[Helios Software is a Boston-based health technology company that delivers professional product engineering services and also offers a FHIR-based clinical data solution. - Medium]]></description>
        <link>https://medium.com/helios-software?source=rss----9b1b9ed586ce---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Helios Software - Medium</title>
            <link>https://medium.com/helios-software?source=rss----9b1b9ed586ce---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 04:58:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/helios-software" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Integrative Molecular Diagnosis — A FHIR Integration Approach]]></title>
            <link>https://medium.com/helios-software/integrative-molecular-diagnosis-a-fhir-integration-approach-7c40c98f24ce?source=rss----9b1b9ed586ce---4</link>
            <guid isPermaLink="false">https://medium.com/p/7c40c98f24ce</guid>
            <dc:creator><![CDATA[Steve Munini]]></dc:creator>
            <pubDate>Mon, 12 Jul 2021 19:35:48 GMT</pubDate>
            <atom:updated>2021-07-12T19:35:48.413Z</atom:updated>
            <content:encoded><![CDATA[<h3>Integrative Molecular Diagnosis — A FHIR Integration Approach</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_EonWGwgYDSwTSpPJUqjvw.jpeg" /></figure><p><a href="https://www.chla.org/what-a-difference-a-day-makes">What A Difference A Day Makes</a>¹ is the story of Michelle, the 2-year-old daughter of Christina and Joe Lowry. The lump on Michelle’s neck was initially thought to be a bug bite, or a swollen lymph node resulting from an infection. When antibiotics didn’t work, a biopsy revealed that it was, in fact, a sarcoma.</p><p>The team at Children’s Hospital Los Angeles quickly ruled out radiation and surgery due to the location of the aggressive tumor which had rapidly grown in just a matter of days and was now blocking 50 percent of Michelle’s airway. The only path forward was some type of chemotherapy. The team at Children’s Hospital Los Angeles knew the type of cancer Michelle had, and they knew that they could use <a href="https://www.chla.org/oncokids-cancer-panel">OncoKids®</a>, a unique next-generation, sequence-based panel to identify the genetic alterations of Michelle’s tumor.</p><p>After taking a sample of the tumor, within 24 hours, the gene mutation was understood, and the team turned to rapidly identify a drug target. Michelle was given an oral drug called larotrectinib. Michelle responded to the medication within 24 hours and was shortly able to go home with her family.</p><h3>The Power of Integration</h3><p>Michelle’s successful outcome is the result of the rapid integration of complex healthcare data. Organizing that data, and presenting it in a coherent fashion to clinicians is an orchestration challenge. Just think about the different departments within the hospital that needed to collaborate rapidly to save Michelle’s life:</p><ul><li>Clinicians working directly with the patient</li><li>MRIs performed by the Radiology department</li><li>Molecular data from the <a href="https://www.chla.org/center-personalized-medicine">Center for Personalized Medicine</a></li><li>Slide data originating in the Pathology department and from the Bio Repository department</li></ul><p>It’s unrealistic to think that one individual would understand all of these specialties, their systems, and data, understand the patient’s cancer, and understand the latest treatment options available. A team approach must be employed.</p><p>In recent years, integrative reports have been produced to assist clinicians in their diagnostic work and treatment selection, however, more can be done. Clinicians are now asking the question:</p><blockquote>Can we further accelerate our diagnostic and treatment selection pipelines, especially for cases like Michelle’s which are time-critical?</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2Fb2dplw%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Ff%2Fb2dplw&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/ffca83dc05ecf5bf1c077a247da206ce/href">https://medium.com/media/ffca83dc05ecf5bf1c077a247da206ce/href</a></iframe><h3>FHIR as an Architecture for Integrative Molecular Diagnosis</h3><p>Clinical researchers are asking next-generation machine learning and analytic questions to help accelerate our understanding of the massive amounts of data that emanate from modern imaging, slide data, and genomic systems.</p><p>Questions like:</p><ul><li>Can we predict the cancer type from imaging data?</li><li>Can we predict the gene of interest?</li><li>Can we predict the mutation of interest?</li><li>Can we predict outcome?</li><li>Can we determine the best therapeutic/pharmacological solution?</li><li>How rapidly and safely can we answer these questions?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y1MhCq4XM2nCgD3FRmx2wA.jpeg" /></figure><p>Numerous sources of data must be rapidly accessed, integrated, and analyzed, often using different analysis techniques and technologies. Here is a partial list of data sources that may need to be accessed:</p><ul><li>EMR patient, encounter information, prior and preliminary test results.</li><li>Pathology system slide data for tumor/tissue resection, and molecular reports for genetic testing including cyogenetics, clinical microarrays, and next-generation sequencing tests.</li><li>Electronic Slide Management system</li><li>MRI data</li><li>Molecular data including variant calling files and phenotype/clinical indications</li><li>Oncology database of pharmacogenomics targets</li><li>Oncology database of chemotherapy regimen</li></ul><p>Assembling a complete optimal treatment selection pipeline would be well beyond the scope of this article, however, we wish to explore how FHIR and the Helios FHIR Server may be used to provide an architecture for integrative molecular diagnosis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QJSA_DXf4LSU5_Kk.png" /><figcaption><a href="https://blog.heliossoftware.com/fhir-architectural-patterns-ae828b13d40c">https://blog.heliossoftware.com/fhir-architectural-patterns-ae828b13d40c</a></figcaption></figure><p>Clearly, the integration challenges in this problem set are abundant:</p><ul><li>We need to work with many different kinds and types of healthcare data.</li><li>We need to rapidly integrate the data into a single, unified data model and data environment.</li><li>We need to rapidly apply advanced analytics to the problem at hand.</li></ul><p>FHIR, and the Helios FHIR Server’s implementation of the standard is ideally suited to solving this problem.</p><ul><li>FHIR provides a standards-based domain model. Everyone on the analytics team can think and speak in terms of <a href="https://blog.heliossoftware.com/the-r-in-fhir-resources-eda4a2f3612">FHIR Resources</a>.</li><li>The FHIR Standard has built-in extensibility, enabling us to easily describe nonstandard data elements.</li><li>Support for FHIR by EMRs is growing rapidly, and with new <a href="https://hl7.org/fhir/uv/bulkdata/">bulk data API</a> support becoming available, we will have access to even more FHIR data.</li><li>The Helios FHIR Server is a <a href="https://blog.heliossoftware.com/a-fhir-native-analytics-approach-d977da8538d2">FHIR-native</a> healthcare analytics solution, which uses FHIR as its data model and exposes it for analytic use cases.</li><li>The Helios FHIR Server enables analytics professionals and developers to use their <a href="https://blog.heliossoftware.com/a-fhir-native-analytics-approach-redux-python-cdadceef40c6">preferred tools of choice</a>.</li></ul><p>This article explores two areas of integrative molecular diagnosis:</p><ul><li><strong>Identifying Cancer from Slide Images</strong></li><li><strong>Rapidly Summarizing Complex Textual Reports with NLP</strong></li></ul><blockquote>We use FHIR as an integrative technology to characterize and describe these complex healthcare data types as well as store our resulting computed analysis.</blockquote><h3>Identifying Cancer from Slide Images</h3><p>Let’s dive into one part of the overall pipeline — identifying cancer from slide images. In the example below, we explore how a research team might identify cancer using machine learning, and the Helios FHIR Server. It is important to note that this example is not a production system — it is a showcase of how a FHIR architecture may be implemented.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HinmbVVxMle4TOzdwu1Thg.jpeg" /></figure><p>Below is a step-by-step guide using the Helios FHIR Server, Cassandra, Spark and Python. The overall program flow includes:</p><ul><li>Load required libraries</li><li>Load train and test image data, and train the model using Databrick’s Machine Learning package.</li><li>Search for a patient with last name Chalmers, and navigate the FHIR Resource relationships to collect the patient’s recent Media FHIR Resources containing images to test.</li><li>Perform the image analysis.</li><li>Create a new RiskAssessment FHIR Resource to store the results of the image analysis including its prediction average.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OzFZx1P-ezxODpaIinxrSg.png" /><figcaption>FHIR Resources used in this example.</figcaption></figure><h3>Image Analysis Code Walkthrough</h3><p>The example code below is from the following Jupyter project file:</p><p><a href="https://github.com/HeliosSoftware/pyspark-analytics/blob/master/cancer-prediction-full.ipynb">https://github.com/HeliosSoftware/pyspark-analytics/blob/master/cancer-prediction-full.ipynb</a></p><p>First, we load the train and test data into a dataframe.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1v3IeLP6JhyfhLBKwhHbkg.png" /></figure><p>Next, we prepare the data pipeline. We use the DeepImageFeaturizer that uses TensorFlow which enables us to turn an image file into a machine-understandable data structure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YWJT9fGAGuFPFKokGi2m-Q.png" /></figure><p>Here, we are training the model and transforming them to obtain positive and negative predictions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r5sE0spLxTVXsun-N2om7g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vkor5ZiO70CNxXdz1-pGDg.png" /></figure><h3>Using the Prediction Model</h3><p>Now that we have trained the model (p_model), we will use it in “production” to predict positive/negative image data for a patient with the last name of Chalmers.</p><p>Here, the Python code is performing a series of FHIR queries against the Helios FHIR Server to obtain the necessary image data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e3w47ltQXpbk4YmGtqkkKQ.png" /></figure><p>Next, we use the previously trained model to perform the prediction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1EoZzisi91YewuEBRMChhA.png" /></figure><p>Next, we obtain a prediction average as an expression of prediction confidence:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IjrRydk01m0ENz6IjByPkA.png" /></figure><p>Finally, we create a new <a href="http://hl7.org/fhir/riskassessment.html">RiskAssessment</a> FHIR Resource to store our prediction, linking the <a href="http://hl7.org/fhir/patient.html">Patient</a>, <a href="http://hl7.org/fhir/encounter.html">Encounter</a> and <a href="http://hl7.org/fhir/diagnosticreport.html">DiagnosticReport</a> using FHIR References (See the References Between Resources in <a href="https://blog.heliossoftware.com/the-r-in-fhir-resources-eda4a2f3612">this article</a> for more information on how references work in FHIR).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QSj8rUdZxZdf1RjHI07ihw.png" /></figure><h3>How Does It Work?</h3><p>Image classification is a binary classification problem. The most complicated part is turning the images into a data structure on which the algorithm can run. This implementation uses the “InceptionV3” model in a “DeepImageFeaturizer” to take advantage of TensorFlow to turn the images into features, which are essentially arrays of numbers. Then, we will Spark’s LogisticRegression classifier to build a model that can read the features and labels of malignant or benign images and construct a model (or function) that can take any new feature and output a prediction of either malignant or benign.</p><p>An excellent article describing this approach is <a href="https://medium.com/linagora-engineering/making-image-classification-simple-with-spark-deep-learning-f654a8b876b8">Making Image Classification Simple With Spark Deep Learning</a>.</p><h3>Rapidly Summarizing Complex Textual Reports with NLP</h3><p>In an integrative molecular diagnostic approach, the analysis we did above on cancer image slides is just one data point that may help clinicians rapidly arrive at a diagnosis. Next, we explore using NLP (Natural Language Processing) to quickly synthesize and summarize a potentially complex report for faster reading.</p><p>First, we load the <a href="https://nlp.johnsnowlabs.com/">sparknlp</a> package from John Snow Labs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PyIQC4LLnZ_dWM0dNbPgaw.png" /></figure><p>Next, we summarize the text using NLP for easier, more succinct reading. We use an extractive algorithm that identifies the most important sentences and produces an output of 50 words or less.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lrKIhvmoO1MCyw-hsw6Kug.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z3phtfuC3Bs5Ak4WEDrKTg.png" /></figure><p>Here, we are adding the summary text to the DiagnosticReport, and issuing a PUT command to the Helios FHIR Server which creates a new version (version 2) of the same DiagnosicReport.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O-CeEtGUS4rWQUOb3ddiAw.png" /></figure><h3>Setup HOW TO</h3><p>What follows is a step-by-step guide for running this example yourself. The steps below help you install the necessary prerequisites, install the Cassandra database, install the Helios FHIR Server, install Spark, and finally run the Jupyter notebook.</p><h3>Prerequisites</h3><p>You will need two different versions of Java available on your computer. These instructions assume a Mac environment.</p><ul><li>Java 8 — for running Cassandra and Spark</li></ul><pre>$ brew tap AdoptOpenJDK/openjdk<br>$ brew cask install adoptopenjdk8</pre><ul><li>Java 11 — for running the Helios FHIR Server</li></ul><pre>$ brew cask install adoptopenjdk11</pre><p>Add the following lines to your ~/.bash_profile so you can easily switch between the two versions of Java:</p><pre>export JAVA_8_HOME=$(/usr/libexec/java_home -v1.8)<br>export JAVA_11_HOME=$(/usr/libexec/java_home -v11)<br>alias java8=&#39;export JAVA_HOME=$JAVA_8_HOME&#39;<br>alias java11=&#39;export JAVA_HOME=$JAVA_11_HOME&#39;</pre><p>Refresh your environment:</p><pre>$ source ~/.bash_profile</pre><p>Always check your version of java with:</p><pre>$ java -version<br>openjdk version &quot;11.0.5&quot; 2019-10-15<br>OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.5+10)<br>OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.5+10, mixed mode)</pre><p>Above, you can see I’m running Java 11. Now, with this command, I’m running Java 8.</p><pre>$ java8<br>$ java -version<br>java version &quot;1.8.0_211&quot;<br>Java(TM) SE Runtime Environment (build 1.8.0_211-b12)<br>Java HotSpot(TM) 64-Bit Server VM (build 25.211-b12, mixed mode)</pre><h3>Install Cassandra</h3><p>Follow <a href="https://docs.heliossoftware.com/#cassandra-quickstart">these instructions</a> to install Cassandra locally.</p><h3>Install the Helios FHIR Server</h3><p>Navigate to <a href="https://heliossoftware.com/download-enterprise-edition/">https://heliossoftware.com/download-enterprise-edition/</a> and download the latest version of the Helios FHIR Server Enterprise Edition.</p><p>Follow <a href="https://docs.heliossoftware.com/#installing-helios-fhir-server">these instructions</a> to install the Helios FHIR Server.</p><p>After you have logged in to the administrative user interface, enable the following FHIR Resources:</p><pre>DiagnosticReport<br>Encounter<br>Media<br>Patient<br>Specimen</pre><h3>Clone the pyspark-analytics project</h3><p>This is the GitHub project that contains the Jupyter project we will be using.</p><pre>$ git clone git@github.com:HeliosSoftware/pyspark-analytics.git</pre><p>This project also contains a folder of sample data in “/sample-data”</p><h3>Import the Sample Data</h3><p>Build and run the fhir-importer using Java 11.</p><pre>$ java11<br>$ git clone git@github.com:HeliosSoftware/fhir-importer.git<br>$ cd fhir-importer<br>$ mvn clean install</pre><p>The fhir-importer jar will reside in the /target folder.</p><p>Run the following command.</p><pre>$ java -jar &lt;path to fhir-importer&gt;/fhir-importer-0.0.1-SNAPSHOT.jar -directory &lt;path to pyspark-analytics project&gt;/sample-data</pre><h3>Install Jupyter</h3><p>Assuming you have python installed on your computer, simply execute the following commands:</p><pre>$ sudo pip3 install jupyter<br>$ sudo pip3 install numpy</pre><h3>Install Image Classification Dependencies</h3><pre>pip install tensorflow<br>pip install nose<br>pip install pillow<br>pip install keras<br>pip install h5py<br>pip install py4j</pre><p>Make sure to be running Python 3.7, <em>not</em> 3.8.</p><h3>Install Spark</h3><p>Download and unzip spark from <a href="https://spark.apache.org/downloads.html">https://spark.apache.org/downloads.html</a></p><p>Select the 2.4.x Spark release and the “Prebuilt for Apache Hadoop 2.7and later” package type.</p><p>Un-tar Spark to a convenient folder.</p><p>Add the following to your ~/.bash_profile</p><pre>export SPARK_HOME=&quot;/Users/[your username]/[a directory]/spark-2.4.7-bin-hadoop2.7&quot; <br>export PYSPARK_DRIVER_PYTHON=jupyter <br>export PYSPARK_DRIVER_PYTHON_OPTS=&#39;notebook&#39; <br>export PATH=$SPARK_HOME/bin:$PATH</pre><p>Refresh your environment:</p><pre>$ source ~/.bash_profile</pre><h3>Clone the pyspark-analytics project</h3><p>This is the GitHub project that contains the Jupyter project we will be using.</p><pre>$ git clone git@github.com:HeliosSoftware/pyspark-analytics.git</pre><h3>Run pyspark!</h3><p>Run the following command in the same directory as your jupyter notebook (ie where you cloned the <a href="https://github.com/HeliosSoftware/pyspark-analytics">https://github.com/HeliosSoftware/pyspark-analytics</a> project)</p><p>Make sure to be running Java 8 before running pyspark. Some of the libraries used in this project require Java 8.</p><pre>$ pyspark --driver-memory 12g --packages databricks:spark-deep-learning:1.5.0-spark2.4-s_2.11</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*peFZyg4vEFHuN14_.png" /></figure><p>Open the cancer-prediction-full.ipynb notebook file and run it! You will find detailed comments describing the logic in the notebook itself.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2Fe99955%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Ff%2Fe99955&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/2f6db2f60a2e5b981bbf2efe2826e875/href">https://medium.com/media/2f6db2f60a2e5b981bbf2efe2826e875/href</a></iframe><pre><strong>References</strong></pre><pre>1.  Children&#39;s Hospital of Los Angeles | <a href="https://www.chla.org/what-a-difference-a-day-makes">What A Difference A Day Makes</a> | Updated on November 2019</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c40c98f24ce" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helios-software/integrative-molecular-diagnosis-a-fhir-integration-approach-7c40c98f24ce">Integrative Molecular Diagnosis — A FHIR Integration Approach</a> was originally published in <a href="https://medium.com/helios-software">Helios Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A FHIR-Native Analytics Approach Redux — Python]]></title>
            <link>https://medium.com/helios-software/a-fhir-native-analytics-approach-redux-python-cdadceef40c6?source=rss----9b1b9ed586ce---4</link>
            <guid isPermaLink="false">https://medium.com/p/cdadceef40c6</guid>
            <dc:creator><![CDATA[Steve Munini]]></dc:creator>
            <pubDate>Fri, 26 Feb 2021 15:57:52 GMT</pubDate>
            <atom:updated>2021-02-26T16:05:34.881Z</atom:updated>
            <content:encoded><![CDATA[<h3>A FHIR-Native Analytics Approach Redux — Python</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gf4pUSzoalk500dl1hsr5w.jpeg" /></figure><p>Our original article <a href="https://blog.heliossoftware.com/a-fhir-native-analytics-approach-d977da8538d2">A FHIR-Native Analytics Approach</a> was one of our most popular blog articles. As its readership grew, we decided to do several hands-on workshops using its contents, and we also had many developers independently work through the steps outlined in the article.</p><p>We learned a lot since authoring the original article, and we wanted to refresh, simplify, and improve the article overall. So, here is a redux version of A FHIR-Native Analytics Approach.</p><blockquote><a href="https://www.dictionary.com/browse/redux">redux</a> [ ri-<strong>duhks</strong> ]</blockquote><blockquote><strong>adjective — </strong>brought back; resurgent</blockquote><h3>What did we learn?</h3><p>Since the original publication of A FHIR-Native Analytics Approach, <strong><em>we have only seen strong and increasing demand from developers</em></strong> who wish to ask analytic questions of their FHIR data. This, of course, has a lot to do with the growth of the FHIR standard itself. Most of the interest has come from organizations that are building new products, versus those who are mapping from legacy architectures. We do envision that as newer options for accessing large amounts of FHIR data become available, most notably the <a href="https://hl7.org/fhir/uv/bulkdata/index.html">FHIR Bulk Data Access</a> specification, we will see even more demand for analytic workloads such as the ones we outlined in the original article.</p><p><strong><em>Developers really want access to a FHIR data model.</em></strong> A <a href="https://chat.fhir.org/#narrow/stream/179219-analytics-on.20FHIR/topic/FHIR.20SQL.20Mappings">common question</a> in the FHIR developer community is:</p><blockquote>“Can anybody direct me to a tool (preferably open source tool) that can convert FHIR resources to a relational data model either columnar storage or pure-relational for querying purposes and possibly for analytical workloads?”</blockquote><p>The FHIR Specification doesn’t publish a SQL data model, nor should it. The FHIR Specification is an interoperability standard, and it’s up to implementers of the FHIR Specification to design and implement the standard as they see fit. The Helios FHIR Server provides a Cassandra data model expressly for this purpose.</p><p><strong><em>Developers really want to use their preferred languages and tools.</em></strong> We received some great feedback that readers liked the R example, however many wish that it was also available in Python, which happens to be much more popular than R.</p><p><strong>There have been some significant advancements in the Spark Cassandra Connector driver. </strong>For a complete download of the recent changes, watch Russell Spitzer’s presentation: <a href="https://www.youtube.com/watch?v=CtFWVcuqm0g">DataSource V2 and Cassandra — A Whole New World</a>.</p><h3>Recommended Reading</h3><p>If you have landed here first, and haven’t had a chance to do a complete walk-through of <a href="https://blog.heliossoftware.com/a-fhir-native-analytics-approach-d977da8538d2">A FHIR-Native Analytics Approach</a>, we would recommend reading the following sections of that article:</p><ul><li>The Introduction</li><li>Overview</li><li>Why Cassandra?</li><li>Spark and Cassandra: Working Together</li><li>Helios FHIR Server’s Data Model</li><li>Bringing It All Together</li></ul><h3>What hasn’t changed?</h3><p>Ok! Let’s dive in, but before we do, what hasn’t changed from the original article?</p><ul><li>We are still using Synthea to generate sample data. <a href="https://github.com/synthetichealth/synthea">Synthea</a>, is an open-source tool developed by <a href="https://health.mitre.org/">The MITRE Corporation</a>. Synthea is a Synthetic Patient Population Simulator. Synthea can output synthetic, realistic (but not real), patient data and associated health records in a variety of formats, including HL7 FHIR R4.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/666/0*_5ENdDF-1corLZvt.png" /></figure><ul><li>We are still running Spark on Cassandra.</li><li>We are still using the <a href="https://heliossoftware.com/helios-fhir-server/">Helios FHIR Server</a> of course! There have been several updates and optimizations to the Helios FHIR Server since the original publication of the article, so go ahead and download the latest version.</li><li>The example analytic problem we are solving has not changed. The example predicts which patients have asthma. The overall program flow also has not changed — it’s simply reimplemented in Python. The example prepares data for analysis, trains predictive models, uses cross-validation to select the best model, and finally uses the Lasso algorithm to reduce input complexity.</li></ul><h3>What has changed?</h3><ul><li>In this article, we are using Python instead of R. Python is a more popular programming language, and we wanted to showcase that different language can be used just as easily as R.</li><li>We are using the new <a href="https://github.com/datastax/spark-cassandra-connector">Spark Cassandra Connector</a> from DataStax.</li><li>We are now using the open-source <a href="https://cassandra.apache.org/">Apache Cassandra</a> instead of DataStax Enterprise Analytics. Many of the key enabling features required to connect Cassandra to/from Spark has been moved to the open-source Spark Cassandra Connector. Thank you, DataStax for making this possible!</li><li>The original article included many steps for setting up and configuring 4 EC2 instances on AWS (3 Cassandra nodes, and a Helios FHIR Server). We greatly simplified the steps in this article, and you no longer need to use AWS. The instructions below are intended to be run on your local laptop/desktop environment.</li><li>Instead of R Studio, we are using a <a href="https://jupyter.org/">Jupyter</a> notebook.</li><li>We have a fancy new data upload tool that is really speedy and enables parallel import of the Synthea data. It’s called simply <a href="https://github.com/HeliosSoftware/fhir-importer">fhir-importer</a>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jzfoh_mGpfMgimgpbzQjqg.png" /></figure><h3>Prerequisites</h3><p>You will need two different versions of Java available on your computer. These instructions assume a Mac environment.</p><ul><li>Java 8 — for running Cassandra</li></ul><pre>$ brew tap AdoptOpenJDK/openjdk<br>$ brew cask install adoptopenjdk8</pre><ul><li>Java 11 — for running the Helios FHIR Server</li></ul><pre>$ brew cask install adoptopenjdk11</pre><p>Add the following lines to your ~/.bash_profile so you can easily switch between the two versions of Java:</p><pre>export JAVA_8_HOME=$(/usr/libexec/java_home -v1.8)<br>export JAVA_11_HOME=$(/usr/libexec/java_home -v11)<br>alias java8=&#39;export JAVA_HOME=$JAVA_8_HOME&#39;<br>alias java11=&#39;export JAVA_HOME=$JAVA_11_HOME&#39;</pre><p>Refresh your environment:</p><pre>$ source ~/.bash_profile</pre><p>Always check your version of java with:</p><pre>$ java -version<br>openjdk version &quot;11.0.5&quot; 2019-10-15<br>OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.5+10)<br>OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.5+10, mixed mode)</pre><p>Above, you can see I’m running Java 11. Now, with this command, I’m running Java 8.</p><pre>$ java8<br>$ java -version<br>java version &quot;1.8.0_211&quot;<br>Java(TM) SE Runtime Environment (build 1.8.0_211-b12)<br>Java HotSpot(TM) 64-Bit Server VM (build 25.211-b12, mixed mode)</pre><h3>Install Cassandra</h3><p>Follow <a href="https://docs.heliossoftware.com/#cassandra-quickstart">these instructions</a> to install Cassandra locally.</p><h3>Install the Helios FHIR Server</h3><p>Navigate to <a href="https://heliossoftware.com/download-enterprise-edition/">https://heliossoftware.com/download-enterprise-edition/</a> and download the latest version of the Helios FHIR Server Enterprise Edition.</p><p>Follow <a href="https://docs.heliossoftware.com/#installing-helios-fhir-server">these instructions</a> to install the Helios FHIR Server.</p><p>After you have logged in to the administrative user interface, enable the following FHIR Resources:</p><pre>AllergyIntolerance<br>Bundle<br>CarePlan<br>CareTeam<br>Claim<br>Condition<br>Coverage<br>Device<br>DiagnosticReport<br>DocumentReference<br>Encounter<br>ExplanationOfBenefit<br>ImagingStudy<br>Immunization<br>Location<br>Medication<br>MedicationAdministration<br>MedicationRequest<br>Observation<br>Organization<br>Patient<br>Practitioner<br>PractitionerRole<br>Procedure<br>Provenance<br>ServiceRequest<br>SupplyDelivery<br>ExplanationOfBenefit</pre><h3>Synthea</h3><p>Next, download Synthea from GitHub using <a href="https://git-scm.com/">git</a>.</p><pre>git clone <a href="https://github.com/synthetichealth/synthea.git">https://github.com/synthetichealth/synthea.git</a></pre><p>Let’s generate 1000 simulated patients and data and examine the output.</p><pre>cd synthea<br>./run_synthea -p 1000<br>cd output/fhir<br>[...Examine some of the FHIR output...]</pre><h3>Import the Sample Data</h3><p>Build and run the fhir-importer using Java 11.</p><pre>$ java11<br>$ git clone git@github.com:HeliosSoftware/fhir-importer.git<br>$ cd fhir-importer<br>$ mvn clean install</pre><p>The fhir-importer jar will reside in the /target folder.</p><p>Run the following command.</p><pre>$ java -jar [path to fhir-importer]/fhir-importer-0.0.1-SNAPSHOT.jar -directory [path-to-output/fhir] -regex “.*.json”</pre><h3>Install Jupyter</h3><p>Assuming you have python installed on your computer, simply execute the following commands:</p><pre>$ sudo pip3 install jupyter<br>$ sudo pip3 install numpy</pre><h3>Install Spark</h3><p>Download and unzip spark from <a href="https://spark.apache.org/downloads.html">https://spark.apache.org/downloads.html</a></p><p>Select the 3.0.x Spark release and the “Prebuilt for Apache Hadoop 3.2 and later” package type.</p><p>Un-tar Spark to a convenient folder.</p><p>Add the following to your ~/.bash_profile</p><pre>export SPARK_HOME=&quot;/Users/[your username]/[a directory]/spark-3.0.1-bin-hadoop3.2&quot; <br>export PYSPARK_DRIVER_PYTHON=jupyter <br>export PYSPARK_DRIVER_PYTHON_OPTS=&#39;notebook&#39; <br>export PATH=$SPARK_HOME/bin:$PATH</pre><p>Refresh your environment:</p><pre>$ source ~/.bash_profile</pre><h3>Clone the pyspark-analytics project</h3><p>This is the GitHub project that contains the Jupyter project we will be using.</p><pre>$ git clone git@github.com:HeliosSoftware/pyspark-analytics.git</pre><h3>Run pyspark!</h3><p>Run the following command in the same directory as your jupyter notebook (ie where you cloned the <a href="https://github.com/HeliosSoftware/pyspark-analytics">https://github.com/HeliosSoftware/pyspark-analytics</a> project)</p><pre>$  pyspark --packages com.datastax.spark:spark-cassandra-connector_2.12:3.0.0</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ErHJN4PX2IBKHqRk7tFRww.png" /></figure><p>Open the fhir-analytics-with-python.ipynb notebook file and run it! You will find detailed comments describing the logic in the notebook itself.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2Fe99955%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Ff%2Fe99955&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/2f6db2f60a2e5b981bbf2efe2826e875/href">https://medium.com/media/2f6db2f60a2e5b981bbf2efe2826e875/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cdadceef40c6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helios-software/a-fhir-native-analytics-approach-redux-python-cdadceef40c6">A FHIR-Native Analytics Approach Redux — Python</a> was originally published in <a href="https://medium.com/helios-software">Helios Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[FHIR Implementation Guides & A Provider Directory Implementation]]></title>
            <link>https://medium.com/helios-software/fhir-implementation-guides-a-provider-directory-implementation-3eed4b2f146b?source=rss----9b1b9ed586ce---4</link>
            <guid isPermaLink="false">https://medium.com/p/3eed4b2f146b</guid>
            <dc:creator><![CDATA[Steve Munini]]></dc:creator>
            <pubDate>Wed, 10 Feb 2021 01:43:06 GMT</pubDate>
            <atom:updated>2021-02-10T02:23:25.193Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kVBvaK4T5L_DAhQfAwnLyQ.jpeg" /></figure><h3>Introduction</h3><p>Reaching the summit of Mount Everest is an extremely difficult and dangerous adventure. The first two people to accomplish this historical feat were Edmund Hillary and <a href="https://en.wikipedia.org/wiki/Tenzing_Norgay">Tenzing Norgay</a>. Tenzing Norgay was a Sherpa who helped Hillary plan, climb, and ultimately accomplish the goal of summitting Mount Everest.</p><p>Tenzing Norgay was an accomplished mountaineer and had been involved in numerous Everest scouting expeditions and several unsuccessful summit attempts prior to the successful summit with Hillary in 1953.</p><p>Without Tenzing Norgay, it is unlikely that Edmund Hillary would have known about:</p><ul><li>A climb path up the face of Everest that would yield the highest probability of success</li><li>The intricacies of the Everest weather patterns and knowledge when it is safe to climb, and when to camp</li><li>Equipment to bring, equipment to leave behind, and</li><li>Climbing techniques and strategy specific to Everest.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p4iUKAHveC1iwfDkfiRD6g.png" /></figure><p>Naturally, journalists wanted to know “Which of the two men had the right to the glory of being the first one, and who was merely the second, the follower?” Colonel Hunt, the expedition leader, declared, “They reached it together, as a team.”</p><p>Without Tenzing Norgay’s experience, knowledge, skill, and strength, Edmund Hillary’s place in history may have been limited to placement on a list of yet another mountaineer who unsuccessfully summitted Everest and largely forgotten by history.</p><p>When faced with a challenge, it’s often best to have a team of people who have attempted the challenge before, perhaps many times, and know which mistakes to avoid. Prior knowledge and experience is an invaluable tool helping to guide us on a path to success.</p><p>Thankfully, developing healthcare software isn’t nearly as perilous as climbing Mount Everest! Our industry nonetheless often encounters the same or similar interoperability challenges again and again, and thankfully, we have a way to document and share implementation decisions so that we can learn rapidly from one another in the FHIR Community.</p><h3>Implementation Guides — Defined</h3><p>The HL7 FHIR Specification defines an <a href="https://www.hl7.org/fhir/implementationguide.html">Implementation Guide</a> as:</p><blockquote>“A set of rules of how a particular interoperability or standards problem is solved — typically through the use of FHIR resources. This resource is used to gather all the parts of an implementation guide into a logical whole and to publish a computable definition of all the parts.”</blockquote><p>An Implementation Guide is a set of rules about how FHIR may be used to solve a particular problem in healthcare. The FHIR Specification is quite broad and complete with many FHIR Resources, Search Parameters, Extensions, Profiles, and other capabilities. An Implementation Guide documents design decisions provides context for a developer, and affirmatively lists ingredients of FHIR concepts for the problem at hand.</p><p>It is worthwhile to clarify two terms. The FHIR Specification defines a FHIR Resource named “ImplementationGuide.” FHIR Servers can read, write, and search upon <a href="http://hl7.org/fhir/implementationguide.html">ImplementationGuide FHIR Resources</a>. It is important to distinguish ImplementationGuides from an “Implementation Guide.” Implementation Guides are published on the web and can be generated using the <a href="https://confluence.hl7.org/display/FHIR/IG+Publisher+Documentation">FHIR Implementation Guide Publisher</a> tool.</p><h3>Provider Directory — An Example</h3><p>Let’s look at a real-world example of an Implementation Guide by examining the <a href="http://hl7.org/fhir/us/davinci-pdex-plan-net/">PDEX Payer Network (or Plan-Net) Implementation Guide</a>, and our implementation of it in the <a href="https://heliossoftware.com/provider-directory/">Helios FHIR Server — Provider Directory</a> product.</p><h4>What’s a Provider Directory?</h4><p>A provider directory enables 3rd parties to develop applications that consumers and providers can query the participants in a payer’s network. This fulfills one of the core requirements of the CMS Final Rule and the 21st Century Cures Act. The CMS Final Rule focuses heavily on interoperability. It aims to start the process of liberating data and ensuring patients are the primary beneficiary of this process, and a provider directory is exactly what you need to accomplish this interoperability.</p><p>On January 2021, the CMS Interoperability and Patient Access Final Rule began to take effect (with a 6-month discretionary period due to the pandemic). By July 2021, CMS requires a new standard for both a patient access API and provider access API.</p><p>The patient access API impacts payer organizations in a significant way. It requires them to implement, test, and monitor a secure standard-based API that is accessible to third-party apps and developers. Importantly, these must be FHIR based APIs, and implementing the <a href="http://hl7.org/fhir/us/davinci-pdex-plan-net/">PDEX Payer Network (or Plan-Net) Implementation Guide</a> satisfies this requirement.</p><h4>A Quick Tour Through the Implementation Guide</h4><p>The PDEX Payer Network Implementation Guide is described as:</p><blockquote>“This implementation guide defines a FHIR interface to a health insurer’s insurance plans, their associated networks, and the organizations and providers that participate in these networks. Publication of this data through a standard FHIR-based API will enable third parties to develop applications through which consumers and providers can query the participants in a payer’s network that may provide services that address their health care needs.”</blockquote><p>Put simply, this Implementation Guide defines an open FHIR-based API for querying health plan provider information.</p><p>For this article, we are going to focus only on two areas of the Implementation Guide and how they are supported in Helios FHIR Server:</p><ul><li>Resources</li><li>Search Parameters</li></ul><p>First, let’s have a look at the FHIR Resources involved in this Implementation Guide. We can see from the diagram that Practitioner and PractitionerRole are central to this Implementation Guide. Additionally, other FHIR Resources such as InsurancePlan, Network, Location, and Organization have key relationships in this implementation as well.</p><p>To learn how relationships between FHIR Resources are structured, see the References Between Resources section of <a href="https://blog.heliossoftware.com/the-r-in-fhir-resources-eda4a2f3612">The R in FHIR — Resources</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*41WeXt16x8NkqBCcF3k14Q.png" /><figcaption><a href="http://hl7.org/fhir/us/davinci-pdex-plan-net/index.html#overview-of-payer-directory-resource-relationships">http://hl7.org/fhir/us/davinci-pdex-plan-net/index.html#overview-of-payer-directory-resource-relationships</a></figcaption></figure><p>Next, let’s have a look at the Search Parameters that are defined by this Implementation Guide.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0lXBQnD02kmk2OMF9h1GyA.png" /><figcaption><a href="http://hl7.org/fhir/us/davinci-pdex-plan-net/CapabilityStatement-plan-net.html#resource--details">http://hl7.org/fhir/us/davinci-pdex-plan-net/CapabilityStatement-plan-net.html#resource--details</a></figcaption></figure><p>There are quite a few search parameters defined in this Implementation Guide offering several convenient search paths for our resources, but not all Search Parameters are created equal. Some Search Parameters are defined in the base FHIR Specification, and some are specific to the Implementation Guide.</p><p>For example, <a href="http://hl7.org/fhir/us/davinci-pdex-plan-net/SearchParameter-insuranceplan-name.html">Plannnet_sp_insuranceplan_name</a> enables a client to search on the name or alias attribute of the InsurancePlan resource. This Search Parameter is the same as the <a href="http://hl7.org/fhir/insuranceplan.html#search">name InsurancePlan</a> Search Parameter defined by the base FHIR Specification.</p><p>Implementation Guides may introduce new Search Parameters, not defined in the base FHIR Specification. An example of an Implementation Guide — defined Search Parameter is <a href="http://hl7.org/fhir/us/davinci-pdex-plan-net/SearchParameter-insuranceplan-coverage-area.html">Plannet_sp_insuranceplan_coverage_area</a>. This Search Parameter enables searches on the <em>InsurancePlan.coverageArea</em> FHIR Path expression.</p><h4>Configuring a FHIR Server for the PDEX Payer Network (or Plan-Net) Implementation Guide</h4><p>The FHIR Specification is a large specification that encompasses many areas of the healthcare domain and use cases. In this Implementation Guide, we have seen that there are 8 FHIR Resources and a few dozen Search Parameters that a conformant FHIR Server solution needs to support.</p><blockquote><strong>Key Point: </strong>The Implementation Guide defines the minimum interface that SHALL/SHOULD/MAY be provided by a conformant server and will be expected by clients. If more than the minimum is implemented, clients are unlikely to be able to take advantage of those features, since they are developed for portability. If less than the minimum is provided, it may break some clients. A production implementation of this Implementation Guide should focus expressly on those FHIR Resources that are required for this Implementation Guide, and also implement the Search Parameters that are required too.</blockquote><p>Wouldn’t it be great if a FHIR Server product did just that? That’s exactly what the <a href="https://heliossoftware.com/provider-directory/">Helios FHIR Server — Provider Directory</a> product has done. Because of its modular architecture, only those database tables required to support the specified FHIR Resources in the Implementation Guide are created, only those Karaf bundles that support those Resources are started, and only those Search Parameters are activated. Should you ever need to add additional Resources and Search Parameters to your solution they are available in the distribution, however only those that are defined by the Implementation Guide are activated.</p><h3>Downloading and Installing the Helios FHIR Server — Provider Directory</h3><p>Next, let’s install the Helios FHIR Server, load some data, and test it using a test client! The steps below are similar to how we exercise our product and ensure it’s conformance during a FHIR Connectathon.</p><p>Navigate to <a href="https://heliossoftware.com/download-provider-directory-edition/">https://heliossoftware.com/download-provider-directory-edition/</a> and download a copy of Helios FHIR Server. These instructions assume installation and testing on a local development environment/laptop for simplicity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2NnqPYoYfajqfT1nsezG2Q.png" /></figure><p>If not already installed, download and install Cassandra. Instructions for doing so can be found in our Installation Instructions in the <a href="https://docs.heliossoftware.com/#cassandra-quickstart">Cassandra Quickstart</a> guide.</p><p>Next, un-tar the Helios FHIR Server distribution:</p><pre>$ tar xzvf ${helios-fhir-server-distribution.tar.gz}</pre><p>And run Karaf:</p><pre>$ cd ${helios-fhir-server-distribution}<br>$ bin/karaf</pre><p>The Helios FHIR Server will automatically create the necessary keyspaces in Cassandra, and the necessary tables as well.</p><p>Running a <em>bundle:list</em> command in the Karaf console will show that only the FHIR Resources and Search Parameters required in the PDEX Payer Network Implementation Guide are, in fact Active.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jMjp2rM9swkfkzsoJm0Lgw.png" /></figure><p>One final step is to change the default security setting such that the Helios FHIR Server’s API can be read openly without authentication. This is an important step, as Provider Directory APIs are designed to be completely open for read-only access. Writes are, of course, restricted to authorized users.</p><p>The Helios FHIR Server ships with Basic Authentication turned on, so let’s use the administrative console to turn it off.</p><p>Open the following URL:</p><pre><a href="http://localhost:8181/ui/login">http://localhost:8181/ui/login</a></pre><p>Login using the default credentials:</p><ul><li>Username: admin@heliossoftware.com</li><li>Password: admin</li></ul><p>Select the Settings menu item, flip Basic Enabled to off, and select the Update Settings button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K9N0iPoXSzFxgLTxmnNh-Q.png" /></figure><h4>Let’s Generate Some Data!</h4><p>Next, we’ll need some data. Thankfully, pdex-plan-net-sample-data open-source sample data tool developed by The MITRE Corporation is available expressly for this purpose. All of the MITRE resources mentioned in this article are available under a permissive Apache 2.0 license.</p><p>We have two options for data:</p><h4>Option 1: Run the Ruby application yourself:</h4><p><a href="https://github.com/HL7-DaVinci/pdex-plan-net-sample-data">HL7-DaVinci/pdex-plan-net-sample-data</a></p><pre>$ git clone <a href="/service/mailto:git@github.com">git@github.com</a>:HL7-DaVinci/pdex-plan-net-sample-data.git<br>$ cd pdex-plan-net-sample-data<br>$ bundle install<br>$ bundle exec ruby generate.rb</pre><p>Next, cd into the output directory where the FHIR sample data has been generated and have a look!</p><pre>$ cd output<br>$ ls<br>Endpoint HealthcareService InsurancePlan Location Organization OrganizationAffiliation Practitioner PractitionerRole</pre><h4>Option 2: Download our copy of the sample data if you’re unfamiliar with Ruby or do not wish to install it on your system:</h4><p>Download and un-tar the sample data:</p><pre>$ wget <a href="http://docs.heliossoftware.com/examples/output.tar.gz">http://docs.heliossoftware.com/examples/output.tar.gz</a><br>$ tar -xvf output.tar.gz<br>$ cd output<br>$ ls<br>Endpoint    Location    Practitioner<br>HealthcareService   Organization    PractitionerRole<br>InsurancePlan    OrganizationAffiliation   fhir-importer-0.0.1-SNAPSHOT.jar</pre><p>In addition to the data, we have also added the <a href="https://github.com/HeliosSoftware/fhir-importer">fhir-importer</a> jar for convenience.</p><h4>Import the Sample Data</h4><p>If you are running Helios FHIR Server Locally, and you obtained a copy of the sample data using Option 2 above, you may simply issue this command to import the data.</p><pre>java -jar fhir-importer-0.0.1-SNAPSHOT.jar -directory . -regex “.*.json”</pre><p>If using Option 1, from above, and you wish to build and run the fhir-importer:</p><pre>$ git clone git@github.com:HeliosSoftware/fhir-importer.git<br>$ cd fhir-importer<br>$ mvn clean install</pre><p>The fhir-importer jar will reside in the /target folder.</p><h4>Exercise the API</h4><p>Now if we only had a sample client to use the API! Thanks again to the team at MITRE, we do. The <a href="https://github.com/HL7-DaVinci/plan-net_client">plan-net_client</a> open source reference implementation will issue FHIR-compliant REST calls to a provided open FHIR endpoint.</p><p>The plan-net_client is a sample client, and not at all intended to be for production use, or designed to be used as an example of a consumer-friendly application — it’s main purpose is to show how to a FHIR client may use the services of a Provider Directory FHIR Implementation Guide — compliant API.</p><p>There are two options for using the plan-net_client tool. The first is to download it from GitHub and run it locally:</p><p><a href="https://github.com/HL7-DaVinci/plan-net_client">HL7-DaVinci/plan-net_client</a></p><p>Alternatively, MITRE is hosting the code at this Heroku URL:</p><p><a href="https://plan-net-client.herokuapp.com/">Plan Networks</a></p><p>Simply enter your URL into the text box on the home page, and you’re good to go! Here we are accessing the open Helios FHIR Server sandbox:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p_wBdErzV5vmK3Nuotcojg.png" /></figure><p>In the example below, after selecting the Pharmacies link on top, and selecting one of the Massachusetts insurance plans, we can not only see some of the sample data, but also see the exact FHIR query that was issued against the server:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vDgIm7KD5eHhbVHygJUYMQ.png" /></figure><h3>Summary</h3><p>In this article, we have:</p><ul><li>Provided a simple overview of a FHIR Implementation Guide, why they exist, and what they entail.</li><li>Walked through, at a high-level, a real-world example of an Implementation Guide — the PDEX Payer Network (or Plan-Net) Implementation Guide, a requirement for the CMS Provider Directory regulation.</li><li>Demonstrated how the Helios FHIR Server can easily implement an Implementation Guide, and provide support for precisely the FHIR components required of the Implementation Guide.</li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2Fe99955%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Ff%2Fe99955&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/2f6db2f60a2e5b981bbf2efe2826e875/href">https://medium.com/media/2f6db2f60a2e5b981bbf2efe2826e875/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3eed4b2f146b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helios-software/fhir-implementation-guides-a-provider-directory-implementation-3eed4b2f146b">FHIR Implementation Guides &amp; A Provider Directory Implementation</a> was originally published in <a href="https://medium.com/helios-software">Helios Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A FHIR-Native Analytics Approach]]></title>
            <link>https://medium.com/helios-software/a-fhir-native-analytics-approach-d977da8538d2?source=rss----9b1b9ed586ce---4</link>
            <guid isPermaLink="false">https://medium.com/p/d977da8538d2</guid>
            <dc:creator><![CDATA[Steve Munini]]></dc:creator>
            <pubDate>Wed, 16 Oct 2019 12:14:06 GMT</pubDate>
            <atom:updated>2020-12-01T04:34:42.469Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5lXWH0NXu1F4S5daO-Q_zA.jpeg" /></figure><p>Healthcare applications increasingly require a balance between both <strong><em>real-time application performance </em></strong>and <strong><em>analytic capabilities</em></strong> using FHIR. In our article <a href="https://blog.heliossoftware.com/fhir-architectural-patterns-ae828b13d40c">FHIR Architectural Patterns</a>, we outlined the many ways in which FHIR can be used in healthcare software architecture. One of the most interesting approaches, and the one in which we have received the most interest, especially by organizations that are working with increasingly large FHIR datasets, is the FHIR-Based Analytics Solution mentioned near the end of the article.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/666/1*tUB-VlKqj5roR-CjoN5XOA.png" /></figure><p>This architecture works to keep the data in place and use FHIR as the underlying domain model upon which to perform analysis, rather than transferring data to a separate analytics solution. This approach places processing nodes co-resident with the data storage nodes in a distributed fashion. The fundamental idea is very straightforward: Spark and Cassandra clusters are deployed to the same set of machines where Cassandra is responsible for storing the data and a Spark worker node is running on the same machine is responsible for data processing.</p><p>In this article, we explore this architecture pattern in detail and provide a set of “how-to” instructions for setting up a Cassandra cluster using <a href="https://www.datastax.com/products/datastax-enterprise/dse-analytics">DSE Analytics</a>, install the <a href="http://heliossoftware.com/product.html">Helios FHIR Server</a>, generate demonstration FHIR data, and solve an analytics problem of reasonable complexity using <a href="https://www.r-project.org/">R</a> and the <a href="https://en.wikipedia.org/wiki/Lasso_(statistics)">Lasso algorithm</a> to showcase the technology.</p><h4>First, a few Thank-Yous!</h4><p>This article would not be possible without the help of:</p><ul><li><a href="https://www.datastax.com/">DataStax</a> — The team at DataStax has been enormously helpful, and especially <a href="https://www.linkedin.com/in/jeffrey-carlson-07b64b2/">Jeff Carlson</a> for his expert DataStax Enterprise guidance.</li><li><a href="https://www.linkedin.com/in/darsei/">Darsei Canhasi </a>— For his development of the Lasso algorithm R code and his analytics expertise.</li><li><a href="https://www.linkedin.com/in/misswanchen/">Wan Chen</a> — Wan is Helios Software’s Data Engineering &amp; Analytics Lead and she was instrumental in creating this article and adapting the R code to DSE Spark.</li></ul><h3>Overview</h3><p>We are going to use several technologies and tools in this article to show how the architecture pattern works, how data flows through the system and highlights the architecture&#39;s advantages in terms of performance and flexibility.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wncCJpV2hQi0dHvknCMNzw.png" /></figure><ul><li>Synthea™ — At the start of our workload pipeline, we are going to need some FHIR data. We will be using <a href="https://github.com/synthetichealth/synthea">Synthea</a>, an open-source tool developed by <a href="https://health.mitre.org/">The MITRE Corporation</a>. Synthea is a Synthetic Patient Population Simulator. Synthea can output synthetic, realistic (but not real), patient data and associated health records in a variety of formats, including HL7 FHIR R4.</li><li>Helios FHIR Server — The second step is to import the Synthea-generated FHIR data using the Helios FHIR Server. The Helios FHIR Server is a commercial-grade, clinical data solution based on the HL7® FHIR® standard.</li><li>DSE Analytics &amp; R— The Helios FHIR Server uses DataStax Enterprise as its database. DataStax Enterprise is the always-on, active everywhere, distributed hybrid cloud database built on Apache Cassandra™. <a href="https://www.datastax.com/products/datastax-enterprise/dse-analytics">DSE Analytics</a> integrates analytics capabilities with an enhanced version of <a href="https://spark.apache.org/">Apache Spark™</a> that runs directly on each Cassandra node. <a href="https://spark.apache.org/docs/latest/sparkr.html">Apache SparkR </a>is a front-end for the <a href="https://www.r-project.org/">R programming language</a> for creating analytics applications. DataStax Analytics integrates SparkR to support creating data frames from DSE data.</li><li>RStudio — <a href="https://rstudio.com/">RStudio</a> is an integrated development environment for R, with a console, syntax-highlighting editor that supports direct code execution, and tools for plotting, history, debugging and workspace management. We will be using RStudio to run our R code and visualize the output.</li></ul><h3>Why Cassandra?</h3><p>The Helios FHIR Server exclusively uses Cassandra as its database. We committed to Cassandra after using it during a series of successful healthcare projects. With the increasing popularity and adoption of HL7 FHIR, we foresaw that many organizations would not only want to store FHIR data in a highly performant manner, but they would also want to perform rigorous and complex analytic workloads on these data.</p><p>Relational database technology typically fits very nicely on a single machine, and many healthcare computing problems are entirely solvable with this architectural approach. The combination of much larger datasets and the desire to offer extremely rapid response times while simultaneously needing to compute advanced analytics has led many organizations to consider distributed no-SQL database technologies such as Cassandra.</p><p>Where relational databases scale vertically by adding lots of CPU, RAM and disk capacity on a single machine, relational databases become challenged when a database needs to grow to an environment with multiple instances. Some of these challenges include:</p><ul><li>ACID (Atomicity, Concurrency, Isolation, Durability) breaks down with very large datasets replicated over several relational database instances.</li><li>Database sharding becomes a huge challenge with data spread over multiple locations. Joins and aggregations become challenging, and database designers are often forced to denormalize data considerably. Schema changes across a multiple instance environment are also often difficult and time-consuming.</li><li>Failover is not easily automated, especially across DC’s.</li></ul><p>Cassandra, on the other hand, is ideally suited to solve some of healthcare’s toughest problems. Cassandra is linearly scalable. This means that the capacity or scalability of a Cassandra cluster can be increased by simply adding new nodes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w7sotYPq7EboKNWunEU0OQ.png" /></figure><p>Cassandra’s design as a fast, linearly scalable distributed database offers:</p><ul><li>High availability</li><li>Predictable performance</li><li>No single point of failure</li><li>Multiple Datacenter support out-of-the-box</li><li>Operates on commodity hardware</li><li>Easy to manage operationally</li></ul><p>For a deeper understanding of how Cassandra can scale in this manner, we would recommend watching DataStax’s free online course: <a href="https://academy.datastax.com/resources/ds101-introduction-cassandra">Introduction to Apache Cassandra™</a></p><h3>Spark and Cassandra: Working Together</h3><p>Apache Spark is an open-source distributed general-purpose cluster-computing framework. Using Spark, developers can solve problems in minutes or seconds that once took hours or days on a single machine. Spark is perfectly suited for large-scale complex healthcare data problems.</p><p>Unlike Cassandra, which does not have a master, Spark works with a master/slave configuration, where there is a lightweight master component that acts as an interface to the cluster. The master node is responsible for managing Spark jobs across the cluster.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iKCuC5OCcvQzaG7BOIrVyw.png" /></figure><p>DataStax’s DSE Analytics product offers a special version of Spark that is Cassandra node-aware such that the right jobs are distributed to the right Spark workers where the necessary data may reside.</p><p>For an excellent overview and understanding of DSE Analytics, we highly recommend the course: <a href="https://academy.datastax.com/resources/getting-started-apache-spark">DataStax Enterprise Analytics with Apache Spark™</a></p><h3>Helios FHIR Server’s Data Model</h3><p>Product design is often about tradeoffs. In simple terms, an engineering tradeoff is where one design feature increases and another must decrease. As we studied the complexity and breadth of the FHIR specification as well as the design decisions that other implementers have made, we found the following:</p><ul><li>A relational approach that attempted to map the entire set of FHIR Resources and Search Parameters offered by the specification one-for-one would balloon the table count to a point where relational technologies would struggle to maintain.</li><li>Others opted for using a document database approach, however, we found these implementations were challenged in terms of implementing the complexities of the <a href="http://hl7.org/fhir/search.html">FHIR Search specification</a> in a performant manner.</li><li>Hybrid approaches exist that involve storing the FHIR Resource as a JSON object column while keeping index information in native relational database tables. This is a reasonable engineering tradeoff, however, this means that any tooling that needs to access the FHIR Resource directly needs to be JSON-aware.</li></ul><p>The Helios FHIR Server was designed with the following design goals:</p><ul><li>We wanted the Helios FHIR Server to be very fast. Performance is critical in the kinds of applications we built, and Cassandra’s query-first design approach led us down the path of wanting to take advantage of everything that Cassandra has to offer in terms of blazing-fast response times.</li><li>We wanted the Helios FHIR Server to scale linearly with ease. This one was simple — we had seen the kinds of incredible web-scale problems that Cassandra was solving in other markets, and knew that our customers would demand that kind of simplicity of scalability with our technology as well in the healthcare market.</li><li>We wanted to enable an already mature ecosystem of tools direct access to the Cassandra database tables, especially analytic tools. This design goal was critical — we found that our customers, although they are ramping up rapidly on FHIR, really wanted direct access to the underlying database, with the data organized in a manner that is convenient for them to work.</li></ul><p>These design goals led us to design the Helios FHIR Server with the following approach:</p><ul><li>FHIR Resources are represented directly as native Cassandra tables. In the example below, a <a href="http://hl7.org/fhir/patient.html">FHIR Patient</a> resource, which inherits from a DomainResource, which inherits directly from a Resource results in a single Patient table in Cassandra.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ft2sNjHRBLVWTnHKEG8QrA.png" /></figure><ul><li>FHIR Types such as <a href="http://hl7.org/fhir/datatypes.html#HumanName">HumanName</a>, which inherits from Element in the FHIR model is expressed as a Cassandra User Defined Type.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gyw5H4_yUVqxZOPGDt6blw.png" /></figure><h3>Bringing It All Together</h3><p>Below are a series of “How-To” steps that will walk you through both installation and running this collection of technologies together. At its conclusion, you will be able to:</p><ul><li>Generate synthetic FHIR data using Synthea</li><li>POST data using the HL7 FHIR API to the Helios FHIR Server.</li><li>The data will be stored in the DSE Cassandra cluster.</li><li>Run an R program, first in standalone mode to understand the algorithm, then run the same algorithm using Spark against the data in your cluster.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nG9jTW24LGXxjxm8gFbGtQ.png" /></figure><h3>Amazon EC2 Instances</h3><p>Ok! Let’s begin by setting up three Amazon EC2 instances that will run our Cassandra cluster and one EC2 instance that will run the Helios FHIR Server. For the Cassandra instances, we will be following the guidance from DataStax in this article:</p><ul><li><a href="https://docs.datastax.com/en/dse-planning/doc/planning/planningEC2.html">Planning a DSE or DDAC cluster on Amazon EC2</a></li></ul><p>Log in to your <a href="http://aws.amazon.com/">Amazon AWS</a> account and first set up a Security Group which we will need later. Security Groups contain a set of firewall rules that permit access to various IP ports on each node. Go to the EC2 Dashboard and select Security Groups on the left menu under Network &amp; Security. Select the “Create Security Group.”</p><p>Name this Security Group <strong><em>helios-fhir-server-security-group</em></strong>, and open ports 22 and 8080. Also, a VPC must be selected. Port 22 will be used for remote ssh and scp access, and port 8080 will be used by the Helios FHIR Server to expose the <a href="http://hl7.org/fhir/http.html">FHIR REST API</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vh1mMjMiUeW2yVPpLs9jkA.png" /></figure><p>Next, select Instances on the left menu and launch an EC2 instance. First, we will launch 3 instances that will comprise our Cassandra cluster.</p><p>We will be using Ubuntu for this article, however other Linux distribution AMI types are also listed in the DataStax documentation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*COoFXHO8xCIWKddxtUuNog.png" /></figure><p>We will be creating DSE Analytic nodes and DataStax recommends the <strong><em>i3.4xlarge</em></strong> instance type.</p><p>Next, create 3 instances for our cluster:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2wkB2YwJU0kF5lShv1-6uQ.png" /></figure><p>Increase the root volume to 80 Gigabytes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DVJDJSd3eW45azD2LwD9Cw.png" /></figure><p>I find it handy to label these instances to make it easier to find and work within the AWS console. Here I have labeled them all with the key <strong><em>helios-fhir-blog-article</em></strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1gcCBhJyt1ZmJviks1jD_Q.png" /></figure><p>Next, we will set up a Security Group in AWS for our cluster instances. We will name this Security Group <strong><em>cluster-nodes-security-group</em></strong>. There are quite a few settings for the Cassandra cluster to enable that we need to setup:</p><ul><li>A public port to allow us SSH and SCP access to the nodes — Port 22</li><li>A public port to allow us to access DataStax OpsCenter which we will use to set up and monitor our DSE cluster — Port 8888</li><li>Public ports to allow us access to the Spark Master and Workers web user interface — Ports 7080 and 7081</li><li>A port for accessing the DataStax Enterprise Cluster from our Helios FHIR Server instance — Port 9042</li><li>A set of inter-node communication ports that the DataStax Enterprise database requires.</li><li>A set of inter-node communication ports that Spark requires.</li></ul><p>These ports and port ranges are documented by <a href="https://docs.datastax.com/en/security/6.7/security/secFirewallPorts.html">DataStax in Securing DataStax Enterprise ports</a>, and we have selected only those port settings that are required below.</p><p>Your Security Group settings should initially be as follows when creating the <strong><em>cluster-nodes-security-group. </em></strong>Please note that the Source Custom value for port 9042 is the Group ID of the <strong><em>helios-fhir-server-security-group</em></strong> created in the step above. You will need to navigate (in a separate tab/window) to the Security Groups menu to get that ID.</p><p>Also, note that the bottom 7 entries enable “Anywhere” traffic. This is a temporary setting, and we only wish to enable traffic to/from instances who are in the <strong><em>cluster-nodes-security-group</em></strong>, but … the <strong><em>cluster-nodes-security-group </em></strong>Security Group hasn’t been created yet, so we do this temporarily, and you’ll need to come back and modify those settings as shown in the “Edit inbound rules” image below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZU2i8wVscN-Gl9CVu_jdfQ.png" /></figure><p>Modify your rules as follows. In this example, the <strong><em>helios-fhir-server-security-group</em></strong>’s id is sg-02e1df0a74150b168 and the <strong><em>cluster-nodes-security-group</em></strong>’s id is sg-04e36717c68ed314d. Yours will be different than these values!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qImS9PlywMFcfRZwXZUoIw.png" /></figure><p>The last step before launching your AWS EC2 instances is to download a private key file. Here, we are creating a new key pair, and the downloaded file will be named HeliosBlogArticle.pem. We will need to use this file when accessing our instances remotely using the ssh or scp commands.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2W-HZumxDLQUv1PtoSnKkg.png" /></figure><p>We need one more EC2 instance which will run the Helios FHIR Server.</p><p>Repeat the same steps above, but select a m4.2xlarge instance type, and on the step to set up the security group, select the <strong><em>helios-fhir-server-security-group</em></strong> that we configured earlier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5658QdCxOzygJc0vAGXnsg.png" /></figure><p>After typing the names of each node into the console, you should now have 4 EC2 instances running like this, below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JuvClUTJTg4T73sHe1lb2w.png" /></figure><h3>DataStax OpsCenter</h3><p>Next, we will use DataStax OpsCenter to install DataStax Enterprise on all three nodes. OpsCenter is a management and monitoring solution for DataStax Enterprise (DSE). With OpsCenter, we can quickly provision, upgrade, monitor, backup/restore, and manage our DSE clusters.</p><p>Let’s connect to Node 1 of our Cassandra cluster. We only need to run OpsCenter on one node.</p><p>First, change the permissions of the pem file:</p><pre>chmod 400 HeliosBlogArticle.pem</pre><p>Next, connect to Node 1 with ssh:</p><pre>ssh -i HeliosBlogArticle.pem ubuntu@[Node 1 public IP]</pre><p>Install Java (OpenJDK 8). Please note, that we only need to do this on Node 1 of the Cassandra cluster. OpsCenter will install OpenJDK for us on the other nodes.</p><pre>sudo add-apt-repository ppa:openjdk-r/ppa<br>sudo apt-get update<br>sudo apt-get install openjdk-8-jre</pre><p>Download a copy of OpsCenter to Node 1:</p><pre>wget https://downloads.datastax.com/enterprise/opscenter.tar.gz</pre><p>Next, let’s expand the tarball:</p><pre>tar -xvf opscenter.tar.gz</pre><p>And run it!</p><pre>opscenter-6.7.5/bin/opscenter</pre><p>Back on your local machine, use a browser and access this URL:</p><pre><a href="http://[Node">http://[Node</a> 1 Public IP]:8888</pre><p>Select <strong>Create a new cluster</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*MaVuhB96Bm4XLCHOLpSm_g.png" /></figure><p>We now have 4 easy steps to complete:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*frmgnkv4A4QUkN856YJURw.png" /></figure><p>First, set up SSH Credentials. Here, we will use the <strong><em>ubuntu</em></strong> user and copy the contents of the <strong><em>HeliosBlogArticle.pem</em></strong> file into the <strong><em>Private Key</em></strong> dialog box.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YmoxNwmhzM9cSWnzARy1dg.png" /></figure><p>Next, set up a Config Profile. Here, we have chosen the most recent version of DSE as of the writing of this article.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0scm5WhC_AgYjMGvn0Eaag.png" /></figure><p>We are going to keep things simple for purposes of this article and disable authentication to our cluster. In a production environment, be sure to use an authenticator and authorizer!</p><p>Select the cassandra.yaml entry, and change the <strong><em>authenticator</em></strong> value to “AllowAllAuthenticator” and the <strong><em>authorizer</em></strong> to “AllowAllAuthorizer.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7r5ryE_RxBcBQSLdwoEZJw.png" /></figure><p>You will need a DataStax Academy account for the next step. Go ahead and signup at <a href="http://academy.datastax.com/">academy.datastax.com</a>, and remember your username and password. You’ll need to enter your DataStax Academy username and password in the dialog below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*Nug5ET52BuzLkEXhdeRqCQ.png" /></figure><p>Next, set up a Cluster as follows:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*iXm2IkRUWia7yGyxrrOFdA.png" /></figure><p>The Clusters setup environment will display, and next setup a DataCetner. For this exercise, be sure to select <strong><em>DSE Analytics</em></strong> for the Workloads selection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*UOvpmlI-sGwNOcF-lMYltA.png" /></figure><p>Next, Add three nodes. This is important: Be sure to use <strong><em>Private IPs</em></strong> (not the public IPs) from your AWS EC2 Instance console. Also, use <strong><em>Rack1</em></strong> for all three nodes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xcKvAAsvVFA4vYlqKW4ffA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xPOLDgy84mYsWK5OUur0FA.png" /></figure><p>Your Lifecycle Manager should now look like this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gEl6GI5EZ9LyzM83sq4_eg.png" /></figure><p>Select your cluster, and then Install! Use the defaults on the <strong><em>Run Installation Job</em></strong> dialog.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LDt5nWxU-a74D6UWl55ELg.png" /></figure><p>Watch the job run, and on completion, your job should look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7pC0B-F9nUpXtzky479lfQ.png" /></figure><h3>Helios FHIR Server</h3><p>The steps below will download, install and connect the Helios FHIR Server to your Cassandra cluster.</p><p>The version of the Helios FHIR Server is a preview release of the product. It contains a set of functionality in terms of FHIR Resource support and search parameters that will enable the capabilities in this article. It is not a full-featured version of the Helios FHIR Server. Please <a href="http://heliossoftware.com/contactus.html">contact us</a> if you would like to learn more about the capabilities of the Helios FHIR Server.</p><p>First ssh on over to your Helios FHIR Server EC2 instance:</p><pre>ssh -i HeliosBlogArticle.pem ubuntu@[Helios FHIR Server public IP]</pre><p>Download the DataStax cqlsh command line tool. cqlsh is a command line tool that enables us to connect to our Cassandra cluster, and issue database commands directly.</p><pre>wget https://downloads.datastax.com/enterprise/cqlsh-6.7.tar.gz</pre><p>Expand the cqlsh tar:</p><pre>tar -xvf cqlsh-6.7.tar.gz</pre><p>Add cqlsh to the path:</p><pre>export PATH=cqlsh-6.7.5/bin:$PATH</pre><p>Install Python:</p><pre>sudo apt-get update<br>sudo apt install python</pre><p>Next, install Oracle’s Java.</p><p>From your local machine, navigate to: <a href="https://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html">https://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html</a></p><p>Accept Oracle’s license agreement and download a Linux x64 compressed tar binary, and copy it to your Helios FHIR Server EC2 instance. (Note the colon at the end of this command)</p><pre>scp -i HeliosBlogArticle.pem jdk-8u211-linux-x64.tar.gz ubuntu@[Helios FHIR Server IP Address]:</pre><p>Back on the server, follow these instructions to install Oracle Java:</p><p><a href="https://www.javahelps.com/2015/03/install-oracle-jdk-in-ubuntu.html">Install Oracle JDK 8 on Linux</a></p><p>Download the Helios FHIR Server:</p><pre><a href="https://heliossoftware.com/download-enterprise-edition/">https://heliossoftware.com/download-enterprise-edition/</a></pre><p>Startup the Helios FHIR Server!</p><pre>java -Dcassandra.contactpoints=”[Node 1 Internal IP]” -jar helios-fhir-server-0.0.9-PRERELEASE.jar</pre><p>Note we are offering only one IP contact point in this example. Upon startup, you will see that the DataStax driver finds the other cluster nodes automatically. In a production environment, you should configure more than one cluster node IP address eliminating this single point of failure.</p><p>If your startup is successful, you will see this message in the output:</p><pre>Helios FHIR Server — Started up and READY</pre><p>You can also test the FHIR Server with your browser or the <a href="https://www.getpostman.com/">Postman</a> tool:</p><pre>http://[Helios FHIR Server Public IP]:8080/metadata</pre><p>The /metadata URL is a special URL specified by the FHIR Standard. At this location, a FHIR Server’s <a href="http://hl7.org/fhir/capabilitystatement.html">Capabilities Statement</a> can be found which details the FHIR Resources that the server supports, the search parameters that are available, and numerous other capabilities that are offered by the FHIR Server.</p><h3>Synthea</h3><p>Next, download Synthea from GitHub using <a href="https://git-scm.com/">git</a>.</p><pre>git clone https://github.com/synthetichealth/synthea.git</pre><p>Let’s generate 1000 simulated patients and data and examine the output.</p><pre>cd synthea<br>./run_synthea -p 1000<br>cd output/fhir<br>[...Examine some of the FHIR output...]</pre><p>We have written a short script contained in a ZIP file that modifies the bundle type for import and uses the curl command to post the data to the Helios FHIR Server.</p><pre>wget https://heliossoftware.com/wp-content/uploads/2020/11/BlogArticleFiles.zip<br>unzip BlogArticleFiles.zip import_all.sh<br>chmod u+x import_all.sh<br>./import_all.sh</pre><p>The import_all.sh script will, one-by-one begin to import each of the patient files. This can take some time, so why not use the full capacity of the Helios FHIR Server and Cassandra? Let’s stop the import, and modify the script slightly to show the level of performance possible.</p><p>In bash scripting, by adding an ampersand character at the end of the command&amp; the process starts in the background, so you can continue to use the shell and do not have to wait until the script is finished.</p><p>If you wish, modify the following line in the import_all.sh script as follows. (Simply add the &amp;character to the end of the line.)</p><pre>curl http://localhost:8181/fhir -X POST --header &quot;Content-Type: application/fhir+json&quot; --header &quot;Prefer:return=minimal&quot; --data-binary &quot;@./$filename.batch&quot; &amp;</pre><p>This will, in parallel, import all 1000 patients!</p><p><strong><em>Note:</em></strong><em> In a production environment, we would recommend a more controlled import process, as there is a limit to the parallelism that can be achieved — the above is for demonstration purposes only to showcase the performance of the Helios FHIR Server and Cassandra’s very fast write capabilities.</em></p><h3>RStudio</h3><p>At this point, you have installed your Cassandra cluster, installed the Helios FHIR Server, and imported some data. Next, let’s perform some analysis of the data!</p><p>We have created an example R program that will analyze the data using <a href="https://en.wikipedia.org/wiki/Lasso_(statistics)">Lasso</a>. Lasso is one of the types of variable selection algorithms. Variable selection algorithms are helpful when there are a large number of input variables, and we wish to determine which of those variables can be used without losing prediction accuracy.</p><blockquote>In our example code, we will be using Lasso to identify which of the input variables is predictive of asthma.</blockquote><p>For example, in this exercise, using Lasso, we might find that we can accurately predict asthma using 8 variables instead of a full complement of 15 variables.</p><p>We’re going to do this in two steps.</p><ul><li>In Step 1, we’ll install RStudio and run the Lasso code in a standalone mode using prepared data. This will help to become familiar with R, RStudio, and the example R program and its output.</li><li>In Step 2, we’ll use a modified version of the example R program that has been changed to use the many features of Spark, and we will run this version of the code across all three nodes in our cluster.</li></ul><h4>Step 1: Install R Studio &amp; Run in Standalone Mode</h4><p>Here we have two options. You may either download the <a href="https://rstudio.com/products/rstudio/">RStudio client application</a> and run it locally, or you may wish to use the <a href="https://rstudio.com/products/rstudio/#rstudio-server">RStudio Server</a> version. Below are instructions for installing RStudio Server. If you are using one of the EC2 instances you set up earlier to do this, you will need to open port 8787. This can be accomplished by selecting your EC2 instance in the AWS console, then selecting the Security tab, then select the Security Group hyperlink, then press the “Edit inbound rules” button to add 8787.</p><p>Download and install the necessary packages…</p><pre>sudo apt-get install r-base<br>sudo apt-get install gdebi-core<br>wget https://download2.rstudio.org/server/trusty/amd64/rstudio-server-1.2.5001-amd64.deb<br>sudo gdebi rstudio-server-1.2.5001-amd64.deb</pre><p>Install some R packages we will need later:</p><pre>sudo R<br>install.packages(&quot;glmnet&quot;)<br>install.packages(&quot;MASS&quot;)<br>install.packages(&quot;ROCR&quot;)<br>install.packages(&quot;pbkrtest&quot;)<br>install.packages(&quot;car&quot;)</pre><p>Next, create a “rstudio” Linux user and set the password. You will use this user to login to your RStudio session.</p><pre>sudo useradd -m rstudio<br>sudo passwd rstudio</pre><p>Access RStudio:</p><pre>http://[RStudio Server Public IP]:8787</pre><p>Next, ssh to the RStudio Server, and we will install some files you will need there:</p><pre>ssh -i HeliosBlogArticle.pem ubuntu@[RStudio Server public IP]</pre><p>Change to the rstudio user and its home directory</p><pre>su rstudio<br>cd</pre><p>Download the example R program and associated dataset.</p><pre>wget https://heliossoftware.com/wp-content/uploads/2020/11/BlogArticleFiles.zip<br>unzip BlogArticleFiles.zip lasso-standalone.R<br>unzip BlogArticleFiles.zip AsthmaDataset.csv</pre><p>Back to your browser, create a new R Project and load the lasso-standalone.R program.</p><p>Step through the R program. You will see that it:</p><ul><li>Loads a sample dataset in a file named AsthmaData.csv.</li><li>Several data cleaning steps remove certain unnecessary or duplicate columns. A patient who had an outlier weight was also removed (over 1200kg)</li><li>Next, the program randomly splits the data into two data sets — a train dataset, which is 80% of the data, and a test dataset comprising the remaining 20%</li><li>The column names are then displayed</li><li>A statistical regression model is performed using <em>glm</em> on the train data and saved into <em>fit1</em></li><li>Next, a stepwise model selection is performed on <em>fit1</em>.</li><li>Next, a multicollinearity check is performed which shows that BMI is highly correlated with body weight and body height (not surprisingly), so it is being excluded from the model.</li><li>An Autocorrelation check is performed, but the test doesn’t show any signs of autocorrelation.</li><li>Next, three graphs are produced, and a cutoff point is selected (0.1). <a href="https://acutecaretesting.org/en/articles/roc-curves-what-are-they-and-how-are-they-used">This article</a> does a good job of describing cutoff points.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/970/1*s738aJIEDFu8WZVJ6hMYfQ.png" /></figure><ul><li>The logistical model shows that the overall predictive accuracy is 81.2%. Your results may be different because earlier in the code, we randomly split the data into test and train datasets, so your predictive accuracy value will likely be different than this number.</li><li>The output also indicates that Lasso model accuracy of 80% is higher than the 78% given by the Logistic Regression.</li><li>Next, the Lasso model is run, and shows the following variables:</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jqy5eyQTMO_wTz0rmfvcRQ.png" /></figure><ul><li>This output tells us that these 6 variables can be used to predict Asthma. The variables that are eliminated (marked with a period) can be ignored.</li></ul><h4>Step 2: Install R on all DSE Analytics Cluster Nodes &amp; Run the Spark-Enabled Program</h4><p><strong><em>Note:</em></strong><em> This step can take some time (like 30 mins or more). The install.packages steps below are long-running tasks.</em></p><p>Perform these steps on all three of your DSE Analytics nodes.</p><p>First, install required libraries that R will need to download R packages.</p><pre>sudo apt-get install libcurl4-openssl-dev<br>sudo apt-get install libssl-dev<br>sudo apt-get install libxml2-dev</pre><p>Next, login to the DSE SparkR console as the Linux superuser. We will be logging out when the installs are complete.</p><pre>sudo dse sparkR</pre><p>In the console, install the following R libraries:</p><pre>install.packages(&quot;magrittr&quot;)<br>install.packages(&quot;pipeR&quot;)<br>install.packages(&quot;DBI&quot;)<br>install.packages(&quot;tidyverse&quot;)<br>install.packages(&quot;listviewer&quot;)<br>install.packages(&quot;glmnet&quot;)<br>install.packages(&quot;MASS&quot;)<br>install.packages(&quot;ROCR&quot;)<br>install.packages(&quot;roperators&quot;)<br>install.packages(&quot;car&quot;)</pre><p>Exit the console</p><pre>quit()</pre><p>Download the Spark-enabled version of the Lasso algorithm that will work against the Cassandra Cluster.</p><pre>wget https://heliossoftware.com/wp-content/uploads/2020/11/BlogArticleFiles.zip<br>unzip BlogArticleFiles.zip lasso-spark-cluster.R</pre><p>Run the DSE SparkR console again, this time not as the superuser.</p><pre>dse sparkR</pre><p>In this version of the code, the dataset is no longer loaded from a CSV file. Instead, direct database calls to Cassandra are made and loaded into SparkDataFrames and manipulated by Spark in a distributed fashion. Several examples from the code follow.</p><p>Here, the code is reading directly from the patient table:</p><pre># Read from the Cassandra Patient table into a SparkDataFrame.<br>patientDataFrame &lt;- sql(&quot;select id as PatientId, maritalstatus, birthdate, gender from hfs_data.patient&quot;)</pre><p>The schema of the patient table is directly available to the R program:</p><pre>printSchema(patientDataFrame)</pre><pre>root<br>|-- PatientId: string (nullable = false)<br>|-- maritalstatus: struct (nullable = true)<br>|    |-- coding: array (nullable = true)<br>|    |    |-- element: struct (containsNull = true)<br>|    |    |    |-- code: string (nullable = true)<br>|    |    |    |-- code_extensions: array (nullable = true)<br>|    |    |    |    |-- element: string (containsNull = true)<br>|    |    |    |-- display: string (nullable = true)<br>|    |    |    |-- display_extensions: array (nullable = true)<br>|    |    |    |    |-- element: string (containsNull = true)<br>|    |    |    |-- userselected: boolean (nullable = true)<br>|    |    |    |-- userselected_extensions: array (nullable = true)<br>|    |    |    |    |-- element: string (containsNull = true)<br>|    |    |    |-- system: string (nullable = true)<br>|    |    |    |-- system_extensions: array (nullable = true)<br>|    |    |    |    |-- element: string (containsNull = true)<br>|    |    |    |-- version: string (nullable = true)<br>|    |    |    |-- version_extensions: array (nullable = true)<br>|    |    |    |    |-- element: string (containsNull = true)<br>|    |    |    |-- id: string (nullable = true)<br>|    |    |    |-- extension: array (nullable = true)<br>|    |    |    |    |-- element: string (containsNull = true)<br>|    |-- id: string (nullable = true)<br>|    |-- text_: string (nullable = true)<br>|    |-- text__extensions: array (nullable = true)<br>|    |    |-- element: string (containsNull = true)<br>|    |-- extension: array (nullable = true)<br>|    |    |-- element: string (containsNull = true)<br>|-- birthdate: struct (nullable = true)<br>|    |-- 0: date (nullable = true)<br>|    |-- 1: integer (nullable = true)<br>|-- gender: string (nullable = true)</pre><p>The observation table is read into a SparkDataFrame:</p><pre>observationDataFrame &lt;- sql(&quot;select id as ObservationId, code, valuequantity, subject from hfs_data.observation&quot;)</pre><p>Here, we are creating a blood pressure dataframe to prepare for some further analysis.</p><pre># Create a BP Dataframe...<br>bpDataFrame &lt;- selectExpr(observationDataFrame,<br>  &quot;PatientReferenceId&quot;,<br>  &quot;ObservationId&quot;,<br>  &quot;component[0].code.coding[0].code as DBPCode&quot;,<br>  &quot;component[0].valuequantity.value as `Diastolic Blood Pressure`&quot;,<br>  &quot;component[1].code.coding[0].code as SBPCode&quot;,<br>  &quot;component[1].valuequantity.value as `Systolic Blood Pressure`&quot;)</pre><p>What is important to note with this version of the code is that these statements are evaluated on each Spark node. In other words, the data isn’t moving around the cluster for these kinds of operations. Instead, the data is remaining resident on the node, and Spark operations are distributed, intelligently around the cluster where required. Because iterative algorithms such as those in this example code apply operations repeatedly to data, they benefit from caching datasets across iterations on each node.</p><h3>Summary</h3><p>In this article, we have shown:</p><ul><li>How to create a Cassandra cluster</li><li>How to install and run the Helios FHIR Server</li><li>How to generate sample FHIR data using Synthea and import it into the Helios FHIR Server</li><li>How to run an R program analytic workload on DSE Analytics</li><li>How a FHIR data model can be made directly available to analytics languages.</li></ul><p>If you would like to learn more, or need help with some of the examples in this article, feel free to <a href="http://heliossoftware.com/contactus.html">contact us</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d977da8538d2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helios-software/a-fhir-native-analytics-approach-d977da8538d2">A FHIR-Native Analytics Approach</a> was originally published in <a href="https://medium.com/helios-software">Helios Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[FHIR Training: The early steps of mastering HL7 FHIR]]></title>
            <link>https://medium.com/helios-software/fhir-training-the-early-steps-of-mastering-hl7-fhir-997d8dfa1320?source=rss----9b1b9ed586ce---4</link>
            <guid isPermaLink="false">https://medium.com/p/997d8dfa1320</guid>
            <category><![CDATA[healthcare]]></category>
            <dc:creator><![CDATA[Steve Munini]]></dc:creator>
            <pubDate>Sun, 10 Mar 2019 14:01:22 GMT</pubDate>
            <atom:updated>2019-03-10T14:01:22.432Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y-rvI3RETtJ1PhngnDMOWA.jpeg" /></figure><p>The recent release of HL7 FHIR R4 has brought a lot of attention to the FHIR standard and the FHIR community. This was certainly the case at HIMSS 2019. HIMSS CEO Hal Wolf pointed out a variety of challenges facing healthcare in America. These challenges include an aging population, higher expectations from consumers, and an overall lack of actionable information. He believes these challenges require an increased reliance on digital health.</p><p>Aneesh Chopra, the first United States CTO and President of CareJourney, promoted FHIR as the solution to these issues. He stated:</p><blockquote>“The embrace of FHIR APIs means that we’re not going to have a Betamax-VHS fight in healthcare. We now have an approach to adding more content on the data model. We’re done with the fight.”</blockquote><p>On the eve of the HIMSS conference, the U.S. Department of Health and Human Services issued draft rules calling on the healthcare industry to adopt FHIR data models and the <a href="http://www.hl7.org/fhir/smart-app-launch/">SMART API</a> for launching applications. The proposed rules also remove fees for use of APIs and they also require the use of a means to efficiently access large volumes of information on a group of individuals from EMRs, otherwise known as a <a href="https://github.com/smart-on-fhir/fhir-bulk-data-docs">bulk API.</a> (<a href="https://www.healthit.gov/topic/laws-regulation-and-policy/notice-proposed-rulemaking-improve-interoperability-health">ONC rule</a>, and <a href="https://www.cms.gov/newsroom/fact-sheets/cms-advances-interoperability-patient-access-health-data-through-new-proposals">CMS rule</a>)</p><p>It has never been more important than now to not only learn HL7 FHIR as a healthcare IT professional, but also to ramp up your team’s FHIR knowledge and competency within your organization. FHIR training sessions exist, including <a href="http://heliossoftware.com/fhir-training.html">Helios Software’s two-day on-site training</a>, but first, let’s look at some of the initial steps that individuals and teams take to learn FHIR basics.</p><p><strong>Normative Content</strong></p><p>FHIR introduces a lot of new terms, which can sometimes be overwhelming for people new to the standard. One of which, Normative, has become more relevant with the recent release of FHIR R4. So, what is normative content?</p><p>First, we need to understand that FHIR is a platform standard for healthcare. Because healthcare is so broad and continuously evolving, FHIR cannot be specified all at once. HL7 develops FHIR through a level-based system so users know what components of FHIR are the most mature and what components are still a work in progress. These levels help implementers recognize what to expect as the standard evolves.</p><p>The first level in HL7’s standards development process is Draft. Draft components are not considered complete enough to be safe for implementation. This may be from known issues or the components are still in active development. They’re listed in the publication as a place-holder to solicit feedback from the community. Once reviewed, the content will usually be elevated to Trial Use, the next level of the standard.</p><p>Trial Use content has been well reviewed and can be used in production systems. It has been subjected to ballot and approved as an official standard. What prevents it from elevating to Normative is that it hasn’t seen widespread use across production environments.</p><p>Normative content comes after Trial Use. FHIR R4 provides the first Normative content for FHIR. Normative means that the content has been subject to review and there are production implementations in a variety of environments. It’s considered stable and the content has been ‘locked.’ Any subsequent changes are infrequent and tightly constrained.</p><p>Where Draft and Trial Use content changes may include changes, including breaking changes to the specification, Normative content holds specific <a href="https://www.hl7.org/fhir/versions.html#f-compat">rules for forward and backward compatibility</a>. In other words, when a component of the FHIR specification achieves a Normative status, certain promises relative to change in the specification are made, signaling that the component has reached a stable level of maturity. R4 includes the first set of Normative content for FHIR marked by the letter “N” on <a href="http://www.hl7.org/fhir/documentation.html">the specification</a>.</p><p>As FHIR produces more Normative content, its usage will continue to rise. More use cases and production opportunities will be available, ensuring more healthcare IT professionals will take advantage of the standard. Healthcare IT professionals, armed with the knowledge that the FHIR specification now contains Normative content, are increasingly turning their attention to approaches they can take to using FHIR in their projects.</p><p><strong>Approaches to Using FHIR in your Architecture</strong></p><p>As CEO, CTO, and founder of Helios Software, I often get asked:</p><blockquote>What the best approach to using FHIR?</blockquote><p>While the “right” answer can often only be discussed and designed in one of our <a href="http://heliossoftware.com/fhir-training.html">FHIR training sessions</a> with your development team, I often refer developers and architects to read one of my previous articles about FHIR. One of which, <a href="https://blog.heliossoftware.com/fhir-architectural-patterns-ae828b13d40c">FHIR Architectural Patterns</a>, covers different approaches users can take when using FHIR. Here’s a brief preview:</p><blockquote>“FHIR not only supports extremely common interoperability challenges, but, because of its design as a platform specification and many of FHIR’s interesting features, FHIR opens the door to entirely new, modern, flexible and adaptive sets of healthcare product solution designs.”</blockquote><p>The possibilities of FHIR are seemingly endless for healthcare IT professionals. The article details approaches to FHIR-enabling existing solutions and also using FHIR as a next-generation health data platform. We explore 8 FHIR architectural patterns:</p><ul><li>Interoperability interface</li><li>FHIR broker adapter</li><li>FHIR/proprietary API mixed use</li><li>FHIR API encapsulating a vendor-neutral clinical repository</li><li>FHIR-based clinical data repository</li><li>FHIR-based integration hub</li><li>FHIR-based analytics solution</li><li>Rapid FHIR-based endpoint</li></ul><p>I highly encourage you to read <a href="https://blog.heliossoftware.com/fhir-architectural-patterns-ae828b13d40c">the article</a>. With this information, you’ll be set up to understand how you can fully utilize FHIR and focus your team’s efforts where you want to get started. This, in addition to FHIR training, will ensure your success in an increasingly FHIR-driven healthcare IT landscape.</p><p><strong>FHIR Training is Key</strong></p><p>After having defined a preliminary architectural approach for implementing FHIR, it is time to dive in and learn FHIR as rapidly as possible. Mastering the FHIR specification as health IT professional is essential, but FHIR implementations are about more than the software itself. It is also very important to have a team with the necessary skills, competencies and abilities to make your effort a success. Learning FHIR doesn&#39;t’ have to be a daunting challenge for you and your team.</p><p>FHIR is an industry disrupter, especially in the hands of experienced healthcare IT professionals. <a href="http://heliossoftware.com/fhir-training.html">Helios’ FHIR training</a> takes an entire team and gives them the knowledge they need to start using FHIR and build solutions right away. Hands-on training can be the difference between falling behind and leading the charge for the advancement of healthcare IT.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=997d8dfa1320" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helios-software/fhir-training-the-early-steps-of-mastering-hl7-fhir-997d8dfa1320">FHIR Training: The early steps of mastering HL7 FHIR</a> was originally published in <a href="https://medium.com/helios-software">Helios Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The R in FHIR — Resources]]></title>
            <link>https://medium.com/helios-software/the-r-in-fhir-resources-eda4a2f3612?source=rss----9b1b9ed586ce---4</link>
            <guid isPermaLink="false">https://medium.com/p/eda4a2f3612</guid>
            <category><![CDATA[fhir]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[hl7]]></category>
            <dc:creator><![CDATA[Steve Munini]]></dc:creator>
            <pubDate>Fri, 25 Jan 2019 18:09:39 GMT</pubDate>
            <atom:updated>2019-01-25T18:37:59.470Z</atom:updated>
            <content:encoded><![CDATA[<h3>The R in FHIR — Resources</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hvMhWYcgvwUroiidCWxQ9w.jpeg" /></figure><h3>Introduction</h3><p>The R in <a href="http://hl7.org/fhir/">HL7® FHIR®</a> stands for Resources, but what exactly is a FHIR Resource?</p><p>Before getting into the formal definition of a FHIR Resource, let’s first appreciate some excellent design. In any complex system, we will almost always find an overriding design pattern or principle.</p><ul><li>The game of ice hockey is essentially a game of keep-away. Teams who keep the puck away from the other team the best, and shoot on the goal — win.</li><li>Electronics are bound by relatively simple laws of physics, that, once understood and characterized into common building blocks (diodes, capacitors, resistors, etc.), can be assembled together to create some incredibly complex, and useful devices.</li><li>In developing user interfaces for software, the event-driven programming pattern perfectly suits the task at hand — events happen, such as a mouse click, a key press, or a drag and drop operation; the user interface programmer’s task is to “catch” these events and do something useful with them — save a file, type a letter, or send an email.</li></ul><p>In a similar way, Resources form the main design principle of FHIR and perfectly suit the design problem at hand. In this article, we cover the basics of FHIR Resources.</p><h3>FHIR Resources — Defined</h3><p>Resources represent key concepts found in the healthcare domain, making them the main building blocks of FHIR. Additionally, the FHIR specification defines a set of infrastructure Resources for handling FHIR Resources.</p><p>This may seem like circular logic, but that’s by design. To understand, let’s look at a few examples of FHIR Resources as defined by the FHIR specification.</p><ul><li><a href="http://hl7.org/fhir/patient.html">Patient</a> — The most fundamental of all FHIR Resources. The FHIR specification defines a Patient as: “Demographics and other administrative information about an individual or animal receiving care or other health-related services.” (Animals are included in this definition of patients because it is possible to use FHIR in veterinary settings.)</li><li><a href="http://hl7.org/fhir/medication.html">Medication</a>: Tylenol PM, Percocet or Lorazepam: “This resource is primarily used for the identification and definition of a medication for the purposes of prescribing, dispensing, and administering a medication as well as for making statements about medication use.”</li><li><a href="http://hl7.org/fhir/immunization.html">Immunization</a>: Influenza, or Hepatitis vaccine: “Describes the event of a patient being administered a vaccine or a record of an immunization as reported by a patient, a clinician or another party.”</li><li><a href="http://hl7.org/fhir/searchparameter.html">SearchParameter</a>: “A search parameter that defines a named search item that can be used to search/filter on a resource.”</li><li><a href="http://hl7.org/fhir/capabilitystatement.html">CapabilityStatement</a>: “A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.”</li><li><a href="http://hl7.org/fhir/structuredefinition.html">StructureDefinition</a>: “A definition of a FHIR structure. This resource is used to describe the underlying resources, data types defined in FHIR, and also for describing extensions and constraints on resources and data types.”</li></ul><p>The first three Resources are quite common in healthcare — these are clinically oriented Resources. Patients are prescribed medications. Medications can be administered to a patient as an injection, for example. A patient may be immunized for Influenza.</p><p>The second set of three Resources are quite different — they are infrastructure Resources and are defined to help define and locate FHIR Resources. SearchParameters define the different ways that a FHIR Server may support searching for a patient — by last name for example. A CapabilityStatement Resource contains a list of all supported Resources available in a FHIR Server and the different interactions that may be available (read or write for example). StructureDefinitions are used to define… FHIR Resources. This self-definitional aspect of FHIR makes the FHIR specification quite powerful as a platform specification for healthcare, as we will see later.</p><h3>What does a FHIR Resource Look Like?</h3><p>Below is a Patient FHIR Resource expressed in JSON. XML is also supported by the FHIR specification. As you examine the structure, a FHIR Resource is a collection of elements that contain either primitive values, such as the “active”: true element, or a hierarchy of other elements, such as the “address” element which contains a collection of elements representing a postal address.</p><p>Let’s examine each section in detail.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VK2k7nTgPXbt8yGEns8TjA.png" /></figure><h3>Common Elements of Resources</h3><p>All FHIR Resources have the following characteristics in common.</p><p>FHIR Resources have:</p><ul><li>A known identity where it can be located — its URL. Here is the Patient with id 12345: https://[FHIR server endpoint]/Patient/12345</li><li>A FHIR Resource Type — identification of the type of Resource (e.g. Patient, or Medication)</li><li>A FHIR server specific identifier (its FHIR id — 12345 in this example)</li><li>A consistent set of metadata that provides context and workflow information about the Resource. For example, you will find a lastUpdated value in the metadata section that contains the date and time of the last change to the resource.</li><li>A human-readable representation.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/711/0*ewDFTHivpbdnkfzB" /></figure><p>Above is a UML diagram of the <a href="http://hl7.org/fhir/patient.html">Patient FHR Resource</a>. We can see that the Patient inherits from a <a href="http://hl7.org/fhir/domainresource.html">DomainResource</a>, which in turn inherits from a <a href="http://hl7.org/fhir/resource.html">Resource</a>. These two foundational concepts contain the common elements for all FHIR Resources. We won’t discuss every detail of this diagram — larger topics like Profiles, Extensions, and others will be featured in future articles. Let’s walk through several of the key attributes:</p><h3>Resource Identifier (id)</h3><p>The id attribute in Resource is a logical id that never changes for the lifetime of the Resource. This logical id is either assigned by the FHIR server when creating a new Resource, or some FHIR servers support client-assigned ids, which is a convenient feature to use when duplicating FHIR data from one server to another.</p><p>In the example above, 12345 is the logical id for the Patient. Clients may request this resource by its location which is simply the base url, the resource type (Patient) and the logical id.</p><blockquote>https://fhir.yourcompany.com/fhir/Patient/12345</blockquote><p>It is important to note that the Resource Identifier is completely different than a business identifier (see the Patient “identifier” attribute mentioned below).</p><h3>Metadata (meta)</h3><p>The meta section in each FHIR Resource contains the following attributes which are helpful in resource management:</p><h4>versionId</h4><p>FHIR Resources may be versioned, should the FHIR server support this feature. For example, the initial version if a FHIR Resource may be 1, which can also be accessed at this location:</p><blockquote>https://fhir.yourcompany.com/fhir/Patient/12345/_history/1</blockquote><p>Should Patient/12345 be modified (for example, if a patient has a new, updated address), its name — or logical id will not change. The versionId will be updated to 2 when retrieved from this location:</p><blockquote>https://fhir.yourcompany.com/fhir/Patient/12345</blockquote><p>Additionally, the same resource can be retrieved from:</p><blockquote>https://fhir.yourcompany.com/fhir/Patient/12345/_history/2</blockquote><p>Note: The FHIR Specification does not require that the versionId be an auto-incrementing value beginning at 1. It may be a GUID like this:</p><blockquote>https://fhir.yourcompany.com/fhir/Patient/12345/_history/038d12c2-ae9e-49b5-81d3-ba0af5ece9c3</blockquote><h4>lastUpdated</h4><p>Simply the instant data type representing the last time this Resource has changed.</p><h4>source</h4><p>Answers the question: Where did this resource come from?</p><h4>profile</h4><p>FHIR Resources may conform to zero or more FHIR Profiles. Profiles are defined as StructureDefinitions.</p><h4>security</h4><p>Security labels such as the confidentiality setting of this Resource.</p><h4>tag</h4><p>Tags are simply a way to mark a Resource for future reference.</p><h3>Human Readable Section (text : Narrative)</h3><p>The FHIR Specification includes a text, or Narrative section for each Resource. This section is very helpful and valuable when using FHIR Resources as it contains a summary of the Resource that is intended to be displayed to a human.</p><p>Although FHIR Resources contain structured data elements, the Narrative section has enormous value to clinicians and patients alike in that it is the location where notes reside which has been generated by human brains — knowledge and many years of experience that are required to practice medicine may be found in the Narrative section.</p><p>The Narrative section is formatted in XHTML, which makes it very easy to display. An application can simply choose to render the XHTML as a convenient, and simple display option.</p><h3>References Between Resources</h3><p>Notice this attribute in Patient:</p><blockquote>generalPractitioner 0..* Reference (Organization | Practitioner | PractitionerRole)</blockquote><p>The generalPractitioner attribute is a Reference to another FHIR Resource. It may be a reference to an Organization, a Practitioner, or a PractitionerRole.</p><blockquote>“reference”: “Practitioner/789”</blockquote><p>is a relative URL which means it is relative to this server’s base FHIR URL.</p><p>Reference URLs may also be absolute — they may reference FHIR Resources on completely different FHIR servers or, (optionally) a specific version of a resource like this:</p><blockquote>“reference” : “http://example.org/fhir/Observation/1x2/_history/2&quot;</blockquote><p>References may also refer to a Resource that is “contained” within the current FHIR Resource. For example, #p1 refers to the contained Practitioner resource within this Condition example:</p><pre>{</pre><pre>    “resourceType” : “Condition”,</pre><pre>    “contained”: [ <br>     {</pre><pre>        “resourceType” : “Practitioner”,</pre><pre>        “id” : “p1”,</pre><pre>        “name” : [{</pre><pre>            “family” : “Person”,</pre><pre>            “given” : [“Patricia”]</pre><pre>         }]</pre><pre>    }],</pre><pre>    “asserter” : {</pre><pre>        “reference” : “#p1”</pre><pre>    }<br>}</pre><h3>Summary</h3><p>In this article, we discussed the basics of FHIR Resources, their structure, the common elements of all FHIR Resources the Narrative section, and how Resources may reference each other to form a web of related FHIR Resources.</p><p>As you can see, using FHIR Resources, it is relatively easy to decompose a clinical consultation into a set of FHIR Resources and associated references.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/754/1*5giJF7mvk6dzbuNBDWhUKQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eda4a2f3612" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helios-software/the-r-in-fhir-resources-eda4a2f3612">The R in FHIR — Resources</a> was originally published in <a href="https://medium.com/helios-software">Helios Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[FHIR Architectural Patterns]]></title>
            <link>https://medium.com/helios-software/fhir-architectural-patterns-ae828b13d40c?source=rss----9b1b9ed586ce---4</link>
            <guid isPermaLink="false">https://medium.com/p/ae828b13d40c</guid>
            <category><![CDATA[healthcare]]></category>
            <category><![CDATA[fhir]]></category>
            <dc:creator><![CDATA[Steve Munini]]></dc:creator>
            <pubDate>Thu, 14 Sep 2017 17:37:17 GMT</pubDate>
            <atom:updated>2020-04-25T17:11:46.865Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c0Q8ubkloY7SuLJ1VxuxfA.jpeg" /></figure><p>A common misconception about HL7® FHIR® is that the standard is just an increasingly popular new healthcare data format. While it is true that the healthcare industry is rapidly adopting FHIR, viewing FHIR solely from the perspective that it is just a newer healthcare data format limits the impact FHIR can bring to your healthcare solution design. There are many new, compelling and powerful features that FHIR has to offer a software architect and developing an understanding is critical to building robust solutions and products with FHIR.</p><p>FHIR, fundamentally, is a “platform specification” that provides solutions to many common challenges encountered in describing, managing, sharing, and using clinical data in numerous complex contexts that are found in healthcare. The developers of HL7 FHIR have made some deliberate design decisions when creating FHIR that are huge steps forward in working with healthcare data. <a href="https://blog.heliossoftware.com/is-fhir-an-industry-disrupter-f55333058602">I have described many of them here in our first blog article</a>.</p><p>This article looks at the many ways in which FHIR can be used when designing a solution, or an “Architecture Pattern.” After reading this article, you will find that FHIR not only supports common interoperability challenges but, because of its design as a platform specification and many of FHIR’s interesting features, FHIR opens the door to new, modern, flexible and adaptive sets of healthcare product solution designs. These newer types of FHIR-based architecture patterns are described and I also describe some of the design principles of our own FHIR server.</p><h3>FHIR’s Assumption-Less Design Approach*</h3><p>FHIR makes no assumptions about the design of systems in which it will be used. We can use FHIR to build:</p><ul><li>A lightweight client such as a mobile phone app, or a heavyweight client such as a robust analytics healthcare data solution</li><li>A central server architecture or a peer-to-peer sharing solution</li><li>A push or a pull-based design</li><li>A query approach or publish/subscribe</li><li>A loosely or a tightly coupled system</li><li>Systems that require change history tracking, or those that do not</li></ul><p>FHIR does not impose a specific use model on the solution you are aiming to design. Also, picking one approach does not exclude other approaches. It is also possible to use multiple FHIR architectures in a single solution design. For example, one solution we have worked on uses FHIR to retrieve clinical data from an EMR (the <a href="#932a">Interoperability Interface</a> pattern). The solution also needs to perform analysis on genomic data, so we are exploring the use of a separate, genomic FHIR database endpoint (the <a href="#b8e8">Rapid FHIR-Based Endpoint</a> pattern) which will store clinical genomic sequence information.</p><h3>Two Approaches to FHIR</h3><p>There are two fundamental ways to approach the use of FHIR in your solution architecture. The most common use of FHIR is to add a FHIR API to an existing solution. I cover this scenario first, and then we will look at some new approaches to designing solutions using FHIR.</p><h4>FHIR-Enabling an Existing Solution</h4><p>In this approach, software architects start with an existing solution and work towards making their product or solution capable of offering a FHIR-compliant API. These solutions come in the form of:</p><ul><li>EMR Vendors</li><li>Healthcare Data Interchange Solution Providers</li><li>Claims Systems</li><li>Pharmacy Systems</li><li>Medical Terminology Systems</li><li>Other existing solution vendors</li></ul><p>The path to FHIR-enable an existing solution involves learning the FHIR specification, understanding the existing solution’s desired use of FHIR, selecting a <a href="http://hl7.org/fhir/foundation-module.html">FHIR paradigm</a>, mapping the existing solution’s data model to <a href="https://www.hl7.org/fhir/resourcelist.html">FHIR Resources</a>, specifying the solution’s FHIR capabilities in a <a href="https://www.hl7.org/fhir/capabilitystatement.html">Capability Statement</a>, and then, of course, testing the solution.</p><p>The task at hand is largely a mapping effort as result, and most of the time, these solution providers will never, by design, fully support the entire depth and breadth of the FHIR specification. That’s okay — FHIR was designed to be used incrementally. Some solutions, for example, medical terminology products, only ever need to offer a subset of the complete FHIR specification. Medical terminology servers are focused on providing the <a href="http://hl7.org/fhir/valueset.html">ValueSet resource</a>, as well as their supporting operations, and may not need to support many of the other FHIR resource sets.</p><p>Another example of partial FHIR specification support are EMR vendors themselves. At this current stage in EMR adoption of FHIR, many EMR vendors do not yet support write capabilities on their FHIR interfaces — they only support reads. This may change with time as the industry is rapidly moving to FHIR-based systems, and EMR vendors are being encouraged by their customers to support FHIR writes. Supporting write capabilities by an EMR vendor can be a complex undertaking, especially for those vendors who have application logic and other subsystem capabilities that are triggered to a write event.</p><h4>FHIR As a Next-Generation Health Data Platform</h4><p>Another FHIR architecture option exists in the form of using FHIR as the central design element of a new type of healthcare data technology. FHIR is fundamentally a platform specification, and as such, there are many powerful features that makeup FHIR as a platform solution including:</p><ul><li><a href="http://hl7.org/fhir/structuredefinition.html"><strong>Structure Definitions</strong></a> — Describe FHIR constructs themselves — a meta-language for FHIR. Structure Definitions are used to describe the content defined in the FHIR specification — Resources, data types, and underlying infrastructural types.</li><li><a href="http://hl7.org/fhir/searchparameter.html"><strong>Search Parameters</strong> </a>— Describe the types of search capabilities that are supported by a FHIR server.</li><li><a href="http://hl7.org/fhir/capabilitystatement.html"><strong>Capability Statement</strong> </a>— A way for a FHIR server to “advertise” its set of capabilities to other software systems. A client may simply examine a FHIR server’s Capability Statement to determine, for example, if a particular FHIR Resource is supported and if it can expect to read and write those resources to the server.</li><li><a href="http://hl7.org/fhir/resourcelist.html"><strong>Healthcare Domain Model</strong> </a>— A set of well-defined and well-thought-through resources that describe the domain of healthcare. In the FHIR model, you will find concepts such as a patient, medication, allergy, and many other constructs defined robustly.</li><li><a href="http://hl7.org/fhir/extensibility.html"><strong>Extensions</strong></a> — A built-in way to extend, or add to a FHIR resource, or add to specific elements within a FHIR resource.</li><li><a href="http://hl7.org/fhir/profiling.html"><strong>Profiles</strong></a> — Because FHIR is a platform specification and is quite flexible, often the need arises to specify which parts of the FHIR specification are to be used. Using a Profile, a solution designer can specify which resource elements are used and which are not, which terminologies are used in certain elements, and also how the API may be called.</li></ul><p>These are just some of the features of FHIR and is not intended to be a comprehensive list, but as you can see, with such a well-defined set of platform constructs, it becomes possible to build an entirely new healthcare data product based upon the FHIR specification itself.</p><p>This is the design path that we have followed with the Helios FHIR Server. We have taken the FHIR specification, and have used it to create an entirely new clinical data product on top of the highly scalable, distributed, and extremely fast open-source Apache Cassandra™ database.</p><p>We have started with FHIR Structure Definitions and have used them to generate a Java object model, Cassandra table structures, and user-defined data types, REST API controllers and data access methods. Additionally, we use FHIR-defined Search Parameters to create the necessary indexes that support FHIR searches in a very fast and scalable manner that Cassandra provides. In a future blog post, we will have a deeper look at the internal design of the Helios FHIR Server.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fe99955%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fe99955&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/1125d29e7a4e978e8837e12623a6827d/href">https://medium.com/media/1125d29e7a4e978e8837e12623a6827d/href</a></iframe><h3>8 FHIR Architectural Patterns*</h3><p>Below, I have identified 8 FHIR architectural patterns. Several of these patterns are quite obvious and describe the types of common challenges that FHIR was designed to solve. Other patterns are a bit more advanced and will make you think about the kinds of new products that may arise in the marketplace now that FHIR is here and is being adopted in the industry.</p><p>The first four of these patterns fall under the FHIR-Enabling an Existing Solution approach and the last four fall under the FHIR As a Next Generation Health Data Platform approach.</p><h3>Interoperability Interface</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/357/1*qRd-H-cPHAGTB993sNLy3Q.png" /></figure><p><em>Intent: Supply an interoperable API on top of an existing solution that can be easily understood and consumed by clients.</em></p><p>The interoperability interface architecture pattern is the most common pattern we see. Note that I didn’t call this pattern an EMR interoperability interface, because this pattern is not limited to EMR vendors alone. Many other types of healthcare solutions and vendors adopt this pattern too. For example, terminology vendors use this pattern and provide a FHIR-compliant API that can be used by many other systems in a healthcare computing environment.</p><p>Participants:</p><ul><li>Clinical Database: An EMR’s main database (for example, Epic uses Cache), a relational database such as Oracle, Microsoft’s SQL Server, MySQL, Postgress, or even a nonrelational database such as Apache Cassandra.</li><li>Data Access Layer: A layer of software that knows how to access and understand the proprietary clinical database structure and present it to the next layer of software.</li><li>FHIR Adapter: Software that adapts, or otherwise translates data from a proprietary database to FHIR resources.</li><li>FHIR API: HL7’s FHIR API supplying services most commonly in a <a href="http://www.hl7.org/fhir/http.html">RESTful API</a> paradigm, or other supported paradigms such as <a href="http://www.hl7.org/fhir/messaging.html">Messaging</a>, <a href="http://www.hl7.org/fhir/documents.html">Document</a>, or <a href="http://www.hl7.org/fhir/services.html">Services</a> paradigms.</li></ul><p>A note about the FHIR Architectural Patterns and FHIR Paradigms. I view these two as topics as orthogonal. In other words, one can use a Messaging paradigm in an Interoperability Interface architecture in one solution, and a RESTful paradigm in a FHIR Broker Adapter architecture in the next. Another implementation may flip these paradigm and architecture choices.</p><h3>FHIR Broker Adapter</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rwTeVG3a2-7o2shReo7ysw.png" /></figure><blockquote>Intent: Convert industry-standard healthcare data formats and proprietary formats to and from FHIR “on-the-fly.”</blockquote><p>Healthcare computing environments are complex. Data resides in many different systems, even when there is a single, unified EMR installed. Also, data often needs to go to organizations and systems outside of the four walls of a hospital or healthcare organization in a variety of different formats, using myriad transport methods.</p><p>Healthcare organizations need to send data to and from many systems such as:</p><ul><li>Bi-directional data exchange with other provider groups and payers</li><li>Participate in a health information exchange (HIE) networks</li><li>Integrate with lab orders and results</li><li>Send data to state immunization registries</li><li>Send data to syndromic surveillance public health agencies</li></ul><p>Several interoperability vendors in the market do this work exclusively — it is a specialized area of expertise that takes excellent technology, talented staff, and exceptional operational support to do it well. These vendors sometimes do not persistently store the messages, or if they do, they do not store them forever — these systems are transfer systems — and are not necessarily designed to be permanent long-term storage. FHIR is simply another format with which to transform.</p><h3>FHIR/Proprietary API Mixed-Use</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/377/1*gEu5N1oR6ZyCNb19WCCvKQ.png" /></figure><p><em>Intent: When building a production application that may need to interoperate with several EMRs, use FHIR to achieve code reuse and EMR portability, but also use proprietary APIs to satisfy business requirements.</em></p><p>This architecture approach goes against the grain of how a software architect wishes to ideally design a system. In an ideal design world, a solution would have a complete and comprehensive functional separation layer, simplifying the design and thereby providing an elegant solution.</p><p>Reality often steps in when designing real-world systems. There are two very real reasons why your solution may need to use this architectural pattern.</p><ol><li>The FHIR server with which you intend to integrate doesn’t support the FHIR capabilities you need. A common case here is FHIR write support. Several large EMRs do not support FHIR writes, yet your application solution may have mandatory requirements to store all data in the EMR for compliance purposes. Should a hospital, for example, receive a request for all of a patient’s data, the release of the information department is only going to look for data in one location — the EMR. It is complex, cumbersome, and unrealistic to have that department probe numerous systems for data about a patient — especially when they might not even know about the existence of those other systems.</li><li>The FHIR specification may not describe your healthcare domain concept or use case. If you find this to be the case, consider participating in HL7 to advance the FHIR specification itself! You will find an interested community of other healthcare technologists that want to help advance the state of interoperability along with you.</li></ol><h3>FHIR API Encapsulating a Vendor-Neutral Clinical Repository</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V9ynMD64iBQQDNSzRUT_eA.png" /></figure><blockquote>Intent: Use FHIR as a consistent API to a vendor-neutral repository, increasing substitutability of systems and increasing consistency of data access.</blockquote><p>A common requirement in healthcare organizations is the need to collect many types of data into a single location for numerous reasons, for data warehousing, or analytic projects for example. Often the EMR itself is not a feasible or logical product choice to perform this type of work.</p><p>FHIR has a deep domain model and excellent extension capabilities and profile support to satisfy these requirements.</p><h3>FHIR-Based Clinical Data Repository</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/577/1*DC773_4ED2loe--7CWcHxg.png" /></figure><blockquote>Intent: Instead of mapping a solution to fit FHIR, start with FHIR as a platform design specification, and create a FHIR-native solution from it directly.</blockquote><p>This architectural pattern takes the opposite approach than the previous four patterns. In this architectural pattern, FHIR isn’t a specification to which an existing solution would need to be mapped or adapted. Instead, this architectural pattern begins with FHIR as the key design centerpiece of an entirely new product.</p><p>I wrote earlier about some of the very powerful FHIR constructs that make this architectural pattern possible, such as Structure Definitions, Extensions, Search Parameter definitions and Profile support, so I won’t repeat them here, however it is important to understand these constructs to understand the design approach to this pattern. These constructs and the right set of software tooling that can convert these FHIR constructs to working code make it possible to not only generate a FHIR-compliant system from those artifacts but also create a much more flexible healthcare data solution generally.</p><p>This is the model of the Helios FHIR Server. We have used FHIR as the key design construct for an entirely new product. Let’s look at just one element of what the FHIR specification defines, and then see how that translates to working code.</p><p>Below is a snippet of the FHIR specification that describes a SearchParameter — a way to locate resources by certain values. In this example, the “individual-email” search parameter enables us to find any of the 5 resources at the bottom of the XML example, Person, Patient, etc. by their email address.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EE_QhHdtiGuGRc7mxGGjyw.png" /></figure><p>Using the FHIR SearchParameter, along with other elements of the FHIR specification, we can generate not only the necessary database table structures, and domain object model, but also a Cassandra query such as the one below that will locate all Patients with an email address matching the “?” parameter.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/676/1*I8FujrPSBTDVMuISGNEymg.png" /></figure><p>Products that use this architectural pattern provides incredible flexibility. It certainly future proofs any solution that may wish to integrate with FHIR as the standard evolves, but it also provides a framework for extending and enhancing solutions. Should your solution need to add another search parameter that, perhaps the FHIR standard does not specify — simply add another SearchParameter to your environment, and the necessary indexes and supporting access code is generated.</p><h3>FHIR-Based Integration Hub</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8kaSX4lhCixoR_40STlqjA.png" /></figure><blockquote>Intent: Use FHIR’s domain object model as the native interchange format from which to map a variety of other formats both to and from FHIR.</blockquote><p>Using A native FHIR object model as the basis for a new type of healthcare broker solution has a key advantage. By using FHIR internally as the underlying domain model, this shifts the responsibility of a broker software vendor from maintaining their own internal proprietary format and mapping to another mapping — simplifying the design of these solutions greatly.</p><h3>FHIR-Based Analytics Solution</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/666/1*aRp8GpR8XmTbbmnjlbiP7w.png" /></figure><blockquote>Intent: Instead of transferring data to a separate analytics solution, keep the data in place, and use FHIR as the underlying domain model upon which to perform analysis.</blockquote><p>Online analytical processing systems are those that are configured to use a multidimensional internal data model, allowing for complex analytical and ad hoc queries. These systems are very powerful and have been designed to produce very fast answers to queries on large data sets using a cube-oriented data model architecture. This involves populating cubes from a separate data source which, if not done properly, can introduce data lag (additional time required to get the data from an operational data store to the analytical data store) and synchronization issues (is the correct data available for analytics processing?) in a solution design.</p><p>Using FHIR as the underlying object model and generating a database (or a cluster of nodes in the case of Apace Cassandra) optimized for analysis can be a high-performance solution to some of the challenges with running a separate OLAP system.</p><p>Increasingly, the industry is considering a different approach to analytic processing. One approach is to place processing nodes co-resident with the data storage nodes in a distributed fashion. This is exactly the approach taken with Apache Spark (processing) and Apache Cassandra (storage). The fundamental idea is very straightforward: Spark and Cassandra clusters are deployed to the same set of machines where Cassandra is responsible for storing the data and a Spark worker node, running on the same machine is responsible for data processing.</p><p>Spark is a system that is designed to work with large amounts of data in a batch-oriented fashion. When a task arrives, Spark loads data into memory directly, and since the Spark node is co-resident on the same node as Cassandra, there isn&#39;t network traffic impact that often slows such analytics systems considerably.</p><h3>Rapid FHIR-Based Endpoint</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/565/1*vSjv2p0twlKgWQBY1_GYag.png" /></figure><blockquote>Intent: Provide a FHIR-compliant healthcare data storage solution rapidly.</blockquote><p>FHIR is an excellent integration technology. Sometimes, however, it may be faster, and easier to not use FHIR as an integration technology, but instead, use it as a standalone database. There are many real-world scenarios where it may be faster, easier, and less costly to simply stand-up a FHIR database and begin working with it immediately.</p><ul><li>Prototypes — FHIR is new, and there are many ongoing efforts involving early prototyping with FHIR to better understand it’s capabilities and features. Installing a standalone FHIR-compliant database is a great way to begin prototyping.</li><li>Startups — Healthcare startups often have a large design challenge initially in terms of simply describing the data with which they want to work. For example, if a healthcare startup company is building a solution involving medications, using FHIR as their medication data model is a very easy way to make rapid progress.</li><li>No means to store data otherwise —One of FHIR’s key strengths is its expressive set of foundational resources that enable us to describe healthcare concepts easily and rapidly. Often, when building healthcare products, it is much easier to borrow the tooling of a rapid FHIR-based endpoint than it is to re-create it from other means. For example, if your solution finds that it needs to begin to work with genomic data, and you don’t have a genomic database handy, and don’t want to build one — a rapid FHIR-based endpoint that can both read and write <a href="https://www.hl7.org/fhir/genomics.html">FHIR sequence resources</a> would be a great place to start.</li><li>Easier to store it here, rather than build an adapter there — Sometimes it is just simpler to store data in a temporary location, in the format that you desire, rather than investing the additional development time that may go into building an adapter. Often, it is a question of people too — the development team that may be required to accomplish an adapter development effort may not be available in the timeframe you need.</li></ul><h3>Summary</h3><p>With this article, I have aimed to show you some of the many ways that you can use FHIR in your solution designs, or FHIR Architectural Patterns. There are two fundamental approaches to using FHIR. The first is adapting your solution to fit FHIR by providing FHIR as a new interface on top of an existing solution. This is the most common approach when thinking about using FHIR. I have also outlined an entirely different approach to using FHIR, which is to use the FHIR specification, and all of its expressiveness to create FHIR-native solutions. FHIR-native solutions offer a great amount of flexibility, future-proofing, speed of development and integration, and are a promising new approach to working with healthcare data. Our own Helios FHIR Server follows this design approach.</p><h3>An Offer For You</h3><p>If you have found this blog post to be of interest to you, please do share it on your favorite social media platform.</p><p>Additionally, we have created a group on LinkedIn of the industry’s leading Health IT developers and architects who are building high-performance analytic healthcare applications using FHIR. If topics like the ones I discussed in this blog article are of interest to you, please consider joining our group.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fe99955%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fe99955&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/1125d29e7a4e978e8837e12623a6827d/href">https://medium.com/media/1125d29e7a4e978e8837e12623a6827d/href</a></iframe><h3>* Credits</h3><p>Concepts derived from <a href="https://www.slideshare.net/DevDays2014/rolling-out-fhir-architecture-and-implementation-considerations-by-lloyd-mckenzie">FHIR for Architects</a> presentation, © 2014 HL7 ® Int’l. Licensed under <a href="https://creativecommons.org/licenses/by/3.0/">Creative Commons</a>. HL7, Health Level Seven, FHIR &amp; flame logo are registered trademarks of Health Level Seven International.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae828b13d40c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helios-software/fhir-architectural-patterns-ae828b13d40c">FHIR Architectural Patterns</a> was originally published in <a href="https://medium.com/helios-software">Helios Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SMART on FHIR: Securing the App Store for Health]]></title>
            <link>https://medium.com/helios-software/smart-on-fhir-securing-the-app-store-for-health-fb1f1f3a6ccd?source=rss----9b1b9ed586ce---4</link>
            <guid isPermaLink="false">https://medium.com/p/fb1f1f3a6ccd</guid>
            <category><![CDATA[health-technology]]></category>
            <category><![CDATA[healthcare]]></category>
            <dc:creator><![CDATA[Steve Munini]]></dc:creator>
            <pubDate>Fri, 17 Feb 2017 12:10:36 GMT</pubDate>
            <atom:updated>2020-04-25T16:13:16.198Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TidTy7U4iJzUBwK9BIBjYA.jpeg" /></figure><p>There are over 2 million apps in the Apple App Store, and <a href="https://www.statista.com/statistics/276623/number-of-apps-available-in-leading-app-stores/">over 2.5 million</a> apps in Google Play. Some of my favorites are Waze for driving my son to his next obscurely located hockey rink here in New England, LinkedIn and Twitter for keeping up on industry news and topics, and also lately, several different airline apps that speed the check-in process, and let me be one of the first to be notified of flight delays.</p><p>There is no doubt that the app model has worked brilliantly for the smartphone market, unlocking incredible disruptive innovations since the original launch of the Apple App Store in July of 2008.</p><p>It is not surprising that some of our best thinkers in healthcare information technology, witnessing this success, published an <a href="http://www.nejm.org/doi/full/10.1056/NEJMp0900411">article in JAMA</a> in 2009 outlining what it would take to bring this kind of capability to the healthcare industry. In their article, Dr. Kenneth Mandl and Dr. Isaac Kohane at Boston Children’s Hospital and Harvard Medical School outlined four key ingredients for success:</p><ul><li>There should be liquidity of data — It should be easy to transfer data from one place to another in an agreed-upon form.</li><li>There should be substitutability of applications — We should be able to use a billing system from one vendor and a laboratory information system from another and be able to swap either vendor’s solution out from time to time if we choose.</li><li>The platform should be based on open standards.</li><li>The platform should have a diverse set of applications, enabling an environment of “natural selection” — Let the apps with the highest value and lowest cost win.</li></ul><p>The following year, in 2010, the U.S. government-funded the creation and initial development of SMART with a $15 million contract to create standards, open-source technology and initiate a robust community of developers. SMART, which stands for “Substitutable Medical Apps, Reusable Technology,” was born.</p><p>The SMART Project rapidly got underway, initially developing its own openly licensed clinical data models. Dr. Joshua Mandel, Lead Architect of the SMART Project in his <a href="https://academic.oup.com/jamia/article/23/5/899/2379865">JAMIA article</a> describes the journey of this new technology development and the eventual transition to HL7 FHIR as it emerged during this same timeframe. FHIR, or Fast Healthcare Interoperability Resources is a next-generation healthcare interoperability framework created by HL7. For more information on FHIR, please <a href="https://blog.heliossoftware.com/is-fhir-an-industry-disrupter-f55333058602">read my blog article here</a>. The SMART project transitioned its efforts toward FHIR, and also changed its name to SMART on FHIR.</p><h3>Securing FHIR</h3><p>An “App Store” suitably designed for healthcare would need to address a critical design challenge: How do we enable a third party ecosystem of applications while meeting the rigorous security and access control requirements that healthcare demands?</p><p>FHIR on its own does not specify an approach to security, nor does it require any particular security implementation. The SMART project not only provides a specification for a layer of security on top of FHIR, but it goes beyond that and takes a huge step forward in terms of solving a conundrum that has plagued many third party healthcare application providers. SMART on FHIR makes it easy for clinicians to launch applications from within the EMR itself. Time and time again, we found that doctors who were forced to provide a login and password to another system — don’t. It is simply too time consuming and inconvenient.</p><p>SMART on FHIR has succeeded in delivering a series of specifications that enable a new breed of applications, what Wes Rischel of Gartner has termed <a href="https://fhirblog.com/2015/07/10/fhir-smart-and-sidecar-applications/">“sidecar” applications</a>. Sidecar applications are those that “supplement an enterprise EHR application without taking over the fundamental workflow that is orchestrated by the enterprise app.”</p><p>Now, with SMART on FHIR, there is an <a href="https://gallery.smarthealthit.org/">abundance of sidecar applications </a>that have emerged, from a bilirubin chart to medication management tools, to growth chart apps. And perhaps, the biggest test for SMART on FHIR’s future growth is that large EMRs have embraced SMART on FHIR, notably with Epic’s <a href="http://open.epic.com/">open.epic.com</a> effort as well as Cerner’s <a href="http://fhir.cerner.com/">fhir.cerner.com</a>.</p><h3>How does SMART on FHIR Work?</h3><p>SMART on FHIR specifies, using the <a href="https://oauth.net/2/">OAuth2</a> open standard, a way for applications to register themselves with an EMR and ultimately obtain an access token. SMART also uses <a href="http://openid.net/connect/">OpenID Connect</a>, an authentication layer on top of OAuth2, enabling single sign-on. Think of an access token as a single key to one or more P.O. Boxes at the local post office. A SMART on FHIR sidecar application may be configured to read only a patient’s medication and allergy list, but not its list of diagnoses or medical procedures. In this case, only two P.O. boxes will open with the single key or access token. Maybe the medication management application we are developing doesn’t need access to diagnoses or procedures, so it doesn’t request them. This initial request for permissions is called a “scope.” The post office may or may not choose to enable your key to work — it is their P.O. box, after all, you are just renting the box and the key to open it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NQ1Y2XBbDGXqa1BtRM5NvA.jpeg" /></figure><p>After a sidecar application has obtained an access token, it then sends it back to the FHIR server in an HTTP header with FHIR API requests. If the access token is still valid (it hasn’t been revoked by the server for example), and the API request is within the scope that has been negotiated, the FHIR server will service the request.</p><p>SMART on FHIR also specifies two ways to launch a sidecar application.</p><ul><li>EMR Launch — SMART on FHIR specifies an ability for a sidecar application to be launched from within the EMR itself, passing along information about the active patient, encounter, and location information to the sidecar application.</li><li>Standalone Launch — Additionally, SMART on FHIR also specifies a way to enable users to launch from the sidecar application’s web page, and log in using an EMR user account. We see the same style of login flow all over the Internet when we are asked to “Sign in using Google” or “Login with Facebook.” SMART on FHIR-enabled EMRs use the same set of standards but instead are enabling secure access to EMR user accounts and data.</li></ul><p>Finally, FHIR defines a set of resources — the “R” in FHIR stands for resources. To achieve a level of substitutability that SMART on FHIR aims, FHIR resources need to be further restricted and extended from these base specifications, collectively known as “profiling a resource.” For example, it is insufficient to simply indicate that a solution uses RxNorm for medications and LOINC for observations. Real-world interoperability requires further specificity in terms of insisting that certain data fields be complete, such as a name field when describing a patient, or when presenting a list of medical problems, each problem shall have a current status identified.</p><p>The profiling efforts for SMART are currently evolving. SMART defines a set of profiles that are in the process of transitioning toward the <a href="http://argonautwiki.hl7.org/">Argonaut</a> profiles in the US.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fe99955%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fe99955&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/1125d29e7a4e978e8837e12623a6827d/href">https://medium.com/media/1125d29e7a4e978e8837e12623a6827d/href</a></iframe><h3>Experience and Lessons Learned</h3><p>In 2009, at my prior company, Dossia, we used a very similar approach to enable a healthcare ecosystem of third-party solutions, although our target was not clinicians using EMRs, it was patients directly. We offered our solution to health plans and employers. Our product powered health initiatives for over 900 employers consisting of hundreds of thousands of individual users. Dossia’s API was central to our strategy to enable as many compelling, and effective personal health solutions for our customer’s populations.</p><p>The core technologies utilized by Dossia’s API included:</p><ul><li>OpenID, which enabled shared identity with our ecosystem partners across web sites</li><li>OAuth to allow secure API authorization</li><li>Representational State Transform (REST), which provided for a simple access method for reading and updating health data</li></ul><p>At Dossia, we connected over 40 different personally-controlled health applications. Some we wrote ourselves, but the majority were supplied by third-party application providers. The applications ranged from products written by major healthcare organizations such as Mayo Clinic to small connected health devices built by small startups here in Boston.</p><p>SMART on FHIR uses newer versions of OAuth, and much has changed with OpenID since 2009, in that it now rides “on top” of OAuth, however, the same innovative approach is at work here. I would like to share some of our experience with our Dossia journey, and foreshadow some key areas of complexity that, as SMART on FHIR continues to grow, healthcare providers, health plans and health IT vendors who will be adopting it will need to address.</p><h4>Lessons Learned:</h4><ul><li><strong>There is immense power and benefit in opening up an API.</strong> We issued a press release about the availability of our API and were flooded with requests to integrate. Prioritizing them was hard, but we established a system to manage them. We found that, over the long term, enabling an API benefited both parties equally. As a platform technology vendor, we could focus on enhancing our core product, and our API developer partners focused on improving theirs. API developers created solutions that our team would never dream up on our own, nor did we have the development capacity to implement them if we did. We were able to offer these solutions to our customers easily and inexpensively. <br>The healthcare IT vendor market will follow models from other industries that have seen rapid API adoption. Companies like Salesforce, Yelp, Waze, and many other organizations have extensive public API initiatives. For those health IT vendors who are not yet embracing SMART on FHIR for fear of giving away customer control, or a desire to offer as much capability on your own to your customer base as possible, I would say that those fears are unfounded and you run a greater risk in not acting — in the future, customers may choose vendors who can offer more choice of functionality and substitutability, enabled by SMART on FHIR.</li><li><strong>With great power comes great responsibility.</strong> Increased responsibility exists both on the side of the EMR, and the integrating application vendor. We needed to establish a set of “rules of the road” in terms of how to use our API, what was acceptable use, unacceptable use, responsibilities of both parties in terms of data use, clarity of authorizations for our collective users, privacy policies, terms of use and other considerations.</li><li><strong>User Interface Consistency. </strong>This is perhaps the single largest challenge of third-party application integration. It matters greatly that the user experience can flow beautifully from one application to the next. At Dossia, we worked hard to provide our application partners with sufficient screen real estate via an integrated iFrame approach as well as guidelines for user interface features. We were unique in our market in that other vendors offered more of a hub framework, and the user experience was quite clunky for them, whereas the vendors who chose to integrate with Dossia had prominent placement, and integrated inside of the Dossia user experience in a way that was consistent and fluid. Small items like button shapes, consistent use of fonts, and consistent styling went a long way to create a really great user experience. Just as the Apple App Store, and Google Play have user interface guidelines, it will be important for SMART on FHIR apps to also follow a similar model. As the number of SMART on FHIR enabled applications increase, it will become more important for these applications to have common visual experience themes. This will be exceptionally important as sidecar applications begin to take on areas of the healthcare delivery system where mistakes made by a user of a poorly designed or inconsistent user interface may place a patient at risk.</li><li><strong>Adequate API Developer Support.</strong> EMR vendors who offer FHIR APIs and SMART on FHIR enabled capabilities must professionally and competently support the developer communities that will begin to coalesce around their product. This means having excellent documentation, proper training materials, discussion groups, ways to communicate to knowledgeable engineers, and adequate response times to stumbling blocks that developers may encounter. At Dossia, we initially staffed our API support functions with the developers who created the technology, which worked well, and as time went on, and the requests from API developers were somewhat predictable, we enabled some of our more junior engineers to provide this level of support. This was a great way to train some of our newer members of the staff on the technology, and get a front-line view of how our community of application developers operated. Ultimately, we made the API support function a rotating assignment such that we could spread the knowledge inside our team, and not have any one person in the role for a lengthy period. We found that some of our best enhancement ideas came directly from the API developer community, and it was critical to collect their feedback and improve our product rapidly based on their comments and suggestions.</li><li><strong>Rules of the Road.</strong> Enabling FHIR and SMART on FHIR capabilities means that third party application providers will have a copy of EMR data and they will need to comply with HIPAA regulation. But, in addition to HIPAA, there is a set of other complexities that need to be discussed whenever data is copied. What happens if the data in the EMR is changed — a change of a patient’s address for example? How will the sidecar application’s copy be updated in cases where the app doesn’t pull the data from the API on each view? At what frequency? What if there is a means to update data from within the sidecar application? Will that data be sent back to the EMR? Today, some of the EMRs have enabled read-only FHIR servers, but in the future, as EMRs enable write access, it will be important that sidecar application vendors send data back into the EMR system of record consistently and correctly. There are many “rules of the road” details that will need to be articulated, documented, and followed when EMRs enable write access.</li><li><strong>Maintenance Windows.</strong> It was important to communicate maintenance windows and to coordinate maintenance with our application partners and customers. The kind of architecture that SMART on FHIR enables means that more people need to be involved in the planning of system maintenance that occurs from time to time.</li><li><strong>Uptime Requirements.</strong> Service level agreements with customers often included financial penalties for unplanned downtime. It was important that our application partners also understood these expectations and were able to comply with those requirements.</li><li><strong>Approach to Quality.</strong> At Dossia, we ran a professional development organization that included a specific approach to quality, with documented requirements, test plans, regression tests, and other systems, controls, and policies that are found inside organizations that are creating commercial-grade software. Some of the vendors who had an inexperienced development staff sometimes struggled to meet our level of quality expectations and the rigor that goes into producing high-quality software. Organizations that will utilize SMART on FHIR will also need to be very specific in terms of the quality expectations of integrating sidecar applications.</li><li><strong>Environments.</strong> We had several separate development, integration, and staging environments and a single production environment. We found that some third-party application vendors sometimes had a development environment, and a production environment, and that was it. We needed them to correct their internal environment set up before we would continue. SMART on FHIR sidecar application vendors should mirror the environment setup of the EMR.</li><li><strong>Security.</strong> A tremendous amount of work and resources goes into securing healthcare data systems. Security is a large and continuous task. At Dossia, we also extended our security practices to our API application partners. This meant documented policies, penetration scans, training, audits, and other processes and controls necessary to keep our user’s data safe. SMART on FHIR implementations needs to examine and potentially refresh their security policies and approach to security now that these newer capabilities exist.</li><li><strong>Change Control.</strong> Communicating changes to environments, new releases, changes to APIs, and other, potentially breaking changes is critical in an environment that SMART on FHIR enables.</li><li><strong>IT Governance.</strong> Hospitals and other healthcare organizations likely do not yet have the necessary IT governance, procedures, and policies in place that contemplate SMART on FHIR sidecar applications. Healthcare IT executives and the teams that work under them work very hard to ensure the security, reliability, consistency and availability of internally deployed products. It takes an entirely new set of skills, processes, procedures, and controls when transitioning to a more open IT governance supporting open APIs.</li></ul><h3><strong>SMART on FHIR’s Rapid Growth Path</strong></h3><p>Living in Boston has some excellent advantages. Recently, we attended the first meeting of the Boston SMART on FHIR Interest Group. Dr. Ken Mandl kicked off the meeting and speakers included Dan Gottlieb, Product and Technical Lead, SMART Project / Boston Children’s Hospital, and Josh Mandel, Lead Architect, SMART on FHIR. It was a well-attended event with many engineers, scientists, MDs and enthusiastic informaticists in the room. Josh gave a presentation on CDS Hooks which is a pattern for invoking decision support capabilities that builds on SMART on FHIR.</p><p>At the most recent FHIR Connectathon in San Antonio, the growth of FHIR, and SMART on FHIR was most evident. There were no less that 4 tables of attendees participating in the CDS Hooks track.</p><h3><strong>Summary</strong></h3><p>SMART on FHIR opens the door to entirely new levels of interoperability, user experience and integration while maintaining rigorous security and privacy requirements that were never possible before. With these new capabilities, come additional levels of responsibilities not only by organizations who have implemented EMRs, but also the developer’s community who are creating integrating applications.</p><h3><strong>About Us</strong></h3><p>Helios Software is a Boston-based health technology company that delivers professional product engineering services, and also offers a FHIR-based clinical data solution. We are actively implementing SMART on FHIR solutions for clients. <a href="http://heliossoftware.com/contactus.html">Please get in touch</a> if you are looking for assistance.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fe99955%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fe99955&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/1125d29e7a4e978e8837e12623a6827d/href">https://medium.com/media/1125d29e7a4e978e8837e12623a6827d/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb1f1f3a6ccd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helios-software/smart-on-fhir-securing-the-app-store-for-health-fb1f1f3a6ccd">SMART on FHIR: Securing the App Store for Health</a> was originally published in <a href="https://medium.com/helios-software">Helios Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is FHIR an Industry Disrupter?]]></title>
            <link>https://medium.com/helios-software/is-fhir-an-industry-disrupter-f55333058602?source=rss----9b1b9ed586ce---4</link>
            <guid isPermaLink="false">https://medium.com/p/f55333058602</guid>
            <category><![CDATA[fhir]]></category>
            <category><![CDATA[healthcare]]></category>
            <dc:creator><![CDATA[Steve Munini]]></dc:creator>
            <pubDate>Tue, 06 Dec 2016 13:54:15 GMT</pubDate>
            <atom:updated>2020-04-25T15:09:33.865Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sfPtfID83f3eDjtxagGzKA.jpeg" /></figure><p>I have a passion for innovation. Specifically, I love disruptive innovations — the kind that totally upends an industry, seemingly overnight. I’m talking about the kind of technology innovations that come along from time to time and change everything. We have been lucky to witness many in our lifetime — personal computers, digital photography, and the Internet to name a few. These technologies blow open new opportunities and change the status quo so quickly that vendors providing products and services in the old model are left in the dust. This happens largely because human present bias kicks in: it is easier to continue doing what works now (and is making money now), even though the game has changed entirely.</p><p>The computing industry is the world-record holder for disruptive innovations. Minicomputers in the 70s disrupted the mainframe computer market. The personal computer then disrupted the minicomputer market in the 80s. Entirely new, multi-billion dollar companies are created during disruptive innovation events, while at the same time, very large incumbent vendors are often pushed aside by the new kid in town.</p><p>At the core of disruptive innovations are incredible technology advancements — the kind that can move entire industries. The introduction of low-cost microprocessors by Intel led the way for the PC revolution. Another example is Netflix’s impact on the rented DVD market, and ultimately, the entire entertainment industry.</p><p>Often, disruptive innovations occur not just because of a single technological advancement, but a collection of them, all aligning at the same time. For instance, Netflix would not be possible without sufficient video-capable PCs, tablets, and mobile phones as well as the bandwidth available to stream movies and TV shows.</p><p>Healthcare should be an incredibly target-rich environment for disruptive innovations. The market is huge, making up nearly one-fifth of this country’s GDP. Healthcare is expensive, and we continue to pay more every year, <a href="https://medium.theuxblog.com/the-sad-state-of-product-design-in-healthcare-9226089a7044">yet get the same, or often less for our dollar</a>. There are certainly many entrenched vendors in healthcare from large provider groups, to big insurance companies to big pharmaceutical firms protecting their turf.</p><p>But where are the disruptors?</p><p>In his blog article titled “<a href="https://medium.com/@malay/building-a-big-health-tech-company-76f51ab4da64">Building a big health tech company</a>,” Malay Gandhi does a great job of describing the rather lackluster results of investor attempts at “revolutionizing healthcare.” Innovation in healthcare is exceptionally challenging, and disruptive innovation in healthcare is rare indeed. During the last 5 years, over $17 billion of investor money has gone into healthcare startups, yet there are relatively few billion-dollar valuation companies that have been created during this time period. Gandhi goes on to point out that most of the market gain after healthcare “reform” went to existing incumbents. That’s right — large healthcare firms have seen their market values nearly double since 2011.</p><p>Because of the healthcare market’s size and expansiveness, it’s not surprising that many startups have focused on incrementalism, not revolutionism. It is much easier to take a small cut of a large number of transactions than tackle head-on the huge obstacles of true healthcare transformation. I agree completely with Gandhi when he states: “Health tech companies that want to be big will have to focus on making healthcare different, not just better.”</p><p>Are there any disruptive technology innovations on the horizon for healthcare? The kind that — once understood, matured, and partnered with other innovations — can break open the industry and enable disruption?</p><p>The answer is yes, and the <a href="http://hl7.org/fhir/">HL7® FHIR® standard</a> is exactly that. FHIR® has emerged as a key ingredient technology that enables disruptive innovation, but like other disruptive events, it will take a collection of technologies, practice changes, and new thinking to achieve real disruption in healthcare.</p><p>FHIR is a standard that deserves your attention and offers great advantages to future technology development efforts in healthcare. Below, you will find the reasons why FHIR is different than previous interoperability efforts and healthcare innovation challenges where you can begin applying FHIR today.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fe99955%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fe99955&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/1125d29e7a4e978e8837e12623a6827d/href">https://medium.com/media/1125d29e7a4e978e8837e12623a6827d/href</a></iframe><h3>Healthcare Data Interoperability: A Historical Challenge.</h3><p>Interoperability has always been a challenge, no matter the industry segment. However, many industries have conquered interoperability in ways that benefit both the consumer and the business. One can perform an ATM cash withdrawal nearly anywhere on the globe. Cell phone text messaging works everywhere today and is seamless across mobile carriers. Certainly, healthcare has challenges that are orders of magnitude more complex than these challenges, however, models do exist for solving these problems.</p><h4>The Lack of Interoperability Hurts Everyone</h4><p>The benefits of health data interoperability are too many to list here, but we encounter missed opportunities almost every day. Recently, I was informed by a colleague about yet another missed opportunity for interoperability. As of October 15th, the State of Massachusetts now requires that prescribing doctors and pharmacists utilize the new Massachusetts Prescription Awareness Tool (<a href="http://www.mass.gov/eohhs/gov/departments/dph/programs/hcq/drug-control/pmp/">MassPAT</a>). MassPAT collects dispensing information about patients who are prescribed drugs that are commonly abused. The goal is to help combat the opioid crisis.</p><p>Combating drug abuse in our state is very important, however, this new requirement means more work for doctors. Doctors are reporting that this additional step (which is outside of their EMR workflow) is taking an additional 3 to 5 minutes per patient. Since some medical providers might prescribe for 20 patients per day — this additional work can easily consume an extra hour plus per workday.</p><p>Lack of interoperability is increasing healthcare provider frustration. Doctors are frustrated and angry that their EMRs don’t help them do their jobs efficiently. A <a href="http://jamanetwork.com/journals/jama/article-abstract/2545405">JAMA article</a> sums up provider opinions of EMRs: “There is building resentment against the shackles of the present EHR; every additional click inflicts a nick on physician’s morale.”</p><p>It didn’t need to be this way. If we had basic healthcare data interoperability, the provider’s system could automatically perform the necessary reporting and abuse detection on behalf of the doctor.</p><h4>Designing Workable Healthcare Standards is Hard Work</h4><p>Interoperability opportunities abound, and we have been working on healthcare data interoperability since computers were able to be networked together. HL7 recently celebrated its 30th Annual Plenary Meeting in Baltimore, Maryland. A lot of effort has gone into HL7 standards over those thirty years, and there have been many lessons learned along the way. The healthcare domain is not only deep, but it is also wide too, which presents a considerable design challenge in terms of standards development. HL7 Version 2, the most widely implemented clinical interoperability standard today suffers from the challenge of “if you have seen one v2 interface, you have seen one v2 interface.” V2 implementations require lots of handholding and interpretation and custom logic to function correctly. HL7 worked to address this shortcoming of V2 with V3 and the Reference Information Model (RIM) by specifying, comprehensively, the healthcare interoperability domain to a degree that made working with V3 very complex.</p><p>In a <a href="https://vimeo.com/108800764">video interview</a>, Wes Rishel, former chair of HL7, Wes summarizes the challenges of developing V3 and also working with it, leading to some key design decisions that would end up heavily influencing FHIR. Wes describes working on V3 as “… we would bring a 4’x6’ chart to a meeting with everything in 10 point type…” and “…we ended up with a set of protocols that were very difficult to understand unless you were one of the priests of the model.”</p><h4>The Benefits of a Fresh Approach</h4><p>Anyone who has built a reasonably complex product has come to understand the enormous benefits of starting over. By starting over, I’m not talking about starting from scratch. Sometimes, when building a product, it makes sense to simply declare: “You know what? For us to continue working with what we have built isn’t going to work long term. Let’s take everything we learned, bring the things along that worked, and leave the things that didn’t work behind.” These are often very refreshing events for product development teams. Engineering teams I have led where we have done a “start over” have accomplished incredible feats as a result, resulting in entirely new and better products in very short timeframes. It is cleansing, and freeing and spurs all sorts of energy and enthusiasm.</p><p>This is what is happening with FHIR right now. FHIR addresses many of the interoperability issues that have stifled progress in the industry in the past, and people are excited to be working with something new.</p><h3>What is FHIR and Why is it Better?</h3><p>FHIR is a standard built by developers, for developers.</p><h4>Target Support for Common Scenarios</h4><p>FHIR stands for Fast Healthcare Interoperability Resources and is a next-generation standards framework by HL7. The specification can be found at this web site: <a href="http://hl7.org/fhir">http://hl7.org/fhir</a>. The “resources” referenced in its name are the common building blocks that makeup healthcare, such as patients, medications, procedures, appointments, and claims. Participants in the standards process have agreed on these base definitions, which are straightforward and easy to understand. The FHIR development team has adopted the time-tested and engineer-approved 80% rule for resources: to only define and include concepts applicable to 80% of normal implementations. Adherence to the 80% rule is key to keeping the standard usable and not too overwhelming. At most, FHIR may eventually have around 150 resources as compared to thousands of unwieldy and difficult to recall concepts in other standards.</p><h4>FHIR Has Built-In Extensibility</h4><p>Ok, 80% is great — what about the remaining 20%? FHIR has an extensibility capability built into the standard that can only be described as beautiful (from this engineer’s perspective). Extensions are a normal part of working with FHIR. Extensions can be placed anywhere in the object model for FHIR, allowing incredible expressiveness in the standard.</p><p>Let’s have a look at one simple extension example. Below is an extension that describes an alias for an organization. An alias is something that not all systems might track, but at the same time, it is still very important for certain types of applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/672/1*vxupPPrO4La6KOhuanVdHg.png" /></figure><p>In this bit of XML, we see that there is a web URL and a valueString. At that URL, if you were to retrieve it with a browser, you will find a Structure Definition which describes the extension, again in XML format. This is a very important concept. What this means is that interoperability systems, as they are consuming resources, may encounter new extensions, and then have the means to understand them — immediately, on the fly. Healthcare systems that have the capability to then store an organization’s alias may then do so, or they may choose to simply ignore it.</p><p>FHIR’s extensibility design also means that extensions might be available publicly, encouraging re-use, thereby increasing interoperability. There are many extensions already defined at <a href="http://hl7.org/fhir/extensibility-registry.html">http://hl7.org/fhir/extensibility-registry.html</a>. This design also means that healthcare organizations may use FHIR internally, and add site-specific extensions simply by making a Structure Definition available on an internal intranet site.</p><h4>FHIR’s Focus Is On Implementers</h4><p>It is not uncommon in the tech industry to have a collection of vendors get together, spend months defining a new standard, and then… nothing happens. The failure of standards adoption can be traced to numerous different factors. Such as changing priorities in an industry. Or, because the standards don’t address real development challenges. Or because those who set the standards don’t actually have responsibility for developing shipping products.</p><p>Not so with FHIR.</p><p>I have been incredibly impressed with not only the enthusiasm of the FHIR community but also the level of talent and expertise of the people I have interacted with who are working on the standard itself. Why has FHIR succeeded? Firstly, the specification itself is written for implementers and is easy to read and navigate. HL7 has done some amazing work to bring Agile software development principles to the task of building the standard. The FHIR community, because they are the ones working on developing systems (hands on the keyboard — writing code) are the people who show up to connectathons and HL7 meetings. Prognosticators and theoreticians need not apply. Finally, the process that the FHIR team uses to promote portions of the standard follows a FHIR Maturity Model (FMM) with 5 levels of maturity. If a part of the standard isn’t implemented and tested by independent systems and isn’t eventually used in production systems, well, it remains at lower maturity levels. If, on the other hand, it is widely adopted and used, it marches up the FMM ladder.</p><h4>FHIR Is Free</h4><p>Free? Yes, free. The healthcare industry has a history of declaring standards, and then stifling their growth with limiting access, requiring fees and loading up on licensing requirements. The fact that FHIR is free is a huge step forward.</p><p>You might think this is a small incremental step forward, but it’s not. Think of it this way: what do you typically do when you encounter a web site that requires a fee before you can proceed? Most of us just click on another web site. It’s a barrier to information — it’s a hassle. In the real world of engineering products, that “little” barrier is actually much higher. The fee must be paid for by the employer (with necessary management approvals), and a legal review and approval is likely required as well. What is the likelihood that your average developer is going to go through that hassle, especially when they might be in the research phase of an effort and just learning?</p><p>The FHIR spec is entirely available online and is free to use. The FHIR specification has been licensed under the Creative Commons Public Domain License, a license that permits “You can copy, modify, distribute and perform the work, even for commercial purposes, all without asking permission.”</p><h4>FHIR Uses Modern Web Standards</h4><p>FHIR makes extensive use of web technologies such as XML, JSON, RESTful APIs, OAuth, and others, making FHIR a healthcare data standard that lives and breathes in today’s modern system architectures.</p><p>A word about RESTful APIs. FHIR servers expose their capabilities via a Representational State Transfer Application Programming Interface. Using modern web technologies, this is the same style and kind of APIs that Facebook, Twitter, and Google offer their services to connect with third party applications. These APIs are very easy to learn and use, and they power many of the cool things you see on the Internet.</p><h4>Human Readability Built In</h4><p>One key learning from prior interoperability efforts was that the narrative in a message was exceptionally important. Meaning, the human-readable portion of a message was critical to understanding its contents. For one, it acts as an import method for implementers to quickly ask “What is in here?” without having to parse the machine-readable contents of the message. Additionally (and most importantly), there is enormous value in notes that have been generated by human brains that come from knowledge and many years of experience that are required to practice medicine. The FHIR standard includes a narrative section that is required for each resource.</p><h4>Multiple Paradigm Support</h4><p>Many people approaching the standard for the first time understand that a FHIR server’s capabilities are RESTful, and they assume then that FHIR is limited in scope to REST-style applications. Not true!</p><p>FHIR also supports other styles of use or other paradigm types. A FHIR server may also be used to support a document paradigm, which is quite common in healthcare when one system wants to send over a collection of resources about a patient (for example, a referral to a specialist that involves many medications, diagnoses, and procedures that make up the patient’s history). FHIR also supports the messaging paradigm which is also quite common in healthcare. Messages occur, often based on real-world events. For example, an appointment to see a patient is made, or a patient is discharged from the hospital. Finally, FHIR also fully supports the <a href="http://hl7.org/fhir/services.html">Service Oriented Architecture (SOA)</a> paradigm.</p><h4>Wonderful Community</h4><p>FHIR’s strongest and most valuable asset is its community of like-minded healthcare professionals. I have had the pleasure to attend several HL7 meetings, and the people who participate in the standards process are top-notch. HL7 FHIR Connectathons, which are typically the Saturday and Sunday before a HL7 meeting is a sight to see, with over one hundred software developers attending. The FHIR community is exceptionally strong with not only Connectathons, but many publicly available test servers, <a href="http://chat.fhir.org/">chat groups</a>, and also active participation on <a href="http://stackoverflow.com/questions/tagged/hl7_fhir">StackOverflow</a>. In addition to the exceptional material on the HL7 FHIR web site, there are also <a href="http://wiki.hl7.org/index.php?title=FHIR_Support_Page">many great blogs</a> where you will find some fantastic information.</p><h3>In Summary</h3><p>This article introduced the background and some of the basics of FHIR. I didn’t yet touch on several other really interesting and compelling technical features of FHIR. I will leave those and other topics for future articles.</p><p>I started this article with a discussion of the nature of disruptive innovation in healthcare. There is no doubt that the nature of healthcare is changing — seemingly at once.</p><ul><li>Shared risk arrangements are requiring healthcare organizations to also share data in new and unique ways.</li><li>Patients are demanding better healthcare experiences, and they are demanding their data in mobile applications.</li><li>There is a movement toward transparency of information, especially in terms of what healthcare really costs, and why.</li><li>The market is also seeing increased use of data analytics to help all participants in healthcare make better decisions.</li></ul><p>FHIR will be a key new ingredient technology towards achieving these goals and enabling disruptive innovation in healthcare.</p><h4>Where do we go from here?</h4><p>If you work at a hospital, health plan, health IT vendor, or medical device manufacturer, FHIR is not something new that can be safely ignored. New technology initiatives should consider FHIR as a key architectural component of the solution. We will be seeing an increasing number of FHIR servers in production in the near future and the time to begin is now.</p><p>Steve Munini is Helios Software’s CEO and CTO. <a href="https://www.linkedin.com/in/smunini">Connect with Steve on LinkedIn</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fe99955%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fe99955&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/1125d29e7a4e978e8837e12623a6827d/href">https://medium.com/media/1125d29e7a4e978e8837e12623a6827d/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f55333058602" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helios-software/is-fhir-an-industry-disrupter-f55333058602">Is FHIR an Industry Disrupter?</a> was originally published in <a href="https://medium.com/helios-software">Helios Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>