For hospitals, practices and healthcare organisations: data models with patient and encounter context, FHIR integrations with clinical systems, and applications on Dynamics 365 and Power Platform.
The Microsoft for Healthcare Provider data model, previously called the Healthcare data model, is based on FHIR. It provides a customisable foundation in Dataverse for applications built with Dynamics 365 and Power Apps.
Patient, Practitioner, Encounter and CarePlan describe distinct clinical concepts: who receives care, which professional is involved, and which encounter and care plan are relevant? This grounds the modelling in your care practices. Together, we establish the tables, relationships and additional fields your workflow needs.
These terms link to the HL7 specification (FHIR R4).
Interfaces & integration
Exchange clinical data. Define responsibilities.
FHIR describes resources for exchanging health data. When planning an integration, we review available source interfaces, resource, profile and field mappings, synchronisation rules and data ownership.
A possible integration architecture
Hospital / practice system
Existing clinical system
FHIR interface & mapping
Map the clinical meaning
Dataverse
Dynamics 365 / Power Apps
Before implementation, we establish:
Source of truth & data selection
Which data is needed, who maintains it and which system remains authoritative?
FHIR version & CH Core
Which FHIR version and appropriate Swiss profiles apply to the specific project?
Roles, consent & logging
Who may read or change data, which consents are required and which access events are recorded?
Where needed, Azure Health Data Services offers a managed FHIR service. A Dataverse data model alone is not a FHIR server.
For ZAM.care, we provide CTO as a Service and manage the Microsoft 365 environment on an ongoing basis. We also delivered the migration to Microsoft 365.
Optional cookies and external services need your consent.We use cookies and external services (e.g. Google Maps) to provide you with the best experience on our website. For more information, see ourPrivacy Policy.