Re: [HAPI-devel] Guidance Needed When Dealing with Non-Spec HL7

[John G. <jdg...@gm...>]

The problem is these HL7 messages I'm getting. I've written my own custom
PipeParser to attempt fixing the message midstream. However I'm now onto my
33rd string replacement and I don't even have production messages yet.

I didn't realize how out of specification these messages can be. Is there
an easier way to extract specific segments without parsing the entire
message? I assume there isn't since some version identification must be
discovered first.



On Mon, Jan 4, 2016 at 4:41 PM Jens Villadsen <
jen...@gm...> wrote:

> Could you provide a stacktrace?
>
> On 3 January 2016 at 18:55, John Giotta <jdg...@gm...> wrote:
>
>> I was provided an HL7 file that if I simply trying to consume it with
>> HAPI I get an exception of formatting.
>>
>> How do I handle formatting exceptions, but still access the parts of the
>> HL7 I need?
>>
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> Hl7api-devel mailing list
>> Hl7...@li...
>> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>>
>>
>
>
> --
>
> Med venlig hilsen / Kind regards
>
> *Jens Kristian Villadsen*
> cand.polyt
>
> Stålhøjen 24
> 8240 Risskov
> Denmark
>
> Mobile +4523373806
> jen...@gm...
>