Privacy and Security Considerations for the use of Open APIs for Patient Directed Exchange.

I was honored to host a round table in Washington DC at the second Forum of National Coordination Forum. The incident will take place next week from August 6 to 8. My session is scheduled for the afternoon of August 7th from 1:30 pm to 3:00 pm. The title of my panel is “Aspects of privacy and security when using open APIs for targeted delivery”.

This is the main vision of this picture:

We have given that the vision of human rights defenders and privacy is our goal, and the lack of standards is interruption. It’s not about talking about the goal, but focusing on what keeps major stakeholders from this vision.

General River
Before the tablet is the subject of “blockchain” and “identity and confidence”, then painting is a lighting cycle where some new techniques are presented.

Where Blockchain and lighting are clearly looking for a new and brilliant technology, I expect above all the identities / trusts and the other two.

I have invited committee members to represent huge organizations and organizations established. The reason I did that was because we did not listen to the public from this perspective. The main reason is the change of many variables because of the size of organizational changes. However, the size of this company can not make rapid changes. The size of an organization can make serious changes. The size of an organization requires some criteria to lead it. This standard should be mature and accepted by the partner.
Yes, sometimes a good organization needs. It just happens But it happens in the direction of the norm. For example, Apple takes FHIR.
What is the standard?
Where painting standards represent the broadest perspective. including:
Interoperability standards such as HL7, FHIR and IHE;
Vocabulary standards – such as HL7, SNOMED, ​​LOINC, IEEE, ISO, etc.
Implementation Guidelines – Assessing Specific Tools to Use Specific Solutions – by Argonaut, IHE or ONC;
Practice Standards: HIMSS’s professional community orientation, AMA and other professional medical associations;
UDRP: a legal framework that includes multiple strategies and sets appropriate uses and responsibilities;
Trust framework: A multilateral trust agreement with parties linking with a set of rules and failures by technology (Eg “CA”.) Is supported. For example, Sequoia DURSA or DirectTrust;
Implementation of the Reference: The software provided in the open source of a consensus panel as an application of a standard. How many open source FHIR projects;
Standardized interpretation of regulations such as HHS / ONC has been made, for example using e-mail to patients;
Rules and Rules: We expect all the possible regulations as possible, but sometimes also.
Ideal for privacy-oriented patients
Here are my blog posts on the privacy policy. I hope I can not handle these details, but I’m ready when needed. I think it’s important to understand all these principles, not just “consent”.

The principle of limiting gathering: It has limitations on the collection of personal data giving, and all such information must be obtained in a legitimate and appropriate manner and optionally with the knowledge or consent of the object data.
Quality data data: Personal data must be for purposes where they are used, be relevant and must be accurate, to the extent necessary to be carried out complete and timely.
The purpose of the standard principles: The goals imposed for personal data should be determined at the time of collection of data and subsequent use of the latest, which are limited to the achievement of goals or other purposes that are inconsistent with such purposes as any Opportunity provided to change the purpose.

Leave a Reply

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