Free EMR Newsletter Want to receive the latest news on EMR, Meaningful Use, ARRA and Healthcare IT sent straight to your email? Join thousands of healthcare pros who subscribe to EMR and EHR for FREE!

Enterprise EHR Vendors Consolidating Hold On Doctors

Posted on September 9, 2016 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 FierceHealthcare.com 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.

When I stumbled across a recent study naming the EHRs most widely used by physicians, I don’t know what I expected, but I did not think big-iron enterprise vendors would top the list. I was wrong.

In fact, I should have guessed that things would play out this way for giants like Epic, though not because physicians adore them. Forces bigger than the Cerners and Epics of the world, largely the ongoing trend towards buyouts of medical groups by hospitals, have forced doctors’ hand. But more on this later.

Context on physician EHR adoption
First, some stats for context.  To compile its 2016 EHR Report, Medscape surveyed 15,285 physicians across 25 specialties. Researchers asked them to name their EHR and rate their systems on several criteria, including ease of use and value as a clinical tool.

When it came to usage, Epic came in at first place in both 2012 and 2016, but climbed six percentage points to 28% of users this year. This dovetails with other data points, such that Epic leads the hospital and health system market, according to HIT Consultant, which reported on the study.

Meanwhile, Cerner climbed from third place to second place, but it only gained one percentage point in the study, hitting 10% this year. It took the place of Allscripts, which ranked second in 2012 but has since dropped out of the small practice software market.

eClinicalWorks came in third with 7% share, followed by NextGen (5%) and MEDITECH (4%). eClinicalWorks ranked in fifth place in the 2012 study, but neither NextGen nor MEDITECH were in the top five most used vendors four years ago. This shift comes in part due to the disappearance of Centricity from the list, which came in fourth in the 2012 research.

Independents want different EHRs
I was interested to note that when the researchers surveyed independent practices with their own EHRs, usage trends took a much different turn. eClinicalWorks rated first in usage among this segment, at 12% share, followed by Practice Fusion and NextGen, sharing the second place spot with 8% each.

One particularly striking data point provided by the report was that roughly one-third of these practices reported using “other systems,” notably EMA/Modernizing Medicine (1.6%), Office Practicum (1.2%) and Aprima (0.8%).

I suppose you could read this a number of ways, but my take is that physicians aren’t thrilled by the market-leading systems and are casting about for alternatives. This squares with the results of a study released by Physicians Practice earlier this year, which reported that only a quarter of so of practices felt they were getting a return on investment from their system.

Time for a modular model
So what can we take away from these numbers?  To me, a few things seem apparent:

* While this wasn’t always the case historically, hospitals are pushing out enterprise EHRs to captive physicians, probably the only defensible thing they can do at this point given interoperability concerns. This is giving these vendors more power over doctors than they’ve had in the past.

* Physicians are not incredibly fond of even the EHRs they get to choose. I imagine they’re even less thrilled by EHRs pushed out to them by hospitals and health systems.

* Ergo, if a vendor could create an Epic- or Cerner-compatible module designed specifically – and usably — for outpatient use, they’d offer the best of two worlds. And that could steal the market out from under the eClinicalWorks and NextGens of the world.

It’s possible that one of the existing ambulatory EHR leaders could re-emerge at the top if it created such a module, I imagine. But it’s hard for even middle-aged dogs to learn new tricks. My guess is that this mantle will be taken up by a company we haven’t heard of yet.

In the mean time, it’s anybody’s guess as to whether the physician-first EHR players stand a chance of keeping their market share.

Department Of Defense (DOD) EHR Delayed By “Aggressive Schedule”

Posted on September 7, 2016 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 FierceHealthcare.com 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.

The Department of Defense has announced that it will be delaying the deployment of its massive EHR project, citing issues identified in testing and an “aggressive schedule” as reasons for the decision. If the DoD and its vendors are right, the deployment delay will be a negligible few months, though one setback to an effort of this kind usually to leads to another.

