⚡ Healthcare APEX

BrainWorks — Paediatric Clinical Registry

SickKids Hospital

Challenge

BrainWorks is SickKids' outcome registry for children with central-nervous-system vasculitis: a 148-page Oracle APEX application on Oracle Database 19c that clinicians and researchers rely on. It needed to stay current, take on new clinical measures without a schema change for each one, and be released safely against live clinical data.

Solution

DB Realm took on the registry in 2022: upgraded it to APEX 23.1, built a metadata-driven vital-signs module where categories, metrics and values are defined as data, added visit and dashboard APIs, captured the schema in Liquibase, and moved changes to production through scripted, tested migrations.

Results

  • ✓ 148-page clinical registry upgraded to APEX 23.1
  • ✓ Vital signs stored as rows instead of columns
  • ✓ Visit and dashboard APIs for the registry
  • ✓ Schema in Liquibase; production changes by tested script
Oracle APEX Oracle Database 19c PL/SQL REST APIs Liquibase Clinical Registry

BrainWorks is SickKids’ outcome registry for children with central-nervous-system vasculitis. The condition is rare, so every record counts and the data has to be handled carefully. The registry is an Oracle APEX application of 148 pages on Oracle Database 19c.

Keeping a clinical system current

DB Realm took over the registry from a previous developer in 2022. The first job was the platform itself: the application was upgraded from APEX 22.2 to 23.1, so the registry stayed on a supported release with current security fixes.

Clinical measures as data

New clinical measures are a constant in a registry, and adding a column for each one turns every request into a schema change. The vital-signs module was built the other way round: categories, metrics and values are rows, managed through a PL/SQL API, so a new measure is a data change rather than a release.

APIs and safe releases

Visit handling and the registry dashboards gained PL/SQL APIs, including a JSON API for dashboard data. The schema was captured as Liquibase changelogs so changes could be reviewed and replayed, and production changes, including the vital-signs data migration in 2024, were delivered as scripted migrations tested before they ran against live clinical data.

Ready to Build Something Similar?

Let's discuss how we can bring the same expertise to your organization.

Start a Conversation