Built around the Canadian clinic day. Plan your setup

Your practice, with Flor

Pediatric therapy practice management software

Pediatric services involve children, caregivers, consent authority and often several practitioners. Map the relationships before evaluating screens and features.

Flor is in early access. This page describes workflows to evaluate and product direction. Confirm the exact supported capabilities and rollout scope with the team.

Start with who can see and do what

The person booking a visit is not always the person authorised to receive a report. Review guardian invitations, communication preferences, consent records and changes in access. Use fictional family examples when discussing complicated arrangements.

Coordinate recurring care across disciplines

Families may attend several services on the same day. Test appointment spacing, practitioner availability and the administrative view of the care plan. Clinical access should remain limited to what each role needs.

One child has several authorised contacts

Use a fictional child receiving two therapy disciplines. Distinguish the client record from each guardian relationship and the recipient allowed to complete a particular form. Review how consent status, appointment information and care goals appear to the right team members. If permissions change, staff should know which grant is current. Evaluate the process using invented names and blank forms; public enquiries are not a place for family records.

Example acceptance worksheet
Check in the demonstrationEvidence to record
Client and guardian records are distinctDescribe the observed result using fictional data.
Consent and portal scope reviewedRecord the role, exception and any manual work required.
Shared care preserves role-based accessAgree on pass, follow-up or unavailable before rollout.

Continue with patient portal software for connected care and patient intake forms for therapy practices to test the connected steps. The interactive Flor demo provides fictional examples for the discussion.

Prepare your team for the review

Ask one practitioner and one person who handles scheduling or billing to describe the same fictional visit. Compare what each needs before, during and after the appointment. Bring blank forms, service durations and a list of required integrations, then use the software selection guide to record the outcome.

For a Canadian clinic, confirm CAD receipts, provincial professional requirements and the exact funding or insurer workflows you use. Check the migration checklist before agreeing to a switch date.

Relationship and permission review matrix

Record the person, requested action, clinic reviewer and evidence before any invitation. These are evaluation categories, not legal defaults or permission grants.

Proposed guardian-access evaluation matrix
Review caseScope to testEvidence and limit to record
Scheduling contactAppointments and administrative noticesPurpose, reviewed authority and approved scope; no automatic report access.
Payment recipientInvoice or receipt copyVerified recipient and necessary financial fields, separate from clinical notes.
Report recipientNamed report or record scopeClinic-reviewed decision, subject, version and secure recipient identity.
Changed or unresolved scopeReview-needed stateOwner, reason, effective time, old-session/link behaviour and follow-up.

Test a change, not only the first invitation

Use a fictional family with different scheduling, payment and report recipients. Change one reviewed scope, try an old invitation and already-open session, and confirm that unresolved authority has a named review owner. Ask what is retained in the audit history and what happens to notices queued before the change. Removing portal access cannot recall a file already downloaded. Confirm the applicable provincial rules, professional obligations and the young person’s circumstances with qualified reviewers; a family label or software age setting is not a legal determination.

Use the complete guardian-access demonstration worksheet ↗ Record pass, follow-up or unavailable for every requirement; confirm supported hosted scope before a rollout.

Primary sources checked October 15, 2026: OPC meaningful-consent guidance, joint OPC/Alberta/BC guidance on meaningful consent and provincial privacy-law context. Consent to information handling, treatment consent and record-access authority require separate clinic-specific review.

A few common questions

Are guardian permissions already verified for launch?

Guardian and portal workflows remain part of clinical release acceptance. Ask for evidence of the exact scenario your clinic needs.

Prepared for clinic owners in Canada. Updated . These guides support product evaluation and do not replace professional or legal advice.

Keep exploring.

A good place to begin

Bring your clinic
workflow into focus.

Tell us about your practice. We’ll help you explore whether Flor fits.

Let’s talk about your practice ↗