Directory Architecture
PROVIDER DATA PLATFORM
careMESH has the most advanced and comprehensive Provider Data Platform available. Learn what we’ve done, how we do it and why we feel confident in making this claim.
A Single Source of Truth
DATA SOURCES
Our data comes from many places. Some are public, some we have to pay for, and some of the data we collect ourselves:
CMS and HHS
State Medical Boards
DirectTrust*
Provider Groups and Health Systems
Payers
Direct contact with practices
*DirectTrust data is only available to our Direct Secure Messaging customers due to data sharing rules.
EXTRACT, TRANSFORM, LOAD
We Extract as soon as data is available.
We Transform data into native FHIR elements.
We Load data into each FHIR record we maintain.
Then the magic happens: Our advanced algorithms decide how to combine data, how to resolve conflicts, and which elements are current and accurate. From this, we create a Golden Record—the best possible view of a provider.
Contextualized Views
Not all customers have the same needs, so we created Contextualized Views.
Think of them as a personalized window into the provider database. These views can include your private data, a selection of our sources, your rankings, and custom data elements and search criteria.
Our customers specify exactly how their version of the directory works.
Native FHIR Architecture
We were the first to launch a national provider directory based on the FHIR standards.
Most organizations develop FHIR APIs on top of existing systems: their data architecture stays the same, but only the API conforms to the standard.
The problem with this approach is that the references between people, organizations, locations are often lost. And it’s not “future-proof”.
careMESH built a completely Native FHIR architecture
Resources, profiles, code systems, value sets, and extensions are all data elements saved as FHIR resources. And the resources (Practitioners, Practitioner Roles, Locations, Organizations, and Healthcare Services) are properly referenced to each other.
Why is this important? It makes adding new FHIR resources easy (such as for new Price Transparency data), makes for flexible integrations, and virtually guarantees the relationship between resources, so you find the data you need.
Click one of the buttons below for either the careMESH National Provider Directory FHIR Implementation Guide or a Developer Sandbox (using CMS data).
Data The Way You Want It
FHIR API
You can access data through standards-based APIs. But we’ve also created custom requests and responses.
Say you want to know everything about an Organization—who works for it, their qualifications, and their locations. One request, one response.
And we are happy to create new request/ response combinations to satisfy your use cases. Try it out!
User Interface
You might want to drop our lightweight directory UI into one of your web applications.
Our app is simple to drop into an iFrame. And it can be customized to include your own stylesheet and will, of course, include your Contextualized View of the data.
Here’s a version of the UI that only includes that data sourced from CMS.
DATA EXPORTS
Some of our customers require our data to be combined with theirs. In that case, we’ve developed the ability to export data using the Bulk FHIR standard.
You can request data through APIs. Or you can log into our web app, configure the export you are looking for, and download it as a CSV or JSON formatted file.