On the plus side, military officials said, they’ve made significant progress with developing user-approved workflows, interfaces and technical integration of its legacy system to date. But they’re not ready to engage in the concurrent system configuration, cybersecurity risk management, contractor and government testing yet.

The deployment has been in the works for little over a year. Last summer, the DoD Healthcare System Modernization Program awarded the $4.3 billion contract to upgrade its existing Military Health System EHR to a group including Cerner and defense contracting firm Leidos. The Cerner/Leidos team won out against some tough competition, including a partnership including Allscripts, HP and Computer Sciences Corp. and an Epic/IBM bid.

The ten-year project is about as large and complex an integration effort as you’re likely to see even by Cerner standards. The effort will connect healthcare systems located at Army hospitals, on Naval vessels, in battlefield clinics across the globe. MHS GENESIS will bring all of this data — on active-duty members, reservists, and civilian contractors — into a single open, interoperable platform. The new platform should serve 9.5 million military beneficiaries in roughly 1,000 locations.

The project is upgrading the DoD from AHLTA (Armed Forces Health Longitudinal Technology Application), which has been in place since 2004. AHLTA has many flaws, though none that would surprise a health IT expert. (For example, when patients are referred to non DoD providers, the data is not captured and integrated into the system.)

Ultimately, it won’t matter very much whether the DoD manages to kick off its project on time. The larger question, here, is whether over the course of a 10-year integration effort, the project becomes, as Forbes columnist Loren Thompson puts it, “obsolete before it’s even built” and incapable of the data sharing that fueled its conception. Of course, any systems integration with a long timeline faces that risk, but not all industries are changing as quickly as healthcare.

The truth is, this is arguably an awkward time for any large entity to be making big interoperability plans. I’d argue that while there are more initiatives than ever aimed at the problem, they’ve effectively made things worse rather than better. After all, the unfortunate truth is that the more people compete over interoperability standards, the less possible data sharing becomes.

A Circular Chat On Healthcare Interoperability

Posted on September 6, 2016 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 FierceHealthcare.com 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.

About a week ago, a press release on health data interoperability came into my inbox. I read it over and shook my head. Then I pinged a health tech buddy for some help. This guy has seen it all, and I felt pretty confident that he would know whether there was any real news there.

And this is how our chat went.

—-

“So you got another interoperability pitch from one of those groups. Is this the one that Cerner kicked off to spite Epic?” he asked me.

“No, this is the one that Epic and its buddies kicked off to spite Cerner,” I told him. “You know, health data exchange that can work for anyone that gets involved.”

“Do you mean a set of technical specs? Maybe that one that everyone seems to think is the next big hope for application-based data sharing? The one ONC seems to like.” he observed. “Or at least it did during the DeSalvo administration.”

“No, I mean the group working on a common technical approach to sharing health data securely,” I said. “You know, the one that lets doctors send data straight to another provider without digging into an EMR.”

“You mean that technology that supports underground currency trading? That one seems a little bit too raw to support health data trading,” he said.

“Maybe so. But I was talking about data-sharing standards adopted by an industry group trying to get everyone together under one roof,” I said. “It’s led by vendors but it claims to be serving the entire health IT world. Like a charity, though not very much.”

“Oh, I get it. You must be talking about the industry group that throws that humungous trade show each year.” he told me. “A friend wore through two pairs of wingtips on the trade show floor last year. And he hardly left his booth!”

“Actually, I was talking about a different industry group. You know, one that a few top vendors have created to promote their approach to interoperability.” I said. “Big footprint. Big hopes. Big claims about the future.”

“Oh yeah. You’re talking about that group Epic created to steal a move from Cerner.” he said.

“Um, sure. That must have been it,” I told him. “I’m sure that’s what I meant.”

—-

OK, I made most of this up. You’ve got me. But it is a pretty accurate representation of how most conversations go when I try to figure out who has a chance of actually making interoperability happen. (Of course, I added some snark for laughs, but not much, believe it or not.)

Does this exchange sound familiar to anyone else?

And if it does, is it any wonder we don’t have interoperability in healthcare?

