21–30 of 42 posts
$3 million is enough to make me think crazy so after looking through the spec for a while I downloaded VistA to get an idea of how hard it would be to build something in M and integrate it. To get a flavor of it, here is a random selection from one of the 913 files making up their current scheduling system (said file helpfully named SCAPMC8P.m, pretty much like all the others): SCDATES2,SCN2,SCPTP,SCX,SCXA,SCXE,SCNA,…
$3million? They should go with http://www.makeplans.net instead: starting at $10/month :)
I think the point of the contest is to spur innovation and fresh ideas in a system that's clearly lacking in that department, not just to build a simple "scheduling app"
Judges will determine the number and amount of monetary prizes. Judges may determine that no prize will be awarded.
I've created a web-based calendaring and scheduling system that integrates with a number of cloud services including google calendar. It also works offline and provides a solid foundation for a lot of what they are asking for.
I'm passionate about calendaring and scheduling, and I've been heavily involved in this space for a long time. However, I just can't bring myself to task switch to this and risk 4 months of evenings and weekends when a judge could determine that no prize is to be awarded - or award some small pittance.
In my spare time I'm building a new product to spawn a new division in the fortune company I'm working for. My chances for providing a good stable life for my wife and children are far better at my current employer.
It saddens me to pass on this.
It's not just a scheduling, there are a bunch of legacy systems you have to integrate with. And of course it's health data, so there are more requirements. Anyone want to burn three months on an unpaid spec? :)
Man, contests like this seem like a bad idea for everyone involved. Solicit bids, take 2 million dollars and get a prototype/demonstration of capability from your top 4-8 options. Review the submitted work and communication each contractor provided, select the one that you feel the most comfortable with and just pay them to make the damn thing.
The lack of upfront funding might discourage a lot of potential entries. It might be better to run this as an iterative process. A minimum qualifying round to narrow the field of candidates. Then lightly fund the resulting teams in the next round. Evaluation at another checkpoint weeds out the non-performing teams. And fully fund the last couple entries. Then select the winning entry at the end, and award the long term contract to the winning entry.
This way would be fairer to all parties involved.
I'm with markus2012 here. I have a profitable product already in place that would give me a significant head start on those requirements, but I'm still not at all prepared to head down that thorny trail.
This is a ridiculously open-ended spec, and there's a mountain of federal legislation to comply with. I might go as far as to say that it's a reckless way to try to procure software, as it's very much a product which needs to work and be supported over the long term, not some sort of black-box AI quick win.
To which legislation in particular are you referring? I often see this claim on HN, but I do not think that most people here have any real understanding of the situation. As an anecdote, I work on a medical information system for emergency rooms. The VA uses our system in some locations. Federal regulations are not at all onerous. Things like HIPAA are dealt with using a few really basic rules.
"The replacement product will, as a part of the overall VistA EHR, deliver privacy, security, data integrity, patient accessibility, interoperability and other services required by federal law, regulations and VA policy."
without citing anything specific either.
A summary of those laws, regulations, and policies (and specific pointers to them) would help potential entrants get a real understanding of the situation.
$3 million is enough to make me think crazy so after looking through the spec for a while I downloaded VistA to get an idea of how hard it would be to build something in M and integrate it. To get a flavor of it, here is a random selection from one of the 913 files making up their current scheduling system (said file helpfully named SCAPMC8P.m, pretty much like all the others): SCDATES2,SCN2,SCPTP,SCX,SCXA,SCXE,SCNA,…
If working at a major DoD contractor taught me any anecdotal lessons about software development for the government, its that you are basically disqualified, by logistical means, from making software for the government if the dollar amount in question is anything more than a drop in the bucket for your budget. That may just be a DoD reality, but I wonder how true it probably is for Federal entities. I'm with markus201…
If they actually get involved actively with the teams for this competition, I think they will get good result.
Earlier quoted context omitted.
To which legislation in particular are you referring? I often see this claim on HN, but I do not think that most people here have any real understanding of the situation. As an anecdote, I work on a medical information system for emergency rooms. The VA uses our system in some locations. Federal regulations are not at all onerous. Things like HIPAA are dealt with using a few really basic rules.
I agree with your sentiment, but the contest rules state "The replacement product will, as a part of the overall VistA EHR, deliver privacy, security, data integrity, patient accessibility, interoperability and other services required by federal law, regulations and VA policy." without citing anything specific either. A summary of those laws, regulations, and policies (and specific pointers to them) would help potent…