Tags: StanfordSpezi/SpeziFHIR
Tags
Fix Runtime Crash Due to Unlocked Access to Shared Properties (#21) # Fix Runtime Crash Due to Unlocked Access to Shared Properties ## ♻️ Current situation & Problem - We have received crash reports that applications are crashing due to a shared access to the resources property within the FHIR store. - Closes #16 ## ⚙️ Release Notes - Adds a simple locking mechanism for the FHIR store. Should be updated to an actor-isolated context as documented in #19. ## 📝 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).
Lift to SpeziLLM v0.8, Data race fix (#20) # Lift to SpeziLLM v0.8, Data race fix ## ♻️ Current situation & Problem As of now, the SpeziFHIRLLM target still uses the outdated SpeziLLM v0.7 version, using old APIs. Furthermore, a crash of the `FHIRResourceProcessor` could occur in the case of many parallel summarization, e.g., in the `MultipleResourceChatView.` ## ⚙️ Release Notes - Lift to SpeziLLM v0.8 - Fix a data race in the `FHIRResourceProcessor`, ensuring parallel processing capabilities ## 📚 Documentation -- ## ✅ 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).
Lift to SpeziLLM (#17) # Lift to SpeziLLM ## ♻️ Current situation & Problem Dependent on old version of SpeziLLM ## ⚙️ Release Notes - Update to SpeziLLM version 0.7.0 ## 📚 Documentation Proper docs included ## ✅ Testing All 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).
Fixed procedure dates (#14) # Fixing procedure dates ## ♻️ Current situation & Problem Not all procedures had dates being extracted from the JSON resources. Without all of the dates being sent to the LLM, it cannot understand the full context and timeline of the patients procedures. ## ⚙️ Release Notes The only change in this PR was made in [FHIRResource.swift](2354244). The modification ensures that the end date of the procedure is taken in each of the resources (which is consistent between DSTU2 and R4). ``` if case let .period(period) = procedure.performed { return try? period.end?.value?.asNSDate() } ``` ## 📝 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: Paul Schmiedmayer <[email protected]>
Improve Prompts, Display Name, Date, and Summary Model (#13) # Improve Prompts, Display Name, Date, and Summary Model ## ⚙️ Release Notes - Improve the summary and interpretation prompts - Better holistic to generate a display name that tries to inspect the resource for information - Best effort to determine the date of the FHIR resource - Improvement of the summary and interpretation models as `FHIRResourceProcesser` now has a generic `Content` type. ## 📝 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).
Improve Public API and Improve FHIRResourceSummaryView (#12) # Improve Public API and Improve FHIRResourceSummaryView ## ⚙️ Release Notes - Improve Public API and Improve FHIRResourceSummaryView ## 📝 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).
Adds a FHIR Standard, HealthKit Adapter, Mock Patient, and Interpreta… …tion Target (#11) # Adds a FHIR Standard, HealthKit Adapter, Mock Patient, and Interpretation Target ## ⚙️ Release Notes - New FHIR Standard: Integrated a new standard for developing FHIR-based digital health applications, ensuring compliance and ease of use with FHIR protocols. - HealthKit Adapter: Introduced an adapter for HealthKit, allowing for seamless integration and data exchange between HealthKit and FHIR resources. - Mock Patient Model: Added a mock patient model for testing and development purposes, enabling developers to simulate patient data and interactions based on FHIR R4 `Bundle`s. - Interpretation Target: Implemented an interpretation target to enhance the processing and analysis of FHIR resources including LLM-based interactions. ## 📝 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).
Upgrade Spezi to 0.8.0 (#10) # Upgrade Spezi to 0.8.0 ## ♻️ Current situation & Problem Upgrades Spezi to 0.8.0 ## ⚙️ Release Notes * Upgrades Spezi to 0.8.0 ## 📚 Documentation -- ## ✅ 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). --------- Co-authored-by: Paul Schmiedmayer <[email protected]>
Rework the Spezi FHIR Package (#7) # Rework the Spezi FHIR Package ## ♻️ Current situation & Problem - With the update to Spezi 0.7.0, a `FHIR` standard as originally designed is no longer needed and a responsibility pushed to the developers of a Spezi-based application, allowing a greater level of customization functionality. ## 💡 Proposed solution & Release Notes - The Mock Web Service functionality has moved to its own Swift Package: https://github.com/StanfordSpezi/SpeziMockWebService - The FHIR package will focus on building convenient extensions around the FHIR Package, including extensions to existing FHIR types and other future extensions. ## ➕ Additional Information - This PR builds the first foundation for future extensions to the FHIR package. It contains a minimal feature set from the previous version of the package. Suggestions and ideas are more than welcome! ### 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