PRACTITIONER LEARNING SERIES · LESSON 4 · FREE LESSON

Before You Share an NLS Report

Exporting a PDF is the last software step, but it is not the last practitioner step. This lesson follows Lesson 2’s report-export workflow: open the saved file, check what it says and make sure the person receiving it can understand its limits.

Published 12 November 2026 · By Samantha Roeloffze · No account required

WHAT YOU WILL LEARN
  • Separate automated text, client-reported information and your own observations.
  • Review a report for identity, dates, unsupported conclusions and unnecessary personal information.
  • Explain an output in plain language and complete a deliberate sharing check.

1. Start with the file you will actually send

Open the exported file from its saved location. Check the intended person, session date, selected research items and every page. A correct-looking filename does not guarantee that the report contains the intended session. Look for blank pages, truncated text, old notes and another person’s information.

Keep the original export in protected storage. If you prepare an explanatory summary or correct an error, identify the author, date and version. Do not silently rewrite the original output or remove context to make a result appear more favourable.

2. Identify who is saying what

Use three clear headings: Client report, Software observation and Practitioner explanation. “The client reports interrupted sleep” is different from “The software displays this label.” Neither sentence, on its own, establishes the cause of a symptom.

Read generated paragraphs as carefully as your own notes. If automated wording implies an unverified diagnosis, do not endorse it by sending it without explanation. Prepare a clearly labelled summary where appropriate, preserve the original record and explain what remains unconfirmed. A disclaimer at the end does not correct a misleading claim in the main text.

3. Translate without adding certainty

Instead of “The scan found an infection,” explain: “This entry appeared in the software’s comparison library. It does not confirm an infection.” Instead of “Your organs are healthy,” explain: “This report cannot rule out a medical condition.”

If a client asks whether a changing score means treatment worked, separate the observations: “The displayed value changed, and you reported feeling different. This report alone does not establish what caused either change.” Do not translate a software score into a disease stage, laboratory value or percentage of organ function.

4. Agree what the report is for

Ask what the person needs from the document: a session summary, a record for their own reference or information to discuss with a healthcare professional. Explain the limits before sharing, invite questions and record any agreed next step.

Do not ask a client to stop medication or exclude foods because an entry appeared. If symptoms need medical assessment, say so directly; do not let preparation of a polished report delay care.

5. Make sharing a separate decision

Confirm the intended recipient and agreed sharing method. Recheck the address or number immediately before sending. Include only information needed for that purpose and follow your professional and privacy obligations. These practical checks are not a complete legal compliance checklist.

For teaching or social media, use a fictional example where possible. Removing a name alone may leave identifying details in dates, screenshots, filenames, notes or document properties. Do not upload identifiable reports to public tools or groups as a shortcut.

Print-and-use checklist

Use your browser’s Print → Save as PDF to keep this lesson. Tick the boxes on your printed copy; this page does not collect client information.

Practise with a fictional case

An exported report contains a microorganism name. The client asks you to email it to a family member and write that the scan confirms an infection. What would you change before sharing?

Open the worked answer

Do not confirm an infection from the entry. Explain that it is a software comparison and that suspected infection needs appropriate clinical assessment. Check the report and prepare a clearly labelled explanation without altering the original record to hide what it displayed. Confirm the client’s sharing request, the family member’s recipient details and the agreed method before sending only the necessary information.

Practice prompt: write your own two-sentence explanation, then compare it with the answer. Use invented details, not identifiable client records.

Check your understanding

1. Does saving a PDF mean it has been reviewed or sent?

No. Open and review the saved file, then make a separate, deliberate sharing decision.

2. Does an automated diagnosis become reliable because it appears in a professional-looking report?

No. Formatting and automated wording do not validate the underlying claim.

3. Is removing the client’s name enough for a teaching example?

Not necessarily. Other details may identify the person. Prefer a fictional example and check all visible and embedded information.

Sources and scope

This is an Anavrin educational workflow, not a validated diagnostic protocol or manufacturer-certified instruction. It does not add device button sequences or treatment settings. Follow the manual for your installed edition.

The UK ASA/CAP reports that it has not seen evidence substantiating bioresonance claims to diagnose, prevent or treat disease. This is UK advertising guidance, not South African law. A software output should not be presented as a confirmed medical finding.

Read ASA/CAP: Bioresonance Therapy · Reviewed 12 November 2026.

Continue learning

For more structured learning, explore Academy courses or browse practitioner ebooks.

Educational content only. Bioresonance/NLS outputs do not replace medical assessment or treatment. Do not use them to stop medication, prescribe restrictive diets or delay appropriate care.