Miscellaneous > Generic ADT Interface

Overview

The Plato Generic ADT Interface imports patient demographic into Plato Data Analyzer Professional. Th interface is capable of importing any number or type, and can process order of the fields. It imports flat ASCII files made available to from your hosts system.

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. The Interface configuration will allow setup as to what offset a particular field is.

d.There should be one row for each 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 record. This ID / name should match exactly with the facility defined in Plato Data Analyzer Professional.

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

i.The 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.The 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:

7976, "SMITH, JONES", 343465, 8/21/1950, 48238498, 4/1/2005, 4/6/2005, 343, ER, 10

7976, "SNODEN, JOHN", 975864, 11/11/1951, 65356356, 4/1/2005,,345, ER, 11

7976, "CRAIG, JENNIFER", 234236, 6/11/1963, 63563455, 4/4/2005,, 343, ER, 34

7976, "HEWIT, RODNEY", 643563, 7/31/1976, 45345435, 4/4/2005, 4/5/2005, 654, ER, 16

7976, "CLIPPER, MARY", 634567, 1/26/2001, 54354355, 4/4/2005, 4/5/2005, 545, ER, 101

7976, "DOE, JOHN", 634504, 4/11/1958, 43534666, 4/6/2005, ,565, ER, 54

7976, "KUMAR, SRI", 645645, 6/27/1985, 34534543, 4/7/2005, 4/6/2005, 535, ER, 50

The fields are:

Field No	Description
1	Facility
2	Patient Name
3	Medical Record No
4	DOB
5	Account No.
6	Admit Date
7	Discharge Date
8	Physician
9	Department
10	DRG

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 simplicity's sake let's assume that each of the text fields have 30 characters):

Demographic Data:

Field	Size (bytes)
Facility	30
Patient Name	30
Medical Record Number	15
DOB	19
Other Internal Data	40
Total:	134

Visit Data:

Field	Size (bytes)
Account No.	15
Discharge Date	19
Physician	30
Department	30
DRG	3
Other Internal Data	40
Total:	147