New ONC Scorecard Tool Grades C-CDA Documents

Posted on August 2, 2016 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 FierceHealthcare.com 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.

The ONC has released a new scorecard tool which helps providers and developers find and resolve interoperability problems with C-CDA documents. According to HealthDataManagement, C-CDA docs that score well are coded with appropriate structure and semantics under HL7, and so have a better chance of being parseable by different systems.

The scorecard tool, which can be found here, actually offers two different types of scores for C-CDA documents, which must be uploaded to the site to be analyzed. One score diagnoses whether the document meets the requirements of the 2015 Edition Health IT Certification for Transitions of Care, granting a pass/fail grade. The other score, which is awarded as a letter grade ranging from A+ to D, is based on a set of enhanced interoperability rules developed by HL7.

The C-CDA scorecard takes advantage of the work done to develop SMART (Substitutable Medical Apps Resusable Technologies). SMART leverages FHIR, which is intended to make it simpler for app developers to access data and for EMR vendors to develop an API for this purpose. The scorecard, which leverages open-source technology, focuses on C-CDA 2.1 documents.

The SMART C-CDA scorecard was designed to promote best practices in C-CDA implementation by helping creators figure out how well and how often they follow best practices. The idea is also to highlight improvements that can be made right away (a welcome approach in a world where improvement can be elusive and even hard to define).

As SMART backers note, existing C-CDA validation tools like the Transport Testing Tool provided by NIST and Mode-Driven Health Tools, offer a comprehensive analysis of syntactic conformance to C-CDA specs, but don’t promote higher-level best practices. The new scorecard is intended to close this gap.

In case developers and providers have HIPAA concerns, the ONC makes a point of letting users know that the scorecard tool doesn’t retain submitted C-CDA files, and actually deletes them from the server after the files have been processed. That being said, ONC leaders still suggest that submitters not include any PHI or personally-identifiable information in the scorecards they have analyzed.

Checking up on C-CDA validity is becoming increasingly important, as this format is being used far more often than one might expect. For example, according to a story appearing last year in Modern Healthcare:

  • Epic customers shared 10.2 million C-CDA documents in March 2015, including 1.3 million outside the Epic ecosystem (non-Epic EMRs, HIEs and the health systems for the Defense and Veterans Affairs Departments)
  • Cerner customers sent 7.3 million C-CDA docs that month, more than half of which were consumed by non-Cerner systems.
  • Athenahealth customers sent about 117,000 C-CDA documents directly to other doctors during the first quarter of 2015.

Critics note that it’s still not clear how useful C-CDA information is to care, nor how often these documents are shared relative to the absolute number of patient visits. Still, even if the jury is still out on their benefits, it certainly makes sense to get C-CDA docs right if they’re going to be transmitted this often.

CommonWell and Healthcare Interoperability

Posted on June 27, 2016 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

UPDATE: In case you missed the live interview, you can watch the recorded interview on YouTube below:

2016 June - CommonWell and Healthcare Interoperability-headshots

For our next Healthcare Scene interview, we’ll be sitting down with Scott Stuewe, Director at Cerner Network and Daniel Cane, CEO & Co-Founder at Modernizing Medicine on Wednesday, June 29, 2016 at 3 PM ET (Noon PT). Cerner was one of the Founding Members of CommonWell and Modernizing Medicine just announced they were joining CommonWell. No doubt these diverse perspectives will provide an engaging discussion about the work CommonWell is doing to improve healthcare data sharing.

You can join my live conversation with Scott Stuewe and Daniel Cane and even add your own comments to the discussion or ask them questions. All you need to do to watch live is visit this blog post on Wednesday, June 29, 2016 at 3 PM ET (Noon PT) and watch the video embed at the bottom of the post or you can subscribe to the blab directly. We’re hoping to include as many people in the conversation as possible. The discussion will be recorded as well and available on this post after the interview.

