HIEBus™ SDF Implementation Guide

This specification defines the preferred flat file format to be used in exchanging data with CareEvolution’s HIEBus™. The same file format can be used for sending data to, and receiving data from HIEBus™.

HIEBus™ can leverage the standard data format for inputting data into and extracting data from HIEBus™. A typical strategy for an ongoing interface is to perform a one-time initializing historical extract from the source system followed by periodic incremental updates. The frequency of the incremental updates is determined on a case by case basis. Daily or twice daily updates are the most common.

Each data extract or import is composed of a set of related files with each data type being contained in a distinct file. There may be two files per data type, a “current” file containing currently valid data for that data type and an “archive” file containing records that should be considered deleted or invalid. The field layout for each file will be dependent on the type of data in the file. See Record Types to learn about the field layouts for each data type. The field layout for the current files is identical to the field layout for the archive files. See Data Types and Referential Integrity for a list of data types and follow the links for details on each. The records in each file will have a varying field layout dependent on the type of record contained in the file. The first field in each record will indicate the type of data contained in that file.