The Digital Health Biography: There’s A New Record In Town

Posted on January 18, 2017 I Written By

Anne Zieger is veteran healthcare consultant and analyst with 20 years of industry experience. Zieger formerly served as editor-in-chief of and her commentaries have appeared in dozens of international business publications, including Forbes, Business Week and Information Week. She has also contributed content to hundreds of healthcare and health IT organizations, including several Fortune 500 companies. Contact her at @ziegerhealth on Twitter or visit her site at Zieger Healthcare.

Few of us would argue that using EMRs is not a soul-sucking ordeal for many clinicians. But is there any alternative in sight? Maybe so, according to Robert Graboyes and Dr. Darcy Nikol Bryan, who are touting a new model they’ve named a “digital health biography.”

In a new article published in Real Clear Health, Graboyes, an economist who writes on technology, and Bryan, an OB/GYN, argue that DHBs will be no less than “an essential component of 21st century healthcare.” They then go on to describe the DHB, which has several intriguing features.

Since y’all know what doctors dislike (hate?) about EMRs, I probably don’t need to list the details the pair shares on why they generate such strong feelings. But as they rightly note, EMRs may take away from patient-physician communication, may be unattractively designed and often disrupt physician workflow.

Not only that, they remind us that third parties like insurance companies and healthcare administrators seem to get far more benefits from EMR content than clinicians do. Over time, data analytics efforts may identify factors that improve care, which eventually benefits clinicians, but on a transactional level it’s hard to dispute that many physicians get nothing but aggravation from their systems.

So what makes the DHB model different? Here’s how the authors lay it out:

* Patients own the DHB and data it contains
* Each patient should have only one DHB
* Patient DHBs should incorporate data from all providers, including PCPs, specialists, nurse practitioners, EDs, pharmacists and therapists
* The DHB should incorporate data from wearable telemetry devices like FitBits, insulin pumps and heart monitors
* The DHB should include data entered by patients, including family history, recollections of childhood illness, fears and feelings
* DHB data entry should use natural language rather than structured queries whenever possible
* The DHB should leverage machine learning to extract and organize output specific to specific providers or the patient
* In the DHB model, input and output software are separated into different categories, with vendors competing for both ends separately on functionality and aesthetics
* Common protocols should minimize the difficulty and cost of shifting from one input or output vendor to the other
* The government should not mandate or subsidize any specific vendors or data requirements
* DHB usage should be voluntary, forcing systems to keep proving their worth or risk being dumpted
* Clinical applications shouldn’t be subservient to reimbursement considerations

To summarize, the DHB model calls for a single, patient-controlled, universal record incorporating all available patient health data, including both provider and patient inputs. It differ significantly from existing EMR models in some ways, particularly if it separated data input from output and cut vendors out of the database business.

As described, this model would eliminate the need for separate institutions to own and maintain their own EMRs, which would of course stand existing health IT structures completely on their head. Instead of dumping information into systems owned by providers, the patient would own and control the DHB, perhaps on a server maintained by an independent intermediary.

Unfortunately, it’s hard to imagine a scenario in which providers would be willing to give up control to this great an extent, even if this model was more effective. Still, the article makes some provocative suggestions which are worth discussing. Do you think this approach is viable?