The Australian e-Health Research Centre avatar

The Australian e-Health Research Centre

Official

@aehrc

0Followers
|
188Public Repos
|
20Published Skills

The Australian e-Health Research Centre (AEHRC) is CSIRO’s digital health research program.

Skills Distribution
DomainData Systems...Health-Informatics.. (40%)Distributed-Data-P.. (30%)Software-Engineeri.. (30%)

Agent Skills by The Australian e-Health Research Centre

Showing 20 vetted skills indexed across 1 GitHub repositories.

aehrcaehrc
133

pathling-python

Query and transform FHIR data with the Pathling Python API in Spark.

Official
Intermediate
aehrcaehrc
133

openspec-apply-change

Implement OpenSpec change tasks and update progress automatically.

Official
Advanced
aehrcaehrc
133

hapi-fhir-server

Implement FHIR servers with HAPI FHIR Plain Server framework.

Official
Advanced
aehrcaehrc
133

openspec-explore

Explores ideas and investigates codebases through adaptive dialogue and ASCII diagrams within OpenSpec systems.

Official
Intermediate
aehrcaehrc
133

openspec-verify-change

Verify code implementations against openspec change artifacts using the openspec CLI.

Official
Advanced
aehrcaehrc
133

openspec-new-change

Scaffold a new change directory in the OpenSpec system.

Official
Intermediate
aehrcaehrc
133

radix-ui

Guide building accessible React UIs with Radix Themes and Radix Primitives.

Official
Intermediate
aehrcaehrc
133

sql-on-fhir

Create SQL on FHIR ViewDefinitions to flatten FHIR resources into tabular formats.

Official
Advanced
aehrcaehrc
133

jmh-benchmarks

Write and execute Java microbenchmarks with the Java Microbenchmark Harness.

Official
Intermediate
aehrcaehrc
133

fhir-bulk-data

Implement HL7 FHIR Bulk Data Access with $export and NDJSON workflows.

Official
Advanced
aehrcaehrc
133

fhir-api

Implement FHIR RESTful API servers and clients per HL7 FHIR specifications.

Official
Advanced
aehrcaehrc
133

openspec-archive-change

Archive completed changes after verifying artifact and task completion status.

Official
Advanced
aehrcaehrc
133

fhirpath

Write FHIRPath expressions to navigate, query, and extract data from FHIR resources.

Official
Intermediate
aehrcaehrc
133

openspec-onboard

Guide users through the OpenSpec workflow cycle from task selection to archiving.

Official
Advanced
aehrcaehrc
133

openspec-bulk-archive-change

Archive multiple completed changes and resolve capability spec conflicts via codebase inspection.

Official
Advanced
aehrcaehrc
133

openspec-continue-change

Create the next OpenSpec artifact in a predefined workflow using CLI checks.

Official
Advanced
aehrcaehrc
133

Apache Spark Catalyst API

Create custom expressions and optimize queries in Apache Spark Catalyst.

Official
Advanced
aehrcaehrc
133

openspec-sync-specs

Merge delta specification changes into main openspec documents.

Official
Advanced
aehrcaehrc
133

openspec-ff-change

Create all OpenSpec framework artifacts for a new change in dependency order.

Official
Advanced
aehrcaehrc
133

smart-app-launch

Implement SMART App Launch OAuth 2.0 authorization flows for FHIR applications.

Official
Advanced

Frequently Asked Questions About The Australian e-Health Research Centre

FAQPage Schema
What specific clinical data tasks are enabled by these resources?

These resources enable the transformation, querying, and extraction of clinical data using FHIRPath expressions and SQL-on-FHIR ViewDefinitions. Users can implement RESTful servers, manage bulk data exports via NDJSON, and secure clinical applications using SMART App Launch protocols for standardized health information exchange.

Which technical personas benefit from these implementations?

Health informatics engineers, clinical data architects, and backend developers working on interoperability projects benefit from these resources. They are designed for professionals building HAPI FHIR servers, managing large-scale clinical data pipelines, or integrating secure authorization layers into existing hospital information systems.

What are the primary dependencies for deploying these clinical data solutions?

Deployments typically require a Java runtime environment, Apache Spark for distributed processing, and a compliant HAPI FHIR server instance. Integration with clinical systems necessitates adherence to HL7 FHIR specifications and proper configuration of OAuth 2.0 providers for secure SMART App Launch authentication.