1. What are the various expEDIum Adapters?
iTech Workshop markets a variety of readymade Healthcare adapters built using expEDIum X12N Engine. These adapters support formats such as NSF 2.0, NSF 3.01, UB-92 v5.0/6.0, NSF 3.01 DMERC, NSF 3.20D, NSF 2.01u ERN, Envoy NSF and HCFA 1500 Print Image formats. |
|
2. How does it compare with other EDI Translators?
Typical EDI translators provide EDI Transaction set mapping on a store and use this mapping when processing EDI transactions. expEDIum works differently, expEDIum EDI Engine Architecture “hard-wires” the EDI Transaction mapping information for a given vertical or process .It provides a rich API that is used to build EDI-aware applications rapidly. It’s robust and is capable of processing several hundred thousand transactions per day on appropriate hardware. |
|
3. What are the data formats supported by the expEDIum Adapters?
We have a variety of readymade Healthcare Adapters built using expEDIum X12N Engine. These Adapters support formats such as NSF 2.0, NSF 3.01, UB-92 v5.0/6.0, NSF 3.01 DMERC, NSF 3.20D, NSF 2.01u ERN, Envoy NSF and HCFA 1500 Print Image formats. |
|
4. Can you build custom adapters using your expEDIum framework?
Yes we can build custom adapters rapidly for any other Healthcare formats as per the requirement of our clients. |
|
5. we have to fill in missing data each time we translate a new file?
No you don’t have to, because our adapters have a default GAP mechanism to fill in data that could be missing from the input healthcare format files but are required for generating complete X12N files, by default. |
|
6. What does NSFClaims20 adapter do?
NSFClaims20 Adapter performs ready made conversions of NSF 2.0 health-care format to X12N 837(Professional). The NSFClaims20 Adapter uses its internal expEDIum X12N Engine to perform translations |
|
7. What does NSFClaims301 adapter do?
The NSFClaims301 Adapter performs ready-made conversions of NSF 3.01 healthcare format to X12N 837(Professional). A variation of this adapter handles DMERC claims. NSF Claims 301 Adapter uses its internal expEDIum X12N Engine to perform translations. |
|
8. What does NSFClaims60 adapter do?
The NSFClaims60 Adapter performs readymade conversions of UB-92 v6.0 healthcare formats to X12N 837(Institutional). NSFClaims60 Adapter uses its internal expEDIum X12N Engine to perform translations. |
|
9. What does NSFRemits adapter do?
The NSFRemits Adapter performs readymade conversions of NSF 2.01u ERN healthcare formats to X12N 835. It uses the expEDIum X12N Engine internally to perform translations. |
|
10. What does HCFA Claims adapter do?
The HCFA Claims Adapter performs readymade conversion of HCFA Print Image/CSV files to X12N 837(Professional) based on a HCFA Control file/CSV Map file layout. A HCFA Control/CSV Map file is constructed for every installation to capture the subtle differences between the various HCFA Print Image/CSV files generated by existing healthcare products and solutions. It takes a few hours to construct this HCFA Control/CSV Map file based on HCFA Print Image/CSV file layout and some sample HCFA Print Image/CSV claims. |
|
11. What does UB04Claims adapter do?
The UB04Claims Adapter performs readymade conversion of UB04/UB92 Print Image files to X12N / HIPAA 837(Institutional) based on a UB04/UB92 Control file layout. A UB04 Control file is constructed for every installation to capture the subtle differences between the various UB04/UB92 Print Image files generated by different PMS systems. It takes an hour to construct this UB04 Control file based on UB04/UB92 Print Image layout and some sample UB04/UB92 Print Image claims. |
|
12. What is the performance of expEDIum Engine and the adapters?
Our expEDIum X12N Engine Architecture “hard-wires” the EDI Transaction mapping information and it delivers high performance. We have seen 200+ typical claims being (NSF 3.01 claims with multiple service lines) processed per second. Our architecture is scalable. |
|
13. Do you have any-to-X12N kind of adapters?
No, as of now we don’t have any such adapter, which can convert any file format to X12N. We can build custom adapters on request. |
|
14. How long does it take to build a custom adapter and what does it take to build one?
An adapter would typically have three steps/tasks – the NSF (or any other Legacy Format) Parser, the Mapping- between 837 (or ANSI X12N) to NSF and then programming the map and it typically takes about 2 weeks to develop an adapter this number is a ball-park estimate and the actual estimate might vary once we take a look at the given format. This adapter would use expEDIum X12N API internally to perform EDI translations. |
