Skip to main content

Interface to PointClickCare (PCC): Configuration Options for Residents Moving Between PCC Facilities for Different Levels of Care

Kevin U
  • Updated

About Moving Residents Between PointClickCare (PCC) Facilities

If your MealSuite account utilizes a PCC Connect interface and there are multiple PCC facilities (i.e., Independent Living, Assisted Living, Health Care, Memory Care, Rehabilitation, etc.), you have the following setup options to determine what occurs in MealSuite when a resident is moved between PCC facilities for a different level of care:

PCC_Connect_people_group.png

Keep a Single Profile and Move that Profile Between People Groups (Recommended) 

A profile moves between people groups when the resident of that profile moves between PCC facilities for a different level of care.

Example: John Doe resident is an active resident in the PCC Independent Living facility and the associated Independent Living people group in MealSuite. A John Doe profile with the same Organization Master Patient ID (OMPID) is then admitted to the PCC Health Care facility. The existing John Doe profile in the Independent Living people group will be moved to the Health Care people group rather than a new and separate profile being created.

Benefit: The benefit of this setting is that it eliminates duplicate profiles and keeps the same personal menu customizations and profile notes intact when the resident transitions to a new level of care specific to a PCC facility.

If you are MealSuite Support, ensure the Keep a Single Profile per Resident is selected (i.e., enabled) in PCC Connect Interface: API Settings to maintain one profile and move that profile between people groups. 

Notes:

  • The moving of a resident profile to a people group is trigged via an admit message or LOA return message from the PCC facility linked to that people group in your MealSuite account. Therefore, their latest PCC profile info from that PCC facility (diet order, allergens, rooms, LOA status) will be updated in their profile in the Core system.
  • After the move has occurred to a people group, any subsequent messages received from the previous PCC facility will be ignored and not used to update the associated profile (unless of course the resident is readmitted to the original PCC facility). The Connect screen displays such ignored messages with “Ignored due to PCC transfer”.
  • OMPID is a PCC term and stands for Organization Master Patient ID. Each PCC resident is assigned a unique OMPID that remains the same across all PCC facilities.
  • When a resident is moved to a PCC facility for a different level of care, that resident will be assigned an internal ID and external ID that is specific to the PCC facility. 
  • For MealSuite accounts that use the Touch app or POS, a daily sync is triggered for residents (using the OMPID) to ensure their PCC info is up-to-date.
  • Any assigned meal plan will be lost. Therefore if the meal plan should remain active regardless of the level of care (i.e., a PCC facility), then the profile must be assigned the meal plan each time that profile is transferred to a facility. This can be done manually in Touch Admin; see Assigning a Meal Plan to Diner. However the assignment of meal plans to residents in the POS can also be done automatically via the PCC API. To enable the PCC API to automatically assign meal plans to residents in the POS, see Enabling PointClickCare (PCC) to Assign Meal Plans to Residents in POS.

Keep a Separate Profile in Each People Group

When a resident changes their level of care (i.e., PCC facility), a new and duplicate profile will be created in the people group that is associated with the PCC facility. When an update is made to the resident in a PCC facility, MealSuite updates only the profile in the people group associated with that PCC facility. 

Example: John Doe resident has a profile in the Independent Living people group and another separate profile in the Health Care people group. When the PCC Independent Living facility sends MealSuite a diet order update, then only the profile in the Independent Living people group is updated with the new diet order. 

Benefit: The benefit of maintaining separate profiles is that the resident has unique personal menu preferences and notes specific to the level of care provided by a PCC facility. In addition, POS charges can be made specific to a PCC facility.

If you are MealSuite Support, ensure the Keep a Single Profile per Resident is not selected (i.e., disabled) in PCC Connect Interface: API Settings to maintain separate profiles in each people group. 

Notes:

  • A separate profile in each people group will result in "duplicate" profiles in the Touch app and POS. As long as a profile is active in a PCC facility, then that profile will also be active in the associated people group in your account. 
  • The meal plan associated with a profile will be maintained when that profile is duplicated in another group; and thereby preclude the need to assign the profile in each facility with a meal plan assignment. 

Recommended: Add the People Group Column to the Connect Screen

Regardless of which option you choose, when you have multiple PCC facilities linked to the same
MealSuite account, it is highly recommended to add the People Group column to the Connect
screen to allow you to easily see which people group/PCC facility has sent the Connect message. See the following article for instructions on adding columns: Setting Preferred Columns on the Connect Screen. 

Other Things to Know

If your account is configured to maintain one profile, and a resident is currently archived, then when a LOA return message is received from a facility the resident is not currently in, then the interface will unarchive the resident and move them to the associated people group of the facility the message was received from.

For example, if the resident is archived in People Group A (i.e., Facility A), and a LOA return message is received from Facility B, the resident is unarchived and moved to People Group B.