Bugfix for RemovePatientNameTypeCode transformation #1171
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… with L when there is no extension
|
basiliskus
changed the title
pluckyswan
approved these changes
Jul 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bugfix for RemovePatientNameTypeCode transformation
The
RemovePatientNameTypeCodetransformation, which is supposed to remove PID-5.7, instead was replacing it withL. We found the transformation is working correctly, but theLis being added in RS when converting FHIR => HL7. We found there is%resource.extension(%'rsext-xpn-human-name').extension("XPN.7").exists().not()condition in the mapping that will add character based on the.usefield, when the extension doesn't exist. To fix it, instead of removing the extension we're just setting it to empty.