Platinum 5 – SoupedUp Catering Interface

Leecare Solutions are pleased to provide our clients with the benefits of Platinum 5’s (P5) interface with the SoupedUp Catering Software.  If your organisation is licensed to use SoupedUp Catering Software this interface will enable certain data to link based on the various functions that have been established.

1. Activating the P5 and SoupedUp Catering interface

    

   To obtain a quote for this interface please contact sales@leecare.com.au.

    

   The Leecare client managers will coordinate activation of the interface with the requesting organisation. Please contact clientmanager@leecare.com.au or phone 03 9339 6888 to book in this activity.

    

   An Initial Data load and checklist will be coordinated between Leecare, SoupedUp and the organisation, with clear steps and responsibilities to ensure a successful deployment of the integration interface.

    

   It is highly recommended that a trial interface is conducted to a UAT (test) environment first before a live interface activation occurs.

    

   Note: An upgrade to the latest P5 version may be required.

    

   Note: The ‘SoupedUp’ form will need to be activated or uploaded to your schema for use with this interface. The Leecare Client Manager will organise this activity during the interface activation.

    

   For the initial upload of information, the Leecare Client Manager will coordinate approx. 1.5hrs downtime – to ensure that the information sent in the first instance does not get updated during the initial upload.

    

2. SoupedUp Form vs P5 Dietary Details Form.

    

   A new form has been created to capture the dietary information that will be shared between the two programs, P5 and SoupedUp Catering Software. This has been done to ensure the format of the fields moving forward e.g. tick boxes vs free text etc. will match.

    

   As part of the interface activation, information that has previously been added to certain fields (see below) in the base P5 Dietary Details and Admission Dietary/ Nutrition forms will be migrated to the new P5 ‘SoupedUp’ form.

    

   Note – clients who have made custom changes and new fields to capture dietary information in P5 may need to manually transfer some information the ‘SoupedUp Form’ in P5.

    

   ·         The fields that are migrated should be made ‘not visible’ in the P5 schema once the organisation can confirm that the information has migrated to the new fields correctly.

    

   ·         As part of the initial activation:

   o    Existing P5 client / New SoupedUp Catering client:

   §  Each client’s ‘SoupedUp’ form in P5 will require saving once, immediately following activation, to prevent data being overwritten by SoupedUp Catering resident profiles.

   o    New P5 client / Existing SoupedUp Catering client:

   §  SoupedUp Catering resident profile to be saved after initial upload to migrate data from SoupedUp Catering to P5’s ‘SoupedUp’ form

   o    New P5 client / New SoupedUp Catering client:

   §  Decide which program will be the initial source of truth

   o    Existing P5 client / Existing SoupedUp Catering client:

   §  Decide which program will be the initial source of truth

    

   ·         An initial audit must be conducted by the client to ensure relevant information has been transferred for the above combinations, some information may need further editing e.g. No. of Sugars or Sweetener may come across as a number but not indicate which type.

    

   ·         List reports regarding dietary and drink details will need to be updated by the customer.

    

3. Business rules for the P5 / SoupedUp Interface

    

   • As P5 and SoupedUp Catering have differences in attaching residents to facilities, it is necessary to follow the below process to transfer a resident between facilities:

    

   o   Discharge from existing facility in P5

   • Admit to the new facility in P5 (this will then associate the resident to the facility)

    

   Note: Failure to follow the above process may result in the interface not working the correct way.

    

   • Where information from multiple fields in the Dietary Details form has been merged to the one field in the ‘SoupedUp’ form e.g. the Likes and Dislikes fields, please note that the total field size for the combined fields will be 2999 characters. If more information is present – only the first 2999 characters will be visible in the new fields.

    

   • Allergies are only updated using the P5 Adverse Reaction feature. This will update the ‘SoupedUp’ form in P5.

    

   • To transfer the data to SoupedUp Catering, the P5’s ‘SoupedUp’ form must also be saved.

    

   • If there has been an interface disruption – changes will need to be remade once the interface is reconnected.

    

   • Unadmitted Residents in P5 at time of interface activation

   • • Unadmitted Residents in P5  that have dietary information recorded will have linked information transferred to the ‘SoupedUp’ form in P5

     • Once admitted only new information transfers through the interface.

     • Users will need to be aware of this and ensure information is updated in SoupedUp Catering to ensure all data matches when it feeds back.

    

