Public APIs: The Ultimate Silver Bomb

Congratulations! We have a new buzzword trending in health care IT - Public APIs.  You can say public APIs everywhere you used to say interoperability. You can also replace the very unprofessional “EHRs can’t talk to each other” with “EHRs lack public APIs”. People will nod in solemn agreement, and you will sound very informed and up to date on the latest developments, but just in case you encounter the quintessential child inquiring about the king’s rather scant wardrobe, here is a little background information.

(Very) Brief Introduction to Public APIs

API stands for application programming interface. Yes, interface, like the ones you have with your claims clearinghouse or your lab service provider or pharmacies. There are several ways to classify APIs, but for our discussion, we only need to consider two types of APIs: data APIs and services APIs. Data APIs are the simplest, and go something like this: software A sends a request for information to software B, and software B sends back the required information. Another way is for software A to send unsolicited, but previously agreed upon, information to software B, which will then send back a brief thank you note to software A.

For this exchange to work well, both software A and software B need to agree on a communication protocol and both should share a common understanding of the data. This common understanding of data is called a standard. Standards usually emerge from non-profit organizations dedicated to defining such standards, so for example, your claims interface uses something called ANSI X12 as its exchange standard, your lab interface uses the HL7 standard and your pharmacy interface uses something called NCPDP Script. Turns out you’ve been using APIs all along…

Service APIs are less common in health care, although if you look at the big picture, you could say that claims clearinghouses, labs and electronic prescribing are all really services. A simple example of a pure service API, where software A invokes a piece of code executed by software B, is a warfarin dosing calculator. Here software A sends a few agreed upon parameters (i.e. demographics, diagnosis, medications, INR, genomics, etc.) to software B. Software B performs a highly specialized calculation using those parameters and sends the result back to software A.

APIs are deemed to be public, or open, if the specifications are publicly available on the Internet for anyone to use. Health care APIs are not usually public, and formal business relationships need to be established before any one software developer can use another’s APIs. Google Maps APIs, for example, are said to be public, and so are MapQuest APIs. Note however, that although both serve basically the same purpose, they are not identical or interchangeable, and they are not validated or certified by a public agency. Both Google and MapQuest publish APIs to their mapping software, because it makes business sense for Google and MapQuest to do so.

Why Now?

JASON (as in Jason and the Argonauts) “is an independent scientific advisory group that provides consulting services to the U.S. government on matters of defense science and technology”. JASON was established in 1960 and it “has conducted studies under contract to the Department of Defense (frequently DARPA and the U.S. Navy), the Department of Energy, the U.S. Intelligence Community, and the FBI. Approximately half of the resulting JASON reports are unclassified.” The latest unclassified JASON report, A Robust Health Data Infrastructure, was commissioned by the Department of Health and Human Services (HHS) “to address the nationally significant challenge of developing comprehensive clinical datasets, collected in real world environments and accessible in real time, to support clinical research and to address public health concerns. These datasets could be used to guide clinical research, enhance medical decision-making, and respond quickly to public health challenges.”

The identity of JASON group members is secret, but rumor has it that these are some of the best and brightest scientists in the country and have over the years included several Nobel Prize winners. Although we don’t know who JASON is (or are, or however one refers to an anonymously unaccountable group of advisers), we should note that JASON was introduced to the subject by 18 expert briefers (8 from research and academia, 2 from Microsoft, 2 from IBM, 1 videogames developer, 1 from HIMSS, 1 from Deloitte, 1 from Kaiser, 1 from the White House and 1 from NQF). These representatives of medicine in America guided JASON to useful materials about information technology in health care, and actively participated in subsequent JASON discussions.

Similar to a report put forward by the President’s Council of Advisors on Science and Technology (PCAST) four years ago, JASON recommends that massive amounts of clinical data be collected at the point of care in a format suitable for extraction and combination with non-clinical data, to facilitate large scale “biomedical” research. To that end, HHS should actively engage in the creation of a national clinical data exchange architecture, based on nationally enforced standards and public APIs implementing those standards, and it should engage in these activities immediately and with the full force of a government agency. All the work done to date by HHS and its various initiatives resulted in inadequate proliferation of legacy health IT systems, which should be replaced now, and the aggressive migration path suggested by JASON begins with using those public APIs to extract and reformat clinical data from the vast repositories of legacy systems.

