All Apps
Menu

Architecture Overview

Download Dynamics Dossier

Architecture Overview

System Architecture

Dynamics Dossier follows a modern, extensible architecture built specifically for Microsoft Dynamics 365 Business Central. The system is designed with modularity, scalability, and maintainability in mind.

High-Level Architecture

graph TB
    subgraph "Dynamics 365 Business Central"
        UI[User Interface Layer]
        BL[Business Logic Layer]
        DL[Data Layer]
        API[API Layer]
    end
    
    subgraph "Dynamics Dossier Extension"
        DD_UI[Dossier Pages & Cards]
        DD_BL[Dossier Business Logic]
        DD_DATA[Dossier Tables]
        DD_WF[Workflow Engine]
        DD_MED[Medical Dossier Module\nHL7 FHIR]
    end
    
    subgraph "Dependencies"
        AUTH[Q-Team App Authenticator]
        DND[Drag & Drop]
    end
    
    subgraph "External Systems"
        EMAIL[Email Systems]
        DOC[Document Storage]
        FHIR[FHIR / EPD Systems]
    end
    
    UI --> DD_UI
    BL --> DD_BL
    DL --> DD_DATA
    API --> DD_BL
    
    DD_BL --> AUTH
    DD_UI --> DND
    DD_BL --> DD_WF
    DD_UI --> DD_MED
    DD_BL --> DD_MED
    
    DD_BL --> EMAIL
    DD_BL --> DOC
    DD_MED --> FHIR

Core Components

1. Data Layer

The data layer stores all dossier-related data in structured modules:

Core Dossier Data

  • Dossier — Main dossier records
  • Dossier Type — Dossier categorisation and configuration
  • Dossier Setup — System-wide configuration

Workflow Data

  • Workflow Header — Workflow template definitions
  • Workflow Line — Individual workflow step configurations
  • Workflow Log — Workflow execution history

Supporting Data

  • Dossier Progress — Progress tracking per dossier
  • Dossier Content — Documents and content attached to dossiers
  • Department — Organisational structure

Medical Dossier Data (HL7 FHIR)

  • Medical Dossier — One medical dossier per contact
  • Medical Examination — Examination sessions
  • Medical Text Entry — Clinical text entries (Anamnesis, Physical Examination, etc.)
  • Medical Observation — Structured clinical observations following FHIR standards
  • Observation Components — Sub-values for multi-component observations (e.g. Blood Pressure)
  • Observation Types — Setup: observation type definitions with LOINC codes
  • Observation Units — Setup: UCUM measurement units
  • Observation Devices — Setup: measurement device registry
  • Reference Ranges — Normal value ranges per observation type, gender, and age

2. Business Logic Layer

The business logic layer handles all processing and rules for the application:

  • Dossier management — Creating, updating, and closing dossiers; enforcing business rules per dossier type
  • Workflow engine — Evaluating workflow conditions, creating tasks, and tracking progress
  • Medical dossier — Managing examinations, observations, and clinical text; FHIR round-trip support
  • Document handling — Storing and retrieving documents and content attached to dossiers
  • Confidentiality controls — Enforcing access restrictions for sensitive medical information
  • Notifications — Sending email alerts and reminders based on dossier events and deadlines
  • Licence management — Validating licence entitlements at runtime

3. User Interface Layer

The user interface provides role-specific pages and cards for all dossier operations:

  • Dossier Card — Primary interface for viewing and editing a dossier
  • Dossier List — Overview and search across all dossiers
  • Medical Dossier Card — Medical information, examinations, and observations
  • Dossier Content — Documents and attachments per dossier
  • Dossier Setup — System configuration for administrators
  • Contact Card extension — Medical and dossier information embedded on the contact
  • Role Centres — Dedicated role centres for Medical Inspectors and Dossier Managers

Data Model

Core Entity Relationships

