<< Click to Display Table of Contents >> Navigation:  Introduction > Generic ADT Interface

 

Overview

 

Plato Generic ADT Interface allows you to import your hospital ADT data. In keeping with the spirit of PDA Professional where everything is user defined, interface is capable of importing any number, type and order of the fields. It imports flat ASCII files made available to it from your hospital ADT system. It does not conform to HL7 interface specifications for import over a TCP/IP feed; for which you should consider 'Plato HL7 ADT Interface'. However for the needs of PDA Professional, we recommend this generic interface, as it has been specially designed for this application. Once Plato has received data it can then be integrated with Plato Data Analyzer using PDA Professional Interface.

 

Each hospital has a unique set of fields in their ADT feed and can have different types of fields defined in PDA Professional. ADT systems at the hospitals are rigid in nature in terms of the format and order of the data that can be dumped to an ASCII file. We do not force any field order or format. As long as the data is in a comma-delimited or fixed-width file Plato can import it.

 

Specifications

 

ASCII files must adhere to the following guidelines:

 

a.ASCII files can be either in the CSV (comma separated values) format or fixed-width format. It cannot import files that are delimited by any other character other than comma e.g. tab or semi-colon.

b.ASCII files need to be made available on the drive location accessible to the Plato Interface application, either on its server or on another server (accessible via a share from Plato server).

c.We do not dictate the order and number of the fields; it is up to the hospital to choose the order and number of fields. Interface configuration will allow you to setup at what offset a particular field is.

d.There should be one row for each ADT record including both patient related information (patient demographics) and visit related information.

e.At the most there can be 15 demographic related fields and 30 visit related fields.

f.Each field can be a maximum of 50 characters long.

g.Facility ID or name should be a part of each ADT record. This ID / name should match exactly with the facility defined in PDA Professional.

h.Each ADT record should contain Patient ID (Medical Record Number) and Account ID (Visit ID).

i.Interface is capable of handling the updates i.e. if a record was first sent when patient was admitted and then again when he was discharged or for some other reason; the interface will update the old record.

j.Interface is capable of importing files for more than one facility. ASCII files from all facilities should have the same format e.g. if Patient ID is appearing at offset 3 for the first facility than you cannot have Patient ID at offset 6 for second facility.

 

Sample ASCII File

 

Here is a sample of a comma delimited ASCII file:

The fields are:

 

 

Blank dates can passed as null or 00/00/0000.

 

Space Requirements

 

Each of the 15 demographic related fields and 30 visit related fields are stored in variable length character fields (maximum 50 characters each). It will be decided at the time of implementation how many for those fields to use. Thus the record size will depend on how many fields are used and how much data is put in those fields. For the example above a typical record size will be (for the simplicity of the example we will assume that each of the text fields have 30 characters):

 

Demographic Data:

 

 

Visit Data: