HIE Future is Bright – stepping into 2018

It is a complete summary of the standard section for medical care, privacy and safety. The framework for interpretation of the bright future of HIE comes from WISIN HIE. Sliding floors are now available. Use the following figure to illustrate the future of HIE. I love it, so I use it here.

It is an exciting point of view of what HIE offers today, where it is focused on future help. Other slot covers are described in this plan. This is determined by the bid amount, not just the volume. They have a part that focuses on the coordination of attention as the engine of these changes.

I wrote articles about each of these changes and more. Here they are

introduction
Directory ==> Automated
Center ==> focused on the patient
Multiple connections to point ==> A hub connection
Update @ will match patient notifications ==> if the patient is found elsewhere
Suppliers and payers work separately ==> Shared responsibilities for care management
Business Class API ==> FHIR API for document sharing
My perspective
Great reasons, as I see it:

The form of the document is very important, even if it is frustrating. This is especially true of rings and historical visits. Historical events require a complete context provided by the document model.
The good news is that FHIR has a document model and the FHIR model document contains a direct convertible data model.
FHIR-HIE documents can easily be sent.
The CDA will disappear, but will not disappear. It is very difficult to do.
In the future it will be more about using automation. Right now, we are focusing on implementing EHR or making data available to you. This first step is critical to interoperability. Now we need to focus more on data usage, because the way we use documents is not perfect and still does not work.
The good news is that FHIR is a good data API utilization. So there’s a great opportunity to improve the customer experience.
Business Class API ==> FHIR API for document sharing
FHIR has a subscription model to make API service more efficient and easy
FHIR can be assembled and disassembled without modification or loss
The future will join the country. There is a small number of very large networks today, but there is no connection between them. So, if you live in one part of the country where you need to visit doctors on different networks, you need to move the data manually.
The good news is that there are conversations and actions to join eHEX, CareQuality, CommonWell and others.
Not only technical, but also logical. We need comprehensive guidelines for vocabulary usage, document formats and care planning.
Bad news is that security and privacy are getting worse before they get better. It is a security statement and has no privacy. I do not see any of the future features of privacy abuse, but I’m worried that privacy is not inherently in the design. I am more concerned about security because the FHIR security model is still very low and the interface between FHIR and other worlds where data exists. This does not mean that OAuth is bad, but the use of OAuth for health care is not old, and OAuth health needs are more than OAuth gives.
The good news is that there will be plenty of time in the coming years to work here. All we need are bodies interested in joining open prototypes, tests, documentation and optimization.
It allows the patient’s future to focus more on care. GP is now doing everything. I do not think they like it, but it’s very hard to do anything. Some say that there is a commercial pressure to maintain control within the doctor’s office. I do not believe it is true. I think it’s harder. First, most patients are not technically familiar and are changing. Second, most patients are not good, so it is difficult to take the initiative. The most important thing is putting the community in the middle patient, and we still have no connected society.

Leave a Reply

Your email address will not be published. Required fields are marked *