PCS Cross Check logo PCS Cross Check
Community Paramedicine

The record your funding case is built on.

A Community Paramedicine program lives or dies on being able to show what it did and who it reached. So this module is built around scheduling the visits, recording them in structure, and turning that into the numbers a funding submission actually asks for — not a 911 form with the wording changed. Same platform, same login, its own purpose-built panel.

Every screen below is the live product on demonstration data — no real client information.
The other half of the service

The 911 chart ends at transfer of care.
Community Paramedicine picks up from there.

Scheduled home visits, a longitudinal record, and a program that has to prove its worth to a funder — that is a different job from one call, one chart, signed and filed. And the fields are yours: a service defines its own programs, visit types, referral sources, task types and client tags, adds to them as the program grows, and retires the ones it stops using without breaking a single record already written against them.

Its own panel

A dedicated CP module on the tablet — caseload, calendar and encounters — not a 911 form with the wording changed.

Its own record

Longitudinal client files with consent, tasks, months of encounters and a document file for the outside paperwork — server-backed and encrypted, never living on one device.

Its own numbers

Distinct clients, visit volume and frequency bands — counted the way a funding submission asks for them.

Visit scheduling

The day, the caseload, and the whole service — booked without a phone call CP

A per-medic Day and Month calendar with the visit workflow one tap away; a Plan-a-day tool that turns what the caseload is owed into a booked day in one batch; an Everyone view that reads the whole service's day on one screen so a coordinator can move a visit between medics; and a work pool so a slow afternoon books its own work instead of asking for it.

A community paramedic's day — booked, worked, closed
The CP Day view for today: seven visits for one community paramedic — two already closed with outcomes, one on scene with a lockbox access note showing, the rest booked with On scene, Not home, Close and Cancel workflow buttons one tap away
Today, as it actually runs: the morning's bloodwork and wound care already closed with outcomes, one visit on scene — with the lockbox note right where it's needed — and the afternoon booked, each visit's workflow one tap away.
Plan a day — from what's due
The Plan-a-day view: the caseload's tasks due in the next 14 days grouped by due date — POC INRs, wound care, postural BPs — with five ticked and the batch bar reading 5 selected · Book 5 visits
Plan a day from what the caseload is owed: filter to due-within-14-days, tick five, and book the day in one batch — while the tool keeps two medics from booking the same door.
Everyone's day — the whole service on one screen
The CP Day view with Everyone — all CP medics selected: today's visits for the whole service grouped by medic — each medic's shift line and visit count, visits in clock order with their outcomes, an on-scene visit with a Move to… button, and an Unassigned group last with its own Move to… button — with the Work pool button in the day bar
Pick Everyone and the day reads across the whole service: every community paramedic's visits grouped by medic — closed visits with their outcomes, who's on scene right now, and the unassigned work last, where it can't hide. A coordinator moves a visit to another medic from this screen, through the same gate and with the same audit row as the portal's reassign — and by design this view carries no access notes, so lockbox codes stay on the medic's own day.
Work pool — a slow day finds its own work
The Plan-a-day view opened as the Work pool: preset to Not already booked within 60 days, listing every open task nobody has booked yet — overdue groups first, then upcoming — with two tasks ticked and the batch bar reading 2 selected · Book 2 visits
Tap Work pool and the planner opens preset to every open task nobody has booked yet — overdue first — so a medic with a light afternoon books the work instead of calling the coordinator to ask for it. Tick, book, done.
The encounter

A real SOAP chart — with the monitor's 12-lead inside it

Structured clinical documentation, not a memo field: chief complaint, Subjective, Objective, Assessment and Plan, vitals, PRISMA-7 frailty and falls-risk screens, medication reconciliation, interventions, referrals and a disposition — with the same one-tap cardiac-monitor pull as the 911 side. A signed encounter locks immutable.

The encounter — a real SOAP chart, signed and locked
A signed CP encounter: encounter details, a vitals row, and the Assessment block with chief complaint and all four SOAP fields — Subjective, Objective, Assessment and Plan — filled for a CHF follow-up, under the Signed & Locked banner
Structured clinical documentation, not a memo field: chief complaint and a full S/O/A/P for a CHF follow-up, with vitals attached — and once signed, the encounter locks immutable.
Monitor captures — the 12-lead in the home visit
A signed CP encounter's Monitor Captures block: a real 12-lead ECG and a Lead II rhythm strip pulled from the cardiac monitor, each with its interpretation filled in
The same one-tap monitor pull as the 911 side: the 12-lead and Lead II land in the encounter with their interpretations — a baseline the next visit can be compared against.
The longitudinal record

