Flat File Integrations - Appointments
File Name
When sending the file to the server it should be named using the following format: "appointments_{timestamp}.csv"
Which Data
We support sending all future appointments up to 14 days in advance and all appointments that occurred in the previous 7 days
Data Fields
NOTE: Please follow all field name and note formats, including case sensitivity.
Item | Field name | Format | Req’d | Notes |
identifiers | identifiers | Identity |
Y | See id format |
mrn | mrn | string | Y | MRN of the patient this appointment belongs to |
start time | start | FHIR dateTime | Y | E.g. 2022-05-03T14:35:50 See https://www.hl7.org/fhir/datatypes.html#dateTime |
duration | minutesDuration | integer | Y | Duration of the appointment in minutes. |
status | status | proposed | pending | booked | arrived | fulfilled | cancelled | noshow | Y | See https://www.hl7.org/fhir/valueset-appointmentstatus.html |
Primary provider | providerId | string | Y | |
Organization | organizationId | string | Y | This will be used to tie the appointment to a care episode in the event careEpisode Id is not provided. |
Episode of Care | careEpisodeId | string | n | If care episode integration is enabled |
Service Type | serviceType | string | n | See https://www.hl7.org/fhir/valueset-service-type.html for default codeset, we can also handle other/custom codesets |
42 CFR Part II status | coveredBy42CfrPart2 |
yes/no | N | Valid “yes” values are “1”, “y”, “yes” and “true”. Valid “no” values are “0”, “n”,”no” and “false”. |