HackerTrans
TopNewTrendsCommentsPastAskShowJobs

racking7

no profile record

comments

racking7
·4 năm trước·discuss
You should check out doing an Aerobic Threshold (AeT) test and an Anaerobic Threshold (AnT) test. I believe there are details on the Uphill Athlete site. But you should absolutely determine your AeT if you’re trying to base build in zone 2 (180-age is a good place to start, but it is likely lower). AnT is useful as well for higher zone training. It’s a more demanding test than AeT but will give you a more practical upper bound for speed workouts than max HR.
racking7
·4 năm trước·discuss
This is definitely true for cloud retail prices. However, this becomes not true in cases I've seen when there is an existing discount. Reserved instances, for example.
racking7
·4 năm trước·discuss
Just read the MBA/Founder books instead of getting an MBA. Find a new job where you'll be challenged and can put the MBA/Founder skills to use, then quit your current job.
racking7
·4 năm trước·discuss
FHIR provides a structure for communicating these data, but does not solve the hard problem in the parent comment about the massive heterogeneity of health care data across institutions (and even within institutions). The same messiness of the original raw data in the proprietary EHR data format can be replicated in FHIR. But at least the mess is available then in an open data format and a bit more regimented on canonical elements (i.e. things like effectiveDate/DateTime).

Have you used HAPI FHIR in production at any scale? Our experience is that it completely falls over under any reasonable strain. Try working with a few thousands patents and ~100M Observations and you will see HAPI work very poorly. It's great that HAPI is very feature rich on the API side--they've implemented most of the spec. But JPA and how they're using it is not a healthcare-scale technology. Google's (Spanner based) and Microsoft's (CosmosDB & SQL Sever based) FHIR API are better at scale but have far fewer features. I'm actually ok with that because the FHIR spec's query functionality is actually much more limited. Google's BigQuery integration really helps here. I'm interested to see where AWS is going with Health Lake. In talking with them I believe they have the best paradigm for their technical implementation.

It is a shame that the open source FHIR servers haven't been great. I think they will probably improve once a scalable paradigm for working with FHIR emerges.