4.7 File Based Import

OHI Components applications support file based data import for the following entities:

• Import Providers and Provider Groups
• Import Relations

Uploading files and processing the file contents is a two step process:

1. Upload the file using Data file set integration Point
2. Process the file contents by initiating the proper activity type using the Activities Integration Point.  

• Provider Import activity type to process the file based request for the provider integration point.
• Relation Import activity type to process the file based request for relation integration point.

Parameters

The parameters for the file import based activity are as follows:

• Data File Set Code
  This parameter indicates the data file set that needs to be processed. 

The activity can be created only when the Indicator Locked on the data file set code is 'N' otherwise an error ACT-VL-FIAT-001 is raised. 

Once the activity picks up a data file set for processing (i.e. starts an created activity), it places a lock on it by updating the indicator Locked to 'Y'. If the indicator Locked is already found to be 'Y' then an error ACT-VL-FIAT-001 is raised. Activity must unlock the data file set in case if the processing completes with the error(s).

• Response Data File Set Code
  The data file set code that should be used for the data file set of the response file. If not provided the system generates a UUID based value as data file set code.

Data File Validation

The first step in every data file import activity is to check whether the datafile that is provided through the parameters is valid for the specific data import. The following checks are executed:

1. Does the datafile exist (i.e. is there a datafile in the datafile set)?
2. Is the datafile empty?
3. Is the datafile of the correct type for the import activity (i.e. does it have the correct root element)?

Error Message

The file import based activity can result  in the following messages:

Code	Sev	Message
ACT-VL-FIAT-001	Fatal	Data file set {code} is locked and cannot be picked up for processing.
ACT-VL-DAFI-001	Fatal	No data file exists in datafile set {code}.
ACT-VL-DAFI-002	Fatal	Data file {code} is empty.
ACT-VL-DAFI-003	Fatal	Data file {code} is of incorrect type for this integration point.