Implementation

Six phases, live in weeks, not quarters.

Aged-care EMR rollouts have a well-trodden path — discovery, design, build, migration, training, go-live and hypercare. We follow it, with CarePoint-specific tooling at each step. Move the selector to see what the timeline looks like for a facility your size.

✓Single named implementation lead from our team
✓Configurations built collaboratively, not by remote
✓Train-the-trainer for sustainable role coverage
✓Hypercare for at least four weeks after go-live
The six phases

What actually happens, week by week.

Each phase has a CarePoint-side workstream and a facility-side workstream — running in parallel, with clearly named outputs that close the phase. Industry-standard EMR rollout pattern, applied to residential aged care.

Phase 01

Discovery & kickoff

Duration: 3–5 business days Owner: CarePoint implementation lead + facility executive sponsor

A focused first week to make sure the right people are at the table, the right systems are mapped, and there are no surprises on day one. Without a clean kickoff, every later phase pays interest.

CarePoint does
  • Assign your named implementation lead — your single point of contact through go-live
  • Run the kickoff workshop on-site or video (~2 hours)
  • Document the current-state system landscape and integration points
  • Build the implementation plan and shared project tracker
  • Assess data sources for migration scope and feasibility
Your facility does
  • Nominate an executive sponsor (typically DON or Facility Manager)
  • Identify clinical and admin super-users (3–5 per facility)
  • Provide access to current systems for data scoping
  • Communicate the change to the broader team
  • Confirm hardware readiness (tablets, trolleys, Wi-Fi)
Phase outputs: Signed implementation plan · stakeholder map · current-state document · data migration scope · go-live target date.
Phase 02

Configuration design

Duration: 5–10 business days Owner: Implementation lead + facility super-users

The most important phase. We sit with your super-users and design the system around your facility — ward structure, role permissions, forms, alert thresholds, family-portal visibility. Decisions made here shape every shift after go-live.

CarePoint does
  • Facilitate workshops covering roles, wards, forms, alerts and family-portal visibility
  • Document configuration decisions in your project workspace
  • Map your existing forms and assessments to CarePoint equivalents
  • Flag risks: places where current practice and standard configuration disagree
Your facility does
  • Super-users attend 2–4 design workshops (1.5h each)
  • Provide samples of current paper or digital forms
  • Agree to role permission matrix and ward structure
  • Confirm clinical alert thresholds with your DON and Clinical Manager
Phase outputs: Configuration design document · approved role permission matrix · ward / room structure · form & chart inventory · alert rule list · family-portal visibility plan.
Phase 03

System build & configuration

Duration: 1–3 weeks (overlaps with data prep) Owner: CarePoint implementation lead with super-user review

We provision your tenant, apply everything from the design phase, and put a working environment in front of your super-users for sign-off. Iterations happen here — not after go-live.

CarePoint does
  • Provision your facility-specific subdomain and tenant
  • Configure wards, roles, users, forms, charts, assessments, alert rules and care-plan structure
  • Build the configured environment in a staging tenant for review
  • Run internal QA against your design document
  • Deliver the staging environment to super-users for walkthroughs
Your facility does
  • Super-users review the staging tenant against the design document
  • Submit configuration change requests via your project workspace
  • Approve the final configuration before data load
Phase outputs: Configured staging tenant · super-user walkthrough sign-off · production tenant provisioned.
Phase 04

Data migration & validation

Duration: 1–3 weeks (parallel with build) Owner: CarePoint migration engineer + facility data lead

Resident demographics, current medications, allergies, NOK and active care plans are the priority. Historical incident registers and assessments are migrated where the source data supports it. Everything is validated on a sample before bulk load.

CarePoint does
  • Run an extract from your current system or accept CSV / Excel files
  • Map source fields to CarePoint records
  • Load a 10% sample for validation
  • Run reconciliation reports for the data lead to sign off
  • Execute the full load on the production tenant
Your facility does
  • Nominate a data lead (usually the DON or admin manager)
  • Run reconciliation checks against the 10% sample
  • Sign off the full load before go-live week
  • Identify any residents requiring manual data entry
Phase outputs: Validated migration report · production tenant loaded · exceptions list with owners.
Phase 05

Training delivery

Duration: 1–2 weeks, ending 3–5 days before go-live Owner: CarePoint training lead + facility super-users

A train-the-trainer model — your super-users learn deeply, then deliver role-specific sessions to the rest of the staff with CarePoint trainers in the room. The result is internal capability, not vendor dependency.

CarePoint does
  • Deliver super-user training (full day, hands-on, on configured tenant)
  • Co-deliver role-specific sessions: nursing, carer, allied health, lifestyle, admin
  • Provide role-specific quick-reference cards
  • Run dry-run scenarios — handover, med round, incident, admission
Your facility does
  • Roster super-users into the training week (5–7 hours total)
  • Roster role-specific sessions across all shifts (60–90 mins per role)
  • Confirm 100% of clinical staff trained before go-live
Phase outputs: Training attendance record · super-users certified · quick-reference distributed · dry-run completed.
Phase 06

Go-live & hypercare

Duration: Cutover day + 4–6 weeks hypercare Owner: CarePoint implementation lead on-site or live remote

A planned cutover at a low-clinical-activity window — typically a Sunday morning or weekday off-peak. CarePoint staff are on-site or on a live channel for the first 72 hours, then a defined hypercare period of intensive support.

CarePoint does
  • Run the final cutover and verify all logins, residents and configurations
  • Provide on-site or live-channel support for the first 72 hours
  • Daily check-in calls during week one
  • Twice-weekly check-ins for weeks 2–4
  • Triage and resolve issues with prioritised SLA
