You and everyone else in this thread should know that "immunologist" is an existing specialty. Find one. Make sure it's not just an allergist, but an academic type with multi-system hospital privileges.
Any tips on finding one? I'm assuming you don't mean infectious disease specialist. I'm familiar with most of the allergists in my area and none are immunologists.I just did a search on google and I can't seem to find any in SoCal.
Are they clustered somewhere in the country? Like how all the geneticists seem to be on the east coast, and the limited geneticists here all seem to be in children's hospitals.
At least one regional electric utility uses an Excel macro to scrape its own public web site to gather aggregate usage and price data. This method allows them to save the data, and maybe analyze it later.
Yes, it's essentially Backbone & d3 (with topojson for data). And it's a better intro to "real life Backbone" than todos, so if you're interested, take a look.
For Android, there is a very simple free app called ExerTime ( https://play.google.com/store/apps/details?id=com.aisknab.ex... ). It's not pretty and the configuration UI is both annoying and confusing (you must enter the total elapsed time at each step, not the time-per-step), but the normal use case works really well. The right options are available (notification sound, audio channel, text-to-speech, screen lock).
I get GSM quality calls on my Nexus 4 (at minimum) via cSIPsimple, pbxes.org, and Google Voice, usually over a mediocre repeated WiFi connection. If there's interest, I'll write it up.
Mild configuration hassle but reliable. Helps to move Google Voice to an account where where you never IM.
1) A mega platform on top of existing EHR's won't be an easy thing. It would require them to play ball and large players, like Epic, probably won't.
They definitely won't play ball with a platform attempting to integrate all of them. That's just a risk; there's no upside. It's possible that none of them would welcome a "platform" at all.
But survey the landscape of EHR vendors. There are a few unique positions of strength out there. Each aspect of uniqueness defines a hypothetical market. The mere existence of some of those markets would develop an asymmetry that simultaneously penalizes competitors and solves a big problem for the partner. Build the spark of the market and you have a significant ally with a strong incentive to nurture your business.
Idea quality indicator: you want the existing player aligned with you, not buying your company (then killing it). They should need you externally.
I'm building a business on one of these hypothetical markets. I made my choice based on my personal capability and fit with the details of the problem. But there are a huge number of different ways to improve both the quality and efficiency of healthcare. (You don't get to solve big problems if there are no big problems.)
EDIT:
See the video posted by stevenrace above. It's a sort of controlled road test with some good engineering moments. In sum, there are a lot of subtle factors that make the car surprisingly stable and maneuverable - for more obvious reasons, it just doesn't behave exactly as we'd intuitively expect.
Please excuse the off-topic rant:
It's my mission right now to change something a little different about EMR design. You're looking at the output. That's wonderful and I am really happy about it. We also need to fix input. EMR/EHR interfaces are mostly terrible; that has significant negative consequences for both patients and providers.
You're looking for an output design that is effective as a physical document. Please consider a follow-up challenge for EMR input UI/UX.
Thanks to commieneko and ssp for a couple of good posts.
Followup questions:
What do you think about the effect that pixel-alignment produces specifically in the context of this comparison?
There seem to be a couple of basic problems with the "clarity" of the pixel-aligned images (please correct):
- As lines diverge from rectilinear, aliasing is inevitable. Either the aliasing or the anti-aliasing will produce discontinuity.
- High-contrast neighbors on pixel boundaries are more likely to highlight perceptual problems related to frequency.
The part that interests me here is the presentation of this comparison on Dustin Curtis' site. His site seems to be pursuing visual impact as an ultimate goal, and contrast is a big part of that:
http://i.imgur.com/UC8ZX.png (OP with histogram overlay)
Does the context minimize the negative effects you've described? Do the filtered images look out of place in such a stark environment?
I'm of the design philosophy that's best exemplified by this old vaudeville joke:
Patient: Doctor, Doctor! It hurts when I do this!
Doctor: Well don't do that!
Thank you, thank you. I'll be here all week ...
Seriously ...
With sampled images displayed on a rectilinear grid, you are going to get into pathological situations that hurt. So don't do that.
One trick you can sometimes get away with is to rotate the work so that it isn't orthogonal to the display grid. Of course then, parts that were okay before may become problems. And the client, bless them, may not like it. No body said life was going to be easy.
Contrast at the edges is where you have the most hurt in this case. Drop shadows, very subtle, please, can help as can can vignetted edges. I've been known to do unclean things like create a 2 or 3 pixel rule the shape of the edge, blur it and multiply or screen it on top of the offending parts. You can even dodge and burn it more or less in the nasty bits. (blending modes are a big topic!) Worse case scenario, try and use the problem as a design element. Once I took a particularly truculent logo and grudged it up with some high frequency noise that was applied with a transparency just so.
Now one thing I used to do all the time for animation was to use temporal sampling to smooth over the rough edges. Even for seemingly static elements, a little bit of focus wiggle or even a slow, smooth slide, barely perceptible, will often cover a world of sins. We probably aren't to the point where that kind of thing is going to be useful on web pages for "static" elements, but the day is coming. There are other advantages, as this allows the graphics to "breath" and seem part of an environment. Of course you may very well not want that effect. But even so, higher resolution displays, faster processors, more resources, will mean that such things, subtly applied, can give us more tools to work with in troublesome situations.
But the best advice, for nearly every case, is "Then don't do that!"