As we usually do with these interviews, we’ll be doing a more formal interview with Scott Stuewe and Daniel Cane for the first ~30 minutes of this conversation. Then, we’ll open up the floor for others to ask questions or join us on camera. CommonWell has become a big player in the healthcare interoperability space with most of the major EHR vendors involved, so we’re excited to learn more about what’s happening with CommonWell.

If you’d like to see the archives of Healthcare Scene’s past interviews, you can find and subscribe to all of Healthcare Scene’s interviews on YouTube.

Low-Profile HIT Player Leidos A Major Presence

Posted on June 1, 2016 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 FierceHealthcare.com 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.

Here where I live in the Washington, DC metro, federal IT is a major presence. Government IT consulting firms cluster along the area’s highways, and their executives own countless sprawling manses in the nearby suburbs. Those players include Leidos, a northern Virginia-based contracting firm with clients in IT, biomedical research and public health.

Though the firm has annual revenues of about $5.1 billion, and 18,000 employees, Leidos generates little fanfare here, despite a pedigree that includes a $5 billion partnership with Lockheed Martin’s Information Systems & Global Solutions segment that provides IT and intelligence services. However, Leidos is actually the new identity of long-established power player SAIC, which restructured and changed its name in late 2013 and has deep roots in national security and government IT contracting.

Most readers probably care little about government IT unless they service that industry. But I’d argue that we should all know about Leidos Health which, among other distinctions, was part of the team (Cerner, Leidos and Accenture Federal) that won the $4.3 billion plus contract to implement an EMR for the US Department of Defense last summer.

The DoD contract was hotly contested, by teams that included an Epic, IBM and Impact Advisors combination, but the Cerner-fronted team pulled off a win that may have saved the EMR vendor’s brand in a brutally competitive market. While it’s not clear what role Leidos played in the win, a DoD official was quoted as saying that a Cerner deal was projected to be “much cheaper,” and it’s possible Leidos support pricing played some role in its calculations. Perhaps more tellingly, DoD officials said cybersecurity considerations played a major role in the award, which plays to Leidos’ strengths.

Leidos Health hasn’t had unmitigated success. Most recently, it was part of a team scheduled to assist with a little-mentioned Epic EMR rollout for the US Coast Guard, which was cancelled due to “various irregularities.” The Coast Guard, which pulled the plug on the rollout in April, had been planning its EMR implementation since 2010.

However, this probably wasn’t much of a setback. And Leidos still delivers health IT services to several other federal agencies, including HHS and the Department of Veterans Affairs, including cybersecurity, health analytics, IT infrastructure and support and software development. And it works with the gamut of enterprise EMR vendors, including Allscripts, Cerner, Epic, McKesson and Meditech.

Truth be told, Leidos may not deserve the “quiet company” label given to it by Healthcare Informatics magazine, which recently dubbed it one the most interesting vendors of 2016. I’m sure Beltway execs who compete for federal contracts are well aware of Leidos Health, which had annual revenues of $593 million last year. And government IT decision-makers are well acquainted with parent company SAIC, a pillar of federal contracting which has been in the business since 1969. (In fact, SAIC president of technology and engineering Deborah Lee James was sworn in as Secretary of the Air Force in late 2013.)

That being said, the DoD deal has dramatically raised Leidos Health’s visibility in the broader health IT world. It will be interesting to see what it does going forward, don’t you think?

Will New Group Steal Thunder From CommonWell Health Alliance?

Posted on January 26, 2016 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 FierceHealthcare.com 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.

Back in March 0f 2013, six health IT vendors came together to announce the launch of the CommonWell Health Alliance. The group, which included Cerner, McKesson, Allscripts, athenahealth, Greenway Medical Technologies and RelayHealth, said they were forming the not-for-profit organization to foster national health data interoperability. (Being a cynical type, I immediately put it in a mental file tagged “The Group Epic Refused To Join,” but maybe that wasn’t fair since it looks like the other EHR vendors might have left Epic out on purpose.)

Looked at from some perspectives, the initiative has been a success. Over the past couple of years or so, CommonWell developed service specifications for interoperability and deployed a national network for health data sharing. The group has also attracted nearly three dozen HIT companies as members, with capabilities extending well beyond EMRs.

