#HITsm T2: Geography should follow architecture behind DNS (how we organize the Internet). We pick a "home base" & the world finds us.
— Jared Alfson (@jalfson) September 5, 2014
I was absolutely intrigued by the idea of structuring the healthcare data architecture after DNS. As a techguy, I’m quite familiar with the structure of DNS and it has a lot of advantages (Check out the Wikipedia for DNS if you’re not familiar with it).
There are a lot of really great advantages to a system like DNS. How beautiful would it be for your data to be sent to your home base versus our current system which requires the patient to go out and try and collect the data from all of their health care providers. Plus, the data they get from each provider is never in the same format (unless you consider paper a format).
One challenge with the idea of structuring the healthcare data architecture like DNS is getting everyone a DNS entry. How do you handle the use case where a patient doesn’t have a “home” on the internet for their healthcare data? Will the first provider that you see, sign you up for a home on the internet? What if you forget your previous healthcare data home and the next provider provides you a new home. I guess the solution is to have really amazing merging and transfer tools between the various healthcare data homes.
I imagine that some people involved in Direct Project might suggest that a direct address could serve as the “home” for a patient’s health data. While Direct has mostly been focused on doctors sharing patient data with other doctors and healthcare providers, patients can have a direct address as well. Could that direct address by your home on the internet?
This will certainly take some more thought and consideration, but I’m fascinated by the distributed DNS system. I think we healthcare data interoperability can learn something from how DNS works.