Presently I'm using IBM Integration Bus v9.0 and I have a doubt.
is INR to USD conversion, Transformation or Translation? please give me the answer.
Thanks in advance.
That's not really a technical question. It sounds as if there is something behind the question; maybe a contractual dispute? Please define your terms ( what do you mean by translation? ) and explain why you need to know.
Its translation, keep this in mind
Perform transformation on a message to make its structure comply with the receiving system’s requirements.
Perform data translation on a message so that its data is represented according to the receiving system’s conventions.
Simple translation might be required if the two systems use different values to represent the same information for a given field.
Complex translation might involve augmenting or replacing groups of fields with a completely different structure and encoding.
Money has a fixed value whether its in INR or USD, there's no structure to it but value with a unit, the unit is interpreted differently by different system, so its translation
Related
Does anyone know what ZCD may refer to? It is described as a segment with a link back to PreManage for the patient!
Can anyone please provide more details?
The Z segments (segments those begin with the letter "Z") are custom segments. Those are not defined in specifications. They vary from vendor to vendor. Vendor may publish a document explaining usage of segment. Two connected parties should know in advance and decide the usage by mutual understanding.
As those are custom, and if there is no way to know what data they contain, it may be safe to neglect them hoping the sender have not put critical data in it.
Please refer to this:
Z-segments can be inserted anywhere in the HL7 message. A popular approach is to place the Z-segment within a group of segments that contain similar information, such as insurance. Z-segments are also often placed at the end of the message. The advantage of doing so is that this placement prevents systems configured to parse “standard” HL7 format from requiring any configuration modifications in order to process the message. The application simply reads the segments in the order expected and then extracts the data from the Z-segment (if needed) via parser modifications.
Working with unexpected Z-segments
Sometimes systems may send unexpected Z-segments, whether or not they were part of the original specifications. Even if you are not interested in the data in the Z-segment, you may still (depending on its location) need to take the segment into account while testing and developing your interface.
I have a project with topic what is checksum, I would like to explain where to be focused on, and to make more attractive from others colleagues.
What checksum?
Where is used and how can I explain it with a short term?
Checksum is a digit representing the sum of the correct digits in a piece of stored or transmitted digital data, against which later comparisons can be made to detect errors in the data.
You can refer below links for more detail:
1. http://www.online-tech-tips.com/cool-websites/what-is-checksum/
http://www.thegeekstuff.com/2012/05/ip-header-checksum
Hope it will help you.
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.
I have a confusion in understanding the structure of PAL device.
My first question is that if we buy a PAL device , then how can we know that how many min terms are added by each OR gate in the OR array? In other words I am asking, is there any standard by which we can know the number inputs each OR gate has in the OR array?
The next thing is that we have an AND array in the PAL device which is programmable. Now suppose we have 4 inputs , then each AND gate in the AND array must need 8 inputs. It is up to us how many variables we apply on it, but there is a possiblity that we can apply all the variables on the AND gate therefore it should have 8 inputs. Please tell me am i right or not. If not then please explain.
I think there is no universal standard for either of your questions. The data-sheet for each device specifies those parameters. You should look up the data-sheets and decide what suits your needs.
Specifically on your second question, an ideal PAL should be as you say (like this simplified circuit). But usually you don't want to apply all the variables (and their negations) to the AND gates, so each AND gate can have less inputs (of course using the grid you can choose any of the variables to apply, just not all of them together).
All,
Our application requires data on ISO countries and currencies (where the data must be up to date). We did purchase country/currency data from ISO themselves, however we still needed to perform alot of manual manipulation of the data, as well as write our own tool to read and process the data into our database.
Are we going about getting this data the wrong way?
What is the norm in relation to the acquisition of country/currency data?
Is there any well known providers out there that are offer to provide this data as a service or through some other medium in a usable format?
Any help will be greatly appreciated.
The .NET CultureInfo class provides formatting for currencies (as well as dates, times, numbers, etc). I would never have even considered buying the data from ISO when it's available for free in the .NET runtime.
You might be interested by IBM's International Component for Unicode (ICU) library.
Open source, well known, supports "numbers, dates, times and currency amounts" formatting.
Not sure if it helps your case, but this info might be useful for somebody else... :-)