|
Things
to know about EDI file submissions:
1.
Do not ignore the warnings in the warnings file. These may contain important
information requiring action on your part.
2.
The only updates that are allowed to existing diagnoses via new EDI files are
changes in primary/secondary status. If the date or DSM code on an existing
diagnosis are changed, the change will be entered as a new diagnosis, and the
old diagnosis will need to be deleted via the AIMS Data Manager application.
3.
Services cannot be updated at all via EDI files. If the service units or
location of service (LOS) are changed on an existing service and this revision
is sent in a file, you will get a duplicate service warning, and the existing
service will not be changed. To change units or LOS you must use the AIMS Data
Manager. If other data, such as service code, is changed on an existing
service and the revision is sent in a file, the system will consider the
revision as an entirely new service. In this case you will need to manually
delete the original service via the AIMS Data Manager.
4.
Screenings are also not updateable via EDI files. Once screenings have
been established for a consumer on a given date, any changes to those screenings
must be done using the AIMS Data Manager. If a new file tries to send
screening information with the same date as existing screenings, a duplicate
screening warning will be generated, and the screening information from the new
file will not be applied to the database.
5.
If a CM or CSS Stop Reason is sent in a file without an accompanying
chronicity, an implied chronicity will be associated with the stop reason.
This will be whatever chronicity the consumer had most recently prior to the
new stop reason. (In other words, the existing chronicity for the consumer
will be maintained.) You will get a data warning if this happens, and can
explicitly adjust the chronicity if desired.
6.
In order to update an existing CSR record via EDI file, both the report period
and the review date for the original CSR must be matched. If either report
period or review date does not match, the submitted data will be entered as a
new CSR.
7.
CBCL data is supposed to be sent at six month intervals. If CBCL data is sent
too early, it will be rejected and will generate a data warning. In some cases
these early CBCLs may be intentional; the only way to enter an intentionally
early CBCL is via the AIMS Data Manager.
8.
If the AIMS UID for a consumer is changed in your database, you must also
change the AIMS UID in the AIMS Repository with the AIMS Data Manager
application. If this is not done, you run the risk of duplicate consumers and
possible lengthy data cleanup. Once an AIMS UID is changed, it is important to
send the new UID in all future files.
|
