Hello,
When creating an outbound X12 file (834, 835, 837, etc), what's the easiest way to keep a segment count to use in the SE01 element? Other mapping tools I've used either detect it's an X12 file and do this automatically, or there's an option to keep a count after each outputted segment. The Data Transformation tool within Health Connect doesn't seem to have similar functionality, but I could just be missing something. Any help would be greatly appreciated!
Thanks,
Jason
Hello, our X12 File Service won't process files we encountered X12 files where they inserted CR LF after 80 bytes repeatedly in the middle of segments. X12 Parser does not seem to like it. I see there is a Whitespace property in Adapter. I am not sure if it ignores white space in the middle of a segment. I also heard about TolerateNewLine setting but I believe this also does not tolerate New Lines in the middle of a segment. We will probably have to read the file, strip out any CR and LF, write to a new file that the X12 file service can process. If there is a better solution I would like to find out about it. Thanks
When a X12 message comes into Ensemble as a Whole Batch how do you search on a segment within the body of the message? For example, a REF segment. It appears the only way is to set the Service to a single session batch, but this doesn't allow you to send the message as a Whole Batch to the Operation.
Hello,
We have defined four BPL Business Processes. One gets occasionally errors when pool size is two. No errors happen with pool size one. The error happens on calling %Save() on a large objects with many references to other objects.
Error #5803: Failed to acquire exclusive lock on instance of 'classname'.
Error #5002: Cache error: <ROLLFAIL> %TRollBack+10^%occTransaction
The error happens on a particular large object.
Our FileService gets the same Errors #5803 and #5002 with class 'EnsLib.EDI.X12.Document'
Another BPL gets the same errors #5803 and #5002 with lock on instance of 'EDIGW.BPL.ST837.Context
Any explanation or suggestion are welcome.
Hello, our Team is trying to develop Ensemble DTL to transform incoming X12 files into persistent data records. We created a persistent class and we can insert data using SQL. We tried to verify that %Save() gets called by adding %AddToSaveSet() method to persistent class and there writing to a global. We had to extend our persistent class with Ens.VDoc.Interface class or we could not see %Save() being called from Ensemble DTL. We suspect that %Save() gets some kind of error. We tried to debug by overwriting Transform() method in our DTL class. We got "<METHOD DOES NOT EXIST> 148 zTransform+2^TESTOTW.DTL2TABLE.1 Transform,Ens.DataTransformDTL" error when we called set ^TEST(-1)=##super(source,.target,.aux).
We wonder if anybody else has already achieved what we are trying and/or run into the errors we are facing and could shed some light on it for us or guide us what we need to look out for
Hello,
I am running a transformDTL through COS that transforms an EDI document to JSON and would like to validate the document and throw an error if it does not validate or build a map.
I am looking at available methods and haven't been able to find one that sort of does: Set tSC = ##class(*).Validate(tDoc,"HIPAA_5100").
Any help here would be appreciated, it seems like I am missing something simple.
Hi Community. I have a vendor sending us X12 837 claims, they are sending a mixture of 4010 and 5010 formatted claims. Is there a way I can examine the file contents and determine the message format and route to two separate folders based on format (4010 vs 5010). I've tried setting up a record map, stream container and vdoc services and processes with no luck. Any help would be appreciated.
My organization has been tasked with parsing raw EDI 271 messages into JSON strings in order to feed a downstream application. A few key details about the task:
Medicare Example JSON
Framing refers to the characters that mark the start and end of an HL7 message (or other types of framed messages). Most HL7 services and operations have a Framing setting that allows the user to define this framing. The most common choices are available as defaults, but with the AsciiMM/NN setting, components can be configured to recognize any framing characters.
The most common framing error is ErrEndBlock. Other typical errors include a warning saying "Discarding received non-HL7 data", a warning saying "Returning unused unexpected n-char segment", and "Discarding leftover input ''".
These errors will usually report what character was expected and which character was missing or unexpected. For non-printing characters, it will report these using a mapping to printing characters as in the following table
I'm trying to find a good way to control the Filename for X12 Acknowledgement files, but there doesn't seem to be a way to do that without custom coding. Here's what I figured out so far:
EnsLib.EDI.X12.Service.FileService allows you to set a Reply Target Config, which would likely be an X12 File Operation. The Service doesn’t have any settings related to the name of the Acknowledgement file though. That’s determined entirely by the Operation.
The Operation allows the outbound filename to be derived from the X12 Document’s Source property, by including %f in the File Name spec. The Source property is something you can set, such as in a DTL, but the File Service doesn’t set it when generating the Reply document.
The result is that Reply files consist of a timestamp and unique counter only, as defined by the Operation’s default File Name spec, %f_%Q%!+(_a)
