It is possible to pull Microsoft my analytics data via rest service since it is sensitive in nature so I am a bit skeptical if it's possible. any leads?
No, it's not possible to pull personal data due to privacy regulations, such as General Data Protection Regulation (GDPR). Please read this documentation for more information.
Related
In this answer
It is stated that "Log analytics does not capture any PII"
But here it states otherwise. When enabled auditing the username was not visible in Log Analytics but when the same data was sent to storage account it was available there. So is Log Analalytics really messing up with sensitive data?
It's recommended to follow Microsoft documentation and you can always stop collection of, obfuscate, anonymize, or otherwise adjust the data being collected to exclude it from being considered PII.
I have a general question related to the Azure FHIR server. Specifically, are there "technical" reasons to use it to store electronic health records (EHR)?
People told me major healthcare providers are using FHIR server to store EHR. I understand the business reason. But, technically, Azure cloud is HIPAA compliant. Anything stored and run in Azure is HIPAA compliant. So, if there are other ways such as SQL Server and Data Lake to store EHR, why do we have to store them in FHIR server?
Another reason I ask this question is that my team feels it is not efficient to store EHR via API calls, and it is difficult to query data in JSON format for reporting. So, they feel if Azure is HIPAA compliant they would prefer to store EHR in SQL Server or Data Lake for ease of data management. Both also provide role based security to limit unauthorized access with encryption.
No sure if I miss anything. Can anyone tell me the "technical" differences / advantages of storing EHR in FHIR server? Thanks in advance for your replies.
FHIR is primarily for health data interchange using more modern formats such as JSON, so you don't necessarily have to store the EHR data in FHIR format; you can instead have a layer that transforms your EHR data (in SQL or any other format you prefer) to FHIR format (JSON/XML/RDF) as and when needed.
Without a modern standard like FHIR, for the most part, it is very costly and time consuming to design and develop "interfaces" for healthcare data interchange;
Does that help clarify the "technical" need for FHIR?
Since ADC is provided by MS as SaaS to customers, is MS taking backups of the dataset and business glossary? If yes, how often and how can a customer get access to the backups for recovery purposes?
Unfortunately, there is no explicit backup/restore feature available for catalogs.
I would suggest you to vote up an idea submitted by another Azure customer.
https://feedback.azure.com/forums/906052-data-catalog/suggestions/33125845-azure-data-catalog-backup-feature
All of the feedback you share in these forums will be monitored and reviewed by the Microsoft engineering teams responsible for building Azure.
The closest way to achieve this with current functionality is to use the Azure Data Catalog REST API to extract all assets and persist them locally (and re import them manually later).
There is a sample application available that demonstrates this technique: Data Catalog Import/Export sample tool.
My organization wants to use Microsoft Text Analytics API for sentiment analysis. But my employer concern is that MS will be using that data for the live training of their sentiment engine. Is this the case?
See the Microsoft Trust Center for your answer.
How we manage your data
With Microsoft, you are the owner of your customer data.
Microsoft will use your customer data only to provide the services we
have agreed upon, and for purposes that are compatible with providing
those services. We do not share your data with our
advertiser-supported services, nor do we mine it for marketing or
advertising. If you leave the service, we take the necessary steps to
ensure the continued ownership of your data.
I've been researching the new unified API for office365 (graph.microsoft.com). Currently one can authenticate to it using an organisationalID and it will return information from emails-from-exchange/OneDrive4Business/Skype4Business(future)/calendar-from-exchange/exchange-contacts/etc...
The ability to surface such a plethora of information from one endpoint strikes me as being hugely valuable. In the future I'd really like to see information relating to Azure be surfaced in here also. For example, I'd love to use graph.microsoft.com to access lists of:
Azure storage accounts
Azure SQL DB servers and databases
Azure SQL DB firewall rules
Azure ML experiments
Countless other things
Are such things on the roadmap?
That is a great question, and it's great to see such enthusiasm around a single endpoint surfacing this information. We're not sure when Azure resource providers would be a part of the unified API, but it would be great to have them. There are a number of other teams who are very interested, and in general we've been pretty focused on user or person centric developer experiences here as you should be able to see from Yina Arena's //Build or Ignite presentations.