A shared data platform for Queensland rare disease research
Rare diseases are individually uncommon, yet together they affect many Australians and need coordinated specialist care. A patient may appear in a hospital registry, university cohort, biobank and follow-up service, with no shared record connecting the evidence. A common platform can reveal disease trajectories that small datasets conceal.
Queensland universities and health services conduct world-class research through different workflows and approvals. Queensland’s public hospitals sit within the Queensland Health system, while private specialists, Medicare and the Pharmaceutical Benefits Scheme provide complementary data. A statewide platform could connect these sources while giving patients, families and carers a meaningful voice in information use.
Why shared rare disease data matters in Queensland
Queensland’s geography makes collaboration essential. The University of Queensland and Queensland University of Technology are based in Brisbane, Griffith has a major Gold Coast presence, and James Cook University anchors northern research in Townsville, with partners through Cairns and Toowoomba. Regional patients may travel for diagnosis, making longitudinal records and telehealth follow-up valuable.
Uncommon-condition data are split across genetics services, hospitals, registries and community organisations. Researchers can spend months reconciling records, while clinicians may lack a clear testing history. Building a data sharing platform for rare disease research across Queensland universities would connect evidence through governance without forcing every participant into one database.
The coordinating experience of Queensland health partnerships is a strong foundation. Shared governance, standards and project support can reduce duplication. Measure success through usable cohorts, faster recruitment and changes to care rather than the volume of records loaded.
Governance that earns institutional trust
A governance committee should include universities, Queensland Health, patients, families, Indigenous data expertise, ethics specialists and cybersecurity staff. It should approve a minimum dataset, review projects and resolve access, attribution and publication disputes. A small executive sponsor group can handle urgent decisions between quarterly meetings.
Queensland projects navigate Commonwealth and state obligations. Depending on the controller, relevant rules may include the federal Privacy Act 1988, Queensland’s Health Records Act 2001, Queensland Health privacy requirements and approval from a human research ethics committee. The platform needs data use agreements, de-identification, retention rules and consent for secondary use.
Access should match sensitivity. Public summaries may remain open, while identifiable linkage needs approval, security training and monitoring. Outputs leaving controlled environments require disclosure checks. Recording every request, decision and correction gives participants and institutions a transparent audit trail.
A standards-based platform architecture
Use a common data model rather than forcing identical source systems into one format. FHIR can support clinical exchange, OMOP can standardise observational analysis, and HPO, SNOMED CT and LOINC can align phenotypes, diagnoses and tests. Persistent study identifiers, consistent dates and findable, accessible, interoperable and reusable metadata support reliable linkage.
International work offers useful minimum datasets and registry patterns. HARP registry resources provide a reference for harmonising rare disease information. Queensland teams can adopt proven elements while preserving disease-specific fields and room for rapidly changing research.
Security belongs in every layer, from consent and identity services to analysis rooms and backups. Role-based controls can protect de-identified extracts, while small, re-identifiable cohorts need tighter limits. Automated checks should flag missing dates, duplicate participants and inconsistent coding before analysis.
Consent, privacy and community authority
Consent should explain future uses in plain language. Participants need to know which organisations hold data, whether genomic results may be shared, retention periods and withdrawal options. My Health Records is opt-out for most Australians, but research reuse of identifiable information still needs specific governance and ethical consent.
Queensland includes distinct Aboriginal and Torres Strait Islander and remote communities with strong expectations of self-determination. The network should fund Indigenous data governance, apply protocols such as the Maiam nayri Wingara principles and establish local benefit processes. Generic consent forms cannot replace relationships negotiated with communities affected by extractive research.
Patients and carers can act as data stewards rather than recruitment sources. They should review plain-language summaries, advise on acceptable outputs and receive useful results, including updated variant interpretations. Compensation, feedback and accessible materials build trust and support long-term participation.
Building the partnership around the platform
A partnership office should define who curates data, answers requests and maintains standards. Each university needs a data steward, while Queensland Health provides approved linkage and clinical validation routes. Shared intake can identify eligible participants before duplication starts, and an online catalogue should display available cohorts, variables and biospecimens.
Rare conditions often appear where family studies overlap with maternal, neonatal or paediatric services. The collaborative approach in maternal and child research models linked family cohorts. Approved governance can connect pregnancy, birth and childhood outcomes with genomic findings, developmental records and parent-reported experience.
Funding must cover people and infrastructure. Grants should include stewardship, terminology management, training, community engagement and software maintenance. Universities can credit curation, recruitment and linkage in research reviews, while a shared service desk reduces burden on small disease teams. Reports should track completeness, turnaround, satisfaction and clinical impact.
Choosing the right data operating model
Queensland can operate a central repository, federated network or hybrid. The choice depends on sensitivity, institutional appetite, cohort size and cross-site analysis needs. Central storage supports rich analysis; federation keeps source data in place; a hybrid combines a searchable index with secure source linkage.
International case studies, including cross-border registry practice, reinforce common definitions, durable identifiers and transparent access criteria. Migration alone cannot solve governance. A sustainable service needs interoperable local data, funded stewardship and agreements that endure changes in conditions, funding and personnel.
| Operating model | Data approach | Advantages | Main trade-off | Queensland fit |
|---|---|---|---|---|
| Central repository | Curated de-identified data held centrally | Rich analysis and consistent quality checks | Privacy burden and duplicate curation | Larger disease registries |
| Federated network | Data remain at sites while shared queries run across them | Strong local control and easier scale-up | Technical variation and slower exploration | University-wide collaboration |
| Hybrid linked service | Central metadata index with secure linkage to sources | Longitudinal analysis without one large copy | Complex agreements and identity management | Core platform with specialist cohorts |
A practical path to coordinated action
Begin with a limited number of cross-institutional cohorts while core governance, standards and participant protections are settled. A staged rollout exposes workflow problems and cost drivers before statewide procurement, while pilots demonstrate value to participants and research teams.
- Form a steering group with patient, family, carer and Indigenous governance representation.
- Approve a minimum dataset, identifiers, FAIR metadata and quality measures before procurement.
- Pilot federated querying and secure linkage across Brisbane and a regional centre.
- Establish an access panel, appeal process and publication and attribution policy.
- Fund stewards, training, community engagement and infrastructure as operating costs.
- Publish yearly metrics on completeness, request times, experience and impact.
Each university should nominate a senior sponsor, data steward and clinical lead, then endorse one shared access and governance framework. Existing research offices and patient advisory groups can review the draft before software selection, preventing procurement from setting rules that communities cannot accept.
The immediate next step is a joint meeting convened through the statewide research partnership, with Queensland Health, participating universities and consumer representatives invited. The group should assign owners, confirm the pilot scope and agree the evidence required for platform approval.
