To return to the live map, visit ertrack.net
At this time we are supporting two API endpoints:
https://ertrack.net/api/hospitals/
This will return a JSON object of all facilities tracked with fields:
Field | Explanation | Type | Example |
---|---|---|---|
hospital_id | Unique ID for querying data from ERTrack | Integer | “347” |
hospital_name | Name of facility | String | “Medical City Weatherford” |
address | Street address of facility | String | “713 East Anderson Street, Weatherford, TX 76086” |
lat | Latitude | Float | “32.748191” |
lng | Longitude | Float | “-97.78565” |
county | County in which facility is located | String | “Parker” |
state | State in which facility is located | String | “TX” |
fips | 15 digit FIPS code | String | “483671402003000” |
https://ertrack.net/api/hospital/{hospital_id}/metadata/
Returns a JSON object with the metadata for hospital with a given hospital_id
, containing the same fields as above.
https://ertrack.net/api/hospital/{hospital_id}/history/
Returns a JSON object with the history for hospital with a given hospital_id
, containing the same fields as above.
Field | Explanation | Type | Example |
---|---|---|---|
observation_times | List of times for which we have observations | List of time strings | [“2020-03-26 20:35:34+00:00”, “2020-03-26 20:50:34+00:00”, …] |
wait_time_mins | Value in minutes (-1 if facility closed at that time) | List of integers | [“10”, “11”, “7”,… ] |
Different facilities have different history lengths, depending on how long they have been in our database. The times are all based on public feeds from the facilities and different facilities may construe “wait time” to mean different things. By “wait time” some facilities mean time to next appointment, while others mean “time to intake for walk-ins”. For this reason we urge caution when comparing between different facilities.
For inquiries, contact us.