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 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 on the HQ laptop, a schedule board that lays out the whole program's week by medic; 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.
HQ — the CP schedule board, every medic's week
The admin portal's Community Paramedicine tabs with Schedule selected: this week's board, a row for each of four community paramedics and a column for each day from Monday to Sunday, today highlighted. Each visit shows its time, the client's CP code and initials and the visit type. Monday's visits are marked Done, two proposed visits are dashed, clinic, meeting, LTC round and admin blocks sit among the visits, days off and one day of booked leave are shaded, and a visit left on the leave day carries a warning mark. The To book list is folded to a button reading To book (8).
At HQ, on a laptop: the coordinator's week on one board. A row for each community paramedic, with their days off and booked leave shaded from the roster; finished visits marked Done, proposed visits waiting to be confirmed, and clinics and admin blocks in place. Clients show as a CP code and initials; opening a visit shows the name, and that is logged. Move… hands a visit to another medic or day, and a clash, like the visit left on a day of booked leave, is flagged, never blocked.
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 module15 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.
  • Remote patient monitoring — a client's home readings (blood pressure, heart rate, oxygen level, blood sugar) on their profile, from a tablet set up with a 6-digit code: the last 7 days, 4-week and 3-month trends, and HQ's Home monitoring view. Plain values, not watched in real time.
  • 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 — a community paramedic can package encounters and linked reports for a physician or NP right from the tablet, PIN-gated, by fax or by secure link, as in the admin portal.
  • A CP fax line — faxes to the program’s line land in one fax inbox, reached from the tablet beside Key Nav and from the admin panel; a person files each one to the client, and it moves into that client’s documents. Records go out by fax by default, only to a number the service has checked, or by secure link and access code — one or the other, never both.
  • 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. And the question a funder always asks next — did enrolment change how often these clients call 911? — is answered as a measurement with its limits printed on its face, never as a claim about cause.

The program's numbers — Community Paramedicine only
The Community Paramedicine reporting card over a funding year: program KPIs — 29 referrals received, 47 distinct clients seen across 211 CP visits, 4.5 visits per client, 184 of 211 visits timed with a 38-minute median — beside the caseload by status right now, encounters by month with notes from 911 calls on their own line, how-often-clients-were-seen bands, a by-clinician table and 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.
911 use before and after enrolment — with its limits printed on it
The 911-use-before-and-after-enrolment statistic: four headline tiles — 0.58 and 0.27 911 calls per client per 30 days before and after enrolment, a change of minus 54 percent with its likely range, and 51 of 54 clients analysed — above a highlighted honesty line, five checks on the number, and tables of who is counted, the change per client, calls and transports, what is not counted as 911 use, and how calls were matched to clients
The number a funder asks for, printed with everything that qualifies it. Before and after enrolment — not proof of cause: the card says so on its face, shows how many of the before-calls fell in the last 30 days before enrolment, and repeats the comparison with those 30 days left out. Five checks sit under it — a likely range, the clients who have a full twelve months on each side, the whole service’s call volume over the same days, and the after-calls that landed on a day the client had a CP visit. It also prints who was left out and why, what it refused to count as a 911 call, and how calls were matched to clients. The honesty line and the checks are rows in the CSV, Excel and PDF exports, so they travel with the number instead of staying on the screen.
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.
Remote patient monitoring

Between visits, the readings come to the chart RPM

A simple tablet at home sends a client's blood pressure, heart rate, oxygen level and blood sugar to their chart. The community paramedic sets it up with a 6-digit code on the iPad; a Bluetooth cuff and oximeter send by themselves. The chart shows the last 7 days and plain trends, HQ sees the whole program on a laptop without a single value on the list, and every look is in the access log. Not watched in real time — a home reading alerts nobody.

The last 7 days, on the client's profile
The Remote patient monitoring section on a CP client's profile: the tablet line with Turn off and Set up a new tablet, Last 7 days with Show trends, and today's and yesterday's home readings in 24-hour time with units, each marked from the BP monitor or from the oximeter
On the paramedic's iPad, right above Encounters & Notes: the week's home readings, newest first, as plain values, each with how it got in.
HQ — Home monitoring, counts and times only
The admin portal's Community Paramedicine tabs with Home monitoring selected, and its seven count tiles over a list of clients with a home tablet, showing each one's tablet state, who set it up, the last reading received and the 7-day count, with no reading values
At HQ, on a laptop: seven counts and every client with a home tablet — its state, when the last reading arrived and the 7-day count. No reading values on the list.
Explore Remote Patient Monitoring →
The CP fax line

Faxes in, filed to the client. Faxes out, only to a checked number. Fax

Referrals and physician replies still come by fax. The program’s fax line puts them in one fax inbox — on the iPad, beside Key Nav, and in the admin panel — where a person opens each one and files it to the client it belongs to, and it moves into that client’s documents. Nothing is filed automatically, and nothing in the inbox is ever deleted automatically. Going the other way, fax is the default way to send a record to a physician or nurse practitioner, and it only goes to a number someone at the service has checked and recorded. The physician receives the same signed record, with your service’s name and phone number on it. Every step is recorded under the person who took it.

