Skip to content

Feature 13294 doctor declarations xml esante adapter#13332

Merged
raulbob merged 7 commits intodevelopmentfrom
feature-13294_doctor_declarations_xml_esante_adapter
Apr 16, 2025
Merged

Feature 13294 doctor declarations xml esante adapter#13332
raulbob merged 7 commits intodevelopmentfrom
feature-13294_doctor_declarations_xml_esante_adapter

Conversation

@raulbob
Copy link
Copy Markdown
Contributor

@raulbob raulbob commented Apr 15, 2025

Fixes #

raulbob added 6 commits April 15, 2025 15:04
…essageProcessingFlow

Refactored the lab message package and related classes to extract common functionality allowing doctor declaration to use the same implementation.
In the UI part the physician report has been replaced by doctor declaration which is a duplicate of lab message interface.

## API and Backend changes

Extracted common functionality from `AbstractLabMessageProcessingFlow` to :

- `AbstractMessageProcessingFlowBase`

Modified classes to allow sharing of funtinality:

- `AbstractProcessingFlow`
- `AbstractLabMessageProcessingFlow`
- `AutomaticLabMessageProcessor`

Moved the lab message specific objects to a common processing package:

- `EventValidationResult`
- `PersonAndPickOrCreateEntryResult`
- `PickOrCreateEventResult`
- `PickOrCreateSampleResult`

Modified unit tests :

- `AbstractLabMessageProcessingFlowTest`

## UI changes

Adapted existing classes following refactoring and to include doctor declaration:

- `LabMessageProcessingFlow`
- `AbstractPhysiciansReportProcessingFlow`
- `PhysiciansReportProcessingFlow`
- `ExternalMessageController`
- `ExternalMessageGrid`

Added classes specific to doctor declaration:

- `DoctorDeclarationMessageProcessingFlow`
- `DoctorDeclarationSlider`
- `DoctorDeclarationUiHelper`
DoctorDeclarationMessageProcessingFlow was using wrong package.
…ocessing

## API Changes

- `ExternalMessageDto`
- `ExternalMessage`
- `ExternalMessageFacadeEjb`

## Backend changes

- `sormas_schema.sql`

## UI changes

- `CaseCreateForm`
## Changes

- Fixed merge issue in `AutomaticLabMessageProcessor`

## Updated test cases

- `ExternalMessageFacadeEjbMappingTest`
- `ExternalMessageFacadeEjbUnitTest`
…factoring of message processing

- Added notifier and additional fields to external message
  - `ExternalMessageDto`
  - `ExternalMessage`
  - `ExternalMessageProcessingFacade`
  - `ExternalMessageFacadeEjbMappingTest`
  - `ExternalMessageController`
  - `sormas_schema.sql`

- Refactored lab message related classes :
  - `DoctorDeclarationMessageProcessingFlow`
  - `AbstractPhysiciansReportProcessingFlow`
  - `AbstractProcessingFlow`
  - `AbstractLabMessageProcessingFlow`

- Update implemenation and cleaned up the code
  - `AbstractMessageProcessingFlowBase`

- Corrected empty list handling :
  - `EntrySelectionComponentForExternalMessage`
@raulbob raulbob force-pushed the feature-13294_doctor_declarations_xml_esante_adapter branch from 98cf033 to 6f22e22 Compare April 15, 2025 13:20
@sormas-vitagroup
Copy link
Copy Markdown
Contributor

@raulbob raulbob merged commit 4227118 into development Apr 16, 2025
7 of 13 checks passed
@raulbob raulbob deleted the feature-13294_doctor_declarations_xml_esante_adapter branch April 16, 2025 16:12
@raulbob raulbob restored the feature-13294_doctor_declarations_xml_esante_adapter branch April 16, 2025 16:12
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.

Doctor Declarations handling and XML parsing to E-Sante adapter

3 participants