What was the scope of their involvement?
Behavioral Tech Research developed Linehan Suicide Safety Net with a grant. It was a phase I grant that was deemed good enough to go to market with. Usually, things go to market only after a phase II grant. Though in the original development the user side of the program was fully developed there were a number of gaps in the administrative features of the program so there was still additional work needed before we could take it to market. Because it’s a program that works with client protected health information, it needed to have an HIPAA review and audit, so there were extra things we needed to do to make the program HIPAA compliant.
NIRD helped us put the features that were missing in place to make the program HIPAA compliant. That was what we originally hired NIRD for. In the process of doing that, we discovered several development issues with the program that made it unstable from a development perspective, which is not what you want when you are working with an HIPAA-compliant program.
It started out with a small scope of work, but we quickly identified there was a lot more work needed. We ended up totally reworking two parts of the program on the backend to make it more stable so that we could bring it to market.
How did you come to work with Northwest Independent Ruby Development?
We found NIRD by doing a search for Seattle-based Ruby on Rails developers. In addition to meeting both of these criteria- NIRD also had experience working with HIPAA compliant programs.
How much have you invested with Northwest Independent Ruby Development?
It’s been about $45,000. The original work wasn’t super significant, but there were many issues that NIRD helped us work through.
What is the status of this engagement?
We hired NIRD late spring 2015 to do the simple few things we thought needed to be done to finish the program and software and take it to market. We were hoping to get it done in two months, but over the course, we started to realize there were serious problems with the code, so there were two timelines we were working with.
The original scope of work took 2–4 months to identify the problem. We then came together again 2–4 months later and re-did the scope of work and made it much broader. It became a more comprehensive overhaul of a couple of segments of the program. That work started in January/February 2016 and finished in July/August 2016.