I’d just suggest dropping a ReplaceText into the flow replacing ^\s+ with 
nothing; I think \s+ should cover \v since it’s a vertical tab, but I’m always 
surprised by how Java does its regex so if that doesn’t work then ^[\s\v\h]+ 
would cover those too.

-joey

On Dec 20, 2017, 10:50 AM -0600, Austin Duncan <[email protected]>, 
wrote:
> and our files are delimited by \r
>
> > On Wed, Dec 20, 2017 at 10:40 AM, Austin Duncan <[email protected]> 
> > wrote:
> > > it appears that the red dot is a "\v" which is the only one in the file. 
> > > does that mean anything to you?
> > >
> > > > On Wed, Dec 20, 2017 at 10:18 AM, Joey Frazee <[email protected]> 
> > > > wrote:
> > > > > If you’re on a unix system you can run `od -c` on the file and it’ll 
> > > > > spit out what all the characters are so you should be able to see 
> > > > > what the red dot is, as well as whether the lines are delimited by \r 
> > > > > or \r\n.
> > > > >
> > > > > -joey
> > > > >
> > > > > On Dec 20, 2017, 9:04 AM -0600, Austin Duncan 
> > > > > <[email protected]>, wrote:
> > > > > > I'll try it but i dont know what the character is also each line 
> > > > > > doesn't have anything on the end of it it just ends with the last 
> > > > > > bit of data.
> > > > > >
> > > > > > > On Wed, Dec 20, 2017 at 9:56 AM, Joey Frazee 
> > > > > > > <[email protected]> wrote:
> > > > > > > > Yeah, you don’t need to share the whole thing at all. Really 
> > > > > > > > just that one field.
> > > > > > > >
> > > > > > > > The red dot is a little weird. Can you try stripping that off 
> > > > > > > > the file and running it back through? If you know what 
> > > > > > > > character it is you can put a ReplaceText before the extract 
> > > > > > > > and just drop it off if it’s present.
> > > > > > > >
> > > > > > > > -joey
> > > > > > > >
> > > > > > > > On Dec 20, 2017, 8:50 AM -0600, Austin Duncan 
> > > > > > > > <[email protected]>, wrote:
> > > > > > > > > I dont really feel comfortable sharing the hl7 messages 
> > > > > > > > > because they contain phi data. but the first two fields are: 
> > > > > > > > > MSH|^~&| and there is a red dot before the MSH
> > > > > > > > >
> > > > > > > > > > On Wed, Dec 20, 2017 at 9:45 AM, Joey Frazee 
> > > > > > > > > > <[email protected]> wrote:
> > > > > > > > > > > This would/should mean that the encoding specified in the 
> > > > > > > > > > > MSH segment (message header) isn’t right for some reason. 
> > > > > > > > > > > This is the second field in the MSH and usually looks 
> > > > > > > > > > > something like '^~\&'. Is that what yours is? If not, can 
> > > > > > > > > > > you share what yours is?
> > > > > > > > > > >
> > > > > > > > > > > Also, there’s a very strict requirement that segments are 
> > > > > > > > > > > delimited by \r (you can do CRLF, \r\n too where the \n 
> > > > > > > > > > > is just to make it viewable in an editor) and the errors 
> > > > > > > > > > > you see if that’s not the case tend to be all over the 
> > > > > > > > > > > map.
> > > > > > > > > > >
> > > > > > > > > > > -joey
> > > > > > > > > > >
> > > > > > > > > > > On Dec 20, 2017, 8:33 AM -0600, Austin Duncan 
> > > > > > > > > > > <[email protected]>, wrote:
> > > > > > > > > > > > All,
> > > > > > > > > > > > I am trying to use the ExtractHL7Attributes processor 
> > > > > > > > > > > > to extract an ADT. However I am getting the error: 
> > > > > > > > > > > > failed to extract attributes... due to 
> > > > > > > > > > > > ca.uhn.hl7v2.parser..EndcodingNotSupportedException: 
> > > > > > > > > > > > Determine encoding for message. I am not 100 percent 
> > > > > > > > > > > > sure what it means by encoding. Does it mean UTF-8? 
> > > > > > > > > > > > because it should be in UTF-8. I have used this 
> > > > > > > > > > > > processor before with no trouble so I am just not sure.
> > > > > > > > > > > >
> > > > > > > > > > > > --
> > > > > > > > > > > > ​Austin Duncan
> > > > > > > > > > > > ​Researcher
> > > > > > > > > > > >
> > > > > > > > > > > > PYA Analytics
> > > > > > > > > > > > 2220 Sutherland Avenue
> > > > > > > > > > > > Knoxville, TN 37919
> > > > > > > > > > > > 423-260-4172
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > ​Austin Duncan
> > > > > > > > > ​Researcher
> > > > > > > > >
> > > > > > > > > PYA Analytics
> > > > > > > > > 2220 Sutherland Avenue
> > > > > > > > > Knoxville, TN 37919
> > > > > > > > > 423-260-4172
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > ​Austin Duncan
> > > > > > ​Researcher
> > > > > >
> > > > > > PYA Analytics
> > > > > > 2220 Sutherland Avenue
> > > > > > Knoxville, TN 37919
> > > > > > 423-260-4172
> > >
> > >
> > >
> > > --
> > > ​Austin Duncan
> > > ​Researcher
> > >
> > > PYA Analytics
> > > 2220 Sutherland Avenue
> > > Knoxville, TN 37919
> > > 423-260-4172
>
>
>
> --
> ​Austin Duncan
> ​Researcher
>
> PYA Analytics
> 2220 Sutherland Avenue
> Knoxville, TN 37919
> 423-260-4172

Reply via email to