To date, HHS has spent over $25 billion of taxpayer money on partially reimbursing hospitals and physicians for the purchase of health IT systems. The much larger remaining costs of buying, implementing and using these systems is unknown. According to the CMS data, there are close to half a million clinicians and almost five thousand hospitals registered to participate in the Meaningful Use program, all using certified EHRs. Practically all these legacy EHRs have found ways to routinely exchange billing information, medications information, laboratory and imaging information, and more recently, referral information, immunizations information, generic messaging and a host of other document based notifications. This may be a great start for patient care delivered by people who can read, but it is totally and completely unacceptable for global biomedical research.

Faced with distinguished panels of scientists and technology experts stating that medical care is basically a gigantic experimental research project, and a government thoroughly convinced that peace, prosperity and good health are a direct function of the amount of information collected about each and single one of us, what should we do next? Should we immediately start ripping and replacing the brand new legacy systems in use by 80% to 90% of doctors and hospitals, because more powerful vendors would also like to make money in health care? Or should we take a subtler approach and slap a host of new regulations on legacy vendors forcing them to build and maintain a public API infrastructure to benefit all newcomers? After vigorously protesting the JASON findings, the government seems to have chosen the latter.

As Microsoft, IBM, Apple, Google, Facebook, Verizon, Salesforce (I kid you not), and everybody with a registered web address, join the health care feast, you should expect more colorful user interfaces, with interminable scrolling screens filled with extra-large fonts, big flat smoky colored buttons, eye-popping images and practically no functionality, as is fashionable in consumer websites. Most of this “software” will be geared towards your patients, the ultimate generators of marketable biomedical research data. Your current EHR vendor will be exhausting all its resources on creating, maintaining, testing, certifying and publishing mostly data APIs, but in the short term also services APIs, to pave the road for giant technology aggregators and tiny app builders.

If your certified EHR vendor is small to medium in size, expect it to fail and go bankrupt in the next few years. If your EHR vendor is large, expect it to be acquired and decimated by a global corporation. Barring a miracle, the passive-aggressive grumbling of physicians will finally subside, and the march to defragmentation of our “broken”, “stove-piped”, “siloed”, “walled-garden” system (a.k.a. competitive, free-market, let the best man win, type of system), will continue at a brisk pace.

For better or worse, we need to recognize that in this country health care is a business, a very large and profitable business. Perhaps it shouldn’t be, but it is. Health care is being told day in and day out that it should learn from other industries. Well then, how would the banking industry react to a requirement to create public APIs allowing wholesale extraction of fully identified transactional data of their customers and all the communications conducted around such transactions between the banks and their clients? What would be the response of airlines, car manufacturers, restaurants, or even Google and Apple, if the government demanded that they invest in infrastructure solely intended to help other companies put them out of business? Take a wild guess...

Is Meat Unhealthy? Part II

Over time, animals adapt to the foods they regularly consume.  This is how archaeologists can, for example, determine that Triceratops was an herbivore and Tyrannosaurus was a carnivore just by looking at the structure of the skeleton.  Adaptations to diet extend beyond skeletal structure, into digestion, metabolism, the brain, musculature, and other aspects of physical function.  What is our evolutionary history with meat?

Human Evolutionary History with Meat: 200 to 2.6 Million Years Ago

Mammals evolved from ancestral "mammal-like reptiles" (therapsids, then cynodonts) approximately 220 million years ago (Richard Klein. The Human Career. 2009).  Roughly 100 million years ago, placental mammals emerged.  The earliest placental mammals are thought to have been nocturnal shrew-like beasts that subsisted primarily on insects, similar to modern shrews and moles.  Mammalian teeth continued to show features specialized for insect consumption until the rise of the primates.

65 million years ago, coinciding with the evolution of the first fruiting plants, our ancestors took to the trees and became primates.  For most of the time between then and now, our ancestors likely ate the prototypical primate diet of fruit, seeds, leaves/stems, and insects (1).  Some primates also hunt smaller animals and thus eat the flesh of mammals, birds, reptiles, amphibians, and fish in addition to insects.  However, the contribution of non-insect meat to the diet is usually small.