And according to recently-appointed executive director Jitin Asnaani, CommonWell is poised to have more than 5,000 provider sites using its services across the U.S. That will include more than 1,200 of Cerner’s provider sites. Also, Greenway Health and McKesson provider sites should be able to share health data with other CommonWell participants.

While all of this sounds promising, it’s not as though we’ve seen a great leap in interoperability for most providers. This is probably why new interoperability-focused initiatives have emerged. Just last week, five major HIT players announced that they would be the first to implement the Carequality Interoperability Framework.

The five vendors include, notably, Epic, along with athenahealth, eClinicalWorks, NextGen Healthcare and Surescripts. While the Carequality team might not be couching things this way, to me it seems likely that it intends to roll on past (if not over) the CommonWell effort.

Carequality is an initiative of The Sequoia Project, a DC-area non-profit. While it shares CommonWell’s general mission in fostering nationwide health information exchange, that’s where its similarities to CommonWell appear to end:

* Unlike CommonWell, which is almost entirely vendor-focused, Sequoia’s members also include the AMA, Kaiser Permanente, Minute Clinic, Walgreens and Surescripts.

* The Carequality Interoperability Framework includes not only technical specifications for achieving interoperability, but also legal and governance documents helping implementers set up data sharing in legally-appropriate ways between themselves and patients.

* The Framework is designed to allow providers, payers and other health organizations to integrate pre-existing connectivity efforts such as previously-implemented HIEs.

I don’t know whether the Carequality effort is complimentary to CommonWell or an attempt to eclipse it. It’s hard for me to tell whether the presence of a vendor on both membership lists (athenahealth) is an attempt to learn from both sides or a preparation for jumping ship. In other words, I’m not sure whether this is a “game changer,” as one health IT trade pub put it, or just more buzz around interoperability.

But if I were a betting woman, I’d stake hard, cold dollars that Carequality is destined to pick up the torch CommonWell lit. That being said, I do hope the two cooperate or even merge, as I’m sure the very smart people associated with these efforts can learn from each other. If they fight for mindshare, it’d be a major waste of time and talent.

Is Cerner Edging Up On Epic?

Posted on January 7, 2016 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 FierceHealthcare.com 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.

At Verona, Wisc.-based Epic Systems, growth is a way of life. In fact, the EMR vendor now boasts a workforce of 9,400, which is estimated to be an increase of 1,400 staffers over the past year.

Not only that, Epic is confident enough to build cute. Its Campus 4, dubbed the “Wizards Academy Campus,” is designed to resemble the fictional Hogwarts school of Harry Potter fame — or if you’re academically-minded, England’s Oxford University. When completed this summer, Campus 4 will add 1,508 offices and 2,000 parking spaces to the Epic headquarters.

I could go on with details of the Disneyland Epic is making of its HQ, but you get the picture. Epic leaders are confident that they’re only going to expand their business, and they want to make sure the endless streams of young eggheads they recruit are impressed when they visit. My guess is that the Epic campus is being designed as a, well, campus speaks to the idea of seeing the company as a home. When I was 25, unique surroundings would have worked on me!

In any event, if I was running the place, I’d be pretty confident too. After all, if its own stats are correct, Epic software is either being used by or installed at 360 healthcare organizations in 10 countries. The EMR giant also reports that its platform manages records for 180 million Americans, or about 55 percent of the entire U.S. population. It also reported generating a not-so-shabby $1.8 billion in revenues for 2014.

But a little-noticed report issued by analyst firm KLAS last year raises questions as to whether the Epic steamroller can maintain its momentum. According to the report, which admittedly came out about a year ago, “the competition between Epic and Cerner is closer than it has been in years past as customers determine their future purchasing plans,” analysts wrote.

According to KLAS researchers, potential EMR buyers are largely legacy customers deciding how to upgrade. These potential customers are giving both Cerner and Epic a serous look, with the remainder split between Meditech and McKesson upgrades.

