A facility may download encounters for patients in their catchment for offline access to patients' records. This applies to any other system like a CHW system, or other subsystems requiring access to data either for clinical or for analytical purpose.
The API returns encounters of patients in a given catchment. The catchment is defined by central systems like a Facility Registry.
In BDHIE context, the catchment is defined as a "location id" defined by the "Location Registry", corresponding to the Geo location codes defined by BBS and provided through Location Registry (DGHS HRM system).
The applicable catchment definition for an establishment is done through the "Facility Registry" (DGHS HRM system).
For example:
Location of Dohar Upazila of Dhaka district is defined as
/locations/302618.json
{
"code": "18",
"id": "302618",
"name": "Dohar",
"type": "upazila",
"active": "1",
"hierarchy": [
{
"code": "30",
"name": "Dhaka",
"type": "division"
},
{
"code": "26",
"name": "Dhaka",
"type": "district"
},
{
"code": "18",
"name": "Dohar",
"type": "upazila"
}
]
}
The "id" attribute (above) defines the "catchment id" for the catchment encounters API.
catchment is defined as extended attribute "catchment" above. Note that a facility may have multiple catchment, in which case, the catchment attribute will list comma-separated values of the location id.
For example, if the above facility also serves people of "Dhamrai" upazila of Dhaka district, then the catchment returned be ["302614", "302618"]
NOTE: An establishment can also request encounters for locations included within the catchment as well. For example, "Dohar Upazila Health Complex" can request for "Dhamrai Paurasava" (30261860).
Authentication & Authorization
Only authenticated establishment having requested catchment will be returned with appropriate results.
API
URL
GET /catchments/{catchment id}/encounters
Request
{catchment id} - id of catchment requesting patient encounters for.
Filters
updatedSince - return patient encounters updated since a particular date expressed in ISO 8601 format. e.g) 2014-10-16T18:22:20Z supported formats are listed below. For example, consider date is Nov 03 17:24:52 IST 2014
yyyy-MM-dd'T'HH:mm:ss.SSSZ - ISO Date with milliseconds. e.g. 2014-11-03T17:24:52.769+0530
yyyy-mm-dd'T'HH:mm:ssZ - ISO Date with seconds. e.g. 2014-24-03T17:24:52+0530
yyyy-MM-dd HH:mm:ss.SSSZ - UTC Date with milliseconds e.g. 2014-11-03 17:24:52.769+0530
yyyy-MM-dd HH:mm:ssZ - UTC Date with seconds e.g. 2014-11-03 17:24:52+0530
yyyy-MM-dd HH:mm:ss - Current Date with seconds e.g. 2014-11-03 17:24:52
yyyy-MM-dd - Simple Date e.g 2014-11-03
No labels
0 Comments
You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.
0 Comments