Your facility does
  • Roster super-users on every shift in week one
  • Run pre-cutover paper / old-system standdown
  • Submit issues via the prioritised support channel
  • Attend the 30-day retrospective
Phase outputs: Live production tenant · cutover sign-off · 30-day retrospective report · BAU support transition.
The two highest-risk workstreams, explained

Data migration and training, in detail.

Most EMR rollouts that struggle do so on one of these two workstreams. Here's exactly how we approach each.

Data migration

What comes across, and what doesn't.

We're realistic about migration scope. Active records — the ones that matter for tomorrow's shift — come across in full. Deep history is migrated where the source system supports it cleanly, archived where it doesn't.

Always migrated

  • Resident demographics, NOK and GP details
  • Current active medications with prescriber and frequency
  • Allergies and adverse reaction flags
  • Active care plans (translated into CarePoint's domain structure)
  • Current ACD and Goals of Care documents
  • Current ward and room assignment

Migrated where the source supports it

  • Recent progress notes (last 12 months by default)
  • Last 6 months of charting and observations
  • Active referrals and restrictive practice authorisations
  • SIRS register entries for the current reporting period
  • Assessment scores from validated tools (DEMMI, MMSE, etc.)

Generally not migrated — archived instead

  • Closed incidents older than the reporting window
  • Discharged-resident historical records (kept as read-only export)
  • Free-text legacy fields without a clean mapping target
  • Scanned PDFs (attached to records rather than parsed)
Training

Train-the-trainer, with us in the room.

Training is the cheapest insurance against a poor go-live. We use a layered model — deep super-user training, role-specific sessions co-delivered with super-users, then refresher modules during hypercare.

Layer 1 — Super-user deep training

  • Full-day session covering every module
  • Hands-on practice on your configured tenant
  • Scenario walkthroughs: handover, med round, incident, admission, discharge
  • Admin panel training for ongoing configuration ownership

Layer 2 — Role-specific sessions

  • Nursing (RN / EN): 90 minutes — eMAR, charting, handover, alerts
  • Care staff (PCA): 60 minutes — mobile-first task list, ADL charting
  • Allied health: 60 minutes — assessments, care plan, referrals
  • Lifestyle: 45 minutes — engagement charting, lifestyle notes
  • Admin: 90 minutes — user management, audit log, reporting

Layer 3 — Hypercare refreshers

  • 30-minute optional drop-in sessions in weeks 2 and 4
  • Topic-specific micro-trainings as issues surface (e.g. NQI, restrictive practices)
  • One-on-one with super-users for case-by-case coaching
What success looks like

The 30 / 60 / 90 milestones.

A healthy implementation hits these markers without heroics. We track them with you in the post-go-live retrospectives.

30
Days post go-live

Adoption baseline

  • 100% of clinical staff logging in independently
  • eMAR rounds completed digitally on every shift
  • Handover report read on the floor, not printed
  • Incident form completion rate ≥ 95% within 24h
  • First 30-day retrospective held with the executive sponsor
60
Days post go-live

Embedded use

  • Super-users self-sufficient on the admin panel
  • NQI dashboard populated and reviewed monthly
  • Care minutes tracking compared against funded target
  • Family portal enabled (if scoped) for first cohort
  • Average documentation time reduced vs paper baseline
90
Days post go-live

Quality outcomes

  • First quarterly NQI submission generated from CarePoint
  • SIRS register fully digital with priority deadlines tracked
  • Audit-ready evidence on the floor, not assembled retroactively
  • BAU support transition complete — quarterly business reviews scheduled
  • Net Promoter Score collected from clinical staff
Common questions

What facilities ask before signing.

Quick answers to the implementation questions we hear most often on demo calls.

How long does implementation really take? +
For most facilities, four to twelve weeks from kickoff to go-live, depending on bed count, data complexity and how quickly your team can attend design workshops. Small facilities (≤60 beds) often complete in four to six weeks; large facilities (120+ beds) commonly run twelve to fourteen weeks. The Gantt at the top of this page is indicative.
What hardware do we need? +
CarePoint is responsive — phone, tablet and desktop. Most facilities use a mix: tablets on medication trolleys, desktops at the nursing station, and personal devices for management. We can advise on procurement during Phase 1 if you don't already have a hardware plan.
What about our current paper records? +
Active resident records are migrated digitally where possible, and physical files are retained as your data-handling policy requires. Scanned documents can be attached to resident records via the Files tab. We provide a documented archive process for paper that's no longer required day-to-day.
Who needs to be involved from our side? +
An executive sponsor (usually DON or Facility Manager) for sign-off authority; a data lead for migration reconciliation; and three to five super-users from across nursing, care, allied health and administration. Most other staff are involved only during their role-specific training session and on go-live day.
What happens if we discover something during the build phase that needs to change? +
That's expected — Phase 3 exists specifically so the staging tenant catches design gaps before go-live. Change requests during build are handled in your project workspace and don't typically affect the go-live date. Material scope changes are scheduled into the post-go-live roadmap.
How is the cutover handled? +
Cutover happens at a low-clinical-activity window — typically a Sunday morning. The night-shift handover is run on the old system; the morning handover is run on CarePoint. Super-users are rostered for the first 72 hours, and a CarePoint implementation lead is on-site or available on a live channel throughout.
What does ongoing support look like after hypercare? +
Direct access to the CarePoint clinical and engineering team — not a tiered support queue. Standard response is same business day for clinical issues, with a defined SLA for incident severity. Quarterly business reviews keep your roadmap and configuration aligned with how your facility evolves.

Want to see what your timeline would look like?

Book a discovery call and we'll map your facility against the six-phase plan — bed count, current systems, super-user availability, target go-live. You leave with a date, not a brochure.

Book a demo