Patient Schedule / Demographics File Field Specification (CSV)
schedule_in.csv
schedule_in.csv.resp
File format is standard CSV (http://www.ietf.org/rfc/rfc4180.txt).
Patient Visit
| Field Index | Description | Format | Required | Max Len |
|---|---|---|---|---|
| 1 | Appointment Date | mm/dd/yyyy | No | 10 |
| 2 | Appointment Time | HH:MM (AM/PM) | No | 15 |
Patient Information
| Field Index | Description | Format | Required | Max Len |
|---|---|---|---|---|
| 3 | First Name | Yes | 50 | |
| 4 | Last Name | Yes | 50 | |
| 5 | NPI | No | 20 | |
| 6 | Patient ID | No | 50 | |
| 7 | Encounter ID | No | 50 | |
| 8 | Date of Birth | mm/dd/yyyy | No | 10 |
| 9 | Gender | M = Male, F = Female | No | 1 |
| 10 | Address Line 1 | No | 50 | |
| 11 | Address Line 2 | No | 50 | |
| 12 | City | No | 50 | |
| 13 | State | No | 2 | |
| 14 | ZIP Code | 999999999 | No | 9 |
| 15 | Primary Phone Number | 9999999999 | No | 10 |
| 16 | Mobile Phone Number | 9999999999 | No | 10 |
| 17 | Email Address | No | 128 |
Primary Carrier
| Field Index | Description | Format | Required | Max Len |
|---|---|---|---|---|
| 18 | Payer Name/ID | No | 50 | |
| 19 | Plan Name/ID | No | 50 | |
| 20 | Member ID | No | 50 | |
| 21 | Group ID | No | 50 |
Example record
"05/03/2011","10:00 AM","SMITH","JOHN","0977875","CLG.11224"," CLG.11224*66","11/28/1971","M","1400 BIRCH ST","","HINESVILLE", "GA","31313","9123211234","9123211235","JSMITH@MYISP.COM","UNITED HEALTHCARE","932000000","700000","8ACC00-1"
Response File
A response file will be generated during the import of the schedule file. There will be a row in the response file for each record processed. The row will contain the line number in the schedule file being processed, the Patient ID, and the Encounter ID. If an exception occurs during the processing of a record, the details of the exception will be included at the end of the row.
Example response file
"1","CLG.11224","CLG.11224*66" "2","CLG.11233","CLG.11233*170","Data too long for field ZIP Code"
Notes
If the Patient ID field is populated, a patient record will be created for the patient if one does not already exist. If a matching patient record is found, it will be updated with the data from the file.
The patient schedule file can be used to load patient demographics by leaving the appointment data end time fields empty. The Patient ID field must be populated in order to create a patient record.