Read more »

Vanilla Protein Bliss Balls

Bliss balls... Little bites of gooey, chewy, sweet deliciousness. Nut butters, superfood powders, dried fruit, seeds, grains. The possibilities are - quite literally - endless! So quick and easy to make, bliss balls is one of my favourite vegan treats. This batch was made yesterday, as a result of an intense craving for something sweet that struck, well, by noon. What can I say, my sweet tooth is unstoppable.

Not only are these delicious, they also pack a punch of raw protein from the Purple Balance protein powder that I like to use in my recipes. Hope you like them as much as I do! (Ehrm, make that 'did'. I'm afraid they're all gone now.)

Vanilla Protein Bliss Balls

Ingredients:

200 g soft/medjool/soaked dates (about 18 small)

3 tbsp oat or coconut flour

3 scoops (tbsp) Purple Balance Vanilla Protein (or vegan protein powder of your choice)

A pinch of pure vanilla powder

1 tbsp coconut oil

Coatings:

Raw Lucuma powder, carob/cacao powder and desiccated coconut

How to:

1. Put all ingredients in your food processor and blend until smooth.

2. Scoop the dough out with a spoon and roll into small balls.

3. Place in an airtight container in the fridge to let the coconut oil set, about 30 min-1 hour should suffice. (That is, if they're too soft to roll immediately after blending)

4. Coat the balls by placing a small amount of your powder of choice in a cupped hand, then use both hands to coat the balls, without putting too much pressure on them to keep the round shape.

5. Store in the fridge! 

Food Reward Friday

This week's lucky "winner"... the pumpkin spice latte!!

Read more »

Double Trouble Peanut Butter Banana Ice Cream

Another banana ice cream recipe that I hope you'll enjoy as much as I do! Prepare for DOUBLE trouble with peanuts both in the ice cream and on top...

Banana Ice Cream:

3 medium sized sliced and frozen bananas

1/4 cup of almond milk

1 1/2 tbsp all natural peanut butter

Pinch of salt

Peanut Butter Sauce:

1 tbsp peanut flour

3/4 tbsp almond milk

1 tsp liquid sweetener of choice (I use date syrup)

Optional: 1 tsp of cacao/cocoa and 1 tbsp almond milk (instead of 3/4) for a chocolate peanut butter sauce

How to:
1. Start by making your peanut butter sauce. In a small bowl (Well. I use a shot glass but that's just me.), mix all of the ingredients with a fork until no clumps remain. Easy peasy.
2. If you want your peanut butter to be evenly divided throughout the ice cream, thin it out with a  the almond milk first. Stir in little by little until you have a runny sauce. If you'd rather have peanut butter chunks, feel free to skip this step.
3. Place your bananas and a sprinkle of salt in your high speed blender/food processor and blend on high for about a minute or until there are no bigger pieces of banana left.
4. Carefully remove the top cap/lid on your nana ice cream maker and slowly, as you blend, pour in the almond milk and peanut butter mixture. (Or each of them separately if you skipped the second step.)
5. Blend until you have a wonderfully creamy and smooth consistency. Stop to scrape down the sides if necessary.
6. Spoon up in a bowl/jar, top with the peanut butter sauce and a handful of crushed peanuts and cacao nibs if you so wish, eat and enjoy!

Is Meat Unhealthy? Part I

Introduction

At Dr. McDougall's Advanced Study Weekend, I had the opportunity to hear a number of researchers and advocates make the case for a "plant-based diet", which is a diet containing little or no animal foods.  Many of them voiced the opinion that animal foods contribute substantially to the primary killers in the US, such as heart disease and cancer.  Some of the evidence they presented was provocative and compelling, so it stimulated me to take a deeper look and come to my own conclusions.

No matter what the health implications of meat eating turn out to be, I respect vegetarians and vegans.  Most of them are conscientious, responsible people who make daily personal sacrifices to try to make the world a better place for all of us.

My Experience with Vegetarian and Vegan Diets

Read more »

Strawberry Vanilla Nana Ice Cream

So. Only today did I realise that there is not a single banana ice cream recipe to be found on this blog.   This shan't be the case on a blog owned by nana ice cream's no. 1 fan! (Me!) Please accept my sincerest apologies. Let's just pretend this recipe has been here since the dawn of time lalala. Just smile and wave boys, just smile and wave. 

÷

I may not be the most dedicated blogger but I do care a lot about my followers and I appreciate you all so incredibly much, you literally have no idea. In the future there will be a thorough step-by-step guide uploaded on here but for now, this will have to do. Hope you enjoy the recipe!

Strawberry Vanilla Nana Ice Cream (Finally!)

Serves: 1

Cook time: 5 minutes, tops.

Ingredients:

3 medium sized ripe bananas, sliced and frozen

1/4 cup unsweetened almond milk

1/2 tsp vanilla extract or a pinch of pure vanilla powder

1/2 cup frozen strawberries

How to:

1. Place all of the ingredients except for the almond milk in your food processor/high speed blender.

2. Blend on high until there are only very small pieces of frozen fruit left. This should take about a minute or so.

3. Now, carefully remove the small top lid/cap on your food processor/blender and slowly pour in the almond milk, while blending on high.

4. Watch magic happen. (Ok, you may have to stop and scrape down from the sides a few times but seriously, let the blender do the job. No need to poke around in there too much.)

5. Once the ice cream has turned into a creamy, luscious swirl of amazingness, turn the blender off, spoon up in a jar, bowl or whatever floats your boat, top with coconut chips and devour immediately!

Obesity → Diabetes

A new study adds to the evidence that the prevalence of type 2 diabetes is rapidly increasing in the US, and our national weight problem is largely to blame.

The Centers for Disease Control (CDC) currently estimates that a jaw-dropping 33 percent of US men, and 39 percent of US women, will develop diabetes at some point in their lives (1).  Roughly one out of three people in this country will develop diabetes, and those who don't manage it effectively will suffer debilitating health consequences.  Has the risk of developing diabetes always been so high, and if not, why is it increasing?

In the same issue of the Annals of Internal Medicine as the low-carb vs. low-fat study, appears another study that aims to partially address this question (2).

Read more »

Pasta con Funghi

Pasta con Funghi

Yields one big serving or two small ones.

Cooking time: Approximately 25 min.

2/3 cup uncooked brown rice fusilli or pasta of your choice

Sauce:

1 1/2 cups sliced brown mushrooms

1/2 cup almond milk

2 tbsp vegan cream substitute (I used Oatly's oat cream)

1/2 tbsp brown rice flour or thickening of your choice

1 tsp dijon mustard

1/2 tsp vegetable bouillon powder

1 tbsp nutritional yeast

Salt, pepper and lemon juice (optional) to taste

Start by bringing a pot of water to the boil, to cook your pasta in later.

How to:
1. Place all of the above ingredients except for the brown rice flour, mushrooms and nutritional yeast in a small saucepan.
2. Bring the mixture to the boil.
3. Stir, then lower the heat and let simmer for a few minutes.
4. Next, add the brown rice flour (preferably through a sieve) and whisk as you go.
5. Put the nutritional yeast in, whisk again and leave the sauce to thicken over low heat while you prepare your mushrooms. (At this stage you could put your pasta in the boiling water so the all the components can be ready at the same time!)
6. In a separate pan, lightly sauté the mushrooms to cook some of the liquid off. You might want to use a bit of cooking oil in the bottom unless you have access to a non-stick pan.
7. Fold the sautéed mushrooms into the sauce, have a taste and add more seasoning if it needs it. Let simmer for a few more minutes for a thicker consistency.
8. Toss the pasta in the sauce and top with a few sun-dried tomatoes if you'd like!

Enjoy!

Pumpkin Pie Pancakes

Pumpkin Pie Pancakes

Dry ingredients:

1/3 cup buckwheat flour

2 tbsp coconut flour

1 tsp baking powder

1 tsp pumpkin pie spice

Wet ingredients:

1 chia or flax egg (1 tbsp ground chia/flax seeds mixed with 3 tbsp water)

1 ripe banana, mashed

1/3 cup pumpkin purée 

3 tbsp almond milk

How to:
1. Start by preparing your chia egg. Grind the seeds either using a coffee blender or by hand with a mortar and pestle. Put the ground seeds in a small glass/bowl with 3 tbsp of water and whisk vigorously for 30 seconds or so to prevent clumping if you're using ground chia seeds. let sit and swell while you prepare the rest.
2. In a small bowl, mix all the dry ingredients with a fork until the baking powder is evenly divided.
3. Add the mashed banana, pumpkin puree and almond milk to the dry ingredients and stir until smooth.
4. Lastly, add in the chia/flax egg.
5. Let sit on the countertop for a few minutes (the batter should be THICK) and pre-heat a pan over low to medium heat.
6. Fry in a little coconut oil (unless you have a non-stick frying pan) on medium heat for a couple of minutes on each side.

Chocolate sauce:

2 tbsp plant-based yoghurt
1/2 tbsp cacao or cocoa powder
1/2 tbsp liquid sweetener of your choice (I used date syrup)

How to:
1. Simply mix all of the above with a fork/spoon until smooth. Pour on top of your pancake stack and decorate with a spoonful of plain yoghurt to create the cobweb pattern.

Enjoy!

Food Reward Friday

This week's lucky "winner"... profiteroles!!

Read more »

How Health Care Went Tabloid

Physicians, whether practicing medicine or not, should not be involved in clinical research. They should never be consulted on development of new drugs and medical devices. Doctors should not invent new treatments, and should never supervise clinical trials. They should not travel to or speak at conferences either, and they should banish all entrepreneurial notions out of their heads. If they insist on engaging in these activities, they should do it all for free, out of the goodness of their Hippocratic heart. A medical degree should immediately disqualify you from making money in the health care industry, which is a privilege reserved for technocrats, business executives and garden variety ex-political appointees.

Matt Bai, a veteran political journalist, wrote a new book titled “All The Truth Is Out: The Week Politics Went Tabloid”, where he is attempting to pinpoint the demise of serious political journalism to the Gary Hart scandal of 1987. If you recall, Mr. Hart, the all but certain Democratic candidate for President of the United States at that time, was railroaded out of politics by a romantic dalliance with, of all people, a very pretty pharmaceutical saleswoman. Matt Bai goes on to assert that since the Gary Hart affair “the entire ethos of political journalism has really changed. Because all the attention, all the kudos, is in taking someone down, is in finding hypocrisy”. Political journalism is arguably the heart of journalism, and as the heart goes, so goes the lesser journalistic body, health care reporting included.

This week, the CMS released a new "trove" of information about payments made by pharmaceutical companies and medical devices manufacturers to physicians and hospitals. The dataset includes millions of records ranging from payments of $0.00 (?) to millions of dollars. Some of the records specify the recipient while others do not, and most list the reason for payment. The data is preliminary at best and lots of cleanup activities are to be expected, since various recipients of funds have discovered errors large and small. A database like this one could eventually be useful for example for cross checking disclosures for published papers and education materials, or for people who are studying the financials of life science sectors of the economy. As expected though, the health care media saw things differently, because these data present ample opportunity to find hypocrisy and take someone down.

To put things in perspective, here is a brief summary of the data from an angle nobody saw fit to print. Below is a breakdown of amounts received by named physicians for the largest category of general payments, which includes food, travel, honoraria, consulting, royalties, licensing fees, and a host of other frivolous activities. In addition to this dataset, there are two smaller sets, one for research payments and one for ownership, or equity, in life science companies. And then there are three parallel datasets where the CMS decided to withhold the names of recipients due to uncertainties regarding data validity. We will disregard the list of payments made to unidentified entities, and concentrate on the largest dataset of payments to doctors. There are 358,686 named physicians in this dataset, and this is how total payments are distributed.

It looks like the median payment value is approximately $100, and 9 out of 10 docs who received anything, received less than $1,000 worth of goods, services and sometimes even cash. The big money went to a fraction of a percent at the top, mostly for royalties and licensing of things they designed or invented. I randomly picked a couple of these folks and looked them up on Google. The first one turned out to be a world famous vascular surgeon who invented multiple devices to fix aneurysms, pioneered various types of surgeries, and even got himself a Medal from the Society for Vascular Surgery. The second fellow is an orthopedic surgeon, also world famous who specializes in acute trauma and posttraumatic reconstruction of feet and ankles, and is the inventor of all sorts of plating and nailing systems for his specialty. He has more credentials than you can count and some very prestigious awards to go with that. At this point I stopped searching.

Now let’s look at how the New York Times reported this data release. The first article came one day before the data was published, giving us a heads up on the impending release, educating us on already existing resources, such as the subtly titled Dollars for Docs database, and plainly stating that “most physicians that are in private practice are touched in some way” by the industry. Yes, only private practice docs are “touched” by the scourge. The next article was just a kneejerk litany of complaints about the CMS database functionality, which by the way, I found to be surprisingly nice.

The third New York Times article was cleverly titled “Detailing Financial Links of Doctors and Drug Makers”, a title as innocent as the 1987 Miami Herald story “Miami woman is linked to Hart”. Linkage implies secretive impropriety about to be exposed. You don’t often see headlines saying “Fireman linked to saving baby from burning building”. The article itself is fraught with equally innocent language such as “doctors reaping over half a million dollars each”, “murky financial ties between physicians and the health care industry”, “lucrative arrangements are just some of the findings”, and in a surreal tale of the doomed, a righteous Cleveland Clinic physician is contesting his own listing because “he had spoken at the event but deliberately skipped the lunch”.

The most recent New York Times article is titled “Financial Ties Between Doctors and Health Care Firms Are Detailed”, just in case you missed the “detailing” pun the first time around. This article opens with a series of dramatic one sentence paragraphs. “For some doctors, treating patients isn’t the only way to make money”. You can pretty much hear the thriller music in your head. “A Michigan plastic surgeon was paid more than $300,000 to travel the world teaching doctors about new cosmetic products like a breast implant”. Impropriety is best served with female body parts. “The retired chief executive of the Mayo Clinic, who once helped write its conflict of interest policy, received more than $237,000 in compensation for serving on multiple corporate boards”. Wow, a retired doctor sits on corporate boards. Even the venerable Mayo Clinic has no ethics.

Following the boilerplate “murky financial ties between physicians and the health care industry”, we are informed that “the typical doctor earned only about $1,750 from August to December 2013”. Actually, the “typical” doctor barely eked out a hundred bucks worth of crappy conference food, unless he or she skipped lunch altogether, or maybe just refused the fake éclairs at the end, but math is a very flexible thing.  And on and on goes the litany of naming names, like a bad Seinfeld take on the McCarthy era.

The rationale for this abject witch hunt is that physicians who ingest pharmaceutically sponsored food are likely to return the favor and prescribe expensive brand name drugs instead of cheap generics. According to an IMS report from April 2014, generic medicines are now representing 86% of prescriptions, and have been steadily increasing over recent years. I seriously doubt that the numbers can get much better, and either way during these days of high deductibles and narrow formularies, doctors are rarely at liberty to prescribe brand name drugs when generics are available. Not to mention that as physicians are increasingly losing their independence, pharmaceutical companies are turning their efforts to hospitals, which are much better at financial wheeling and dealing. And yet, all the headlines and all the articles are about doctors, because taking down a person with a name and a face, using innuendos and baseless allegations, is so much easier than picking on a lawyered up corporation, and it is equally fulfilling, it seems.

Metabolic Effects of a Traditional Asian High-carbohydrate Diet

A recent study supports the notion that an 'ancestral diet' focused around high-starch agricultural foods can cultivate leanness and metabolic health.

John McDougall gave Christopher Gardner a hard time at the McDougall Advanced Study Weekend.  Dr. Gardner conducts high-profile randomized controlled trials (RCTs) at Stanford to compare the effectiveness of a variety of diets for weight loss, cardiovascular and metabolic health.  The "A to Z Study", in which Atkins, Zone, Ornish, and LEARN diets were pitted against one another for one year, is one of his best-known trials (1).

Dr. McDougall asked a simple question: why haven't these trials evaluated the diet that has sustained the large majority of the world's population for the last several thousand years?  This is an agriculturalist or horticulturalist diet based around starchy foods such as grains, tubers, legumes, and plantains, and containing little fat or animal foods.  Researchers have studied a number of cultures eating this way, and have usually found them to be lean, with good cardiovascular and metabolic health.  Why not devote resources to studying this time-tested ancestral diet?  I think it's a fair question.

Read more »