Getting the Data

There are multiple options suggested for getting the data into the OpenLDR database. These are the standard options you will see for any data transfer. The goal is to work with whomever manages the data at the originating location in order to find the option which works best for them but is also within your budget and capabilities.

• • Direct inserts into database

  • HL7 import interface

  • Custom file import

Direct Database Inserts

If you have a data provider which has a large amount of data to transfer and the proximity and security work out, they might find it easiest to insert data directly into the repository. There will have to comply to some general rules; like being able to schedule and do a batch update rather than trickle updates.

HL7 File

An HL7 file format has been defined to allow data providers who can produce an HL7 extract of their data. This is a good option for the OpenLDR administrator because if there are many data suppliers there is only a single format for the data. There is not currently an HL7 import engine but when there is a requirement it is planned to use MIRTH and configure it for the OpenLDR data structure. It is not planned to have a direct electronic interface but instead to stick with the file import methodology. No extraction of the data via HL7 from the OpenLDR data structure is planned but could be implemented if needed.

The HL7 file format is defined in the HL7 Specification for V2.5. Version 2.5 is the most common version in use. The segments utilized are documented on the OpenLDR Database table pages.

Custom File Import

Some data providers might find it easier to extract the data in a format other than an HL7 file format. This puts more burden on the OpenLDR administrator because they will have to write an import routine for each file format submitted. One way to alleviate this burden is to suggest they put the data in the same format as the tables. For example, they could send three files, or even just two, that mimic the exact table structure of the OpenLDR tables: Requests, LabResults, Monitoring. Many of the fields would be optional but keeping the file consistent would be advantageous if others found it convenient and easy to use the same file structure. Some suggestions for standardizing the process:

• • ANSI text file

  • Fields delimited using pipe symbol(|)

  • If a delimiter is required within a field use the tilde (~)

  • Scheduled data transfers

It should be assumed that both HL7 and custom data files can contain unique data each time or a complete set of data. The import utility will be required to perform the correct update or insert.