GET /emr/reports/appointments/search


Get EMR appointment summary records either by id (native EMR id), contact_id (Call Center id), last_name (The last name of the patient) or chart (Amkia Account Number). If the id is passed, at most one record will be returned. If the contact_id is passed it is possible that more than one record is returned since a call center contact can have more than one appointment scheduled. When using the last_name parameter the query might be very slow and return a large number of results (depending on the last name).

This API method fetches data from the remote Amkai database (MSSQL).

Use case: Get data directly from the EMR source in its most up to date form (real-time).

Warning: This is an expensive query (joins on 20 tables) and is therefore not very performant. If large resultsets need to be processed use /emr/appointments/nrt/summary instead.

Resource URL

http://www.lsitampa.com/emr/reports/appointments/search.{response_format}

Method

GET

Response Format

json

Parameters

id - optional
The id of the emr appointment record to retreive. In the EMR system this id is the value of scheduling_abstractappointment.abstractscheduleissue_id.
contact_id - optional
The contact_id of the emr appointment record to retreive. In the EMR system this id is the value of reg_externalid.externalid.
type - optional
The type of the emr appointment record to retreive. Ex: surgery, consult, triage
last_name - optional
The last_name of the emr appointment record to search for and retreive. In the EMR system last_name is the value of reg_person.lastname.
chart - optional
The chart of the emr appointment record to search for and retreive. In the EMR system chart is the value of reg_account.accountnumber.
debug - optional
Used for debugging purposes
jsonp_callback - optional
If making cross domain Ajax calls use this as the call-back method name in your Ajax request.

HTTP Errors

400
{
  "error": {
    "code": 400,
    "message": "Bad request (if set by the developer, specific reason for bad request)"
  }
}
404
{
  "error": {
    "code": 404,
    "message": "Not found"
  }
}
500
{
  "error": {
    "code": 500,
    "message": "Internal Server Error"
  }
}