-
Notifications
You must be signed in to change notification settings - Fork 156
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
Incorrect repeat counts for OBX-8/9/10/16 in v2.4 #341
Comments
@stormcrow79 I will take a look into this. |
@stormcrow79 I ran the query in the database and it looks like the database might be incorrect here, I will let the DB maintainer know to see if we can get a fix in to the database before we consider any PRs. |
@stormcrow79 seems it is an issue with the database, when I get an updated copy of the DB I should be able to generate the fix. |
Great, thanks @milkshakeuk . I've been sitting on this one since Sep 2020 when 2.x was unmaintained! |
hey @milkshakeuk what's the release cadence for the db? |
@stormcrow79 good question, I think its probably ready when its ready - but I will check back with Frank! |
@stormcrow79 sorry for the long delay on this, I will check in with Frank probably in the new year now. |
@milkshakeuk thanks for the update - happy holidays! |
@stormcrow79 okay got the latest DB, will look to create a PR for this soon. |
@stormcrow79 this change is in the latest |
NHapi.Model.V24.OBX has incorrect repeat counts for the following fields:
NHapi 2.5.0.6 to 3.1.0 throw HL7Exception from LegacyPipeParser.Parse for a segment that is valid by the spec:
OBX|1|FT|ALLERG^Allergie^MOLIS||dummy report|||A~B~C~D~E|0.5|X~Y~Z|C|||20030331053409||A11^SMITH^JOHN~B22^JONES^FRED~C33^BEAN^MARY";
NHapi 3.1.1 does not raise an exception due to changes in PR #277.
This seems to be due to a problem with the HL7 database and/or codegen affecting only v2.4 - v2.3 and v2.5 have the expected repeat count. This is similar to issue #191.
I'm happy to raise a PR for the model changes.
The text was updated successfully, but these errors were encountered: