Apple has introduced health sectors in its new announcement to help someone is going to keep their health data on their iPhone again. Technically nothing new, but the new is not very important. Importantly, any consideration given to the problem of carrying data on health is good for change.
In my understanding, Apple switches from its own API support to specific APIs of Argonaut programs. Specific Argonaut APIs may be considered “standard” based on #FHIR in an earlier version – DSTU2. Your API API adoption is great. That’s not hard, it’s a lot. But this is great for Apple. And with Apple, we promote the concept of Benefit, and we get an incentive for support providers to support the Argonaut API.
The bad news is that it is DSTU2, and it carries the risk that APIs are frozen in a non-standard version of Fhir. I hope it does not happen in truth. I hope the development of FHIR will be a standard. The fact that they started DSTU2 and ignore the current STU3, is not good news for hope in normative Fhir in the future.
I understand what Apple has done is to take over the security and privacy of Sync for Science for SMART-on-Fhir. They expect that patients (their users and iPhone owners) travel to any of the compatible health care providers and interact with their portal to provide permission for the release of records for the iPhone application. This is a model defined as “Sync for Science”. This is a real unlucky name because the name is from the original domain. However, the solution is usually useful.
The advantages of health care providers are that they manage everything that has to do with the identity that they are the username (the password), which the patient will use on his portal, link them to this user name at his patient ID and permission manage the patient’s disclosure for a specific and independent future application on the iPhone.
Manage healthcare providers labels are usually through a one-time e-mail message to patients who are determined to be users and inmates. The person who logs in their portal, enters the password, and then creates the desired password. When it’s done, the healthcare provider relies on managing the username / password and knowing the strength of each patient who represents it.
Managing Health Care Providers Manage the approval of any system you have within. The permit should not be in a standard form or in a particular format or with a certain availability that exceeds your business needs. You only need to use the OAuth mechanism to associate the sample application that the patient uses with the patient’s consent (permission).
Finally, he publishes data for the patient himself in relation to the patient himself. As a business partner, there are no concerns.
The application only contains Apple in this case and also the author of this application. It is not necessary that they know the patient’s identity, but they will receive extremely sensitive data for the patients.
Why did Apple change everything?
So why is the fact that Apple is doing a lot of applications made before something big?
Apple has many people in the Apple system. Therefore, the effort that the current healthcare provider needs to support Apple is a better return. Even “call-to-call” related to the number of patients with health care providers (blast) is considered to be at the level of effort to do the job (even if it is high). Note that this is the motivation of earlier Apple architecture that uses the API, but the use of standards increases scalability.
Apple believes Apple has kept information and information about what Apple is doing. It differs from other major identifiers like Google or Yahoo. Apple people are special this way, but also Apple’s organization.