What does "configurable digital health platform" actually mean?

Forms, workflows, pathways, content, languages, notifications, dashboards and reports are all configured to your program, shaped to fit, without code. When a program needs something genuinely new, it's built at controlled extension points inside the platform, scoped and named in the plan.

What happens when we need something Concord doesn't have?

We build it inside the platform, not around it. Extensions are scoped in the design phase and named in the delivery plan, so there's never a mystery line item. What's built for one program becomes part of the platform the next program reuses.

What does Concord integrate with?

Concord speaks FHIR AU and HL7, and integrates with EHR/EMR systems, devices and wearables, labs and diagnostics, registries, payments and BI tools. If your program needs a connection we don't have, that's a named extension, not a workaround.

Where does our data live?

In Australia. Concord-managed deployments run on a native FHIR data store with Australian data residency; self-hosted deployments run against your existing data platform under your controls. Either way: ISO 27001, HSS-approved, Privacy Act aligned, audit logged.

How is 18 weeks possible?

Because the foundations aren't rebuilt for each customer. Concord is multi-tenant and built once. Real-world programs continually strengthen the platform layer, so a new program configures proven modules rather than starting from scratch.

The platform

Don’t build it from scratch.
Don’t bend to generic software.

Configure what’s already proven.

Concord is a configurable digital health platform: proven modules, built with Australian health organisations, configured to the way your program works. What we bring to your program, not what we’d build from scratch.

Book a demo See every project

Explore the platformThe experience Platform map The modules Configure & extend Deployment

Illustrative Concord web portals · Example data · Based on the Concord product suite

Illustrative clinician care queue
Patient	Next step	Status	Time
PT–1042	Weekly check-in	Review due	09:00
PT–1048	Care plan review	In progress	09:30
PT–1051	Patient-reported outcome	Review due	10:00
PT–1063	Scheduled follow-up	Scheduled	10:30

The connected platform

Different experiences.
One shared engine.

Follow the connections from the person using Concord to the services and data beneath it. Select any part to explore.

Experiences

Connected through the same platform

01 / Experiences

Patient / family

The person’s experience, connected to the people supporting their care.

Digital health passport & profile
Health tracking & self-management
Appointments, reminders & tasks
Secure messaging & telehealth
Education, surveys & AI support

Platform

Shared capabilities

Core services

Data

FHIR-aligned · Governed · Connected

Deploy your way

Integrations

One architecture, from experience to infrastructure.

The Research experience is on the roadmap. Research data and shared platform services are shown separately.

The third way

Australian health teams are told they have two options. Concord is the one they actually want.

Build it bespoke

Fits your workflow, eventually.

12–18 months to live.
Your funding pays for foundations you maintain forever.
Every change starts from zero.

Configure Concord

Proven modules, configured to the way you work.

Live in 18 weeks.
Built with Australian health organisations.
Your funding goes into the initiative, not the foundations.

Fits your program Starts from ready

Buy generic SaaS

Live quickly, if you bend to fit it.

Outside-in: your workflow conforms to the software.
Not built for Australian care, research or community.
Every gap becomes a workaround.

Concord is the proof that you don’t have to choose between fits and fast.

How it’s organised

One platform.
Four pillars.

Patient engagement

The person's side of the program: apps, forms, messaging and consent, reaching people where they actually are.

Explore modules

Clinical & service orchestration

The team's side: pathways, queues, tasks and reviews that keep the workflow running properly.

Explore modules

Research operations

The program's engine room: recruitment, capture, registries and reporting, with clean data from day one.

Explore modules

Secure data exchange

The connections: FHIR AU, HL7, integrations and exports, using the standards Australian health runs on.

Explore modules

Storage and access control aren’t pillars. They sit beneath all four.

What’s in the box

The modules,
in plain terms.

One platform. Composed around your program.

See how it configures

Patient engagement

App builder

Patient and participant apps, configured without code
iOS, Android and web from one build
Your program’s look, your program’s words

Orchestration

Care pathways

Structured programs from enrolment to outcome
Queues, tasks and assignment for the whole team
Turnaround visible, not guessed

Patient engagement

ePRO & eCOA

Patient-reported outcomes, captured where people are
Scheduled, triggered or ad-hoc collection
Clinician-facing scores, not raw exports

Orchestration