The KLAS summary doesn’t spell out exactly why researchers believe hospital leaders are beginning to take Cerner as seriously as Epic, but some common sense possibilities occur to me:

The price:  I’m not suggesting that Cerner comes cheap, but it’s become clear over the years that even very solvent institutions are struggling to pay for Epic technology. For example, when traditionally flush-with-cash Brigham and Women’s Hospital undershoots its expected surplus by $53 million due (at least in part) to its Epic install, it’s gotta mean something.

Budget overruns: More often than not, it seems that Epic rollouts end up costing a great deal more than expected. For example, when New York City-based Health and Hospital Corp. signed up to implement Epic in 2013, the deal weighed in at $302 million. Since then, the budget has climbed to $764 million, and overall costs could hit $1.4 billion. If I were still on the fence I’d find numbers like those more than a little concerning. And they’re far from unique.

Scarce specialists:  By the company’s own design, Epic specialists are hard to find. (Getting Epic certified seems to take an act of Congress.) It must be quite nerve-wracking to cut a deal with Epic knowing that Epic itself calls the shots on getting qualified help. No doubt this contributes to the high cost of Epic as well.

Despite its control of the U.S. market, Epic seems pretty sure that it has nowhere to go but up. But that’s what Microsoft thought before Google took hold. If that comparison bears any weight, the company that will lap up Epic’s business and reverse its hold on the U.S. market probably already exists. It may not be Cerner, but Epic will face meaningful competition sometime soon.

The State of “Direct Project” in Healthcare

Posted on December 7, 2015 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

Update: Here is the recorded version of this Direct Project panel:

and here’s the video of the Q&A with the audience that followed:

As part of our ongoing series of Healthcare Scene interviews (see all our past Healthcare Scene interviews on YouTube), we’re excited to announce our next interview with an amazing panel of Direct Project experts, Julie Maas, Greg Meyer, and Mark Hefner happening Wednesday, December 9th at 3 PM ET (Noon PT).

As you can imagine, we’ll be digging into everything Direct Project (See CMS’ description of Direct Project for those not famliar with it). I’m excited to learn about ways Direct Project is starting to impact healthcare, but also to learn about the challenges it still faces and how they can be overcome. We’ll probably even dip into where Direct Project fits in with other projects like FHIR and EHR APIs getting all the attention.


Here are a few more details about our panelists:

You can watch our interview on Blab or in the embed below. We’ll be interviewing our panelists for the first 30-40 minutes of the blab and then we’ll open up to the audience for questions for the rest of the hour. We hope you can join us live. We’ll also share the recorded video after the event.

Could the DoD be SMART to Choose Cerner?

Posted on August 4, 2015 I Written By

Andy Oram is an editor at O'Reilly Media, a highly respected book publisher and technology information provider. An employee of the company since 1992, Andy currently specializes in open source, software engineering, and health IT, but his editorial output has ranged from a legal guide covering intellectual property to a graphic novel about teenage hackers. His articles have appeared often on EMR & EHR and other blogs in the health IT space. Andy also writes often for O'Reilly's Radar site (http://oreilly.com/) and other publications on policy issues related to the Internet and on trends affecting technical innovation and its effects on society. Print publications where his work has appeared include The Economist, Communications of the ACM, Copyright World, the Journal of Information Technology & Politics, Vanguardia Dossier, and Internet Law and Business. Conferences where he has presented talks include O'Reilly's Open Source Convention, FISL (Brazil), FOSDEM, and DebConf.

Even before the health IT world could react (with surprise) to the choice of a Cerner EHR (through its lead partner, Leidos Health Solutions Group) by the Department of Defense, rumors have it that Cerner beat out Epic through the perception that it is more open and committed to interoperability. The first roll-out they’ll do at the DoD is certain to be based on HL7 version 2 and more recent version 3 standards (such as the C-CDA) that are in common use today. But the bright shining gems of health exchange–SMART and FHIR–are anticipated for the DoD’s future.

Read more..