A community paramedicine patient enrolled in the Ottawa program generates interactions across multiple touchpoints — scheduled home visits, phone check-ins, care plan reviews, specialist referrals, emergency contacts, and crisis calls that didn't escalate to 911. Each of these is a different Interaction type with a different clinical weight and different documentation requirement. A scheduled home visit where the patient was assessed and found stable has different note requirements than a phone check-in where the patient reported new symptom onset, and a different documentation fingerprint than a referral coordination call with the patient's primary care provider.
Interaction Type as the Care Map
Interaction type is the classification that allows the program to produce a care activity summary for each enrolled client. A client with eight home visits and two phone check-ins in a quarter has a different engagement profile than one with two home visits and eight phone check-ins — and the visit-heavy profile may indicate a client who is stable enough that telephone monitoring is adequate for some interim periods, while the reverse suggests a client who is reluctant to accept physical visits despite clinical need.
The interaction type is also what the program coordinators use to bill and report to Ontario Health, where community paramedicine programs report activity in specific categories. Undifferentiated "contacts" don't support the activity-based reporting that funds program continuation.
interaction ID is the audit trail reference — the unique identifier that links the Memento record to the Ambulance Care Report or other formal clinical documentation that may have been generated during the interaction. A home visit that involves a diagnostic assessment generates an ACR; the interaction ID in the client interaction log is the cross-reference that ties the brief interaction record to the detailed clinical document.
The Note That Connects Interactions
notes is where the clinical continuity lives in a system this simple. With five fields, the note carries the entire clinical context: what was communicated, what was assessed, what was changed in the care plan, what was referred, what the patient reported, what the next scheduled interaction is and what triggers an unscheduled contact before then.
The notes across interactions for a single client, read chronologically, tell the story of the client's health trajectory in the program. A client whose notes shift from "stable, medications compliant, no concerns" to "patient reports increased fatigue and mild dyspnoea, SpO2 93%, BP elevated" over three sequential check-ins is a patient whose escalation pathway needs to be activated now rather than at the next scheduled visit.
Client Profile links each interaction entry to the full client record — OHIP number, medical history, medications, primary care provider, emergency contacts. The barcode or unique identifier in the profile means the client is one scan away from their complete background at every interaction, regardless of which paramedic is conducting the visit.
The date and interaction ID combination creates the auditable timeline. For a program operating under provincial oversight, every client interaction needs to be traceable to a specific date, a specific type of intervention, and a documented clinical note. This five-field structure delivers exactly that, with no redundancy.