Data management

  • מאמר

Data management in Microsoft Cloud for Healthcare enables healthcare customers to develop low-code applications leveraging Microsoft Power Platform. It provides the health standards-based connectivity needed to gain access to the underlying health data estate.

Data management combines industry data models, industry standard data exchange, data mappings, and data connectors. These combined services provide a common platform for both Microsoft and our customers and partners to deliver enterprise-grade applications and improve time to value.

Data integration toolkit​

Note

Sync admin for FHIR has now been rebranded as Data integration toolkit.

The Data integration toolkit is a model-driven app for managing data interoperability tooling within Microsoft Cloud for Healthcare in a single location. This application provides IT admins a single set of administrative tooling for the interoperability and integration components that enable health data exchange in the Power Platform ecosystem. These capabilities include:

  • Guided setup for the Dataverse healthcare APIs and virtual health data tables
  • Entity and attribute map management and validation
  • External systems connectivity settings
  • Access to detailed diagnostic logging

Healthcare data model for Dataverse

The healthcare data model for Dataverse is a FHIR-aligned relational data model designed for Dataverse. The data model contains a subset of FHIR resources needed to power both Microsoft and partner healthcare business applications running on Dataverse.​ This common healthcare aligned data model provides the foundation for customers, partners, and independent software vendors (ISVs) building healthcare applications on Power Platform.

For more information on the data model, go to Data model overview.

Dataverse healthcare APIs

Dataverse healthcare APIs provide a built-in custom API that can accept bundles of FHIR resources for creating and updating records within Dataverse, including writeback of record updates to FHIR endpoints. The solution ships with prebuilt, configurable entity and attribute maps that define the mapping and transformation rules from a FHIR bundle resource to tables in the healthcare data model for Dataverse.

These APIs are another tool for building healthcare applications on Dataverse that use existing customer investments and knowledge around FHIR data exchange. They reduce the implementation time and infrastructure associated with bi-directional synchronization of FHIR data with Dataverse.

For more information, go to Dataverse healthcare APIs.

Virtual health data tables

Virtual health data tables enable building applications that work with or surface clinical data from the Azure Health Data Services FHIR API.​ They offer benefits such as avoiding data duplication, reducing cost of storage for users, and reducing latency and overhead associated with data synchronization.

Customers, partners, and ISVs can surface external data within the Dataverse application to build healthcare applications that extend past the usual Dataverse boundaries and reduce the complexity of dealing with FHIR data interchange.

For more information, go to Overview of virtual health data tables.

Azure Health Data Services

Azure Health Data Services unifies and standardizes data coming from diverse streams such as clinical, imaging, device, and unstructured data using the FHIR framework, DICOM services, and Azure IoT Connector for FHIR. They offer a managed set of APIs to facilitate rapid exchange of data and enable organizations to ingest and view protected health information (PHI) data.

For more information, go to Azure Health Data Services.

Reference architecture

Learn more about successful, robust cloud deployments in the Microsoft Cloud for Healthcare reference architecture center.

See also

What is Microsoft Cloud for Healthcare?
Set up and configure Microsoft Cloud for Healthcare