-
Notifications
You must be signed in to change notification settings - Fork 157
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
getting exceptions when trying to parse hl7 messages containing large data in obx-5 #594
Comments
hi @AlexFJaxFL do you have any example code? |
also @AlexFJaxFL might be worth checking #105 to see if this issue is similar or not? |
Public Shared Function ParseHL7Messages(HL7Messages As String, FType As FeedType) As Boolean
|
i can see there is certain correlation between my issue and discussion that took place in #105, |
maybe this structure does not match what your engine parser is expecting .. |
Hi @AlexFJaxFL we have some unit tests showing how it should look,
There is also this blog which might help. http://healthbase.info/blog/?p=376 |
Ok, this information is very helpful indeed and will be used for .pdf related feeds which we have plenty. |
@AlexFJaxFL I think you can use a similar approach to the pdf for rtf files. |
ok, data does not come in to us in the same format so i will have to do some custom programming to adjust accordingly and then will go from there |
it appears other data types in OBX-2 (like ST, TX and ED which is used in your example above) work with nhapi parser just fine, data comes in like this: OBX|1|FT|^EDIE_VISIT_HISTORY||{\rtf1{\info{\ planning to override FT and make it ST or TX unless perhaps you might provide some other recommendations |
getting the following exception when parsing files containing large embedded images:
Parse error in DoEDieIn: NHapi.Base.DataTypeException: Failed validation rule: Maxumim size <= 65536 characters
at NHapi.Base.Model.Varies.fixOBX5(ISegment segment, IModelClassFactory factory)
at NHapi.Base.Parser.PipeParser.Parse(ISegment destination, String segment, EncodingCharacters encodingChars)
at NHapi.Base.Parser.PipeParser.DoParse(String message, String version)
at NHapi.Base.Parser.ParserBase.Parse(String message, String version)
at EPDHL7ListenerSvc2.EPDHL7ListenerSvc2.TryParseMessage(String HL7Message).
not sure if this limitation is to be expected or maybe it will be resolved in future versions
Regards,
Alex
The text was updated successfully, but these errors were encountered: