skip server error when fetching diagn.serv.items#128
Open
Blue-B-code wants to merge 2 commits intoopenimis:developfrom
Open
skip server error when fetching diagn.serv.items#128Blue-B-code wants to merge 2 commits intoopenimis:developfrom
Blue-B-code wants to merge 2 commits intoopenimis:developfrom
Conversation
Blue-B-code
force-pushed
the
feature-36290
branch
2 times, most recently
from
000374a to
2242c96
Compare
vaneck237
reviewed
Apr 17, 2026
Blue-B-code
force-pushed
the
feature-36290
branch
from
2242c96 to
d1cf331
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
During the download of items, services, and diagnostics, it frequently happens that some resources generate formatting errors (FHIR incompatibilities). These errors interrupt the ongoing data retrieval process and render the application unusable as is currently the case.
While formatting should normally be handled on the Django side, it is necessary, on the mobile side, to ensure that this type of situation does not compromise the overall functionality of the application.
Therefore, we have implemented a mechanism to skip problematic resources, ignoring them when they cannot be processed correctly. This prevents the process from blocking and ensures the continuity of the download and mapping of the remaining data.
Type of Change
Related Issue(s) / Task(s)
Demo
Checklist