-
Notifications
You must be signed in to change notification settings - Fork 5
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
Refactor transformation helpers #1085
Conversation
Quality Gate passedIssues Measures |
I like that the logic is in transformation object. At lease we don't have to go looking else where for it. The only thing that I realize now is that this tightly couples the fhir library to each transformation object. I'm ok leaving it like this or adding the logic to the fhir humble object. |
Right. I think it may be ok as the transformations deal with the inners of the bundle and it may be cumbersome to abstract them from the hapi library, but I'm sure we can make improvements in that direction. This could be a good topic for eng. block. I'll add it |
Yes. I also realize that the FHIR bundle dependency will be a part of the transformation object regardless of where we put the logic. The bundle will have to get passed to the helper function or we will iterate through it if we keep the logic in the transformation objects. |
Small note to please move the magic strings to enums/ constants in the next PR, approving with that note |
Refactor transformation helpers
addMetaTag
instead ofaddEtorTagToBundle
setMessageTypeCoding
instead ofconvertToOmlOrder
HapiHelper
(removedHapiMessageConverterHelper
andHapiOrderConverterHelper
)Issue
#1024
Checklist