Interesting points related to Phynd from an article with EPIC's Judy Faulkner

By Thomas White | December 11, 2014

ynhh_map

In an article published in VentureBeat VentureBeat by Mark Sullivan, Judy Faulkner is interviewed about how open from an interoperability perspective Epic is. 

Some key points Ms. Faulkner makes: 

First, the government might help providers all over the country contribute a sort of “data exchange provider ID.” This would help providers identify each other, as well as to access information about how to request or send data. These provider IDs would be collected in a master “phone book” that would be distributed to all providers. 

I would suggest we need to think bigger than just a phone book on Direct Addresses, which is the implication, to a broader profile that includes all addresses, methods of communications, Direct Address and items such as “is the provider on the OIG exclusionary list.” And by the way, Phynd has a created a unique identifier on all licensed providers in the US. The provider profiles are accessible via the Phynd Network which contains verified master profiles on all providers with the broader information that I mention. 

Faulkner points out that an EHR vendor can easily create a directory of all the health providers that use its software for the sake of exchanging data. But it’s hard for that vendor to include health providers that don’t use its EHR in that directory, because there’s no existing business relationship there. 

We see the problem twofold: First, Ms. Faulkner is accurate that EHR vendor can create directories of Direct Addresses from their customer base, but the associated data (addresses and communication methods) that comes from the EHR is often incorrect, out of date information that overruns the provider data in the hospital systems. Sending the Direct address often creates a lot more issues for the health care institution. Secondly, that you need all providers in your database (not just the random make up of your vendors customers) to effectively clinically communicate, invoice appropriately and on-time and comply with MU and other requirements. Again, this is the Phynd Platform.

Just because data can be sent from vendor to vendor doesn’t mean it is good data. Hospitals need to protect their information and augment what they have with no content such as the Direct Address. Phynd treats hospital provider data as a strategic asset, managing the permissions and update process while tapping its national Phynd Network of verified profiles to add quality data to the health care institution on a per provider basis.

Thomas White

Written by Thomas White

Before founding Phynd, Tom co-founded Newscast Inc. and Vocada, Inc. With over 20 years of leadership experience, Tom has applied his knowledge in building software companies and creating new software categories from idea to large market share. He also serves as a mentor to the start-up accelerator Health Wildcatters.

Subscribe to our Blog