Go Live checklist for CloudPCR

Go Live checklist

1. 1

   Confirm your agency information

   • Open Settings → Demographics → Agency and confirm your agency name, address, NEMSIS state ID, and contact details are correct.
   • These values appear on every PCR you submit to your state and to billing — get them right before any real call is documented.
   • See Agency demographics for the full walkthrough.

   Demographics — Agency Information
2. 2

   Add your locations and facilities

   • Under Settings → Demographics → Locations, add every station, post, and standby location your crews work out of.
   • Under Settings → Demographics → Facilities, add the hospitals, nursing homes, and clinics you transport to.
   • Locations and facilities are shared with CAD, so adding them here means dispatchers can pick them too.
   • See Locations and Facilities for details.

   Demographics — Locations
3. 3

   Add your vehicles and devices

   • Under Settings → Demographics → Vehicles, add every truck your agency runs with its unit number, VIN, call sign, and level of care.
   • Under Settings → Demographics → Devices, add cardiac monitors, ventilators, and any other tracked equipment if your agency uses Stryker LIFENET monitor imports.
   • See Vehicles and Cardiac monitor integration for details.

   Demographics — Vehicles
4. 4

   Add personnel certifications

   • Your crew members already exist from SSO, so you do not need to recreate them.
   • Under Settings → Demographics → Personnel, set each crew member's level of care, certification numbers, and expiration dates.
   • See Personnel certifications for the full walkthrough.

   Demographics — Personnel
5. 5

   Build your medication, procedure, and impression lists

   • Under Settings → Demographics → Configuration, build out the medications, procedures, and impressions your agency actually uses.
   • This populates the picker on the Timeline and Assessment tabs — without this, every search returns No options found.
   • Favorite the items you use most so they appear at the top of each picker.
   • See Demographics Configuration for details.

   Demographics — Configuration
6. 6

   Customize the PCR form for your agency

   • Your state's NEMSIS form is already loaded — CloudPCR knows which fields are required for your state out of the box.
   • Under Settings → Form Configuration, walk through every tab (Incident, Patient, Billing, Assessment, Timeline, Outcome, Narrative, Documents, Signatures) and hide any sections or fields your agency does not use. You can also set agency-specific defaults and favorite the values you pick most often.
   • See Settings overview for context on each panel.

   Form Configuration
7. 7

   Set up your QA workflow

   • Under Settings → QA Workflow, create QA groups, set their routing rules, and assign reviewers to each group. The first matching group (lowest priority number first) wins; set a default catch-all group if you want every other PCR to land in a general review queue.
   • See QA Workflow and The QA PCRs queue for details.

   QA Workflow
8. 8

   Set validation and incident-number preferences

   • Under Settings → Preferences, choose how strict PCR validation should be — Require all errors and warnings to be resolved blocks submission on both errors and warnings, Only require errors to be resolved blocks just errors.
   • If your agency wants CloudPCR to auto-generate incident numbers instead of typing them by hand, turn on Enable automatic incident numbering and set the Next sequence number. The year prefix (YYYY-NNNNNN) updates automatically on January 1st.
   • See Preferences for details.

   Preferences
9. 9

   Have every crew member sign in and run a test PCR

   • Have every crew member sign in to CloudPCR through SSO at least once before their first shift.
   • Walk them through creating a test PCR end to end — see Creating a new PCR.
   • Fill in every tab (Incident, Patient, Billing, Assessment, Timeline, Outcome, Narrative, Documents, Signatures) and submit it — see Submitting a PCR.
   • This surfaces any missing demographics, hidden fields, or permission issues before a real call is documented.

   Creating a new ePCR
10. 10

    Test the full QA loop with a real reviewer

    • Have a reviewer pick the test PCR out of the QA queue and send a flag back to the creator — see Responding to a QA flag.
    • Have the creator respond to the flag and resubmit.
    • Confirm the reviewer can resolve the flag and approve the PCR.
    • If any step fails, fix the role assignment or workflow before going live.

    Responding to QA flags