Remote monitoring

The program in view between visits
Thresholds and escalation rules you set
Alerts that reach the right person, once

Research operations

Registries & data capture

Clean, structured data from day one
Longitudinal records across projects and sites
Built with Hunter Medical Research

Research operations

Reporting & research access

Real-time, ad-hoc and scheduled reporting
De-identified research access, governed
Exports your analysts actually want

Secure data exchange

Integrations & FHIR AU

FHIR AU base profile, HL7
EHR/EMR, devices, labs, registries, BI
Enterprise security beneath it all, penetration-tested with WA Health

The honest split

Most of your program configures. The rest extends inside the platform, not around it.

Configure

Most of the work

Forms, workflows and content, shaped to fit.

Your pathways, scoring and rules
Your registration and consent journeys
Your content, languages and notifications
Your dashboards and reports

…configured, not coded.

Extend

The honest remainder

Controlled extension points inside the platform.

Program-specific tools and views
New integrations we don’t yet have
Research models shaped to your questions

Scoped in design, named in the plan, never a mystery line item.

Configured in weeks.
Not coded over years.

Built once, reused

Your advanced
starting position.

Concord is multi-tenant and reusable: built once, with the people who use it, and improved by every project after. Portals, forms, messaging, data capture and security already exist, strengthened by every live project. A new program starts from ready: configured, not coded, live in 18 weeks. Your funding goes into the initiative, not the foundations.

How funding shapes Concord

Your next program

01Portals & forms

02Messaging & data capture

03Security & access

Every new customer adds a brick the next one reuses.

Where it runs

Concord-managed,
or on your platform.

Request the security pack

Concord-managed

Native FHIR data store with managed analytics and governance. AU-hosted, Australian data residency.

Self-hosted

Run Concord against your existing data platform. Your infrastructure, your controls, same modules.

ISO 27001
AU-hosted
HSS-approved
Privacy Act
FHIR AU
Audit logging

Works with your stack

EHR/EMR
Devices & wearables
Labs & diagnostics
Registries
Payments
BI tools

2,500+ active end-usersa growing partner communitylive in 18 weeks

Start from ready.

Book a demo Or ask how it would compose for your program

Common questions

Don’t build it from scratch.
Don’t bend to generic software.

The whole day, in view.

Different experiences.
One shared engine.

Experiences

Patient / family

Platform

Data

Integrations

Australian health teams are told they have two options. Concord is the one they actually want.

Build it bespoke

Configure Concord

Buy generic SaaS

One platform.
Four pillars.

Patient engagement

Clinical & service orchestration

Research operations

Secure data exchange

The modules,
in plain terms.

App builder

Care pathways

ePRO & eCOA

Remote monitoring

Registries & data capture

Reporting & research access

Integrations & FHIR AU

Most of your program configures. The rest extends inside the platform, not around it.

Configure

Extend

Your advanced
starting position.

Concord-managed,
or on your platform.

Concord-managed

Self-hosted

Works with your stack

Start from ready.

What buyers ask
about the platform.

Don’t build it from scratch. Don’t bend to generic software.

Explore the Concord web portals

The whole day, in view.

Different experiences. One shared engine.

Experiences

Patient / family

Platform

Data

Integrations

Australian health teams are told they have two options. Concord is the one they actually want.

Build it bespoke

Configure Concord

Buy generic SaaS

One platform. Four pillars.

Patient engagement

Clinical & service orchestration

Research operations

Secure data exchange

The modules, in plain terms.

App builder

Care pathways

ePRO & eCOA

eConsent

Remote monitoring

Registries & data capture

Reporting & research access

Integrations & FHIR AU

Most of your program configures. The rest extends inside the platform, not around it.

Configure

Extend

Your advanced starting position.

Concord-managed, or on your platform.

Concord-managed

Self-hosted

Works with your stack

Start from ready.

What buyers ask about the platform.

01What does "configurable digital health platform" actually mean?

02What happens when we need something Concord doesn't have?

03What does Concord integrate with?

04Where does our data live?

05How is 18 weeks possible?

Don’t build it from scratch.
Don’t bend to generic software.

Different experiences.
One shared engine.

One platform.
Four pillars.

The modules,
in plain terms.

Your advanced
starting position.

Concord-managed,
or on your platform.

What buyers ask
about the platform.