Keep internal notes out of external messages

What this means for your practice

Define the permitted message content and field mapping explicitly. Review the rendered output using fictional examples before enabling an external communication path.

Questions to take to your supplier

Populate a fictional internal-only note and inspect the external preview. Repeat with missing and unusually long values. Ask who approves template changes and how the practice reviews the final wording. The important outcome is the information actually shown to the recipient.

Agree the working process

Start by identifying what the external recipient needs to know for the stated purpose. Choose the permitted input fields from that list rather than giving the template access to every available note. Internal comments can contain working assumptions, staff discussion or information intended for a different audience. Keep those fields clearly separate in the mapping and review process. Ask the supplier to use fictional content that would be unmistakable if it appeared in the outgoing preview.

Test missing values and later edits too, since a safe initial sample does not establish the behaviour of every update. Give template changes an owner and retain the approved combination of wording and inputs. Staff should be able to see whether they are editing internal context or recipient-facing content. Before enabling automatic sending, review the complete rendered message through the organisation's process. If an unintended field reaches a test output, trace the mapping and correct it before treating the connection as ready, rather than merely editing that one sample message.

How to check the result

Count prohibited fields reaching a test output.