spezi-firebase-fhir#270
Conversation
|
TODO: The Web dashboard is apparently accessing |
There was a problem hiding this comment.
Pull Request Overview
This pull request updates ENGAGE-HF to use the standardized FHIR schemas from the spezi-firebase-fhir package instead of maintaining local FHIR type definitions. The changes transition from custom FHIR implementations to the shared library while maintaining backward compatibility.
- Updates all FHIR resources to use spezi-firebase-fhir library
- Simplifies type definitions by removing duplicate FHIR base types
- Maintains API compatibility through wrapper classes extending the new base types
Reviewed Changes
Copilot reviewed 109 out of 118 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
| package.json | Removes local firebase-admin dependency and fixes npm install script |
| functions/package.json | Updates firebase-admin version and removes zod dependency |
| functions/models/package.json | Adds spezi-firebase-fhir dependency |
| functions/models/src/index.ts | Updates exports to remove custom FHIR types and use library types |
| functions/models/src/fhir/*.ts | Replaces custom FHIR implementations with library-based ones |
| functions/models/src/fhir/baseTypes/*.ts | Removes custom FHIR base type definitions |
| functions/src/services/**/*.ts | Updates imports and usage to new FHIR types |
| functions/src/tests/**/*.ts | Updates test data structures to match new FHIR schemas |
Files not reviewed (2)
- functions/models/package-lock.json: Language not supported
- functions/package-lock.json: Language not supported
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
spezi-firebase-fhir
♻️ Current situation & Problem
This pull request intends to change ENGAGE-HF to make use of the schemas defined in spezi-firebase-fhir.
⚙️ Release Notes
Add a bullet point list summary of the feature and possible migration guides if this is a breaking change so this section can be added to the release notes.
Include code snippets that provide examples of the feature implemented or links to the documentation if it appends or changes the public interface.
📚 Documentation
Please ensure that you properly document any additions in conformance to Spezi Documentation Guide.
You can use this section to describe your solution, but we encourage contributors to document your reasoning and changes using in-line documentation.
✅ Testing
Please ensure that the PR meets the testing requirements set by CodeCov and that new functionality is appropriately tested.
This section describes important information about the tests and why some elements might not be testable.
Code of Conduct & Contributing Guidelines
By creating and submitting this pull request, you agree to follow our Code of Conduct and Contributing Guidelines: