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
