Central Terminology Services
Clinical Code Translation & European Healthcare Interoperability
Clinical Terminology Translation Processes
This system leverages a Central Terminology Server with a Master Value Catalogue uploaded via the admin console. Clinical codes from CDA and FHIR R4 resources are automatically translated to display human-readable terminology across European healthcare standards using terminology provided by clinical terminology specialists.
Process 1: Master Value Catalogue Upload
Healthcare administrators upload EU-CTS Master Value Catalogue files through the Django admin console, populating the terminology database with standardized clinical codes and multi-language translations.
ValueSetCatalogue"] -->|Upload MVC Excel| B["Django Admin Interface"] B -->|Parse Sheets| C["Excel Parser Service"] C -->|Extract Value Sets| D[("ValueSetCatalogue
Database Table")] C -->|Extract Concepts| E[("ValueSetConcept
Database Table")] C -->|Extract Translations| F[("ConceptTranslation
Database Table")] D -->|Store| G["Value Set Metadata
OID, Name, Version"] E -->|Store| H["Clinical Codes
Code, System OID, Status"] F -->|Store| I["Multi-Language Translations
EN, DE, FR, PT, etc."] G -.->|Links to| H H -.->|Links to| I style A fill:#007991,stroke:#005570,stroke-width:3px,color:#fff style B fill:#e3f2fd,stroke:#1976d2,stroke-width:2px style C fill:#e3f2fd,stroke:#1976d2,stroke-width:2px style D fill:#b2dfdb,stroke:#00695c,stroke-width:3px style E fill:#b2dfdb,stroke:#00695c,stroke-width:3px style F fill:#b2dfdb,stroke:#00695c,stroke-width:3px style G fill:#fff9c4,stroke:#f57f17,stroke-width:2px style H fill:#fff9c4,stroke:#f57f17,stroke-width:2px style I fill:#fff9c4,stroke:#f57f17,stroke-width:2px
Database Models
- ValueSetCatalogue: Master catalog of terminology value sets provided by clinical terminology specialists
- ValueSetConcept: Individual clinical codes with OIDs, display names, and status
- ConceptTranslation: Multi-language translations for cross-border healthcare
- TerminologySystem: Code system management with OID mappings
Process 2: Clinical Code Lookup from CDA/FHIR Resources
When processing patient clinical documents, the system extracts coded values from CDA or FHIR R4 resources and performs real-time lookups against the Master Value Catalogue to display human-readable terminology.
flowchart TB
A["CDA Document"] -->|Parse XML| C["Enhanced CDA Processor"]
B["FHIR R4 Bundle"] -->|Parse JSON| C
C -->|Extract Codes| D["Code Extraction
From Clinical Documents"]
D -->|Code + System OID| E{"Central Terminology
Service"}
E -->|Query| F[("Master Value
Catalogue Database")]
F -->|Match| G["ValueSetConcept"]
G -->|Get Translation| H["ConceptTranslation
Target Language: EN"]
H -->|Return Display| I["PSTableRenderer"]
I -->|Render| J["Patient Summary Display"]
E -.->|Cache 1 hour| K["Django Cache"]
J -->|Show Patient| M["Clinical Data Table
Human-Readable Terms"]
style A fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
style B fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
style C fill:#007991,stroke:#005570,stroke-width:3px,color:#fff
style D fill:#fff9c4,stroke:#f57f17,stroke-width:2px
style E fill:#ffc107,stroke:#ff8f00,stroke-width:4px
style F fill:#b2dfdb,stroke:#00695c,stroke-width:3px
style G fill:#c8e6c9,stroke:#388e3c,stroke-width:2px
style H fill:#c8e6c9,stroke:#388e3c,stroke-width:2px
style I fill:#e1bee7,stroke:#7b1fa2,stroke-width:2px
style J fill:#f8bbd0,stroke:#c2185b,stroke-width:2px
style K fill:#eeeeee,stroke:#757575,stroke-width:1px
style M fill:#4caf50,stroke:#2e7d32,stroke-width:3px,color:#fff
Code System Management
Supported code systems are determined by the Master Value Catalogue provided by clinical terminology specialists. The system dynamically supports any OID-based terminology system included in the uploaded catalogue.
European Healthcare Interoperability Standards
HL7 FHIR R4
Fast Healthcare Interoperability Resources
- Patient Summary (IPS): International Patient Summary v2.0.0
- Resources: Patient, Observation, MedicationStatement, Condition, AllergyIntolerance
- Profiles: Pregnancy status, EDD, Outcome observations
- Compliance: HL7 FHIR R4 specification with EU extensions
HL7 CDA R2
Clinical Document Architecture Release 2
- epSOS Patient Summary: European patient data exchange
- Sections: LOINC-coded clinical sections (allergies, medications, problems)
- Entries: SNOMED CT coded observations and acts
- Standards: CDA Level 3 with European extensions
PS Display Guidelines
European Patient Summary Presentation
- Rendering: Structured table format for clinical sections
- Terminology Display: Human-readable translations via CTS
- LOINC Sections: 48765-2 (Allergies), 10160-0 (Medications), 11369-6 (Immunizations)
- Accessibility: WCAG 2.1 AA compliance with semantic HTML
epSOS / eHDSI Standards
European Health Digital Services Infrastructure - MyHealth@EU
- Services: Patient Summary, ePrescription, eDispensation
- NCP Gateway: National Contact Point for cross-border exchange
- MyHealth@EU: Digital health services across EU member states
- Security: TLS mutual authentication, SAML assertions
Technical Implementation
Service Layer
-
CTSService- Terminology lookup wrapper -
TerminologyTranslator- Multi-language translation service -
EnhancedCDAProcessor- CDA document parsing with code extraction -
PSTableRenderer- Patient Summary table rendering with CTS integration
Features
- Real-time code lookup with 1-hour caching
- Fallback to hardcoded mappings if database lookup fails
- Multi-language support (EN, DE, FR, PT, etc.)
- Automatic code system detection via OID patterns
Current System Capabilities
- Master Value Catalogue Upload: Admin console integration for MVC Excel files
- CDA Code Extraction: Automatic extraction of SNOMED, LOINC, ICD-10 codes
- FHIR R4 Processing: Patient Summary bundle parsing with terminology lookup
- Real-Time Translation: Database-backed clinical code display
- Patient Summary Display: PS Display Guidelines compliant rendering
- Cross-Border Data Exchange: epSOS/eHDSI NCP Gateway integration