Month: October 2013

Recon takes an analytical look behind select developments in healthcare

Marrying into the right family: the bets underlying United’s revenue cycle management joint venture with Dignity Health

Market for outsourced revenue cycle management could be big The revenue cycle management (RCM) vendor industry is about $2.0B for hospitals and $11 billion for physicians today. The market is constrained because most providers do their own RCM. Vendors only have a ~10% penetration among hospitals and a 25% penetration among physicians (implying that the potential combined hospital and physician market is $60-70B). However, RCM as a function is getting more complex and outsourcing could quickly start looking more attractive: Value-based contracting models raising the stakes in documentation, reporting, benchmarking,

Read More

Declining value of the EMR walled garden? An emerging signpost from Cleveland Clinic

Quick follow-up to our post about the Epic-eClinicalWorks deal: Today’s Healthcare Informatics has an interview with Martin Harrison, CIO of Cleveland Clinic, was asked what is the biggest strategic IT challenge right now. His answer? The challenge element is partly being driven by the complexity of the challenges in this value-driven world. So all the care providers belonging to this collaborative probably will not belong to the same organization. So the biggest challenge to my mind right now is the effectiveness of interoperability. We talk about it a lot, but

Read More

Change in tactics or change of heart? Speculations on the eClinicalWorks–Epic interoperability announcement

Epic is famous for its intense focus on interoperability across its own systems coupled with its conservatism regarding interoperability with other EMRs. In 2012, KLAS said Epic has the “deepest data sharing of all the vendors” across its own practice and hospital EMRs (see this example in which Cleveland Clinic and neighboring system MetroHealth — both on Epic — have put interoperability in place). But when it comes to non-Epic systems, customers must work through defined “exits” to the Epic system (“we don’t let anyone write on top of our

Read More
Search
We use cookies
This website collects cookies to deliver better user experience and to analyze our website traffic and performance; we never collect any personal data or target you with ads.