X12

Syndicate content 6 

Description

X12, chartered by the American National Standards Institute for more than 35 years, develops and maintains EDI standards and XML schemas which drive business processes globally

Most votesArticlesAnnouncementsQuestionsNo answerNo accepted answerAll

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.

Continue Reading
Oliver Wilms's picture
Post by Oliver Wilms 29 January 2019
Last comment 30 January 2019
0 2
0

answers

2

comments
96

views

0

rating

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

Continue Reading
Oliver Wilms's picture
Post by Oliver Wilms 15 October 2018
Last answer 15 October 2018 Last comment 16 October 2018
0 4
1

answers
2

comments
98

views

0

rating

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.

Continue Reading
Ron Sweeney's picture
Post by Ron Sweeney 11 April 2018
Last comment 11 April 2018
0 2
0

answers

1

comments
151

views

0

rating

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.

Continue Reading
Lewis Greitzer's picture
Post by Lewis Greitzer 24 October 2017
Last answer 7 November 2017
0 1
1

answers
0

comments

317

views

0

rating

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:

  • The raw EDI 271 will be coming across as a standard format from a single outbound upstream system
  • The EDI 271 messages adhere to the 5010 standard
  • We do not need EVERY field from the EDI message, only a select number of fields.  However some of the fields we need (e.g. coverage details) are dynamic in size and will be variable in # of segments both on the EDI side as well as the receiving JSON side.
  • We will be looking to build one incoming business operation for the stream of 271 messages which will then be parsed into Medicare and non-Medicare
  • The JSON output has a static format per class of payor (sample can be referenced below for both Medicare and non-Medicare payors):

Medicare Example JSON

Continue Reading
Chris Sanford's picture
Post by Chris Sanford 13 October 2016
Last comment 18 October 2016
0 0
0

answers

6

comments
1181

views

+ 1

rating

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

Continue Reading
Brendan Batchelder's picture
Post by Brendan Batchelder 20 September 2016
0 2
0

comments

545

views

+ 2

rating


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)

Continue Reading
Clayton Lewis's picture
Post by Clayton Lewis 26 April 2016
Last comment 27 April 2016
0 2
0

answers

1

comments
278

views

+ 1

rating