One client, months of care, one timeline

Demographics, enrolment, history, medications, allergies, care team and substitute decision-maker — and beneath them every encounter, quick progress note and note from a 911 crew in a single chronological timeline. Server-backed and encrypted, so nothing lives only on one device; progress notes can't be edited or deleted, so the log stays defensible.

One client, seven months of care
A CP client's longitudinal record: seven numbered encounters from February to August in one chronological timeline — signed follow-ups, interleaved progress notes, and a From-911-call note card — showing months of continuous care
The longitudinal record a program is judged on: seven months of encounters, progress notes and even a 911 crew's note-back, in one chronological timeline. Progress notes can't be edited or deleted, so the log stays defensible.
Inside the CP module13 features
  • Visit scheduling & day planning — a per-medic Day and Month calendar, and a Plan-a-day tool that turns due and overdue tasks into a booked day in one batch — while keeping two medics from booking the same door.
  • The whole service's day, and the work pool — one date, every CP medic's visits grouped by medic with the unassigned last; a coordinator, supervisor or admin moves a visit to another medic from the same screen, through the same gate and audit row as the portal's reassign; and the Work pool opens every open task nobody has booked, overdue first, so a slow day finds its own work. The whole-service view carries no access notes by design — lockbox codes stay on the medic's own day.
  • Reporting a funding submission can use — distinct clients seen over a chosen range, visit volume, visit-frequency bands (how often clients are actually seen), referral sources and program breakdowns, exportable for a submission. Clients and visits are counted separately on purpose — one client seen twelve times is not twelve clients.
  • Your fields, not ours — a service defines its own programs, visit types, referral sources, task types and client tags, adds to them at any time, and retires the ones it no longer uses. Retiring never rewrites a record already filed against that value, so last year's reporting still means what it meant then.
  • Tasks that keep the caseload honest — dozens of visit and follow-up task types, one-off or recurring (a completed task rolls itself forward), with a caseload-wide upcoming view and overdue flags.
  • Patient enrolment & longitudinal record — demographics, conditions, meds, allergies, care team & SDM, with the same health-card scanner — server-backed and encrypted, so nothing lives only on one device.
  • A document file on every client — bloodwork, physician notes, orders, agency updates, photos: filed to the client from the tablet (attach from the file, add a PDF or image, or take a photo — sealed on the device and uploaded by the outbox, so nothing ever touches the camera roll) or dragged in through the admin portal, with no visit required. Encrypted at rest, every open logged, the five most recent kept on the tablet for offline visits, and a retention dial of its own — 12 to 60 months — that never touches the client’s profile.
  • Caseload at a glance — a Today's Visits list, search by name or health card, a My-Patients filter and clinical-tag filters (Wound Care, INR, Vaccinations), all server-backed.
  • Structured encounters — SOAP assessment, vitals, PRISMA-7 frailty & falls-risk screens, with the same monitor import (12-lead & Lead II) as the ePCR; a signed encounter locks immutable.
  • One chronological history — every encounter, quick progress note and note from a 911 crew in a single timeline; progress notes cannot be edited or deleted, so the log stays defensible.
  • Send to provider, securely — a community paramedic can package encounters and linked reports for a physician or NP right from the tablet, PIN-gated, over the same secure-link delivery as the admin portal.
  • Full PHIPA consent trail — program and PHI consent captured with patient and paramedic signatures, PIN-attested and server-locked, with a clean withdraw-and-re-consent path.
  • Documents anywhere — a home visit with no signal still charts safely and syncs when signal returns; the working set on the device is encrypted and wiped at shift end. Fits your service's public-health oversight and reporting.
The document file

The outside paperwork, filed on the client NEW

