...
Base URL: /getPatients
Parameters:
| Name | Type | Mandatory | Description |
|---|---|---|---|
| token | String | Yes | Security Token obtained before. |
| userId | String | Yes | The id of the logged in user. |
| location | ENUM | No | Possible values: ['ORGANIZATION', 'FACILITY', 'WORKSPACE', 'ROOM']. The location that we want to use as filter. If this value is not specified the operation will return all the patients the user can 'see' according to the permission he/she has: LIST_PATIENTS_FROM_ALL_ORGANIZATIONS, LIST_PATIENTS_FROM_CURRENT_ORGANIZATION, LIST_PATIENTS_FROM_CURRENT_FACILITY. |
| locationId | String | No, unless 'location' is specified | The id of the location that we want to use as filter. |
API Sample
curl 'http://192.168.2.102:8080/PresentationServices/getPatients?userId=poda&token=d2360c39-637b-41da-988d-f031db5affbb&_=1395133673254' -H 'Accept: application/json, text/javascript, */*; q=0.01' -H 'User-Agent: Mozilla/5.0 (Linux; Android 4.4.2; Nexus 5 Build/KOT49H) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/30.0.0.0 Mobile Safari/537.36' --compressed
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
{
"patientsFact": {
"statusFact": {
"success": true
},
"patients": [
{ "admissionDate" : "2013-04-12",
"age" : {"32",
"patientIdageUnit" : "000000003f59c2aa013f688d0fee002fwks",
"chartId" : "peggy ncabsi7",
"deliveryType" : "Inborn",
"facilityId" : "Vidant",
"facilityName" : "Vidant",
"headCircumference" : "33.00",
"agelength" : "4033.00",
"ageUnitorganizationId" : "wksUNC",
"weightorganizationName" : "750UNC",
"weightUnitpatientId" : "g777777773d8f5de2013dff67a76e00f6",
"roomId" : "vidant_poda",
"roomName" : "Pod A",
"weight" : "1110.000",
"lengthweightUnit" : "60g",
"headCircumferenceworkspaceId" : "30.0vidant_nursery",
"workspaceName" : "Nursery"
},
{ "admissionDate" : "20142013-03-01",04-12",
"age" : "32",
"ageUnit" : "wks",
"chartId" : "8",
"deliveryType" : "Inborn",
"facilityId" : "Vidant",
"facilityName" : "Vidant",
"headCircumference" : "33.00",
"length" : "33.00",
},"organizationId" : "UNC",
"organizationName" : "UNC",
{ "patientId" : "888888883d8f5de2013dff67a76e00f6",
"roomId" : "(Discharged)",
"roomName" : "000000003f59c2aa013f68922c520035Pod A",
"weight" : ..."1110.000",
"weightUnit" : "g",
"workspaceId" : "vidant_nursery",
"workspaceName" : "Nursery"
},
....
]}} |
Patients Assignment
Current Implementation
A patient can be currently assigned to a user by selecting it from the drop down present in Patients Assignment view, or via NFC or bar code scanning. The association between a patient and a user is used to determine the potential receivers of an alert that is generated for a patient.
Forms can only be submitted for currently assigned patients. This restriction is not enforced in PS but in the client application.
Parameters
Base URL: /associatePatientToProvider
Parameters:
| Name | Type | Mandatory | Description |
|---|---|---|---|
| token | String | Yes | Security Token obtained before. |
| userId | String | Yes | The id of the logged in user. |
| patientId | String | Yes | The id of the patient we want to associate with userId |
API Sample
curl 'http://192.168.2.102:8080/PresentationServices/associatePatientToProvider?patientId=000000003f59c2aa013f6898a5470043&userId=poda&token=d2360c39-637b-41da-988d-f031db5affbb&_=1395133673258' -H 'Accept: application/json, text/javascript, */*; q=0.01' -H 'User-Agent: Mozilla/5.0 (Linux; Android 4.4.2; Nexus 5 Build/KOT49H) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/30.0.0.0 Mobile Safari/537.36' --compressed
...