Skip to content

    Healthcare

    Connect health data. Build workflows around it.

    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.

    30 minutes · free, no obligation

    Microsoft for Healthcare

    A data model with healthcare context.

    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.

    Microsoft: Provider data model(opens in a new tab)
    Concepts in the FHIR standard

    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
    1. Hospital / practice system

      Existing clinical system

    2. FHIR interface & mapping

      Map the clinical meaning

    3. 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.

    Client references

    Our work in healthcare.

    Medi24

    Telemedicine

    CRM operations and development

    CRM operations & development
    During the project, we operated and developed a Dynamics CRM 2016 On-Premises solution over several years.
    Customer Voice & integrations
    Documented APIs and integrations within the project's solution landscape.
    Development & delivery
    Traceable development and delivery processes with Azure DevOps.
    Read the full Medi24 reference
    ZAM.care AG

    CTO as a Service & Modern Workplace

    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.

    Read the ZAM.care reference
    Milan Pincar

    Milan Pincar

    CTO & Consultant · Theia Solutions

    Your contact

    What does your system landscape look like?

    Bring a specific workflow. We will discuss the data, clinical systems and responsibilities involved, and where Theia can support you.

    30 minutesMicrosoft TeamsFree, no obligation
    Talk to Milan

    Prefer email?info@theiasolutions.ch

    Explore other industries

    Cookie Settings

    Optional cookies and external services need your consent. Privacy Policy.