Fix failing because the oml_o33_2 parsing creates a OML_O33_ORDER_PRIOR #99
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
…OR which expect a OBR segment but the parser's implementation puts the OBR segment in the group OML_O33_OBSERVATION_REQUEST
|
This seems an ad-hoc fix for a very specific problem. I would suggest you open an issue explaining what problem you're experiencing and we'll see if there is something wrong with the message structures or something else. Attaching the hl7 message you're trying to parse would help a lot. Thanks. |
|
I tried to fix your own test. As you can see I uncommented your test: https://github.com/crs4/hl7apy/pull/99/files#diff-f1dbe79adfb6e39e76ee4519368bc4b5eaa0e4831f00165e5ac28fede4825bffR105 😄 |
|
Oh, I see, sorry 😄 |
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.
No description provided.