Obviously your lawyer would be present, however, to confirm otherwise.

Unless I'm reading it wrong you're basically disabling webservices like making a SOAP call to a third party on behalf of the connecting user-agent. That's a non-starter for just about all companies that have at least one business partner.

if it can be prescribed then it can be medically necessary then it can billed to insurance/medicare/medicaid. this is a goldmine.

I made the jump from developer to team lead and now on to management. Good management is very very hard, keeping people on task, motivated, and managing burn out is really more of an art than science and I'm not even including dealing with different personality strengths/weaknesses and the various combinations thereof.

If you have a good manager or even just a not-bad manager let them know. It's a difficult position to do well and lots of folks who you respect see you as worthless.

So does your phone steadily run out of RAM as the chips are incinerated? ...I didn't know the batteries were that powerful either, I'm so far behind the times.

How many more companies have these contracts?

Seems like you can pick which vendor gives you the best value based on the use case of your application. Doesn't seem that absurd to me at all.

yeah when i started it was "here's your certs, here's the VPN server IP.. by and don't talk to me ever". I could see it being difficult for a non-tech person to get setup.

One other thing. I work on an Imac and use TunnelBlick to manage the VPN connections. I've had zero issues on a wired connection but sometimes have issues using wifi, the vpn connections will drop and then re-connect after a minute or two. There must be something weird in the office because when I take my mac home i have zero issues on wifi.

I'll answer as best as I can

> Please tell us more about your setup.
We're a Java office in TX with a remote call center in OR and a handful of remote employees ( Chicago ).

> What type of work does the company and you do?
I'm the director of development, we're a j2ee web application development shop with special expertise in Oracle

> Approximately how many users work like this?
All of us ~30

> Does this company operate primarily as a standard physical office environment, or is this a distributed(work from home) startup?
A couple of my developers work from home 3 days a week and most of ops ( the network guys ) work from wherever and, apparently, whenever they want. They're pretty hot shit, published authors, speakers at LISA, etc so they're left alone most of the time.

> Where are the servers, on-site, datacenter, cloud?
We keep our staging and UAT servers on site and colo for production + another colo for failover

> Approximately how many servers?
I have no idea, I know we have some serious SAN gear for the databases. We probably have around 50 virtual servers in our testing setup and maybe 20-25 production server clusters with an average of 3 nodes each. Some physical some virtual.

> What type of applications are used, web, small applications like QB, MS Exchange or SQL systems?
Web applications, we develop/maintain some very large rewards and loyalty programs for the big banks. RDBMS is Oracle, email and IM is handled through Zimbra, project management is handled with Atlassen Jira self hosted.

> What are the negative aspects of this system?
The only problem i've ever faced is the VPN endpoints not staying connected. VPN connectivity becomes mission critical because without it no work can get done. I don't know what they're using for the VPN server, I know ops is a big fan of OpenBSD so it wouldn't surprise me if that's what they are using.

The rj45 jacks in the office are just plain old dirty connections to the Inet. We each have multiple OpenVPN connections on our localhost giving us access to different parts of the network depending on our roles. It's convenient because our workstations work identically wherever we are ( home, work, coffee shop ) and it's convenient when someone leaves because operations just invalidates the VPN certs and the former employee is cut off no matter where they physically are. A side effect is whenever your VPN credentials don't work you're left wondering is you're about to get fired and ops just jumped the gun haha.

In 2016, Nokia can re-enter the cell phone market under its own name. This may mean them going back into designing their own phones, or purchasing Jolla, the spin-off company run by former Nokia engineers. Jolla has already put a very nice looking low-end cell phone on the market, and I expect them to continue to build out their smart phone portfolio in the near future. I can definitely see them once again becoming a part of Nokia in 2016. I don't think Nokia would be content to remain a patent-only business. Also, keep in mind, they are retaining their very lucrative mapping business as well.

I wonder what impact this engine could have on the mobile frameworks out there ( JQM, PhoneJs etc ). The article states that they got the head mobile guy from Facebook. The next few months could get very interesting in that world.

"First of all, you don't need to meet their API spec, they need to meet yours." You're assuming so much in that sentence though. I've had conversations with health insurance companies where when I explain their systems are completely out of compliance with the protocol specification ( NCPDP 5.1 in this case) and talking to their system requires a whole other layer of abstraction just to transform a proper NCPDP 5.1 transmission into their broken implementation their response is literally "so?". When I ask "well what am i suppose to do with the thousands of patients that have your insurance?" they're response, "turn them away".

My team has been talking about healthcare.gov and all the related woes for a while. Pretty much we're all in agreement that we should thank the baby jeebus every day it's not our project haha. Seriously though, for something this complex, if the team grows to over about 15 people it's doomed. And that's just YOUR side, I have a lot of experience interfacing to insurance providers' systems. Half the time the provider you're trying to connect to is broken and doesn't work per their API docs at a basic level let alone have proper capacity let alone have any sense of normal connectivity. I can't even imagine trying to talk to something as huge as the IRS. I bet it's 6 months before you can get a simple spelling fix on an API method pushed out to production.