Even Epic doesn't have the ability to consolidate multiple CDA documents, or even write information directly to the chart. Each one requires manual review. Standards for exchange are not really the problem.
347 karma · joined August 10, 2016
Even Epic doesn't have the ability to consolidate multiple CDA documents, or even write information directly to the chart. Each one requires manual review. Standards for exchange are not really the problem.
This is the government certification data for inpatient software: https://dashboard.healthit.gov/quickstats/pages/2015-edition...
The long tail of software products makes connecting everything exponentially harder.
Here's the common pitfalls as I see them:
1. Sprints offer flexibility but unless you educate the whole company waterfall + gantt charts are what the business side wants
2. Unless you educate all members of a scrum team on what the retrospective is, and let the developers drive it, you won't be effectively improving processes
3. I've always felt conflicted about the agile "working software over comprehensive documentation value". To me it implies that documentation is easier when the product is working and/or the product might change based on feedback, so you don't want to re-write the docs. To people who don't learn scrum/agile it means "don't write documentation"
Occasionally there will be a post on HN about someone who debugged a compiler bug or a even a hardware bug, and it lifts my spirits.
I'm trying to point out that there may a larger crackdown at foot, and if the clubs were involved in especially risky behavior, or hazing or worse we probably won't hear about it.
Here's some frat crackdown news: https://onwardstate.com/2017/11/08/another-one-bites-the-dus...
And some moving reporting about the fraternity death. https://www.theatlantic.com/magazine/archive/2017/11/a-death...
I wouldn’t be surprised if some kind of hazing or even worse behavior is the real reason for the shutdown.
I agree with most of the comments so far this is bad management.
If you’re starting out just ditch the ORM altogether.
Sails is just plain express so if you need to piece it apart at some point in the future it’s not too hard.
That said Sails is great for bootstrapping a reasonably secure and functioning app in short amount of time.
The metaphor in this article fits perfectly- the developer who wrote this borrowed from the future, and without being there at the time, I can’t really judge their calculations.
The most helpful resource I've found about v8 specific performance is the bluebird optimization killers wiki: https://github.com/petkaantonov/bluebird/wiki/Optimization-k... wiki, and the v8 bailout reasons repo: https://github.com/vhf/v8-bailout-reasons
> Caution: Not recommended for moonbats, liberals, Clinton drones or Bernie’s Sandernistas.
See for example Nature: http://www.nature.com/authors/policies/experimental.html
https://news.ycombinator.com/item?id=13859961
Does anyone know the story behind why these slides keep getting updated? Is this a databases class?