<?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[Stories by David Michael Akers on Medium]]></title>
        <description><![CDATA[Stories by David Michael Akers on Medium]]></description>
        <link>https://medium.com/@dmalive?source=rss-6421a1bbaede------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*HjJaSi21CZPu9FX7.jpeg</url>
            <title>Stories by David Michael Akers on Medium</title>
            <link>https://medium.com/@dmalive?source=rss-6421a1bbaede------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 19:24:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dmalive/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Getting Better at Slack]]></title>
            <link>https://medium.com/@dmalive/getting-better-at-slack-8038d4fd6111?source=rss-6421a1bbaede------2</link>
            <guid isPermaLink="false">https://medium.com/p/8038d4fd6111</guid>
            <category><![CDATA[healthcare]]></category>
            <category><![CDATA[simplyvital-health]]></category>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[communication]]></category>
            <dc:creator><![CDATA[David Michael Akers]]></dc:creator>
            <pubDate>Tue, 25 Feb 2020 14:01:01 GMT</pubDate>
            <atom:updated>2020-02-25T14:01:01.626Z</atom:updated>
            <content:encoded><![CDATA[<p>As part of a fast-moving team, communication and being in sync with your team is critical to being able to meet expectations and deliver a quality product on time. At SimplyVital Health we use Slack, as one of the main tools in our team communication toolbox. <a href="https://slack.com/">Slack</a> is a chat application that works on desktop computers and mobile devices, making it very simply to stay connected with everyone on your team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/1*czVPAe88tWJiR85EufxEhQ.png" /><figcaption>photo courtesy of Slack.com</figcaption></figure><p>It’s very easy to start using Slack - you just invite your team, set up some channels and you’re done. Congratulations, you’re now ankle-wading in the great Slack ocean! But if you want to swim you’re going to have to dive into Slack’s many cool communication-enhancing features.</p><p>By taking part in many cross-functional teams at SimplyVital Health I’ve been able to observe how other team members use Slack, and as a result discovered many cool features of Slack that help improve communication. I thought I would take a few minutes to write about them, not because any of these are a big secret, but because one of our values at SimplyVital Health is — Better, Always — which I take as a personal challenge to always look for ways to improve.</p><p>So here are some things I’ve learned, am learning, and hope to get better at using:</p><h3>A Picture Paints a Thousand Words</h3><p>As an engineer I’m on the tech side of the teams I’m a part of — so when getting user feedback about a recently released feature, or a bug report for some newly occurring issue — I always have a bunch of follow-up questions. What browser was being used, what was the error message, what did the console report, what environment did this occur in, what time was it..</p><p>You get the point, there’s about a thousand and one questions I might be able to use to help me quickly identify a problem and replicate it. After a few of these back and forth interrogations — we found that a few screenshots of the web app and Javascript console was the fastest way to get the needed info in the programmers hands.</p><p>The same thing for new feature requests — especially if they are new user interface elements. A quick mockup using something simple like Google presentation can really jump-start the conversation and get us past a ton of hurdles to fully specing out a new feature.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/681/1*kT2-CRcxDdG_yU5By6Ykxw.png" /><figcaption>Take a few screenshots and uploading them using the attachment icon</figcaption></figure><p><a href="https://medium.com/u/41d8e286d83a">Kevin Cheli</a>, one of our front-end engineers has identified the image uploading feature as one of the easiest ways to share screenshots, and uses this to show the tech team errors he’s dealing with when integrating our APIs. This really saves us time when solving problems.</p><h3>Topic-Centered Channels</h3><p>We’ve structured our chat channels in many different ways over the last few years, but as <a href="https://medium.com/u/95b8aafd2dce">Camille Chicklis</a> and <a href="https://medium.com/u/d71aa3935f57">Kat Kuzmeskas</a> identified — making channels that are task or topic centered works best for improving the signal-to-noise ratio of Slack’s notifications. Doing channels that way make it easier to participate in important conversations while making it possible to suppress the noise of conversations that are not relevant to you at that time.</p><p>So big projects should get their own Slack channel — and those people that are part of that project will get the channel notifications for it — but if you’re not working on anything for that project at the moment you can mute the notifications for that channel without too much stress. This way you can selectively participate in conversations that are relevant to you at any given time. Slack even makes it possible to mute a channel for everything except explicit (@ ) mentions so you don’t miss something that someone is specifically leaving for you.</p><blockquote>The feature of Slack that I think improves team communication the most is the ability to see each other’s discussions in topic-centered channels (as opposed to everyone having separate side conversations). This helps me keep updated on what’s going on across projects. I like that I can also mute entire channels when the content is not relevant to me. To avoid being constantly pinged, I have notifications turned off for shared channels except if someone direct mentions me or uses a keyword I have flagged (including my name and project names). <a href="https://medium.com/u/95b8aafd2dce">Camille Chicklis</a></blockquote><p>Being able to reduce the noise of team communication is much harder if you just have member-based channels.</p><h3><strong>Slack’s Emojis are Good</strong></h3><p>Emojis aren’t afterthoughts — they are an important part of Slack’s ability to connect team members and provide feedback to each other. As our CEO <a href="https://medium.com/u/d71aa3935f57">Kat Kuzmeskas</a> says:</p><blockquote>I love the Emojis that I can add to comments by the team members. They&#39;re fun, but also a good way to show the team: I see you, I hear you, I’m on it. They&#39;re efficient.</blockquote><p>One of the issue of posting something in Slack is that you can’t immediately tell if someone has seen your message. A quick thumbs up, or eyeball emoji can let the poster know you have seen the message. This is especially great because it only adds a notification to the original poster — reducing the number of notifications everyone receives in that channel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/781/1*a8EJEKswMQmeO_PCAxeZ5g.png" /><figcaption>from Slack’s Engineering blog</figcaption></figure><p>Slack has a ton of emojis with enough nuance that you can often find the perfect response. But if that’s not enough — you can add your own emojis to round out the expressiveness of your emoji arsenal.</p><p>In our team we have added a whole collection of disco dancing emojis so we can throw dinosaur disco dance parties to celebrate team achievements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/594/1*hplKd9sQ8di6wFsbrhg-Zg.png" /></figure><p>That brings up the other thing emojis are really good at — keeping things a bit lighter. If the team is too serious and using a fun emoji isn’t ever going to be appropriate — then you’ll miss out on this cool Slack feature.</p><h3>Status, everyone has one!</h3><p>Slack has a status feature that let’s you give a brief description about what’s going on with you right now, and let’s you pick an icon to display — then on any message you add your team members can see your status icon and read your message. This makes it possible to let people know when you will be offline, or in a meeting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/555/1*Wu40wKzL-Y2l5AFZfu0g-Q.png" /><figcaption>You can have it clear automatically or manually remove it</figcaption></figure><p>You may have other ways to let people know you’re traveling — like a group Calendar but using Slack status will make it easier for people to access information they need when they try to communicate with you. <a href="https://medium.com/u/ea9798d67b29">Jayshaline Shethna</a> of SimplyVital Health puts it this way:</p><blockquote>“I absolutely love the status feature in Slack, Always helpful know and let others know of my status when communicating. It helps with expecting a response time as well as help me reevaluate my need to see if it is more important &amp; worthy of disturbing my teammate (especially if they’re heads down, in a meeting). “</blockquote><p>I’ve only recently started using status — and have been encouraged with the results. It can really help to make sure everyone understands what’s going on with everyone.</p><h3>Integrate Productivity Enhancing Apps</h3><p>Slack, for all it’s great points, wasn’t designed for managing tasks, tracking timelines, or scheduling business activity. When it comes to those kinds of tasks other apps can be integrated into Slack to make it possible to capture relevant communications shared in Slack.</p><p>Our CTO <a href="https://medium.com/u/db116b3c0c2c">Lucas Hendren</a>, has identified the <a href="https://medium.com/u/4fecc4c082c">Asana</a> app integration as the most valuable way to increase team communication. If someone adds a communication related to an existing task, we can create a task in Asana and assign it to a team member to better specify or follow up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*WWNRN4D8uBs2NwhxQfLb-Q.png" /><figcaption>Clicking on Create a Task — pushes this comment into Asana as a new task</figcaption></figure><p>With this level of integration there is very little stress when things that should be attached to a formal business task end up in a chat channel. Which makes it possible for people to use Slack without much stress, knowing that it’s easy to permanently capture messages and organize them as needed.</p><h3>Reminders</h3><p>Reminders are an indispensable way to make sure conversations that need more thought or action don’t get forgotten. If a team member post a link to an article or some resource and you don’t have time at that moment to review — just dropping a reminder on it for later in the week will make it easy to come back to it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/574/1*mIUOgL64EgdoRnfEK5-2wA.gif" /><figcaption>Reminders helps to make sure followup conversations happen</figcaption></figure><blockquote>“I’ve found myself using this feature a lot, especially when my teammates are busy or consumed in other important tasks, I set a reminder to send them the message at a later time. When the time comes, all I do is COPY + PASTE — This keeps me efficient.” <a href="https://medium.com/u/ea9798d67b29">Jayshaline Shethna</a> of SimplyVital Health</blockquote><p>Reminders can help keep longer conversations from being lost in the sea of quick chats.</p><h3>Wrap it up</h3><p>This article was not an exhaustive look at how you can use Slack features to improve team communication, but rather a quick look at ways we use Slack to be more responsive and thoughtful in small teams. At SimplyVital Health we use images, topic-centered channels, emojis, status updates, productive tool integration, and reminders to help us do communication better.</p><p>If you don’t take advantage of these features in your teams I hope you will try them out and let me know how it goes. Does your team use Slack differently? Give us your feedback in the comments below and let us know if these help you or what other features we should take a look at.</p><p><strong>To learn more about SimplyVital Health, follow us on </strong><a href="https://www.facebook.com/SimplyVitalHealth/"><strong>Facebook</strong></a><strong>, </strong><a href="https://www.twitter.com/SimplyVitalHQ"><strong>Twitter</strong></a><strong>, and </strong><a href="https://www.linkedin.com/company/simplyvital-health/?viewAsMember=true"><strong>LinkedIn</strong></a><strong>. We are hiring at </strong><a href="https://angel.co/simplyvital-health"><strong>AngelList</strong></a><strong>!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8038d4fd6111" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SimplyVital presents Nexus: Hello World]]></title>
            <link>https://medium.com/@dmalive/simplyvital-presents-nexus-hello-world-92f2718fedda?source=rss-6421a1bbaede------2</link>
            <guid isPermaLink="false">https://medium.com/p/92f2718fedda</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[simplyvital-health]]></category>
            <category><![CDATA[smart-contracts]]></category>
            <category><![CDATA[health]]></category>
            <dc:creator><![CDATA[David Michael Akers]]></dc:creator>
            <pubDate>Tue, 14 Jan 2020 14:01:02 GMT</pubDate>
            <atom:updated>2020-01-14T14:01:02.477Z</atom:updated>
            <content:encoded><![CDATA[<p>To developers, the world of blockchains and related technology can seem unfamiliar, and the task of assembling all the necessary components to embark upon one’s initial foray into decentralized application development can seem insurmountable. This is doubly true for those whose work does not intersect this field and find themselves with limited time for exploring new technology.</p><p>Our work, at SimplyVital Health, involves, in part, bringing decentralized technology to healthcare. In this pursuit we are developing Nexus, our healthcare-grade blockchain protocol, and some Nexus-backed healthcare applications. This article describes how to setup and deploy a “Hello World” smart contract on the Nexus development blockchain, using open source tools.</p><p>“Hello World”, is possibly the most popular program of all time, and usually used to quickly introduce programmers to a language’s syntax. In this article I’m using it, not to introduce syntax (though we will look at some Solidity), but to provide an introduction to some tools useful in Dapp (decentralized application) development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/876/1*_ds2Gv9kLvnuWOYGeEXaWQ.png" /></figure><p><em>To avoid the risk of skipping over a step and leaving the reader in a state of confusion concerning the path forward I will attempt to explicitly note the specific steps I took, with graphics if appropriate, and provide references when supplemental information is needed.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kUc_Z7PZ29LeVCD0N9o-Sw.png" /><figcaption>The HelloWorld folder is where our project files will go</figcaption></figure><h3>Step 1: Create a HelloWorld folder</h3><p>I started with a Projects directory, and created a HelloWorld folder inside it. The HelloWorld folder will hold all the files we need for this project so that when I’m done I can just remove this folder to clean up the code, blockchain, app, and tests. Incidentally, I’m running Ubuntu/Linux, however you should be able to do the same on Mac or Windows.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1011/1*dXYteN0K2KH-iF3uMZ65yQ.png" /><figcaption>git clone into your HelloWorld folder</figcaption></figure><h3>Step 2: Get the Nexus source code</h3><p>After I created the directory I opened a terminal (on your system you may refer to this as a command prompt or console), and inside the HelloWorld directory use Git to clone the source code for the Nexus development blockchain. You’ll need to source code to compile the blockchain client for your system.</p><pre>/Projects/HelloWorld$ git clone https://github.com/Health-Nexus/blockchain.git</pre><p><a href="https://git-scm.com/">Git</a></p><p>You will need to install Git and have an account on <a href="https://github.com/">github.com</a> as well request access to our private development blockchain repository. To get access to Nexus while our blockchain is development contact us at david[at]simplyvitalhealth[dot]com.</p><p>Cloning the repository will require you provide your Github credentials.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1011/1*ZwygH155vDv0yzOuyokFSA.png" /></figure><h3>Step 3: Compile the blockchain client</h3><p>From your terminal go into your newly cloned blockchain directory and compile the source code.</p><pre>/Projects/HelloWorld/blockchain$ make geth</pre><p>Once complete, you will see the “Done building.” followed by the directions needed to start the blockchain client. The go-ethereum project, on which Nexus is based, is written in Go. Depending on your system you may need to install the needed libraries to compile Go code. For more info on dependencies for your system please checkout the, <a href="https://geth.ethereum.org/docs/install-and-build/installing-geth#build-go-ethereum-from-source-code">Installing Geth Guide</a> from the go-ethereum project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C-nM-hmg1AFRQq-qD_IiXA.png" /><figcaption>Create a folder for the blockchain data</figcaption></figure><h3>Step 4: Create a data folder</h3><p>Now that I’ve compiled the blockchain client, I’m going to create a folder to hold all the data the blockchain will begin to sync once I start the blockchain. To do this I move back into my HelloWorld folder and create new folder called, rather uncreatively, data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FEgeFR4Epj2qGm0XZjKDmA.png" /><figcaption>Start the blockchain for the fist time</figcaption></figure><h3>Step 5: Run Nexus for the first time</h3><p>I opened a terminal window from inside the data directory and started Nexus for the first time to verify the blockchain client was working correctly.</p><pre>/Projects/HelloWorld/data$ &quot;/Projects/HelloWorld/blockchain/build/bin/geth&quot; --healthnexus --datadir ./ --port 7330</pre><p>Please look at the screen above to see that the flags need to be denoted with two subtraction characters (which Medium sometimes auto-replaces with a single longer character).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/822/1*5EXtGjMUZjQFNUq9S2GptA.png" /></figure><p>Starting the blockchain will automatically start syncing blocks. Once I verified it was working I stopped it, using Ctrl C. Now that I have a working blockchain client I want to create an account I can use to send transactions to the blockchain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/822/1*bFk_CiSy52Qedfc3S_N4CA.png" /><figcaption>create a new account</figcaption></figure><h3>Step 6: Create an Account</h3><p>In my terminal, still in the data folder, I use a modified version of the first command (adding “account new”) to the end to create a new account. This process will ask for a password, twice. It is very important to remember this password as it it irrecoverable should you lose it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/822/1*5UKVJSK1CDFxmEPojxzMgw.png" /></figure><p>Once you complete the process the public address is displayed. In this case my public address is 0xd79B9CCd05B505B69cE0237ddD6a5612D790106C.</p><p>Also note that what happens behind the scenes here is that a secret key file is created in the data/keystore directory. This will enable you to move your account to another machine (or wallet) if later you want to relocate your blockchain client.</p><p><strong>Now that you have your public address you can follow the instructions you received when you emailed for access to the code repository, to get some development crypto-currency. You will to fund your account before you will be able to deploy transactions.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8_WQDkWZCGodJCMVH4KlEQ.png" /><figcaption>create a password.txt file</figcaption></figure><h3>Step 7: Create a password.txt file</h3><p>At this point I want to make it clear that I am setting up a development blockchain, that uses free development crypto-currency. Because this is strictly a development blockchain we will not overly concern ourselves with securing our account password, network, or implementing practices that improve security at the expense of introducing unnecessary complexity.</p><p>In this I go into the HelloWorld/data directory and create a new file. You can call it whatever you like, I chose password.txt because that’s all this file will contain. Inside the file I place the password I used when I created my new account — just the password, no spaces or newline characters.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*0WNmFBdoA7smekyJPA4c3g.png" /><figcaption>start Nexus again, this time with your unlocked account</figcaption></figure><h3>Step 8: Start Nexus with your unlocked account</h3><p>Now that my password file is created I can start the blockchain again, this time with my account unlocked. In this step not only will I be unlocking my account, but we will be enabling RPC, which will allow us to send transactions from other applications running locally.</p><pre>/Projects/HelloWorld/data$ &quot;/Projects/HelloWorld/blockchain/build/bin/geth&quot; --healthnexus --datadir ./ --port 7330 --unlock &quot;0xd79B9CCd05B505B69cE0237ddD6a5612D790106C&quot; --password ./password.txt --rpc --rpcapi &quot;eth,web3,personal,net&quot; --allow-insecure-unlock</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*phokcqMDFdXBKF5YmVRCbQ.png" /></figure><p>Once I started my blockchain again, I was to see that it correctly “Unlocked account” and it created the ‘HTTP’ endpoint at 127.00.0.1 (localhost default).</p><p>Again, I want to stress, this is generally an insecure way of running a blockchain and us recommend only for this limited developmental mode.</p><h3>Step 9: Install Truffle</h3><p><a href="https://www.trufflesuite.com/truffle">Truffle | Truffle Suite</a></p><p>Truffle is a very useful framework for developing decentralized applications in the Ethereum ecosystem. Because Nexus is based on Ethereum, we are able to leverage the Truffle open source framework to develop Nexus applications.</p><p>Opening a new terminal (leaving the existing running Nexus in the background), and changing to the HelloWorld folder I installed truffle using:</p><pre>/Projects/HelloWorld$ npm install -g truffle</pre><p>You can visit the <a href="https://www.trufflesuite.com/">Truffle website</a> to find out more about the entire suite of open source tools available to help you develop on Nexus. Truffle does require <a href="https://nodejs.org/en/">Node.js</a>, so please install that first if you don’t already have it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vjfb_KTegWCdRSzHVV5FCA.png" /><figcaption>inside HelloWorld create an app folder</figcaption></figure><h3>Step 10: Create an app folder</h3><p>Inside the HelloWorld folder I created another folder name “app”. This is where we will download an Hello World project from Truffle to deploy on Nexus.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*sm-2GCElOvzhJgiaznuD6g.png" /><figcaption>Let’s use a truffle box to get started</figcaption></figure><h3>Step 11: Get a basic Hello World app</h3><p>Back in my terminal window, inside the new app directory, I use the truffle unbox command to download and install a pre-configured project.</p><pre>/Projects/HelloWorld/app$ truffle unbox azure-hello-blockchain</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*uiMa-S4jWwXsEbkniCucOA.png" /></figure><p>Truffle Boxes are the easiest way to get started. They are example applications that range from the simple smart contracts with integrated testing, to full-featured dapps (decentralized applications) implemented in the most popular frameworks.</p><p>Browsing the Truffle box page I was able to discover three “Hello World” boxes that implemented a simple sender/response dapp using a smart contract. I picked this one because it provided everything we need to compile, migrate, and test our dapp without any unwanted boilerplate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/858/1*s6t6-8brYfNV3s_lB2pphg.png" /></figure><h3>Step 12: Update truffle.js</h3><p>The truffle unboxing completes with a new truffle.js file in the app folder you created. Open the truffle.js and modify that file as follows:</p><pre>module.exports = {<br>  // See &lt;<a href="http://truffleframework.com/docs/advanced/configuration">http://truffleframework.com/docs/advanced/configuration</a>&gt;<br>  // to customize your Truffle configuration!<br>  networks: {<br>    nexus: {<br>      host: &quot;127.0.0.1&quot;,<br>      port: 8545,<br>      network_id: &quot;*&quot;<br>    }<br>  },<br>  compilers: {<br>    solc: {<br>      version: &quot;0.4.23&quot;,<br>    },<br>  }<br>};</pre><p>Here we add a new network, nexus, and specify the solc version we need for this box. That saved, now we can move on to compile the smart contracts.</p><h3>Step 13: Review the smart contracts</h3><p>The two smart contracts included with the truffle box are HelloBlockchain.sol and Migrations.sol. Migrations is part of the truffle’s life cycle management where it will keep track of smart contract revisions and selective enable migrating changed smart contracts as needed. The HelloBlockchain smart contract is a fairly simple contract that stores some strings and allows you to set a request message (as the contract owner — Requestor in this case), and sent a response message.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1008/1*M_o93SCr6qXBJdZKGCg0hw.png" /><figcaption>Overly complicated for Hello World</figcaption></figure><p>This let’s us put our “Hello, World!” into the blockchain and read it back and allows someone to respond in kind.</p><p>For what we want it to do it’s overly complicated, but that also gives us some space to explore more advanced concepts in Solidity, such as inheritance and the design choices behind using (or not) modifiers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*B8_dmTiHE-Nt0siK2eCfpA.png" /><figcaption>truffle compile</figcaption></figure><h3>Step 14: Compile the smart contracts</h3><p>Truffle has some useful tools that makes developing smart contracts easier. Smart contracts in truffle are written in Solidity, the most popular smart-contract language for Ethereum.</p><p>Inside my terminal window, while in the app folder, I use the truffle compile command to compile the HelloBlockchain and Migrations smart contract in preparation for deploying them.</p><pre>/Projects/HelloWorld/app? truffle compile</pre><blockquote>While compiling you may see some compilation warnings. Solidity has changed since these smart contracts were written, making this syntax obsolete. However, it should still compile if you specified the solc version in your truffle.js as indicated above<em>.</em></blockquote><p>Now compiled, I could use another of truffle’s commands (migrate) to deploy them to Nexus. However, I want to deploy them and run the test all at once.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*zIICTUetjNlWTvH3YuQDxw.png" /></figure><h3>Step 15: Testing our smart contract</h3><p>Again, from the same terminal window we compiled our smart contracts run the tests using truffle test.</p><pre>/Projects/HelloWorld/app$ truffle test --network nexus</pre><p>Using the network flag in our truffle command told Truffle to use the network we configured when we modified our truffle.js earlier. Truffle will first start by looking to see if the contract needed to be compiled again (or first if you never compiled then), then quickly move onto running the test in the app/test folder.</p><p>A quick look shows that it’s deploying the HelloBlockchain to the blockchain and checking for the initial state to be as expected before setting our request message to Hello World!</p><p>And that’s how you deploy a simple smart contract to Nexus using popular open source tools. <em>Note: If you try this before receiving the development crypto currency on your account, then this will fail to work and you may receive unhelpful warnings about “exeeding gas limit”.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/903/1*hCUcrLj1s192ixBHBwwP4Q.png" /><figcaption>truffle migrate</figcaption></figure><p>If you’ve gotten this far you can now use truffle migrate --network nexus to deploy the contracts and get back the contract address so you can interact with it independently or using other tools.</p><pre>truffle migrate --network nexus</pre><h3>And We’re Done</h3><p>So I deployed the smart contract to Nexus and used it to update the Response Text stored on the blockchain to “Hello World”, which is enough to get you started as you explore the tools for Dapp development.</p><p>Here’s what I was able to do in the process:</p><ul><li>Build the Nexus blockchain client</li><li>Create a new account on the Nexus development blockchain</li><li>Start the Nexus blockchain for development</li><li>Use Truffle to deploy a smart contract to Nexus</li></ul><p>What I wasn’t able to fully explore, because of length constraints, was the built-in testing for Truffle, how to extend testing using more familiar Javascript testing frameworks, or how using a pure development blockchain like Ganache can greatly increase your efficiency in dapp development.</p><p>I used Truffle Boxes partially with the hope that you would poke around there a bit and see what other starter projects could provide inspiration for your own dapps.</p><p>If you’re interested in developing healthcare related applications that leverage decentralized technology, contact us at SimplyVital Health or at our following sites. We are also hiring!</p><p><a href="https://angel.co/company/simplyvital-health">https://angel.co/company/simplyvital-health</a></p><p><a href="https://www.simplyvitalhealth.com/">https://www.simplyvitalhealth.com/</a></p><p><a href="https://www.facebook.com/SimplyVitalHealth/">https://www.facebook.com/SimplyVitalHealth/</a></p><p>Please contribute to the discussion in the comments below. Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92f2718fedda" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to participate in the Health Nexus Token Generation Event]]></title>
            <link>https://medium.com/@dmalive/how-to-participate-in-the-health-nexus-token-generation-event-18e84e6c4fc1?source=rss-6421a1bbaede------2</link>
            <guid isPermaLink="false">https://medium.com/p/18e84e6c4fc1</guid>
            <category><![CDATA[healthcare]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[token]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[David Michael Akers]]></dc:creator>
            <pubDate>Wed, 16 May 2018 20:06:22 GMT</pubDate>
            <atom:updated>2018-05-17T15:21:26.966Z</atom:updated>
            <content:encoded><![CDATA[<p>The Health Nexus token generation event will begin on May 21st, 2018. If you have completed our interest survey and the KYC process you will be able to participate. If you haven’t done that yet, head over to our <a href="https://token.simplyvitalhealth.com/">token site</a>. To get started register for the wait list or if you are already registered then login and find the interest survey on the secure dashboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/817/1*Ax3OIk2EFBLe7KvXTydKUw.png" /><figcaption>Get started by completing the Interest Survey.</figcaption></figure><p>Health Nexus is a secure new blockchain where patient data and healthcare professionals can safely interact.</p><p>Our token generation event will give those members of our community with an immediate interest in our <a href="https://medium.com/simplyvital/lets-hit-the-ground-running-with-health-nexus-5c25df21c56d">opensource Key Pair system</a> the ability to access and support that utility.</p><p>Once Health Nexus is commercially available the tokens will be voluntarily exchangeable (1 for 1) with health cash , the transactional currency of Health Nexus.</p><p>This article will provide an overview of the contribution process to prepare those community members who are selected to participate.</p><h3>Contribution Overview and Getting Started</h3><p>There are three steps to the contribution process:</p><ul><li>Verifying your wallet address</li><li>Contributing Ether</li><li>Confirming your token balance</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/843/1*rhn0kIYhLI_-vO5QXrwVLQ.png" /><figcaption>Get stated by using the “Contribute” button.</figcaption></figure><p>To get started go to our website: <a href="https://token.simplyvitalhealth.com/">https://token.simplyvitalhealth.com</a> and login by using the “Login” button at the top. Those approved to participate will notice a blue “Contribute” button on the dashboard. Use the button to begin the process.</p><p>The remainder of this article will cover each of these steps in detail beginning with verifying your wallet address.</p><h3>Verifying your wallet address</h3><p>To participate you will first have to verify your Ethereum wallet address, that it is a correct Ethereum address, that it belongs to you, and that it is a token compatible address.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/769/1*Wn_4mgjd9bI9b-aIINbLbw.png" /><figcaption>When you complete this process you will see your Wallet address here. You can change your wallet address here if needed.</figcaption></figure><p>You can change your wallet address during this step, but please note — once you check both checkboxes and click next you will be unable to change your wallet address afterwards. Be sure your wallet address is token compatible before proceeding.</p><blockquote><strong><em>Your eth wallet on Coinbase is not token compatible: do not attempt to send any ether from Coinbase directly!</em></strong></blockquote><p>If you are unsure if your wallet is ERC20 token compatible here’s are the most popular token compatible wallets you can use:</p><ul><li><a href="https://www.myetherwallet.com/">MyEtherWallet</a> (no download needed)</li><li><a href="https://metamask.io/">MetaMask </a>(Firefox and Chrome browser addon)</li><li><a href="https://github.com/ethereum/mist/releases">Mist</a> (Desktop App)</li><li><a href="https://token.im/">imToken</a> (iPhone &amp; Android)</li></ul><p>All of these wallets work well, but it is worth mentioning that if you are using using Chrome or Firefox as your web browser, MetaMask makes creating a token compatible wallet and funding it with ether very easy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/759/1*bRVJfGRUoJGnNmc9w_syAg.png" /><figcaption>I’ve verified that I will contribute only from this address, and that this is a token compatible wallet.</figcaption></figure><p>Note: You will have to send your Ether from the same address where your tokens will be distributed — your token compatible wallet.</p><p>Once you complete this process we will verify your Ethereum address. It will look like this.</p><p>Use the “Next” button to proceed to the next step.</p><h3>Contributing Ether</h3><p>As you will be using your token wallet to contribute to the Health Nexus token generation event we have provided all the information you need to complete a successful transaction on the contribute page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*fenJ8iZci-nzVCIpwXd_vQ.png" /><figcaption>Tip: You can use the copy buttons to the left of the fields to quickly copy them to your clipboard.</figcaption></figure><blockquote><strong>Do not use the information provided in the included screenshots, those are just examples — get your data directly from the secure dashboard.</strong></blockquote><p>With your wallet, create an Ethereum transaction using the details provided on the contribute page. You need to copy the entire field (copy buttons are provided to make this easy). These are required to successfully contribute:</p><ul><li>Address</li><li>Data</li><li>Amount Eth</li></ul><p>The minimum contribution for the token generation event is .10 Ether. We have also provided recommended values for gas limit, and gas price.</p><p><strong>Trouble To Avoid</strong></p><ul><li>Transactions for less than the minimum of .10 will fail.</li><li>Transactions that do not come from your verified Ethereum address will fail. Only use the wallet address you verified in the previous step.</li><li>Transactions that do not include all the Data field will fail.</li></ul><p>Failed transactions will return any ether you contributed but will consume all the gas you provided.</p><p>After your transaction is confirmed you will be able to verify your token distribution. Network conditions can impact the time it takes to confirm transactions.</p><h3>Confirm Your Token Balance</h3><p>After the transaction is confirmed you will be able to verify the token distribution using two methods. These two methods are described in the Check Tokens step as shown.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/789/1*zRxzYYPE_ALnvFeMqH78SA.png" /><figcaption>This is sample data provided for this article. Get your data directly from the secure dashboard.</figcaption></figure><p>Depending on network conditions you may have to wait some time before seeing your token balance. Once you verified your token balance you will have successfully participated in the Health Nexus token generation event.</p><p>You may have questions about these instructions or some part of the process as you are going through it. Find us on <a href="https://t.me/HealthNexus">telegram</a> or <a href="https://discordapp.com/invite/2Wfg524">discord</a> and we will help answer your questions.</p><p>All of our token contracts are opensource, audited by Hosho, and available in our github repo: <a href="https://github.com/Health-Nexus/healthcashtoken">https://github.com/Health-Nexus/healthcashtoken</a></p><h3>About SimplyVital Health</h3><p>SimplyVital Health is making decentralized technology accessible to the healthcare industry by creating Health Nexus, a healthcare-safe opensource blockchain.</p><p><a href="https://www.simplyvitalhealth.com/">https://www.simplyvitalhealth.com/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18e84e6c4fc1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Health Nexus and Trustless Systems]]></title>
            <link>https://medium.com/@dmalive/health-nexus-and-trustless-systems-afcfe4b72b31?source=rss-6421a1bbaede------2</link>
            <guid isPermaLink="false">https://medium.com/p/afcfe4b72b31</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[token-sale]]></category>
            <category><![CDATA[healthcare]]></category>
            <dc:creator><![CDATA[David Michael Akers]]></dc:creator>
            <pubDate>Tue, 13 Mar 2018 12:18:27 GMT</pubDate>
            <atom:updated>2019-02-13T16:07:14.531Z</atom:updated>
            <content:encoded><![CDATA[<p>You don’t know me and I don’t know you, yet we live and breathe on the same planet at the same time. If you drive, as I do, we may even pass each other on the road as we go from place to place. I know I pass a great many people when I’m driving around, people I don’t know. And yet I trust them to operate heavy vehicles traveling at dangerous velocities just meters away from me? Do they trust me too, even though they don’t know me?</p><p>Not really.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XfKwT_vwlnqPW_OtT0Qz2g.jpeg" /><figcaption>Do we really trust anonymous drivers?</figcaption></figure><h3>Trustless Systems</h3><p>Our system of self-directed road travel is made possible by a shared trust, but it’s not trust in anonymous drivers. There’s something more fundamental and reliable that undergirds this communal trust; we trust the system, and I don’t just mean we trust our local municipalities to filter out unsafe drivers.</p><p>Instinctively we understand that driving is a self-filtering activity. People that can’t drive safely either learn quickly or stop trying. That’s why new drivers are among the most dangerous drivers, not just because they are learning new skills, but also because the system hasn’t had enough time to filter them out. In time they will be tested, not just because we have driving instructors that test people prior to licencing, but because every trip in a car is a test, every stop, every turn, every choice: all pass-or-fail tests.</p><p>It’s not a perfect system but however imperfect the system is, that people are comfortable driving on roads alongside anonymous drivers demonstrates the value we place on <strong>trustless systems</strong> — systems that work consistently and predictably without regard to the individual choices or actions of others.</p><h3>Trust-based Systems</h3><p>I used that example because I think it’s something that’s very familiar to most people — even if not entirely obvious. The alternative, trust-based systems, or systems that only work when trusted parties choose to honor their agreements, are also familiar to most people.</p><p>In computer technology any centralized systems are trust-based. Take any social media platform as an example: you sign up, you create a profile, you gather followers, you build an online relationship with your followers. On that platform you are trusting them to relay your messages to your followers in an accurate and timely fashion.</p><p>You will likely be happy with the platform as long as you believe they are honoring their agreements. But here’s the thing, you have to trust them to do it. At any time they might decide to stop sending out your messages, or only send them out to some followers and not others, or only send them out a week later, or edit your content etc. You have to trust them.</p><p>But what if you didn’t? What if you could achieve the same goal — sending your message to your followers — without trusting an intermediary to relay it for you?</p><blockquote>What we’re finding is given the choice <strong>people overwhelmingly prefer systems that require less trust</strong>.</blockquote><h3>Health Nexus</h3><p>Blockchains, like Health Nexus, enable trustless computing systems: systems that work consistently and predictably without regard to the individual choices or actions of others. This is done through immutable smart-contracts stored on the blockchain.</p><p>To build a trustless system on Health Nexus you would:</p><ul><li>Program your smart contracts</li><li>Have them audited for security and compliance by a reputable third party.</li><li>Publish the audit results along with your unmodified source code.</li><li>Deploy your smart contract to the Health Nexus blockchain.</li><li>Provide proof your deployed contracts match your audited opensource code. (Anyone with the contract address and source code can do this for themselves)</li></ul><p>Once deployed smart contract code can not be modified and will continue to operate as designed forever.</p><p>There are seemingly unlimited uses for trustless systems in healthcare. Checkout <a href="https://medium.com/simplyvital/decentralized-technology-and-healthcare-c01f979d4b0">this article</a> for practical systems that will bring value on Health Nexus. Once these systems become available will consumers and healthcare providers prefer them to existing trust-based systems? We think so.</p><p><em>Systems will evolve towards trustlessness as decentralized technology improves and our understanding of the application of it matures.</em></p><p>If you have questions about this, Health Nexus, or getting started find us in our <a href="https://t.me/HealthNexus">telegram group</a>. If you are interested in partnering with us to create dapps on Health Nexus or want to receive developer updates or training material please <a href="https://goo.gl/forms/dFy5PWvmOJMlv6P23">register your interest here</a>.</p><h3>About SimplyVital Health</h3><p>SimplyVital Health is making decentralized technology accessible to the healthcare industry by creating Health Nexus, a healthcare-safe opensource blockchain.</p><p><a href="https://www.simplyvitalhealth.com/">https://www.simplyvitalhealth.com/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=afcfe4b72b31" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Developing Healthcare Dapps for Health Nexus Today]]></title>
            <link>https://medium.com/@dmalive/developing-healthcare-dapps-for-health-nexus-today-1945d4e84cd2?source=rss-6421a1bbaede------2</link>
            <guid isPermaLink="false">https://medium.com/p/1945d4e84cd2</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[token-sale]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[healthcare]]></category>
            <dc:creator><![CDATA[David Michael Akers]]></dc:creator>
            <pubDate>Tue, 06 Mar 2018 13:25:44 GMT</pubDate>
            <atom:updated>2018-03-06T13:25:44.253Z</atom:updated>
            <content:encoded><![CDATA[<p>In one of my recent articles I explained how to <a href="https://medium.com/simplyvital/using-mist-with-health-nexus-e858a576d574">get started using Health Nexus</a> with the Mist client. In this article I wanted to expand on that to discuss developing decentralized applications (dapps) on Health Nexus.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*LXZU0K_5f6D7ayImc1QTBw.jpeg" /></figure><p>Health Nexus is a fork of Ethereum with adaptions that make it safe for use by the healthcare industry. The Health Nexus protocol is HIPPA compatible and adapted for use with today’s healthcare technology. To get more details on what we are changing check out <a href="https://medium.com/simplyvital/what-makes-health-nexus-different-than-ethereum-8cf992f901a">this article.</a></p><p>The first phase of Health Nexus is implemented on top of Ethereum and will be going live shortly. In our first phase we introduce our DRS protocol which enables decentralized management of data services and permissions. The Health Nexus DRS smart contract is available right now on the Rinkeby test network.</p><h3><strong>Why chose Ethereum?</strong></h3><p>People ask why we chose Ethereum as the core of the Health Nexus project. Lucas Hendren, the CTO of SimplyVital Health, expresses this in the article <a href="https://medium.com/simplyvital/why-ethereum-core-instead-of-3be018861337"><strong><em>Why Ethereum core instead of _________?</em></strong></a></p><blockquote>“Ethereum has been extensively tested compared to most other blockchains. Ethereum has dealt with numerous issues over the years thus the community has learned from each other — and continues to develop better standards and higher quality smart contracts.”</blockquote><h3><strong>Developers. Developers. Developers.</strong></h3><p>When it comes to developing dapps one of the largest obstacles to getting started is the relative scarcity of blockchain developers.</p><blockquote>“The job of developing <a href="https://www.computerworld.com/article/3191077/security/what-is-blockchain-the-most-disruptive-tech-in-decades.html?nsdr=true">blockchain distributed ledgers</a> for businesses was recently ranked <a href="https://www.computerworld.com/article/3235972/it-careers/blockchain-jobs-continue-to-explode-offer-salary-premiums.html">second among the top 20 fastest-growing job skills</a>, and postings for workers with those skills grew more than 200% last year.” — <a href="https://www.computerworld.com/article/3258848/blockchain/the-blockchain-market-is-hot-heres-how-to-learn-the-skills-for-it.html">Lucas Mearian</a></blockquote><p>While companies are <a href="https://hugethinking.com/post/3-ways-organizations-are-dealing-with-the-blockchain-developer-shortage/">finding ways to overcome these challenges</a>, the Health Nexus team wanted to make developing healthcare dapps as friction free as possible.</p><p>The Ethereum development community is by far the largest, most supported, and experienced group of developers working with blockchain technology today and this trend is likely to continue for many years.</p><p>By creating Health Nexus from Ethereum, Ethereum developers will have no difficulty creating Health Nexus dapps. The blockchains share the same basic programming language and similar tooling.</p><h3>Get started today</h3><p>Developers can start creating Health Nexus dapps today. Porting those dapps to the Health Nexus blockchain from Ethereum will require almost no changes in the underlying code. To utilize the Health Nexus DRS protocol developers can review our code and documentation in the <a href="https://github.com/Health-Nexus/drs">github repo</a>.</p><p>In the immediate future our DRS protocol will go live on the Ethereum main network, we will publish an opensource data gatekeeper and dapp interface for the DRS protocol, and will begin work on creating a training program for software developers looking to get started developing on Health Nexus.</p><p>If you have questions about this, Health Nexus, or getting started find us in our <a href="https://t.me/HealthNexus">telegram group</a>. If you are interested in partnering with us to create dapps on Health Nexus or want to receive developer updates or training material please <a href="https://goo.gl/forms/dFy5PWvmOJMlv6P23">register your interest here</a>.</p><h3>About SimplyVital Health</h3><p>SimplyVital Health is making decentralized technology accessible to the healthcare industry by creating Health Nexus, a healthcare-safe opensource blockchain.</p><p><a href="https://www.simplyvitalhealth.com/">https://www.simplyvitalhealth.com/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1945d4e84cd2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Mist with Health Nexus]]></title>
            <link>https://medium.com/@dmalive/using-mist-with-health-nexus-e858a576d574?source=rss-6421a1bbaede------2</link>
            <guid isPermaLink="false">https://medium.com/p/e858a576d574</guid>
            <category><![CDATA[token-sale]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[healthcare]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[David Michael Akers]]></dc:creator>
            <pubDate>Wed, 21 Feb 2018 14:13:51 GMT</pubDate>
            <atom:updated>2018-08-09T15:43:17.862Z</atom:updated>
            <content:encoded><![CDATA[<p>In this article I’m going to explain how to access the phase one utility of our Health Nexus project using the Mist Ethereum browser. Most of the utility provided by our smart contracts are for creating, permissioning, and managing a decentralized record service (DRS) of your own. This article is intended for more technical users interested in getting started testing, developing, and using our smart contracts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0OfypiwT5dgNPbJuYXD6hg.png" /></figure><blockquote>Before we get started, you’re going to need the <a href="https://github.com/ethereum/mist/releases">Mist Client</a> and access to the <a href="https://www.rinkeby.io/#stats">Rinkeby </a>test network. Getting these installed and configured are beyond the scope of this article, but instructions can be found <a href="https://gist.github.com/cryptogoth/10a98e8078cfd69f7ca892ddbdcf26bc">here</a> and <a href="https://www.rinkeby.io/#mist">here.</a> Once you have these up and running you are ready to begin.</blockquote><h3>Table of Contents</h3><ol><li><a href="https://medium.com/simplyvital/using-mist-with-health-nexus-e858a576d574#cb52"><strong>Overview </strong></a><br>High-level overview of the Health Nexus DRS smart contract and the basic terminology used in this article.</li><li><a href="https://medium.com/simplyvital/using-mist-with-health-nexus-e858a576d574#a725"><strong>Setting up Health Nexus DRS in Mist</strong></a><strong><br></strong>How to add the Rinkeby Health Nexus DRS contract to your Mist client</li><li><a href="https://medium.com/simplyvital/using-mist-with-health-nexus-e858a576d574#0adf"><strong>Services</strong></a><br>Overview of the service struct in Health Nexus DRS</li><li><a href="https://medium.com/simplyvital/using-mist-with-health-nexus-e858a576d574#66df"><strong>Create a Service</strong></a><br>Create a service using a data access endpoint</li><li><a href="https://medium.com/simplyvital/using-mist-with-health-nexus-e858a576d574#b6e0"><strong>Sharing a Service</strong></a><br>You can share a service to have different accounts using the same service, or to delegate responsibility.</li><li><a href="https://medium.com/simplyvital/using-mist-with-health-nexus-e858a576d574#8627"><strong>Recovering a Service</strong></a><br>If you lose your service hash here’s how to recover it.</li><li><a href="https://medium.com/simplyvital/using-mist-with-health-nexus-e858a576d574#9f8d"><strong>Service Related Functions</strong></a><br>Functions to get the service endpoint or update the service endpoint.</li><li><a href="https://medium.com/simplyvital/using-mist-with-health-nexus-e858a576d574#82e4"><strong>Keys</strong></a><br>An overview of keys in Health Nexus DRS.</li><li><a href="https://medium.com/simplyvital/using-mist-with-health-nexus-e858a576d574#7943"><strong>Creating &amp; Issuing</strong></a><br>Create keys to permission, sell or issue them directly to accounts.</li><li><a href="https://medium.com/simplyvital/using-mist-with-health-nexus-e858a576d574#fdfb"><strong>Permissions</strong></a><br>Service owners can enable share, trade, and sell permissions on keys.</li><li><a href="https://medium.com/simplyvital/using-mist-with-health-nexus-e858a576d574#521c"><strong>Sharing</strong></a><br>Keys enabled for sharing can be shared with multiple accounts.</li><li><a href="https://medium.com/simplyvital/using-mist-with-health-nexus-e858a576d574#7dd9"><strong>Selling</strong></a><br>Key owners can offer keys for sale if selling is enabled.</li><li><a href="https://medium.com/simplyvital/using-mist-with-health-nexus-e858a576d574#0788"><strong>Trading</strong></a><br>Keys enabled for trading can be offered for specific trades.</li><li><a href="https://medium.com/simplyvital/using-mist-with-health-nexus-e858a576d574#59b0"><strong>Recovering a Key</strong></a><br>Learn how to recover your key hash if you lost it.</li><li><a href="https://medium.com/simplyvital/using-mist-with-health-nexus-e858a576d574#6752"><strong>Key Related Functions</strong></a><br>Get the service endpoint from the key hash.</li><li><a href="https://medium.com/simplyvital/using-mist-with-health-nexus-e858a576d574#ea13"><strong>Logging &amp; Messaging</strong></a><strong><br></strong>Service and key owners can create auditable messages on the blockchain.</li><li><a href="https://medium.com/simplyvital/using-mist-with-health-nexus-e858a576d574#003e"><strong>Using Health Cash (HLTH)</strong></a><br>You have to explicitly approve the Health Nexus DRS contract to use your health cash.</li></ol><h3>Overview</h3><p>The first phase of Health Nexus is designed to give early access to the key/pair protocol change we are implementing on the Health Nexus blockchain. These keys are used to secure, blockchain-based identities and system of on-chain permissions to enable collaborative access to off-chain data.</p><p>The Health Nexus DRS contract is designed to support a variety of DRS implementations concurrently. This is accomplished, in part, by a simplified on-chain <strong>service</strong> structure which enables the registration of endpoint urls and creates an immutable record of that service and associated owner. Service owners can then create and issue <strong>keys</strong> for that service.</p><p>Keys are unique, ownable records that can be used to establish the identity of valid off-chain service consumers through a side-channel process that requires verifying messages signed by the key owner. Services can permission keys to extend the default functionality to enable trading, sharing, and selling.</p><p>A service owner can allow keys to be purchased using Health Cash (HLTH).</p><h3><strong>Setting up Health Nexus DRS in Mist</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/338/1*2aM2JPeVcUGenS3-6YXNqg.png" /><figcaption>From the Contracts tab, click Watch Contract</figcaption></figure><p>To start using the Health Nexus DRS you will need to add the contract to your Mist client. This is done by clicking “Watch Contract”, and adding the Rinkeby DRS contract.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/452/1*uA3ZVJjB-udNP4Y7mMPkog.png" /></figure><p>Enter the following information to correctly add the Rinkeby Health Nexus DRS contract:</p><p><strong>Contract Address:</strong> 0xF54a6dE3F1FE973c73BfBb9a5B35D3695Ea277D2</p><p><strong>Contract Name:</strong> Rinkeby Health Nexus DRS (You can put whatever here, and change it later. I shortened it to Rinkeby DRS to keep the name on one line)</p><p><strong>JSON Interface:</strong> Copy and paste the full <a href="https://github.com/Health-Nexus/drs/blob/master/developer.abi"><em>developer.abi</em></a> into this field.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/817/1*L_UITxQHe1pCFAsLHs45Rw.png" /></figure><p>Once you complete this process you should see the contract in your contracts list. Clicking on it will give you access to all the functions you need to read and write to the contract.</p><p>On the left side of the interface are all the READ operations. These can be used freely as reading from the Ethereum blockchain does not cost any Ether.</p><p>On the right site of the contract interface are all the WRITE functions. These will modify the state of the contract in some way and will require a transaction and cost Ether.</p><h4>Using READ and WRITE functions together will give you access to all the utility you need to create and manage your own data gateway service.</h4><h3>Services</h3><p>At the core of the Health Nexus DRS is the immutable record of registered services, the ownership, and the authority service-owners have over the keys they create and issue. Any account is free to create services and issue keys using the Health Nexus DRS contract.</p><p>On the blockchain, a service is represented by the cryptographic hash of its endpoint and creator and stored as a struct containing the endpoint and the primary owner in the services mapping.</p><h3>Create a Service</h3><p>Services are uniquely identified by the cryptographic hash of their endpoint URL and owner. To create a service, pass the Create Service function a URL. If that service has not already been created a new one will be added.</p><p><strong>Note: You will need the service hash to create or manage keys, so you must store it for future use. To get the service hash, first check the service count after you create a service. Then use the count to retrieve the service hash.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/262/1*q-p7qCe6kn96Jd6yevOD_Q.png" /><figcaption>1. Creating a service writes to the blockchain and will require an Ether transaction.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/1*SR-i3-EeiABFKxH8L4tymg.png" /><figcaption>2. First get the service count</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/447/1*i0d5lzYCAmdKbigIzs3iow.png" /><figcaption>3. Subtract 1 to get the location it falls in the list (arrays are indexed starting at 0).</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/448/1*B5_77NYHlt_MvYnS9c0eUw.png" /><figcaption>4. Copy and paste the service hash into the Services field to read and verify your service endpoint and owner.</figcaption></figure><h3>Sharing a Service</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/374/1*lA7r7z894zMZw-jc3K9RCw.png" /></figure><p>You may want to decentralize control over your service’s keys. To share a service, use the “Share Service” function to pass your service id and the account address you wish to share. Only owners can share a service, so make sure you use the service owner’s account to call Share Service.</p><p>You can add and remove Shared owners. Shared owners can be added and removed by any service owner. However the primary owner is immutable. It resides in the service struct.</p><h3>Recovering a Service</h3><p>If you lose your service id, there are multiple ways to recover it.</p><ul><li>Recreate it by calculating the cryptographic hash of the original url and original account address used to create the service.</li><li>Lookup the _service key from the ServiceCreated event, using your account’s address for _owner.</li><li>Iterate through the serviceList, calling getService for each key until you find one that matches your original url or account address.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/674/1*cFxef4-XI4Y_wqA1DrUh3g.png" /><figcaption>Iterate through the service list to get the service hash.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/666/1*cO5W5oblTQWt8pOU4kcAAQ.png" /><figcaption>Use the service hash and Get Service to verify service owner and endpoint.</figcaption></figure><h3>Service Related Functions</h3><h3>Get the URL</h3><p>You can retrieve a service’s url, using the Get url function, passing the service hash. This function returns a string of variable length making it unsuitable for cross-contract use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/670/1*ijerNT8Uo32O0-Ovm8uR2g.png" /><figcaption>Return service URL using a service hash.</figcaption></figure><h3>Update the URL</h3><p>A service owner can update the service’s url.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/343/1*yswGJmIo4u2UKBDtOTwvrg.png" /><figcaption>You can change your service endpoint, but doing so will reduce the recover options should you misplace your service hash.</figcaption></figure><h3>Keys</h3><p>A key establishes a relationship between accounts and services. Only a service owner can create a key, and only for a service they own. A key’s service is immutable, granting irrevocable rights to the related service owners. Additionally, a key also records the owner and if it can be sold, shared, or traded. When created, a key is unable to be sold, shared, or traded. A service owner must explicitly enable these permissions for a key.</p><h3>Creating &amp; Issuing Keys</h3><p>Keys are identified by the cryptographic hash of: the service id, the time the key is created, and the address the key is issued to. This makes them impractical to regenerate, so the key should be stored.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/370/1*r9_SJVzWPlPZWTWa9NPYFg.png" /><figcaption>Create a key for your service</figcaption></figure><p>A service owner can create a key by passing a service to the Create Key function. This creates a new key for that service and issues it to the service owner’s account. A transaction will be returned with a log containing a KeyCreated event denoting the _owner, and the new _key. In Mist, you need to track the key count, like so:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/1*bXNdKNUj4-XOBDYKiFA5dQ.png" /><figcaption>Note the key count before you create a key</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/677/1*QuxatU9j4Qx5JIApyVkpug.png" /><figcaption>Similar to getting your service hash, subtract 1 from the count to get your position in the key list. This is your key hash. You should store it somewhere as you will need it to permission or share your key.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/672/1*VTe3FCeKA_xIIFyPhUWo1g.png" /><figcaption>Using the key hash you can see the primary key owner and the key permissions (share, trade, sell).</figcaption></figure><p>Alternatively you can pass an account address and service to the Issue Key function to directly issue a key to any account address.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/363/1*u39wFJTqFLIwIvOqdYu5Xw.png" /><figcaption>You can create and issue a new key directly to an Ethereum Account.</figcaption></figure><h3>Permissions</h3><p>You are unable to sell, trade, or share newly created keys. The service owners can selectively enable or disable these permissions using the Set Key Permissions function.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*t9aC-rPY2CP4ihT1nZ9KOQ.png" /></figure><p>When disabling these permission, any active trade offers, sales offers, or shared owners will be removed for that key.</p><h3>Sharing</h3><p>A key with permission to share can be shared by the owner by passing the key and account address to the Share Key function. Shared owners have identical permissions as the primary owner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/366/1*XR38RFpQTNQAGaV1Il6bog.png" /><figcaption>After sharing is enabled on keys the key owner can share it.</figcaption></figure><p>Any owner can also unshare a key by passing the key and account address to remove. Primary key owners can not be removed, only shared owners.</p><h3>Selling</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/371/1*iPIStfvjlFMGO3GrsgWrgA.png" /></figure><p>Keys can only be sold if the service owner assigns canSell permissions. If enabled, a key owner can then sell a key by creating a sales offer for a specific buyer. To create a sales offer, pass the key, the buyer’s account address, the price (in HLTH), and after-sale permissions to the Create Sales Offer function.</p><p>When creating a sales offer with a _can sell value of false, future sales of the key will be disabled at the point of sale. The key owner can cancel a sales offer by passing the key to the Cancel Sales Offer function.</p><p>To purchase a key that’s been offered to you, pass the key to the Purchase Key function. Note: This requires that you have previously authorized the Health Nexus DRS contract to spend a sufficient amount of HLTH to cover the purchase price.</p><blockquote>The Health Nexus DRS contract cannot spend your HLTH tokens without your explicit authorization.</blockquote><p>A successful sale will return a transaction with a logged KeySold event.</p><h3>Trading</h3><p>To trade keys, both keys have to be authorized to trade by their respective services. To make a trade offer, pass the key you have and the key you want to the Create Trade Offer function. If a matching trade offer exists, the trade will complete. Otherwise a trade offer will be created to potentially be filled at a later time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/362/1*hDaE-X6bIOYPu2oi2XrDKQ.png" /></figure><p>You can cancel a trade offer using the Cancel Trade Offer function.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/340/1*EQepdueuoPFNSuKT8VpRlQ.png" /></figure><p>Completing a trade offer returns a transaction with a logged KeysTraded event and cancels any related sales offer.</p><h3>Recovering a Key</h3><p>If you lose your key, there are two ways to recover it.</p><ul><li>Lookup the key from the appropriate event, depending on how you acquired the key. For example, if you created the key, you can filter the KeyCreated events by _owner to retrieve the _key. Other events include: KeySold, KeysTraded, and Log.</li><li>Iterate through the keyList, calling getKey for each key until you find the key.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/672/1*Kl-2BrQgHV3FiHhHMohuYA.png" /><figcaption>Iterate through the key list.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/673/1*y7rld1I6vkxs0rvyvYXs1Q.png" /><figcaption>Use the keys returned above to find your owned keys.</figcaption></figure><h3>Key Related Functions</h3><h3>Get url from key</h3><p>You can retrieve a key’s service’s url using the “Get url from key” function, passing the key. This function returns a string of variable length making it unsuitable for cross-contract use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/684/1*V4zF3qx_hAip4W2NE2tENg.png" /></figure><h3>Logging &amp; Messaging</h3><p>This contract provides two general purpose events, Message and Log, that a decentralized app or gatekeeper service can use. A third event, Access, can only be created by a service owner and only for their service’s keys. This is to provide an immutable access record that can be audited.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/347/1*2RfLk_xbJA5bHQSB1M2Lyg.png" /><figcaption>Logs can be created to provide a history of actions.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/357/1*WYni_Ur9H3PHCbmJY3ivlQ.png" /><figcaption>You can use the Message function to create a history between a key and service.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/339/1*YXKE40JFGB83n8rjvfIwrg.png" /><figcaption>The Log Access event only be created by a service for one of their keys.</figcaption></figure><h3>Using Health Cash (HLTH)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/348/1*ii-qm5cT4ILe2HNKW5oaHw.png" /></figure><p>The Health Nexus DRS contract allows for the purchase of keys using Health Cash (HLTH). To purchase a key with HLTH, you must approve the contract to spend your HLTH using the standard EIP 20 approve function.</p><p>A dapp or service that uses this functionality will have to provide the two stage interface to pre-approve the necessary HLTH. You can manually add this functionality to the Mist client by adding the Rinkeby Health Cash Token contract (0x8a1eD83DfB3ea079ee7F057e1E7eCE964A1c6259) and requesting Rinkeby HLTH as a developing partner. Contact <a href="/service/mailto:info@simplyvitalhealth.com">info@simplyvitalhealth.com</a> for how to apply as a developing partner.</p><h3>Summary</h3><p>Using the Mist client, you are able to create services, create and issue keys, and permission keys for use in a decentralized record service. This covers all the on-chain utility needed to create and manage a data gateway service that uses the Health Nexus smart contract for cryptographic identity management.</p><p>For a more technical overview, check out out the <a href="https://github.com/Health-Nexus/drs/wiki">project wiki</a> on github. Our smart contract code and security audit can be found in our <a href="https://github.com/Health-Nexus/drs">github repo.</a></p><p>If you have questions about this, Health Nexus, or our token, find us in our <a href="https://t.me/HealthNexus">telegram group</a>.</p><h3>About SimplyVital Health</h3><p>SimplyVital Health is making decentralized technology accessible to the healthcare industry by creating Health Nexus, a healthcare-safe opensource blockchain.</p><p><a href="https://www.simplyvitalhealth.com/">https://www.simplyvitalhealth.com/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e858a576d574" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What makes Health Nexus different than Ethereum?]]></title>
            <link>https://medium.com/@dmalive/what-makes-health-nexus-different-than-ethereum-8cf992f901a?source=rss-6421a1bbaede------2</link>
            <guid isPermaLink="false">https://medium.com/p/8cf992f901a</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[token-sale]]></category>
            <category><![CDATA[healthcare]]></category>
            <dc:creator><![CDATA[David Michael Akers]]></dc:creator>
            <pubDate>Tue, 13 Feb 2018 13:03:42 GMT</pubDate>
            <atom:updated>2018-02-13T13:03:42.672Z</atom:updated>
            <content:encoded><![CDATA[<p>I often get questions asking us what the difference is between Health Nexus and this-or-that project. I want to answer that in this article, however I’m not going to be talking so much about what makes our <strong><em>project</em></strong> different; that would require I cover our incredible team, our unique qualifying experience, our strategic partners, and our world-class advisers. I’ll leave that task for another team member and will instead narrow my response to how our <strong><em>technology</em></strong> is different.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WTKGE1WQko9ajeLQFaJPCQ.jpeg" /><figcaption>There are some rather significant differences between Health Nexus and Ethereum because we are building Health Nexus to meet and exceed healthcare industry requirements.</figcaption></figure><p>Most of the time when we get that question Health Nexus is being compared with a healthcare-related decentralized application (dapp). In the broadest sense, if they are showing you a user interface, a mobile app, or something that looks like an application then that is something that could run <strong><em>on</em></strong> Health Nexus. Health Nexus supports all kinds of healthcare applications because it is a blockchain like Ethereum.</p><blockquote>Anyone who wants to offer a decentralized application for healthcare will be able to use Health Nexus to support their decentralized requirements. We see all these healthcare dapps as potential partners <strong>not as competition</strong>.</blockquote><p>Sometimes though the comparison is between Health Nexus and another actual blockchain and in that case the answer depends on the differences in the underlying technology or how the technology will change over time. For practical reasons I’m going to answer the question by contrasting Health Nexus with Ethereum. That should provide you enough information to compare Health Nexus with any other project.</p><h3>How are Health Nexus and Ethereum Similar?</h3><p>Here at SimplyVital Health we’re big fans of Ethereum and the incredible community that surrounds it. When looking at technology that was tried and tested, that had forward momentum, and that had significant efforts being applied to the scaling issues Ethereum stood out. That’s why we selected it as the foundation for Health Nexus.</p><p>Health Nexus is a fork of the Ethereum blockchain. Ethereum is a blockchain like Bitcoin with an added virtual machine that runs code stored on the blockchain, called smart contracts. These smart contracts can be used for creating decentralized applications. Things Health Nexus has in common with Ethereum include:</p><ul><li>Smart Contracts</li><li>Open source</li><li>Free to develop on</li><li>Proof-of-Stake Planned</li></ul><p>So Health Nexus and Ethereum are very similar, however healthcare technology and the regulations around healthcare required us to make some changes. Let’s get into those.</p><h3>So how is Health Nexus different?</h3><p>There are some rather significant differences between Health Nexus and Ethereum because we are building Health Nexus to meet and exceed healthcare industry requirements. They are:</p><p><strong>Governance Protocol</strong><br>Decentralized governance is built into the protocol though executive accounts that are able to participate in a democratic governing process. The consortium will be responsible for establishing standards, certifying and whitelisting miners and data nodes, and proposing and voting on protocol updates. You can read more about our <a href="https://medium.com/simplyvital/power-to-the-people-our-governance-protocol-explained-3d8a6820374b">governance changes</a>.</p><p><strong>HIPAA Compliant Nodes</strong><br>Unlike Ethereum where anyone with enough power can mine blocks, to mine blocks on Health Nexus a node will have to pass HIPAA (Health Insurance Portability and Accountability Act) certification and be whitelisted by an executive account in compliance with the validation standards established by the governing consortium. This increases the security of the blockchain and meets healthcare regulations.</p><p><strong>Decentralized Record Management</strong><br>The most common requirement for a decentralized healthcare applications is securely exchanging medical data. Our protocol adds a key pair system so that accounts can create and permission multiple keys, and use those keys to verify blockchain identity as part of responding to secure request to offchain data. This provides protocol-level support to decentralized record management. You can read more about our <a href="https://medium.com/simplyvital/the-key-to-simplyvital-health-84d3d4dff684">key pair system</a>.</p><p><strong>Decentralized Storage and Responsive Data Events</strong><br>Data storage contracts and corresponding decentralized data storage allows decentralized applications to store more data than is practical on the blockchain alone. Combined with data-aware smart contract events, and contract-paid transactions, smart contracts will be able to respond in real-time to partnered systems creating or modify data.</p><h3><strong>So what’s the bottom line?</strong></h3><p>The changes we are making to Health Nexus will make blockchain technology safe for the healthcare industry. We believe that will make Health Nexus dapps easier to integrate and faster to sell to healthcare providers and give software providers delivering dapps on Health Nexus a competitive advantage.</p><p>For more information about Health Nexus checkout our other <a href="https://medium.com/simplyvital">articles</a> or visit our <a href="https://token.simplyvitalhealth.com/">token sale site</a>. If you have questions about Health Nexus checkout our <a href="https://docsend.com/view/cuufmc5">whitepaper</a> or find us in our <a href="https://t.me/HealthNexus">telegram group</a>.</p><h3>About SimplyVital Health:</h3><p>SimplyVital Health is making decentralized technology accessible to the healthcare industry by creating Health Nexus, a healthcare-grade blockchain and paired data storage. Their principal application, ConnectingCare, augments existing hospital care systems to extract data and create care pathway flexibility, prospectively track financials, maintain immutable records, and accurately monitor analytics.</p><p>Website: <a href="https://tokensale.simplyvitalhealth.com/">https://tokensale.simplyvitalhealth.com/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8cf992f901a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Decentralized technology and healthcare]]></title>
            <link>https://medium.com/@dmalive/decentralized-technology-and-healthcare-c01f979d4b0?source=rss-6421a1bbaede------2</link>
            <guid isPermaLink="false">https://medium.com/p/c01f979d4b0</guid>
            <category><![CDATA[token-sale]]></category>
            <category><![CDATA[decentralized-apps]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[healthcare]]></category>
            <dc:creator><![CDATA[David Michael Akers]]></dc:creator>
            <pubDate>Tue, 30 Jan 2018 14:33:08 GMT</pubDate>
            <atom:updated>2019-09-26T19:40:55.589Z</atom:updated>
            <content:encoded><![CDATA[<p>At SimplyVital Health we are creating a healthcare-safe blockchain designed to bring decentralized technology to the healthcare industry. Naturally we are very interested in how the healthcare industry will adopt our technology, what kinds of problems will be solved with it, and how it will be used to realized new value.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LfQydwDGOjwnWRNEtyf2Ow.png" /><figcaption>Health Nexus — a healthcare-safe opensource blockchain</figcaption></figure><p>With our existing blockchain-based application, ConnectingCare, we address the lack of visibility that makes coordinated care difficult for hospitals that rely on post-acute care facilities. Care coordinators needed a way to monitor a patient’s care after they left the hospital. It’s a perfect use for blockchain technology and is paired with the healthcare industry’s move towards value-based care.</p><p>What other healthcare applications can benefit from decentralized technology? Because we’re getting into speculative territory, and it’s too easy to imagine a world where anything possible, we need to constrain ourselves to ideas that meet the criteria for a successful healthcare decentralized application (Dapp). There are only two things we are looking for. They are:</p><ol><li>The application must require decentralized technology.</li><li>The value added, or problem solved, must be worth paying for.</li></ol><h3><strong>Applications that require decentralized technology</strong></h3><p>There is a tendency to assume that every application that uses a blockchain requires it, or even benefits from it. Why else would they do it right? But the hype and the misunderstanding around blockchain and decentralization generally means that often times decentralized technology is applied to solve problems that don’t require it, or even benefit from it that much.</p><p>We are going to limit ourselves to applications that couldn’t work without it — that couldn’t have been made before the advent of it, or at the very least could not have been successfully implemented before.</p><h3>The value added, or problem solved, must be worth paying for</h3><p>This is just another way of saying it has to be commercially viable. While this may seem rather obvious, a quick look around at the many blockchain-based healthcare applications being promoted today may leave you a bit puzzled. It’s not enough to have a good idea, you have to identify a segment of users that would be willing to spend money implementing it before they are able to see any returns. We are going to limit ourselves to applications that solve problems or provide value people are willing to pay for.</p><p>With those criteria in mind here’s a list of some of the ways we see the healthcare industry using Health Nexus.</p><ul><li><strong>Patient owned and Patient Generated data</strong> <br>Applications that record biometric data decentrally can be linked to medical wearables or in-home medical monitors and used to provide real-time feeds to services that monitor patient conditions or route in-home care units where they are needed. Patients can voluntarily participate in clinical research by sharing their biometric feeds with researchers or data aggregators that provide information on public health to world governments or health organizations.</li><li><strong>Clinical Trials and Medical Research</strong><br>Applications that pre-register clinical trial formulations and trial results and share that data on the blockchain can encourage data-sharing and improve outcomes. Patient consent and safety analysis can be stored decentrally and provide audit trails of activity to the public or financiers.</li><li><strong>Public Health Alert System</strong><br>Data aggregators that leverage decentralized data and artificial intelligence will be able to sort and store de-identified patient data in near real-time allowing for rapid identification of related cases of infectious diseases, project spread, and respond by providing alerts or mobilizing emergency resources.</li><li><strong>Life-saving Medical Data</strong><br>Voluntary emergency data applications that allow first-responders access to crucial medical information such as allergies, existing conditions, or important prescriptions can be reliably provided on chain and secured with biometric access allowing access even if the patient is unresponsive.</li><li><strong>Prescription Registry </strong><br>A unified registry of patient prescriptions will allow care providers the ability to see all the medications prescribe to their patients, by all care providers, and track expiration dates, renewals, and missed pickups.</li><li><strong>Administrative Processing </strong><br>The process of processing medical insurance claims can be automated, in-part, driving cost down and improving responsiveness while becoming more transparent to the patient and healthcare providers.</li></ul><p>These are just some of the ways we see the healthcare industry using Health Nexus!</p><p>Of course the holy grail of decentralized healthcare systems is providing healthcare providers universal access to their patient medical records and enabling coordinated care between all providers. Health Nexus fully supports this but there are many more applications for this technology than just coordinated care.</p><p>If you have questions about this, Health Nexus, or our token sale find us in our <a href="https://t.me/HealthNexus">telegram group</a>.</p><h3>About SimplyVital Health:</h3><p>SimplyVital Health is making decentralized technology accessible to the healthcare industry by creating Health Nexus, a healthcare-safe opensource blockchain.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c01f979d4b0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to purchase Ether with Fiat]]></title>
            <link>https://medium.com/@dmalive/how-to-purchase-ether-with-fiat-b45a8c40e1e2?source=rss-6421a1bbaede------2</link>
            <guid isPermaLink="false">https://medium.com/p/b45a8c40e1e2</guid>
            <category><![CDATA[token-sale]]></category>
            <category><![CDATA[healthcare]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[David Michael Akers]]></dc:creator>
            <pubDate>Wed, 24 Jan 2018 14:28:16 GMT</pubDate>
            <atom:updated>2018-01-24T14:28:16.113Z</atom:updated>
            <content:encoded><![CDATA[<p>If you are new to crypto the term fiat currency may be new; it just means any currency that is issued and backed by a government. The US Dollar (USD), British Pound (GBP), or Yen (JPY) are all fiat currencies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*916xjYMN0LX9FddJ." /></figure><p>In this brief guide I will describe how to acquire Ether (the cyptocurrency of the Ethereum blockchain) using fiat currency. The are three steps in the process:</p><ol><li>Register on an exchange</li><li>Verify your identity</li><li>Purchasing Ether</li></ol><p>There are a few exchanges that will allow you to purchase ether with fiat currency: Kraken, Gemini, and Coinbase are the most popular.</p><h3>1. Register on an exchange</h3><p>Registration on an exchange is as simple as completing a brief online form. Here you can find the registration forms for:</p><ul><li><a href="https://exchange.gemini.com/register">Gemini</a></li><li><a href="https://www.kraken.com/">Kraken</a> (click Sign up)</li><li><a href="https://www.coinbase.com/">Coinbase</a> (click Sign up)</li></ul><h3>2. Verify your Identity</h3><p>You may need to upload documents proving you are who you say you are. This is done to protect against fraud. Once you upload your documents you’ll wait for your account to be verified. Depending on the platform and how busy they are the verification process may take longer than a day.</p><p>Some Exchanges require proof of address and photo identification to carry out “Know Your Customer” (KYC) and Anti-Money Laundering checks. You must complete this step before depositing funds and prior to withdrawal.</p><p>More funding options and higher deposit limits may be available depending on the results of this verification process so try to provide everything required for the highest level of verification.</p><h3>3. Purchasing Ether</h3><p>Each exchange will offer their own purchasing methods which can be a mix of bank wire transfers, SEPA, credit/debit card and/or PayPal payments. The fees charged and the weekly limits will likely vary vary for each purchasing method so review the fees and limitations before picking a purchasing method.</p><p><strong>Deposit Funds<br></strong>If you choose to deposit funds before purchasing (as opposed to purchasing using a credit card or some other method) keep in mind that deposit times will vary from very fast to very slow depending on the exchange and the deposit method chosen.</p><blockquote><strong><em>It might take you a week or longer to verify your account and deposit funds.</em></strong></blockquote><p><strong>Trade for Ether</strong><br>Once your fiat currency has arrived in your exchange account (or you use a credit card or other payment option) the process for purchasing Ether is usually very simple but differs depending on the exchange you are using.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*otD_MaF1T9F0CVIB." /><figcaption>Kraken: Here you can see someone purchasing ETH with EUR.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*atP_PR-3m-ivPj3tU7p_Ew.png" /><figcaption>Gemini: Purchasing ETH with USD</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2kXHrkAsmiiePK2qYYyjOA.png" /><figcaption>coinbase: Purchasing ETH with MasterCard Debit</figcaption></figure><p>That’s it! Exchanging Fiat for ETH is that simple. Keep in mind though you still need to move that Ether to a ERC 20 token compatible wallet. <a href="https://medium.com/simplyvital/getting-ready-for-the-health-nexus-token-sale-158df4c0b050">Read this article that includes a list of token compatible wallets.</a></p><p>If you have questions about this or Health Nexus and our token sale find us in our <a href="https://t.me/HealthNexus">telegram group</a>.</p><h3>About SimplyVital Health:</h3><p>SimplyVital Health is making decentralized technology accessible to the healthcare industry by creating Health Nexus, a healthcare-safe blockchain.</p><p>To participate in this project join our token sale here: <a href="https://tokensale.simplyvitalhealth.com/">https://tokensale.simplyvitalhealth.com/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b45a8c40e1e2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Healthcare and Cryptocurrency]]></title>
            <link>https://medium.com/@dmalive/healthcare-and-cryptocurrency-3a34493d48d1?source=rss-6421a1bbaede------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a34493d48d1</guid>
            <category><![CDATA[healthcare]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[token-sale]]></category>
            <dc:creator><![CDATA[David Michael Akers]]></dc:creator>
            <pubDate>Tue, 16 Jan 2018 13:15:38 GMT</pubDate>
            <atom:updated>2018-01-16T13:15:38.914Z</atom:updated>
            <content:encoded><![CDATA[<p>As one of the first digital healthcare companies using blockchain technology in a revenue generating application we get a ton of questions about the blockchain and how it works.</p><p>I understand the curiosity and the confusion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_osCwtEnd2Jm9PQmQ9MrSA.jpeg" /></figure><p>Blockchains and other decentralized technology are relatively new. So new, I think it’s fair to say that we are still in the infancy of decentralized technology. It’s not just the technology though, as a species we are in the earliest stages of understanding how best to make use of these innovations.</p><p>There’s a ton of hype around blockchains. If you plan on reading up on the subject you better get your waders on: soon you’re going to be knee deep in buzzwords, exaggerated claims or worse. You’re going to read words like disruptive, revolutionary, game-changing, break-through. Often those words will be in reference to specific protocols or projects.</p><blockquote>Anyone who can navigate the morass of marketing spin and technological gobbledygook that surrounds blockchains and arrive on solid ground deserves major props.</blockquote><p>It’s with that in mind that I’m going to tell you about Health Nexus and how we see the healthcare industry adopting decentralized technology. I’m going to keep this as hype-free as I possibly can so as not to add to the quagmire that surrounds this tech.</p><p>In my last article I dove into transactions and how Health Nexus is shaping up differently than Ethereum with regard to those. I’m going to lean on that a bit in discussing cryptocurrency and how the healthcare industry is likely to use it.</p><p>Cryptocurrency is fundamental to successful blockchains for a few reasons:</p><ol><li>Blocks can only contain a finite number of transactions.</li><li>There are only two ways to program a system to allocate finite resources: pricing mechanisms or rationing algorithms.</li><li>Pricing mechanisms are more effective when the demand is not entirely known beforehand.</li></ol><p>I’m not going to elaborate on that much except to say that those three points are foundational to crypto-economics and explain why blockchains not only use cryptocurrency but require it.</p><p>Health Nexus, like Ethereum, will require the use of cryptocurrency. On Health Nexus we call it health cash (on Ethereum it’s ether). But how will healthcare providers use cryptocurrency? Will there be a purchasing agent in the IT department of your local hospital responsible for procuring cryptocurrency for the various decentralized applications they use?</p><p>Maybe in the future. Today, we don’t think they are quite there yet.</p><p>We believe the fastest way to get the healthcare industry using decentralized technology is to give third-party service providers an easy way to meter cryptocurrency use for their customers. Those third-party providers will be able to enter traditional commercial agreements with healthcare providers and include use fees as part of those agreements, providing a very familiar interface to the healthcare industry.</p><p><strong>This decentralization as a service (DAAS) model will make it possible for every healthcare provider to participate on Health Nexus.</strong></p><p>Of course, from the get go, healthcare providers and patients will be able to procure their own health cash and use it for any application. <em>We expect crypto-savy consumers to take advantage of this. </em>But if they run out will the decentralized applications stop working? Not for those with commercial agreements that include cryptocurrency usage. They can benefit from buying health cash themselves and having their service providers provide it if needed.</p><p>These flexible payment models are enabled by changes in the blockchain protocol I discussed in the last article, and are just one example of how Health Nexus is designed specifically for healthcare.</p><p>No hype. We’re bringing decentralized technology to healthcare. Is that disruptive, revolutionary, or game-changing? I don’t know. It’s sure is cool though.</p><p>For more information about Health Nexus checkout our <a href="https://docsend.com/view/cuufmc5">whitepaper</a>. To follow up with questions about Health Nexus or our token sale find us in our <a href="https://t.me/HealthNexus">telegram group</a>.</p><h3>About SimplyVital Health:</h3><p>SimplyVital Health is making decentralized technology accessible to the healthcare industry by creating Health Nexus, a healthcare-grade blockchain and paired data storage. Their principal application, ConnectingCare, augments existing hospital care systems to extract data and create care pathway flexibility, prospectively track financials, maintain immutable records, and accurately monitor analytics.</p><p>Website: <a href="https://tokensale.simplyvitalhealth.com/">https://tokensale.simplyvitalhealth.com/</a></p><p>News and Articles by us: <a href="https://medium.com/simplyvital">https://medium.com/simplyvital</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a34493d48d1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>