Skip to content
OSS powering free and open source Advanced Directives
Branch: development
Clone or download
Latest commit a6b131f Aug 4, 2016
Type Name Latest commit message Commit time
Failed to load latest commit information.
app links added (#13) Jul 24, 2016
bin updated deploy script Jun 28, 2016
config links added (#13) Jul 24, 2016
db directive crud done (#4) Jun 28, 2016
directive-templates add drafts of mission and directive-template Jun 27, 2016
lib initial commit Jun 25, 2016
spec links added (#13) Jul 24, 2016
vendor/assets initial commit Jun 25, 2016
.ctags initial commit Jun 25, 2016
.env initial commit Jun 25, 2016
.gitignore initial commit Jun 25, 2016
.hound.yml directive crud done (#4) Jun 28, 2016
.ruby-style.yml directive crud done (#4) Jun 28, 2016
.ruby-version initial commit Jun 25, 2016
Gemfile.lock added text to homepage (#9) Jul 3, 2016 Create Aug 3, 2016
Procfile initial commit Jun 25, 2016 add link to 3d print qr code repo Jul 21, 2016
Rakefile initial commit Jun 25, 2016
app.json initial commit Jun 25, 2016
browserslist initial commit Jun 25, 2016
circle.yml initial commit Jun 25, 2016 update mission and make default readme Jul 1, 2016 ([github] (

free and open source advanced advance directives

I would like to die peacefully with Thomas Tallis on my iPod before the disease takes me over and I hope that will not be for quite some time to come, because if I knew that I could die at any time I wanted, then suddenly every day would be as precious as a million pounds. If I knew that I could die, I would live. My life, my death, my choice.

-Terry Pratchett

why are advance directives so complicated?

We live in an era when 5th degree friends are alerted on their mobile devices at near the speed of light with snapshots of one's meals, ubiquitous government surveillance apparatuses that would make the most elite of Nazi or Soviet secret police overflow with jealousy, and both nearly the entirety of the world's collective cinema and door-delivered oreos are one click away. Yet when it comes to some of the most important of life's decisions, such as advanced directives or DNR verifications, these are often transmitted via crumpled loose paper that follows patients only after a significant delay from their hospital arrival.

general pitfalls of advance directives

  • accessibility
    • many do not have advance directives when they would prove of the most utility
    • those who have advance directives do not always have these communicated to health care providers in extreme circumstances when they would be of the greatest value
  • lack of nuance for the experienced *not easy to stipulate treatment measures to be undertaken based on evidence-based prognostication measures
  • lack of lay understanding
    • many may not understand the basics of advance directives or code status
    • those not in healthcare may create advance directives without understanding what they are signing

how we attempt to improve advance directives

  • provide advance directive templates
  • develop a framework for easily storing and rapidly retrieving advance directives
  • develop tools to dynamically generate advance directives with the inclusion of algorithmic treatment directives (e.g. an intracranial hemorrhage grade 5 should result in complete cessation of therapies aimed at exclusively at life extension)
  • provide resources to make it easier for laypeople to make and understand healthcare directives, and reduce misunderstanding of advance directive content and implications
  • accomplish the above via an open collaborative framework under the unrestrictive BSD license

project drafts / links


  • authors/contributors accept no liability for how site/code/directives are used
  • code/documents associated with this project presently intended only for research (non-clinical) purposes
You can’t perform that action at this time.