I am looking for a message definition document for a TRADACOMS UTLHDR message (Utility Bill File, version 3).
Context: Need to setup an ETL process involving generation of UTLHDR message but I am missing the message definition document needed to successfully code / test creation of these files. I am reasonably familiar with EDI formats in general, but without a specification it is 'challenging' to correctly sequence the message segments.
The message type is open / non-propriety, just there seems to be very little published information left despite many hours searching. TRADACOMS invoice help (EDI Invoice) was closest I got, but the tools mentioned do not support the message version I am working with.
Any help much appreciated!
While I cannot find a specification for UTLHDR transaction, the UTLBIL format might get you started in the right direction. That is available online, or via export from an EDI dictionary.
Related
I am looking to decode intents from many strings from many conversations I have stored in a database, so I can use machine learning to create an intelligent chatbot. I have heard and tested tools like Amazon Lex, but I am looking to receive the intent from a string not create my own intents. Here is a sample starting question from the data I am working with:
Hi, can I please find out the location of the nearest Depot to Meadow Springs WA 6210?
Is there any chance we could get 34 cases from Melbourne to Sydney by Friday. I am hoping it will be a Sydney to Sydney tomorrow but if not can anyone do this by Friday from Melbourne?
can you tell me how the warranty claim is going on booking number 9528 thanks
Intents are usually created for a specific application by providing examples. However, some services do provide pre-defined intents you can use.
LUIS provides prebuilt "domains" which include some place related queries
Snips has an "intents library" that you can use
That may be able to get you started. If that doesn't work, this guide to a from-scratch implementation may be useful.
Context
A friend of mine is having trouble printing source code to a human readable format.
The compiled (I assume) programs of their welding robot have the .rpg extension. They want to collect print-outs in human-readable format, possibly for backup or future reference.
Their supplier can provide the software that accomplishes this, be it at a considerable cost (and possibly: an annual license). Because of this, my friend decided to ask me if a easier/cheaper solution exists.
Examples & Pictures
The files can be read on the console of the robot, an example:
I've done some minor research and I'm fairly sure this is the Report Program Generator (RPG) language developed by IBM. The Assembly-like syntax seems to match; it might be one of the later versions of the language.
My friend has send me an example .rpg file, the contents seem binary with some string literals scattered throughout. Screenshot of the contents of an example file in hexadecimal:
The Question
There is not much, if any, clear information to be found online so I suppose I have multiple questions (for anyone that might know more about this):
Is this (first image) Report Program Generator (RPG) code?
Does the .rpg file contain compiled or processed code? Maybe an intermediate format?
Is it possible to convert files as shown in the example, back to source-code or human-readable format, kind of 'disassemble' it?
If anyone knows more, don't hesitate to give me any information or ask more details if necessary. Thanks in advance!
And maybe not an important question but still something that bugs me (and might indicate I'm on the wrong track):
If this is indeed an RPG program, why would the compiled/processed binary have the .rpg extension, shouldn't the source-file have that? This leads me to believe I'm either (a) assuming the wrong things (the language, etc...) or (b) this is an intermediate format, easier for machines to read, that has to be interpreted by some kind of runtime system.
I don't think that's any version of IBM's RPG language. RPG does have a MOVEL opcode, but it doesn't have any of the others.
Also, all the versions of the IBM language have been intended for business programming. I doubt that it would have been used for robotics.
My guess is that's a proprietary language of the company that makes the robot.
There are some similarities but it does not look like IBM RPG language.
RPG sources are in fact source physical file members. They are not stored in the "traditional" file system but in OS/400 libraries. Therefore RPG sources have no extension. They can be converted to Integrated File System stream file though.
I can't answer this question I'm afraid as it's unknown language to me.
I expect possibly that the OP misidentifies the file type/extension; that the extension is actually .prg, and the files serve as instructions for a Panasonic Industrial Welding Robot. The following forum [drilled down to Panasonic Robots] bills itself as the biggest Industrial Robots Supportforum worldwide!; perhaps a good place to ask about those images provided in the OP, and the inquiry about getting source from what appears to be a binary instruction stream.
FWiW, the first image seems to show that the Ezed utility [on the console] gives that human-readable format, so then the question might be how to get that saved and then how to transfer that elsewhere; e.g. what type of comm ports and file transfer utilities are available from whatever platform/OS.
I'm using the Mirth Connect listener and so can receive HL7 XML fine (apparently). I've been asked, though, if I am able to receive CCD messages.
Looking at Wikipedia, "The CCD specification is a constraint on the HL7 Clinical Document Architecture (CDA) standard". To me, that says I can at least receive the message via my normal process. Parsing the message could be something altogether different, though.
Can anyone tell me whether or not I am correct in this reading of the description? Is Mirth going to have any trouble receiving the CCD message/s?
Thanks.
The answer is yes, mostly. Below is an example of how to setup for receiving a CDA Message.
The real issue comes into play depending on how you need to receive the message and what needs to be done with it. CDA and HL7 v3 messaging is not as trivial as HL7 v2 (your typical pipe delimited HL7 message) is. The message structures are highly complex and will require a lot of learning. Additionally, CDA messages are not transferred over the MLLP protocol like HL7 v2. I have generally seen people transferring these messages using the XDS profiles. So, depending on how you need to receive the message, there may some additional work to be done.
I believe the paid/licensed version of Mirth offers some components to aid with CDA/HL7 v3 messages, but it is not included in the OSS version.
Receiving a CDA Message in Mirth
Mirth would have no issue receiving the XML message. Just make sure to set the data type to XML in the channel.
From there, you can setup your receive and destination. If you need to work with the XML of the CDA, in the message transformer make sure to provide a sample CDA in the message templates section. Once you do that, the message should show up in teh Message Trees section.
My very old HL7 parser has just hit a snag as it is now getting some messages with a ZDS segment present. It was easy to fix by adding a ZDS object to my parser, but I am trying to find out what it is used for. Googling hasn't helped much. This is a sample
ZDS|PERFORM|p0001236^PATEL^ATEST^^^^^^HHB_INOP_PRSNL^^^^OTHER|20100714101800|CD:653
ZDS|TRANSCRIBE|p0001236^PATEL^ATEST^^^^^^HHB_INOP_PRSNL^^^^OTHER|20100714101800|CD:653
ZDS|SIGN|p0001236^PATEL^ATEST^^^^^^HHB_INOP_PRSNL^^^^OTHER|20100714101912|CD:653
So, I'm interested in what each field is though looking at this sample data, it seems I don't lose much by just dropping the whole segment.
In HL7, all segments that begin with the letter Z are considered to be custom and are not defined further by the HL7 standard. You will need to find out what system is responsible for generating these ZDS segments and ask the owners of that system to provide you their specification.
As Scott said, "Z" segments are custom and can vary from vendor to vendor. In the Cerner realm, however, ZDS segments are typically used for "Document Succession" purposes -- a means of document version tracking and synchronization between two supportive systems.
The ZDS segment is used to communicate document endorsement information (actions done or to be done) in Unsolicited Document Results. only a specific solution of Millennium use it, so if you don't need just ignore it.
For a web app I'm working on, I need to know the lat/lon of about 300 US cities. I also need to know the lat/lon for every US zip code.
Does anyone know of a free source to get this information?
Freebase will likely be able to help you. Here is New York and it has Lat/Long.
The Wal-Mart Expansion video used Freebase to get it's data, and it sounds like you're doing something similar.
Take a look at Ben Fry's Zip Code Visualizer. This is part of his book Visualizing Data.
There is an online database at Geocoder.us. And a simple perl module (we added a soap service to this so we could simply access it from any language, and the longest part of the development process was downloading database (it's about 4 GB).) The geocoing database is available from the US census bureau, a good article on getting this setup can be found here.