Objectives
1. Manually fetch full patient lists from an existing
PointClickCare community to import into FullCount.
Prerequisites
Ability
to make an HTTP request. Instructions will use Curl, but other options
include PostMan or other online tools.
Access
to Integrations keepass.
Microsoft
Excel installed.
Instructions
Obtain PointClickCare patient list for a FullCount
Community.
The
FullCount integration-pcc application has an endpoint open to basic header
authentication located at ../internal/patients/{orgId}
The
endpoint is designed to get all Patients for a provided Point Click Care orgUuid
and facId.
HTTP Request
Authorization
Header value: "Authorization: Basic
<Base64 encoded username:password>"
note: username and password values as well as the
base64 value can be found in Integration keepass under 'PCC Integration -
Internal' entry.
Parameters
Path Parameter : 'orgUuid' - Point Click Care designated
Organization UUId
Query Parameter : 'facId' (required) - Point Click Care
designated Facility Id
Query Parameter : 'status' (optional,
available={'Current', 'Discharged', 'New'}, default='Current') - desired
patientStatus to fetch
Query Parameter : 'withAllergies' (optional, available =
true/false, default = false) - true if allergy information should also be
gathered for each patient. (Note: this is a separate api call, and will add
significant time to the request). If false no allergy information will be
included.
Query Parameter : 'withFacility' (optional, available =
true/false, default = true) - true if facility information should also be
gathered for each patient. (Note: this is a separate api call). If false no
facility information will be included.
Query Parameter :'withNutritionOrders' (optional,
available = true/false, default = false) - true if nutrition order information
should also be gathered for each patient. (Note: this is a separate api call,
and will add significant time to the request). If false no nutrition
information will be included.
Response
Successful response Http Status Code 200 with Response
Body similar to below example:
{
"paging": {
"hasMore": false,
"page": 1,
"pageSize": 107
},
"data": [{
"orgId": 1504955675,
"facId": 22,
"patientId": 7792,
"roomId": 2083,
"floorId": 243,
"unitDesc": "44C8D75E-",
"patientStatus": "Current",
"bedDesc":
"A",
"bedId": 3910,
"roomDesc": "24",
"floorDesc": "Main",
"unitId": 494,
"firstName": "Louie",
"lastName": "Abbott",
"birthDate": "1948-09-11",
"admissionDate": "2015-11-29",
"deceased": false,
"gender": "FEMALE",
"hasPhoto": true
},
...
]}
Paging - PageSize will be total records found.
Data - List containing JSON entries representing
individual Point Click Care Patients.
The Json response body should be placed into a file that
we can then access from excel.
example Curl:
Generate a valid Excel file for upload
Open
Microsoft Excel
Navigate
to 'Data' ribbon, then 'Get Data -> From File -> From JSON'
Select
recently created patient .json file.
Right
Click on 'List', then 'Into Table', accept blank delimeter.
Click
on expand columns (Make sure 'Use original column name as previx' is NOT
checked)
This
should expand all Patient data into separate columns. Now click 'Close
& Load'
Save
the document.
Synchronize PointClickCare patient list for a FullCount
Community
The
FullCount integration-pcc application has an endpoint open to basic header
authentication located at ../internal/patients/{orgUuid}/synchronize
The
endpoint is designed to get all Patients for a provided Point Click Care orgUuid
and facId.
HTTP Request
Authorization
Header value: "Authorization: Basic
<Base64 encoded username:password>"
Note: username and password values as well as the
base64 value can be found in Integration keepass under 'PCC Integration -
Internal' entry.
Parameters
Path Parameter : 'orgUuid' - Point Click Care designated
Organization Id
Query Parameter : 'facId' (required) - Point Click Care
designated Facility Id
Query Parameter : 'communityId' (required) – FullCount
Community Id
Query Parameter : 'status' (optional,
available={'Current', 'Discharged', 'New'}, default='Current') - desired
patientStatus to fetch
Query Parameter : 'withAllergies' (optional, available =
true/false, default = false) - true if allergy information should also be
gathered for each patient. (Note: this is a separate api call, and will add
significant time to the request). If false no allergy information will be
included.
Query Parameter : 'withPhoto' (optional, available =
true/false, default = true) - true if photos should also be gathered for each
patient. (Note: this is a separate api call, and will add significant time to
the request). If false no photos will be included.
Query Parameter : ‘withFacility’ (optional, available =
true/false, default = true) - true if facility information should also be
gathered for each patient. (Note: this is a separate api call, and will add
significant time to the request). If false no facility information will be
included.
Query Parameter : ‘withNutritionOrders’ (optional,
available = true/false, default = false) - true if nutrition order information
should also be gathered for each patient. (Note: this is a separate api call,
and will add significant time to the request). If false no nutrition order
information will be included.
Response
Successful response Http Status Code 200 with Response
Body similar to below example:
100 rows created.
example Curl: