|
HIPAA 837 to NSF
|
|
|
Introduction
-
HIPAA 837
Professional to
NSF Version 3.01
|
This map
definition is designed to act as
a basis for the translation from
the HIPAA 837 Professional
format to the
NSF Version 3.01 format .
Almost all of the elements have
been already mapped, and notes
have been documented to those
elements which require
attention. This ready-to-go map
is intended to help users
quickly generate the HIPAA
compliance message for
healthcare claims.
This map also includes
the following features:
- HIPAA 837 professional
set to the NSF standard and vice versa
- Different HL loops mapped to different NSF records
- Conditional mapping
- Code Conversion between X12 and NSF
- String manipulations
- Automatic counter, e.g., number of CA0
or DA0 records
- Automatic calculation of line charges and total line charges
- Automatically generates an IFD/OFD to interface
with the Redix Format Converter
- Calculates days, as well as date string manipulation
An in-depth
map document (HIPAA_837_ProftoHCFA_NSF_31.xls)
from the HIPAA 837 Professional
format to the
NSF 3.01 format
is
also available to Redix XML
HIPAA Package users. |
|
Input - Before
Translation
|
Before: a
HIPAA 837 Professional
File |
|
|
Output - After
Translation
|
|
Above is a
before and after look of the
translation. The above
information can be found in the
Redix XML HIPAA Package in the
Mapper's Conversion area. |
 |
|
The image
above demonstrates a
user using the Redix
Drag and Drop GUI to
perform a 1:1 mapping of
a
HIPAA 837 professional
SV1_01:02 field (Product
Service ID) to a
FA0_08 element (HCPCS
Procedure Code). |
|
|
This map is
fully operational with the Redix
XML HIPAA Package. The map
definition allows users to
translate a file from the HIPAA
837 Professional format
to the NSF Version 3.01
format, while also validating
the input for completeness, as
well as syntax and code
validation
and versions. Additional
effort has been made to provide
a 1:1 mapping ratio of the NSF
fields to HIPAA 837 elements. |
Documentation
|
A spreadsheet
(HIPAA_837_ProftoHCFA_NSF_31.xls)
is provided to document the map
definition on an element level.
Every element is marked as a
mapped, unused, constant, or
conditional map. |
|
|
Integrating the
Map Definition into the Project
Environment
|
Once the map
files (IFD and OFD) are
generated, the user may then add
the IFD and OFD files to the
production environment. |
|
Redix offers
the ability to add a translation
file to the production
environment through the use of
the Application Programming
Interface (API). The API is
supported in C/C++, Visual C++,
Visual Basic, JAVA™, and
command-line formats, e.g.,
redix. If the user uses the
Redix Automation Processor
(RAP), then the user can also
use the RAP's API with the above
programming languages.
|
|
After the
Configuration tab is filled in
and saved, a user may then move
to the Integration tab, where
Redix provides a GUI to
automatically generate API
details. A similar GUI exists
for both the AnyToAny, AnyToXML,
and Redix Automation Processor
Areas. |
|
The user can
use the information generated
from the Integration tab to
automatically generate API
statements or JAVA classes that
can be copied and pasted into
the user's existing application
environment. |
|
Direct Engine
Interface
redix_app_ext(String
input_filename, String
ifd_filename, String
ofd_filename, String
ack_filename, String
error_filename, String
output_filename, char
conversion_flag, char
segment_terminator, char
element_separator, char
composite_separator, char
release_char, String UserData); |
|
Redix Automation
Processor Interface
redix_process(String
input_filename, String
configuration_filename, String
log_filename, String userdata,
String last_event_log, String
last_filename, String
summary_filename); |
|
Redix
also
provides
a similar set of
API's for those who would prefer
to do the conversion using the
memory approach.
|
|
With the use
of the Redix API, the HIPAA 837
Professional
to the NSF Version 3.01
map can be added to any existing
application. |
|
|
|
|
|
|
