-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add RR extraction to PHDI SDK #800
Conversation
… into emma/737-really
… into emma/737-really
Codecov Report
@@ Coverage Diff @@
## main #800 +/- ##
==========================================
+ Coverage 96.35% 96.42% +0.06%
==========================================
Files 45 45
Lines 2576 2626 +50
==========================================
+ Hits 2482 2532 +50
Misses 94 94
Flags with carried forward coverage won't be shown. Click here to find out more.
|
@@ -13,7 +13,7 @@ python = "^3.10" | |||
smartystreets-python-sdk = "^4.10.6" | |||
pydantic = "^1.10.9" | |||
fastapi = "^0.96.0" | |||
httpx = "^0.23.3" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Had to update HTTPX because otherwise phdi
couldn't be added as a dependency of the FHIR converter container.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have been trying not to add phdi
as a dependency in the FHIR converter to avoid making a larger image even larger. If we need to do this for now I think that is fine, but I'd like to have a conversation about breaking the SDK into smaller packages, each published to pypi separately so that each BB can be more selective in terms of what parts of the SDK to include as dependencies.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a good catch actually! I think breaking up the containers/sdk into smaller packages is a good way to go.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Happy to chat more about this offline! But for now I'm in favor of importing phdi
in the FHIR converter as-is. If we decide to break up the SDK, I think that should be a separate effort.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, my thought is that as the project continues to evolve the single SDK model doesn't really fit our current use case.
Your point 4. (Eventually) LAC pipeline is updated to send both eICR and RR data to validation BB/FHIR Converter may be incorrect. If the read source data function in the LAC pipeline already grabs both eICR and RR then they can just pass those into the validator, as they do now, but then after that step only a single eICR message with the RR should be passed back, as we don't want to necessarily repeat the extraction process in both BBs, if that makes sense. Then the FHIR Converter would still just receive a single eICR message for LAC pipeline. However, we want this extraction process in both BBs to keep them completely modular. Let me know if that makes sense. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
PULL REQUEST
Summary
Moves the RR extraction logic from the
ReadSourceData
function app inphdi-azure
to the SDK.Related Issue
Part 1 of #737
Additional Information
Order of PRs here will be roughly:
phdi-azure
calls this SDK function