Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Unable to parse OBX out of ORU01 if message has PID segment #1

Closed
chanskw opened this issue Jun 23, 2016 · 1 comment
Closed

Unable to parse OBX out of ORU01 if message has PID segment #1

chanskw opened this issue Jun 23, 2016 · 1 comment

Comments

@chanskw
Copy link
Collaborator

chanskw commented Jun 23, 2016

In a testcase where the ORU01 message has a PID segment, the parser is unable to parse out the OBR and OBX segment.

The problem is in the ObxToSplMapper code, where we expect a flat structure in the message.

In the case where PID is present, the OBR and OBX segments are nested into a Patient object.
chanskw pushed a commit that referenced this issue Jun 23, 2016
#1: Fixed parsing problem when PID is present
cf96f5a
@chanskw
Copy link
Collaborator Author

chanskw commented Jun 23, 2016

Fixed

@chanskw chanskw closed this as completed Jun 23, 2016
chanskw added a commit that referenced this issue Dec 5, 2016
@chanskw
Merge pull request #1 from IBMStreams/master
9adf40d 
merge from master
natashadsilva added a commit that referenced this issue Sep 1, 2020
@natashadsilva
Merge pull request #1 from IBMStreams/develop
7974109 
Merge latest changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@chanskw