4. Information shared through the interface

    

   This interface enables:

    

   1.       The sharing of information from the ‘SoupedUp’ form in P5 to SoupedUp Catering.  The tables below are colour coded to help you identify the information.

    

   2.       Adding New Units, SubUnits, Beds and Rooms in P5 will automatically add them into SoupedUp Catering.

    

   3.       Admitting New Residents in P5 – automatically adds them to SoupedUp Catering.

    

    

   Information Sharing:

   • Green = information sent from P5 to SoupedUp Catering Only

   • Blue = information sent from P5 to SoupedUp Catering and SoupedUp Catering to P5

   • Pink = New Fields not previously included in P5

   • * = Existing information from Dietary Details form migrated to SoupedUp Form

    

   Field Name	Field Type	Look Up selections if applicable	* Data will be migrated from existing Dietary Details form to new SoupedUp form
   General Information
   First Name			*
   Last Name			*
   Preferred Name			*
   Gender			*
   Date of Birth			*
   Facility			*
   Unit (Wing)			*
   Room Number			*
   Consistency/ Texture/ Portion Size
   Serve Size	Drop Down	XS - Extra Small S – Small M – Medium L – Large XL - Extra Large	* Very Small = 'XS - Extra Small' Small = 'S – Small' Medium = 'M – Medium’ Large = 'L – Large' Very Large = 'XL - Extra Large'
   Diet Type (Food Texture)	Dropdown Selection	R - Regular S - Soft Cu - Cut Up S/CU - Soft/Cut Up MM - Minced Moist P - Puree PMSV - Puree Meat Soft Vegetables NBM - Nil By Mouth MMMSV - Minced Moist Meat Soft Vegetables	* Diet Type (Food Texture) Main Part of Meal only Normal='R - Regular' Texture A- Soft = 'S - Soft' Cut-Up = 'Cu - Cut Up' Texture B - Minced and Moist ='MM - Minced Moist' Texture C - Soft Pureed = 'P - Puree' Nil Orally ='NBM - Nil By Mouth' Not Mapped= Others
   Is the resident on fluid restrictions? - Tick if Yes	Check Box
   'Is the resident on fluid restrictions? (Specify daily allowance)'	Text box		* This field NOT currently mapped to SoupedUp itself but is on the SoupedUp form in P5
   Drink type/consistency (Thickened Fluids)	Dropdown Selection	MILD MOD EXT	* Level 150 / Mildly Thick (nectar)= Mild Level 400 / Moderately Thick (room temperature honey)= Mod Level 900 / Extremely Thick (pudding or mousse)= EXT NOT MAPPED -  Thin; Nil by mouth - fluids via enteral route; Nil by mouth - fluids via intravenous route; Nil by mouth - fluids via subcutaneous infusion; Nil by mouth Level 2 - Cream (please choose other option now as this term is no longer used by Speech Pathologists);
   Diet Type Fields
   Coeliac (C)	Check Box
   Dairy Free (DF)	Check Box
   Extra Gravy (EG)	Check Box
   Fortified (F)	Check Box
   Gluten Free (GF)	Check Box		*
   Halal (H)	Check Box
   High Calcium (HC)	Check Box		*
   High Energy (HE)	Check Box
   High Fat (HFT)	Check Box
   High Fibre (HF)	Check Box		*
   High Protein (HP)	Check Box		*
   Kosher (K)	Check Box
   Lactose Free (LFR)	Check Box
   Low Cholesterol (LC)	Check Box
   Low Fat (LFT)	Check Box
   Low Fibre (LF)	Check Box
   Low Potassium (LP)	Check Box
   Low Salt (LS)	Check Box
   Lactose Free (LFR)	Check Box
   Low Cholesterol (LC)	Check Box
   Low Fat (LFT)	Check Box
   Low Fibre (LF)	Check Box
   Low Potassium (LP)	Check Box
   Low Salt (LS)	Check Box
   No Acid (NA)	Check Box
   No Fat (NF)	Check Box
   No Mixed Consistency (NMC)	Check Box
   PEG Feed (PEG)	Check Box
   Vegetarian (V)	Check Box		*
   Weight Reduction Diet (WRD)	Check Box		*
   Type of diabetes	Radio - Button	Type 1 Type 2 Other	*
   Assistive Devices/ Cultural Religious
   Food Assistive Devices	Text Box		* Combines the three fields for: Plate; specific eating aids/utensils and Special Cutlery into the one Text field
   Beverage Assistive Devices	Text box Suggest	Tumbler, Thermal Mug, Double handed mug, Lid, Straw, Plastic feeder cup, Mug	*
   Cultural/Religious Specific Comments	Text Box		*
   Allergies
   Food/fluid allergies	Layered text		*
   Food/fluid sensitivities	Layered text		*
   Likes Dislikes
   Food and Drink Dislikes	Text Box		* Combines the seven P5 fields into the existing Food Likes field and rename to Food and Drink Dislikes
   Food and Drink Likes	Text Box		* Combines the six P5 fields into the existing Food Likes field and rename to Food and Drink Likes
   Breakfast
   Cereal	Text Box Suggest		* Porridge / oats, Corn flakes or similar, Weetbix or similar, Bran or similar, Muesli, Rice Bubbles, Nutrigrain, Special K or similar, Sultana Bran or similar, Other
   Milk	Text Box Suggest		* Hot, Cold, Regular, Skim
   Fruit	Text Box Suggest		* Prunes Whole X, Puree Prunes, Banana, Puree Fruit
   Toast	Text Box Suggest		* White, Wholemeal, Raisin Toast
   Spread	Text Box Suggest		* Butter, Margarine, Any, Marmalade, Vegemite, Peanut Butter, Honey, Strawberry Jam, Apricot Jam
   Juice	Text Box Suggest		* Orange, Apple, Prune
   Tea Coffee	Text Box Suggest		* Existing P5 four fields  Tea, Coffee, White, Black, Sugar, Equal
   Other Breakfast information	Text Box		*
   Drinks
   Morning Tea	Text Box Suggest		* Existing 13 fields to concatenate and transfer data to new P5 ‘SoupedUp’ form
   Snack	Text Box
   Lunch	Text Box Suggest		* Existing 13 fields to concatenate and transfer data to new P5 ‘SoupedUp’ form
   Afternoon Tea	Text Box Suggest		* Existing 13 fields to concatenate and transfer data to new P5 ‘SoupedUp’ form
   Snack 2	Text Box
   Dinner	Text Box Suggest		* Existing 13 fields to concatenate and transfer data to new P5 - SoupedUp form
   Supper	Text Box Suggest		* Existing 13 fields to concatenate and transfer data to new P5 ‘SoupedUp’ form
   Supplements
   Breakfast Supplement	Text Box		*
   Morning Tea Supplement	Text Box		*
   Lunch Supplement	Text Box		*
   Afternoon Supplement	Text Box		*
   Dinner Supplement	Text Box		*
   Supper Supplement	Text Box		*
   Dining Preferences
   Breakfast Pref seating	Text Box		*
   Morning Tea	Text Box
   Lunch Pref seating	Text Box		*
   Afternoon Tea Pref seating	Text Box
   Dinner Pref seating	Text Box		*
   Supper Pref seating	Text Box

    

    

   How to change the Apache Tomcat Default Logging Parameter in Platinum 5

   By default Platinum 5 sets the Apache Tomcat Logging Level to DEBUG.  It is set to the logging level of DEBUG to assist our Application Engineers in identifying and resolving issues within the Platinum 5 environment.

    

   Fig 1. Default Debug Logging Settings

   

   In Platinum 5.61.7 and above Leecare has implemented the ability to change the Logging Levels accordingly. Here’s how to change the Debug Logging Level in your environment.

    

   Adding Debug Edit Functionality to a role

   Step 1.  From the Home Menu click on Tools  

   Step 2.  Locate “User Permissions and Role Management”

   Step 3.  Click on Manage Roles

   Step 4.  Locate the CEO/Administrator/Don role or role you want to set the permission on.

   Step 5.  Click on Edit

   Step 6.  Locate the Admin Tab and click it

   Step 7.  Check the Allow permission for

    

   Step 8.  Save the change.

   Step 9.  Logout and then log back in.

    

   Step 10.  From the Home Menu click on Tools  

   Step 11.  Locate “Others” (hint: At the bottom of the Applications page)

   Step 12.  Select Manage Logging Level

    

   The following screen appears:

    

   

    

   Step 13.  Change the Logging Level to “ERROR” for each Log4J Logger Name to reduce the amount of logging.

    

   Appendix A: 

   The default setting and the preferred setting is DEBUG.

    

   Explanation of the Logging Level options:

    

   FATAL:                Small log files in size, but low technical information.

   ERROR:                Slightly larger log files and slightly more technical information.

   WARN: Larger log files and more technical information.

   DEBUG:               Large log files and detailed technical information.

   TRACE:                Even larger log files and more detailed technical information.

   ALL:                      Extremely large log files and the most detailed technical information.

    

    

   Leecare & CBORD NetMenu ADT Interface: Role Permissions

   Leecare Solutions are pleased to provide our customers with the benefits of Platinum 5’s ADT interface with the CBORD NetMenu program. If you have licensed your organisation to use CBORD NetMenu, the request to enable the interface can be made by contacting Leecare Client Manager at clientmanager@leecare.com.au to organise the interface activity.

    

   In this ‘How To’ Card, we will show how to grant a particular Role the relevant permission to manage adverse reaction groups and agents provided by CBORD.

    

5. ‘Can Configure the Adverse Reaction Substance Groups’ Permission

Another new permission ‘Can configure the adverse reaction substance groups’ is implemented in the ‘Administration’ tab of Role screen to regulate user access to the area where CBORD specific Adverse Reaction Substance Groups and Agents can be added and edited. This permission should be ticked for all Roles users of which are required to access ‘Manage Adverse Reaction Substance Groups’ link in Tools.

To access the below screen

1. Click Tools

2. Click Manage Roles

3. Click Add Role / Edit

4. Click Administration Tab

All users who have been assigned a Role with ‘Can configure the adverse reaction substance groups’ permission will be able to access the below highlighted link in ‘Tools’ area of the system. To access:

1. Click Tools

‘Manage Adverse Reaction Substance Groups’ link will be visible.

Once this link is clicked, the Adverse Reaction Substance Groups screen will appear. From that screen, a user can add new Adverse Reaction Substance Groups or edit the existing ones will appear. It is discussed in a separate How To Card.