Bloodwork, physician notes, orders, agency updates, photos: every client gets a chronological document file. File from the tablet — attach from the file, add a PDF or image, or take a photo, sealed on the device and uploaded by the outbox — or drag it in from the desk through the admin portal, with no visit required. Encrypted at rest, every open logged, the five most recent kept on the tablet for the day's visits, and a retention dial of its own — 12 to 60 months — that never touches the client's profile.

The client’s document file — filed from the tablet, no visit required
A CP client record’s Documents strip: nine documents newest first — an INR result sheet, CBC and electrolytes from a community laboratory, a physician note, a lab requisition, a home oxygen order, a wound photo, a discharge summary, an agency update and the signed program consent — five marked saved on this device, with Add PDF / image and Take photo buttons beneath
Months of outside paperwork, filed on the client instead of the fridge door: lab results, the physician’s note, the oxygen order, an agency update, the signed consent — every document encrypted at rest, every open logged, the five most recent kept on the tablet for the day’s visits. Add a PDF or take a photo straight from the record; it’s sealed on the device and uploaded by the outbox, so nothing ever lands in the camera roll.
Attached to the visit — the lab report rendered inside the signed record
A signed CP encounter record’s Attached Documents section: an INR result sheet collapsed behind a Show button, and a CBC + electrolytes report from a community laboratory rendered as a page image inside the visit — patient block, electrolytes with a flagged low potassium, and the CBC — above the Signed and locked footer
Attach a document to the visit and it renders inside the signed record as page images — the lab report the medic acted on sits right under the assessment it informed, Show or Hide per document — and once the visit is signed, it’s locked with everything else.
Reporting a funding submission can use

Counted the way a funder asks — and the way a medic can defend

It counts carefully: distinct clients seen is reported separately from visit volume, because one client seen twelve times is not twelve clients — and a CP visit taken during a 911 call is not fundable program activity. Overstating reach in a funding submission is not a mistake you want the software to make for you. The same card supervisors see in the portal is here for the medics who do the work.

The program's numbers — Community Paramedicine only
The Community Paramedicine reporting card: program KPIs for the selected period — referrals received, 47 distinct clients seen across 211 visits, average visits per client, timed-visit coverage and median duration — the current caseload by status, encounters by month, how often clients were seen, and a by-clinician table with a reconciliation note
And the numbers the program lives on, in one place: distinct clients seen counted apart from visit volume, how often clients are really seen, caseload by status, and each clinician's share — CP data only, the 911 side stays in its own reports. The same card supervisors see, so when the team makes its case for funding or staffing, everyone is arguing from the same numbers.
One patient, both sides of the service

When a CP client calls 911, the crew already knows them

Chart an enrolled client on a 911 call and their on-file history, meds, allergies, substitute decision-maker, physician and DNR surface right on the call report — behind a wrong-patient gate, importing only blank fields — and at sign-off the crew can leave a note that lands back in the CP timeline. The two sides of the service read the same patient.

The CP file, surfacing on a 911 chart
A 911 call report's demographics section after a health-card scan, with the Community Paramedic patient banner showing the client's on-file history, medications, allergies, substitute decision-maker, physician and DNR, and the Known patient — 3 prior calls · CP client row
The moment the health card is scanned on a 911 call, the CP file is on the chart: history, meds, allergies, SDM, physician, DNR — and a one-tap import that fills only what's blank.
One patient, both sides of the service5 features
  • On-file banner on a 911 call — when a 911 crew charts a patient already enrolled in CP, their history, meds, allergies, substitute decision-maker, physician and DNR/care goals surface right on the call report — with lookups fast enough to disappear, even at tens of thousands of patients.
  • Wrong-patient safety gate — on a name-and-DOB-only match the full summary stays hidden until the medic confirms it's the right person.
  • One-tap import into the ACR — pull the CP patient's history, meds, allergies and address into the call report, filling only blank fields.
  • 911 → CP note-back — at sign-off the 911 crew can leave a note for the CP team; it's delivered as a background CP encounter, so a weak signal never blocks or loses it.
  • Read the 911 report from the CP chart — a community paramedic opens the finalized call report tied to their patient, read-only and audit-logged, without leaving the app.
Keep exploring

The rest of the platform

The same login runs the 911 call report, the scheduling system and the supervisors' audit & reporting portal — and the free-standing protocol app puts the directives in every medic's pocket.

The ePCR → Admin & Reporting → Book a live demo