HN user

pillfill

304 karma
Posts4
Comments20
View on HN

Apothesource | Charleston, SC or Remote (US only) | Full-Time, Remote OK! | https://apothesource.com

Apothesource is a healthcare consulting company that specializes in building software that integrates directly with Electronic Health Record (EHR) and other healthcare systems.

Open Roles:

Java Service Developer: Develop RESTful microservices using Java, Maven, Spring Boot, and Docker / Kubernetes

Web API Wrapper: Extract information from existing web front-ends and develop new RESTful APIs on top of legacy web forms.

Please send your resume to hnjobs@apothesource.com

It'll be really interesting to see where this goes. We currently use Fabric8's Docker Maven Plugin (https://dmp.fabric8.io/) for our Java-based containers. It's a little verbose but works really well- it allows us to run our integration tests directly against the final container images (+ any container dependencies) as part of the standard Maven build.

There's nothing inherently political about the this article or the science in general here.

There is, however, a very concerted effort to convince people that the science of climate change 'is political' in order to give those who find the issue uncomfortable license to question the legitimacy of the entire field of study. That's as dangerous as it is absurd, and it's important that it's challenged whenever it's encountered.

Apothesource | Healthcare IT | South Carolina | Full time | REMOTE (limited to US Citizens)

We're a small team of senior Healthcare IT engineers headquartered in Charleston SC. We specialize in building and orchestrating REST microservices for large healthcare providers. Primary qualification is experience building REST services using a Java-based microservice framework (e.g. Spring Boot, Dropwizard). We're also a shop heavily focused on containerization, so any previous experience or desire to learn Docker and/or Kubernetes will be put to good use.

If interested, please send your resume to jobs@apothesource.com.

While FHIR is certainly making health records development more approachable and sane for developers, it isn't going to fix the large-scale data interoperability problem. Even if we completely suspended disbelief and assumed it was perfectly and consistently adopted across all EHR products, it still is just a structured way of exchanging data like HL7- the much more complicated issues preventing semantic interoperability of clinical data still exist.

The news is that they are injecting it even when you have opted out of CNPI.

The disturbing part is a unique ID that follows you despite private browsing and across browsers. The worst part is that it goes to every site you visit (not just VZW or selected advertisers). It can be trivially linked to your existing cookies/identity to follow you even after clearing cookies, changing browsers, switching devices, etc.

Sure, but you're missing the bigger picture- The point is to reduce the total number of passwords a user has to manage in general. The fewer passwords you have to remember, the more likely you are to protect those few 'root identity' accounts (by using a strong auth/password).

This seems painfully sensationalized to me. Unrestricted OAuth redirect URIs paired with not requiring signed requests has been known to be dangerous. Google and Facebook both have configurable whitelists for OAuth redirect URIs.