erDiagram
    DOSSIER ||--o{ DOSSIER-CONTENT : contains
    DOSSIER }o--|| DOSSIER-TYPE : "has type"
    DOSSIER }o--|| CONTACT : "primary contact"
    DOSSIER ||--o{ WORKFLOW-LOG : "executes"
    
    DOSSIER-TYPE ||--o{ WORKFLOW-HEADER : "uses"
    WORKFLOW-HEADER ||--o{ WORKFLOW-LINE : contains
    WORKFLOW-LOG }o--|| WORKFLOW-HEADER : "follows"
    
    CONTACT ||--o{ DOSSIER : "can have multiple"
    
    DOSSIER {
        string No PK
        string Primary-Contact-No FK
        string Dossier-Type-Code FK
        string Description
        date Start-Date
        date End-Date
        enum Status
        text Comments
    }
    
    DOSSIER-TYPE {
        string Code PK
        string Description
        boolean Sickness
        duration Duration-of-Dossier
        enum Category
    }
    
    CONTACT {
        string No PK
        string Name
        string Type
        text Address
    }

Field-Level Architecture

Primary Key Strategy

  • Dossier Numbers: Generated using Business Central Number Series
  • Sequential IDs: Used for log entries and progress tracking
  • Code Fields: Used for setup and configuration tables

Data Classification

All fields are properly classified according to Business Central data classification requirements:

  • CustomerContent: Business data that can contain customer information
  • EndUserIdentifiableInformation: Data that can identify end users
  • SystemMetadata: System-generated administrative data

Integration Architecture

Authentication & Security

  • Integrates with Business Central permission system
  • Uses Q-Team App Authenticator for enhanced security
  • Role-based access control for sensitive medical data
  • Field-level security for confidential information

External System Integration

Email Integration

  • Queue-based email processing
  • Template-based email generation
  • Automatic notification system
  • Error handling and retry mechanisms

Document Management

  • Integration with SharePoint/OneDrive
  • Local file system support
  • Document versioning and history
  • Drag & drop functionality via dedicated extension

Medical Systems

  • Configurable medical system connections
  • Data import/export capabilities
  • Patient number matching
  • Compliance with medical data standards

Workflow Engine

Workflow Architecture

The workflow system provides flexible, configurable process automation:

Components

  1. Workflow Headers - Define workflow templates
  2. Workflow Lines - Individual workflow steps
  3. Workflow Log Entries - Track execution and progress

Workflow Types

  • Time-based: Trigger after specified durations
  • Event-based: Trigger on dossier state changes
  • Manual: User-initiated workflow steps

Process Flow

flowchart TD
    A[Dossier Created] --> B{Workflow Assigned?}
    B -->|Yes| C[Initialize Workflow]
    B -->|No| D[Standard Processing]
    
    C --> E[Create Initial Tasks]
    E --> F[Monitor Progress]
    F --> G{Step Complete?}
    G -->|No| H[Send Reminders]
    H --> F
    G -->|Yes| I[Next Step]
    I --> J{More Steps?}
    J -->|Yes| F
    J -->|No| K[Complete Workflow]
    
    K --> L[Update Dossier Status]
    D --> L

Performance Considerations

Optimization Strategies

  • Indexed Fields: Strategic indexing on frequently queried fields
  • FlowFields: Calculated fields for real-time data aggregation
  • Filtered Views: Reduce data load through smart filtering
  • Caching: Temporary storage of frequently accessed data

Scalability Features

  • Batch Processing: Handle large volumes of dossiers efficiently
  • Background Processing: Non-blocking operations for long-running tasks
  • Pagination: Efficient handling of large result sets
  • Resource Management: Optimized memory and database usage

Security Architecture

Data Protection

  • Field-Level Security: Restrict access to sensitive fields
  • Record-Level Security: Control access to entire dossiers
  • Audit Trail: Complete history of all changes
  • Data Encryption: Sensitive data encryption at rest and in transit

Compliance Features

  • GDPR Compliance: Data protection and right to be forgotten
  • Medical Data Compliance: Healthcare data protection standards
  • Role-Based Access: Granular permission control
  • Data Retention: Configurable data retention policies

Deployment Architecture

Application Structure

Dynamics Dossier
├── Core Tables (Dossier, Setup, Types)
├── Workflow Engine (Headers, Lines, Logs)
├── Business Logic (Management Codeunits)
├── User Interface (Pages, Extensions)
├── Integration (APIs, External Connections)
└── Security (Permissions, Entitlements)

Dependencies

  • Q-Team App Authenticator: Authentication services
  • Drag & Drop Extension: Enhanced UI capabilities
  • Base Application: Microsoft Dynamics 365 Business Central

Next: Learn about installation and setup of Dynamics Dossier.