CP tablet — the Inbox button, beside Key Nav
The CP tablet’s top bars on a client record: the PCS Cross Check header marked CP, Community Paramedic, with Switch Panel; the tab row Patients, Day, Month, Plan a day, Patient Record, Encounter, Referrals, Forms, Enrol Patient and Key Nav, then the Inbox button with a badge reading 1, the bell and End Shift; and beneath them the client strip for Whitfield, Gordon with date of birth 1962:03:14, a health card number and 2 encounters
Two ways in, one inbox. On the iPad the fax inbox is this Inbox button beside Key Nav; at the desk it is the Fax tab in the admin panel. Both open the same list with the same actions, so a fax filed at the desk leaves the tablet’s list too. The badge counts the faxes waiting to be filed from the moment one arrives, and if one sits unfiled the reminder says plainly that it may be a referral. Nothing in the inbox is ever deleted or archived on its own.
CP tablet — Fax inbox
The tablet’s Fax inbox, headed Acting as A. Sinclair, with Refresh and Close, the Open, Archived and Closed views, and one fax: received 2026:09:25 09:08, marked New, from +1 613-555-0142, 2 pages, to the CP line +1 613-555-0110, waiting under an hour, with an Open button
The inbox on the medic’s iPad: when each fax arrived, the number it came from, the page count, which line it came in on and how long it has waited. The line under the title says who is acting — on a shared iPad, every open, filing and disposal is recorded under the medic doing it, here A. Sinclair, not under the iPad’s sign-in. Opening a fax writes the access log before the image is shown, and received faxes are stored encrypted.
CP tablet — a faxed referral, opened
An opened fax on the tablet: received 2026:09:25 09:08, from +1 613-555-0142, 2 pages, to +1 613-555-0110, status New — not read yet; the buttons Mark read, File to a client, Archive, Delete and Not ours; and the top of page 1 — a Community Paramedicine referral from Lakeview Family Health Team to the Community Paramedicine Program at Demo Paramedic Service, fax 613-555-0110, from Dr. Helen Marchetti, for the client Gordon Whitfield with his date of birth, health card, address and phone
Dr. Marchetti’s referral, opened on the iPad. Every choice is recorded with who made it: Mark read keeps it in the inbox; File to a client moves it into the client’s documents; Archive sets it aside and can be undone; Delete asks for a reason, destroys the image and keeps a record that the fax arrived; and Not ours is for a fax that reached the wrong service — its image is destroyed and it is never forwarded.
CP tablet — file a fax to a client
The File this fax to a client sheet: the line This fax: received 2026:09:25 09:08, from +1 613-555-0142, 2 pages, to the CP line +1 613-555-0110; a search for Whitfield under Find the client — last name, first name, health card number or CP code — matched to Whitfield, Gordon with date of birth 1962:03:14, CP code, the last digits of the health card and active; Filing to that client; document type Referral form; title CP referral — Dr. Marchetti; date on the document 2026-09-24; an optional note; and File to this client
Filing is a lookup, not a chart: find the client by name, health card or CP code, check the match against the date of birth and the end of the health card number, then give the fax a type, a title and the date on the document. It moves into the client’s documents and leaves the inbox — the tablet answers “Filed to Whitfield, Gordon’s documents. It has left the inbox.” The encrypted file is moved to the client as it is; it is never decrypted and sealed again to be filed.
CP tablet — send by fax
The tablet’s send sheet: How to send, with Fax — to a verified fax number — chosen and Secure link + access code — link by email, code by text — not chosen; Fax to, a list set to Dr. Helen Marchetti, Lakeview Family Health Team, +1 613-555-0142; the recipient’s name and the type Physician / NP; the reason for disclosure, continuity of care — visit record for the family physician; 1 item selected; a note that the PIN is asked at Send; and Send by fax
Sending the visit record to the family physician. Fax is the default; a secure link with the access code sent by text is the alternative — one or the other for each send, never both. The fax number is chosen from the service’s list of checked numbers; nobody types one at send time. The medic confirms with their PIN. The tablet’s part ends when the fax is queued: whether it was delivered shows in the admin panel, where only “Delivered” means the receiving machine confirmed it.
The visit record as faxed — page 1
Page 1 of 2 of the faxed Community Paramedicine Encounter Record. The header names the service — Demo Paramedic Service · 613-555-0100 — with the client Whitfield, Gordon, visit date 2026:09:24, a home visit, status Signed and locked; below it the client block, the visit block with the time 10:30 and paramedic A. Sinclair, the presenting concern, a scheduled heart failure follow-up, and the full SOAP assessment, whose plan is to fax the record to Dr. Marchetti for a diuretic review
What goes to Lakeview: the same signed record, not a form retyped for the fax, with your service’s name and phone number in its header — every document that can leave the platform carries that line. The cover page sent in front of it names your service and its phone number, with a confidentiality notice telling anyone who received it by mistake to call that number. And a record whose disclosure is revoked before its fax goes out is never sent.
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