Tags: StanfordSpezi/SpeziFHIR
Tags
Fix attachment handling for duplicate content types (#38) # Fix attachment handling for duplicate content types ## ♻️ Current situation & Problem When attachments are loaded, only the first element with a specific MIME or content type are selected. However, multiple elements often share the same MIME or content type. ## ⚙️ Release Notes Improved attachment handling to update all resources with the same content type rather than just the first match. ## 📚 Documentation N/A ## ✅ Testing Unit tests for the process attachment functions. ## 📝 Code of Conduct & Contributing Guidelines By creating and submitting this pull request, you agree to follow our [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md): - [x] I agree to follow the [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md).
Implement date fallback strategy for Observations (#35) # Implement date fallback strategy for Observations ## ♻️ Current situation & Problem Observation resources sometimes lack an issued date, causing the system to return nil for their date property. This creates a bad user experience in chronologically-sorted resource lists, as these observations are pushed to the bottom of lists due to missing date information, despite often containing an alternative effective date that could provide meaningful context. ## ⚙️ Release Notes When extracting dates from Observation resources, now properly supports using the effective date as a fallback when issued date is missing. ## 📚 Documentation N/A ## ✅ Testing Added new unit tests covering issued date and the effective date. ## 📝 Code of Conduct & Contributing Guidelines By creating and submitting this pull request, you agree to follow our [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md): - [x] I agree to follow the [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md).
10000
Support Diagnostics for Document Parsing (#33) # Support Diagnostics for Document Parsing ## ⚙️ Release Notes - Support Diagnostics for Document Parsing ## 📝 Code of Conduct & Contributing Guidelines By creating and submitting this pull request, you agree to follow our [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md): - [x] I agree to follow the [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md).
Support the Parsing and Extraction of Clinical Notes (#32) # Support the Parsing and Extraction of Clinical Notes ## ♻️ Current situation & Problem - SpeziFHIR currently doesn't currently explicit support documents as a dedicated resource type + as way to parse the information when extracting them from HealthKit. ## ⚙️ Release Notes - Adds explicit document handling - Improves FHIR parsing form HealthKit records ## 📝 Code of Conduct & Contributing Guidelines By creating and submitting this pull request, you agree to follow our [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md): - [x] I agree to follow the [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md).
Tests `FHIRResource` and its extensions (#28) # Write tests for `FHIRResource` and its extensions. ## ♻️ Current situation & Problem The `FHIRResource` class and its extensions currently have 0% test coverage. We should increase the code coverage as much as possible, to ensure long-term maintainability. ## ⚙️ Release Notes - This PR doesn't change any features. It adds tests for the `FHIRResource`, `FHIRResource+Search`, and `ResourceProxy+DisplayName`. - For the `FHIRResource+Category` tests, it's best to wait until PR #26 is merged into the main branch, avoiding any potential conflicts or inconsistencies. ## 📚 Documentation Comments are added throughout the code. ## ✅ Testing Aim for >90% code coverage, but >80% is acceptable in this case. ## 📝 Code of Conduct & Contributing Guidelines By submitting creating this pull request, you agree to follow our [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md): - [x] I agree to follow the [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md). --------- Co-authored-by: Philipp Zagar <zagar@stanford.edu>
`FHIRStore` actor isolation (#26) # `FHIRStore` actor isolation ## ♻️ Current situation & Problem As references in #25, the current `FHIRStore` implementation is not ideal as it still uses preconcurrency locking mechanisms. Therefore, the `FHIRStore` should be reimplemented to use Swift's structured concurrency and isolation mechanisms. ## ⚙️ Release Notes - `FHIRStore` actor isolation with structured concurrency, not relying on locks anymore. - `FHIRResource`s are not `Sendable` anymore (underlying ModelsR4 class is not `Sendable`) ## 📚 Documentation Documented all isolation thoughts ## ✅ Testing -- ## 📝 Code of Conduct & Contributing Guidelines By submitting creating this pull request, you agree to follow our [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md): - [X] I agree to follow the [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md).
Remove LLM Functionality from Package (#24) # Remove LLM Functionality from Package ## ♻️ Current situation & Problem Remove the LLM summary and interpretation logic from this package, as it uses application-specific functionality that does not belong within the package ## 📝 Code of Conduct & Contributing Guidelines By submitting creating this pull request, you agree to follow our [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md): - [x] I agree to follow the [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md). --------- Co-authored-by: Leon Nissen <>
Remove LLM Functionality from Package (#24) # Remove LLM Functionality from Package ## ♻️ Current situation & Problem Remove the LLM summary and interpretation logic from this package, as it uses application-specific functionality that does not belong within the package ## 📝 Code of Conduct & Contributing Guidelines By submitting creating this pull request, you agree to follow our [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md): - [x] I agree to follow the [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md). --------- Co-authored-by: Leon Nissen <>
Swift 6 language mode readiness and bump dependencies (#23) # Swift 6 language mode readiness and bump dependencies ## ♻️ Current situation & Problem As the repo wasn't properly maintained for quite some months, most dependencies have been severely outdated. ## ⚙️ Release Notes - Swift 6 language mode readiness - Bump dependencies to the newest versions ## 📚 Documentation -- ## ✅ Testing Tested locally and UI tests passing ## 📝 Code of Conduct & Contributing Guidelines By submitting creating this pull request, you agree to follow our [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md): - [x] I agree to follow the [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md).
PreviousNext