Interface to PointClickCare (PCC): Data Points

Interface to PointClickCare (PCC): Data Points
- Webhook Trigger from PCC and Two-Minute Delay
How Diet Interventions are Handled
How Do Not Serves are Handled

The following PCC data points are processed by the PCC Connect interface during a PCC sync with resident/patient profile:

PCC Data	Processed in Resident/Patient Profile As (i.e., the Field that is Populated)
First Name Last Name Middle Name	First Name Last Name M.I.
Sex	Gender
Date of Birth	Date of Birth
Admission Date	Admit Date
External ID (contains MRN as the value)	Client ID
MRN	MRN
Ethnicity	Ethnicity
Unit Floor Room Bed	Area Floor Room Bed
Leave of absence	Person Off Premise Dates (optional)
Diet Texture Fluid Diet intervention Additional directions note*	Diet Type or Diet Intervention Texture Type Fluid Type Diet Intervention or Diet Type Profile Notes (optional)
Diet Order On Hold	Populates NPO to Diet, Texture, and Fluid fields in resident/patient profile.
Food Allergies Intolerances	Allergens Intolerances can be processed as Do Not Serve or Allergens
Resident Photo	Profile photo (optional)

*Supplements do not flow automatically to the resident profile. If you add an Additional directions note in PCC, the note comes through as a profile note in the resident's profile. You can then use this note to customize the resident's personal menu with a supplement. To do so, see Supplements.

*Adaptive aides do not flow automatically to the resident profile. If you add an Additional directions note in PCC, the note comes through as a profile note in the resident's profile. You can then use this note to customize the resident's personal menu with an adaptive aide. To do so, see Adaptive Aides (Equipment).

Webhook Trigger from PCC and Two-Minute Delay

Immediately upon a patient being updated in PCC, a webhook notifies MealSuite to trigger a call and run a profile sync to update the entire profile to match the PCC profile.

By default, a two minute delay exists between when Connect receives the webhook and when Connect retrieves the updated info from PCC. Having this delay allows time for the data in the PCC backend tables to be updated before Connect retrieves it; therefore ensuring information is complete in MealSuite.

How Diet Interventions are Handled

If an EHR diet intervention exists in a Connect mapping relationship, then it can be subsequently unassigned from a MealSuite resident/patient profile during a PCC sync if that diet intervention no longer exists in the EHR profile.

When a diet intervention is added directly in your account (as opposed to being sent from PCC), it will therefore not exist in a Connect mapping relationship. As such, if such a diet intervention is assigned to a resident/patient profile, then that diet intervention is unaffected from a PCC sync and therefore cannot be unassigned from a resident/patient profile. For example, if you have a decaf coffee intervention that was created directly in your MealSuite account, then during a PCC sync the decaf coffee intervention will never be removed from profiles that it is assigned to.

How Do Not Serves are Handled

Assuming intolerances are configured to be processed as do not serve (DNS) customizations in a MealSuite account, the following occurs:

If a DNS customization (i.e., preference group is marked as DNS) was assigned to a MealSuite resident/patient profile as a result of an EHR intolerance, and assuming that preference group is not mapped to another EHR intolerance, then the DNS customization can be subsequently unassigned from the MealSuite resident/patient profile during a PCC sync if that intolerance no longer exists in the EHR profile.

Note that the PCC Connect interface will never remove any DNS that was directly added to a resident/patient profile in a MealSuite account.

Webhook Trigger from PCC and Two-Minute Delay

Immediately upon a patient being updated in PCC, a webhook notifies MealSuite to trigger a call and run a profile sync to update the entire profile to match the PCC profile.