Skip to content

Conversation

@cybernop
Copy link
Contributor

@cybernop cybernop commented Jan 6, 2026

No description provided.

Hendrejvr and others added 30 commits June 18, 2025 11:37
Bei Feldern, die im Target-Profil nicht vorhanden sind, wird nun unterschieden,
ob das Feld im Source-Profil effektiv deaktiviert ist (min=0, max=0,
mustSupport=false). In diesem Fall gilt die Konstellation als kompatibel.

Ist das Feld im Source hingegen potenziell belegt (min>0, max_num≠0 oder
mustSupport=true), wird die Feldzuordnung als inkompatibel klassifiziert.

Diese Änderung verhindert fälschliche INCOMPAT-Bewertungen in Fällen, in denen
ein Feld zwar formal existiert, aber im Source-Profil explizit ausgeschlossen ist.
…ppings for kbv.ita.erp version update from 1.3.2 to 1.4.0
- Added new mappings for various medication-related profiles, including:
  - Medication Category
  - Medication Ingredient Form
  - Prescription
  - Dosage Flag
  - Emergency Services Fee
  - Medication Compounding Instruction
  - Medication Ingredient Amount
  - Medication Packaging
  - Medication Packaging Size
  - Medication Vaccine
  - Multiple Prescription
  - Practice Supply Payor
  - Prescriber ID
  - Bundle
  - Composition
  - Medication Compounding
  - Medication Free Text
  - Medication Ingredient
  - Medication PZN
  - Practice Supply

- Each mapping includes source and target profiles with updated URLs and versions.
- All mappings marked as active and last updated timestamp set to "2025-11-10T11:37:21.432175".
- Introduced MappingEvaluator class to evaluate mappings with detailed compatibility assessments, warnings, and recommendations based on mapping actions.
- Created EvaluationResult enum for categorizing evaluation outcomes.
- Implemented EvaluationIssue and FieldEvaluation dataclasses to encapsulate evaluation details.
- Developed methods for evaluating various mapping actions (USE, EXTENSION, COPY_FROM, etc.) with appropriate issue handling.
- Added Pydantic models for structured representation of evaluation results and issues.
- Integrated mapping evaluation endpoints in the serve.py file for API access.
- Updated manual_entries.yaml to reflect changes in mapping actions for testing purposes.
- Implemented `manual_entries_id_mapping.py` for mapping legacy IDs to current mapping IDs based on FHIR resource types.
- Implemented `manual_entries_migration.py` for migrating legacy manual_entries.yaml formats to the current structure.
- Enhanced `serve.py` to support importing and migrating legacy manual entries via a new API endpoint.
- Added unit tests for both migration and ID mapping functionalities to ensure correctness and reliability.
- Created a new test file `test_manual_entries_migration.py` to validate the functionality of the `migrate_manual_entries` function.
- Implemented tests for various scenarios including migration of new format data, legacy format data, handling of empty legacy data, and error handling for invalid inputs.
- Updated `manual_entries.yaml` to include comprehensive entries with various actions and classifications for medication and practitioner data.
florianschoffke and others added 29 commits December 11, 2025 07:03
…tion

- Implemented MappingFieldResolver to recursively resolve profile references in mapping fields, handling fixedUri, fixedCanonical, type[].profile[], and type[].targetProfile[].
- Introduced a new endpoint to retrieve resolved mapping fields with configurable max depth and reference inclusion.
- Added comprehensive unit tests for MappingFieldResolver covering various scenarios including basic resolution, recursive resolution, cycle detection, max depth enforcement, and unresolved reference tracking.
- Enhanced profile resolution with caching and version handling.
@cybernop cybernop closed this Jan 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants