CUT TO:
INT. PROJECT ARCHIVE — STORYBOARD ROOM
The USER opens TCC360.
DIVAKAR DESSAI
Let's run through the shots.
CASE FILE / Healthcare / Full Stack / FHIR / AI
TCC360Customisable Digital Care Plans
A healthcare software project developed as my UNSW thesis, focused on creating flexible and interoperable clinical care plans for patients with complex multimorbidity.
01–02 / OPENING SEQUENCE
Establishing the world
01 / Establishing Shot
The Problem
Patients with complex multimorbidity often require care plans that differ significantly between individuals. A rigid monitoring configuration makes it difficult for clinicians to adapt thresholds, goals, questionnaires and schedules to the needs of each patient.
02 / Wide Shot
The Context
The project was developed as my UNSW Software Engineering Honours thesis within the TCC360 healthcare research environment. It extended an existing remote patient monitoring platform used to support virtual care workflows.
03 / CHARACTER NOTE
DIVAKAR'S ROLE
Subject
Divakar Dessai
Production
TCC360
Take
03 / Role
Role notes
DIVAKAR DESSAI
I worked across frontend, backend and healthcare data modelling, implementing new care-plan functionality while integrating it with the existing TCC system and FHIR-based data structures.
04 / CLOSE-UP
THE ENGINEERING CHALLENGE
The main engineering challenge was introducing flexible care-plan configuration without breaking the assumptions of an existing healthcare platform. New functionality also had to fit clinical workflows and remain compatible with interoperable healthcare data models.
05 / TRACKING SHOT
THE APPROACH
A plan emerges.
I modelled care-plan functionality around FHIR resources and extended the application with interfaces for thresholds, goals, questionnaires and scheduling. The backend supported care-plan lifecycle operations while the frontend exposed these capabilities through reusable React components. Later development also explored AI-assisted interactions and FHIR Communication-based messaging.
06 / INSERT SHOTS
KEY FEATURES
The system takes shape.
07 / DIRECTOR'S NOTES
DESIGN DECISIONS
Things we decided along the way
01
Used FHIR resources to preserve interoperability with the existing healthcare platform.
02
Separated reusable clinical templates from patient-specific configuration.
03
Designed care-plan functionality as modular frontend components rather than a single monolithic interface.
04
Preserved backend support for multiple care plans while simplifying the visible clinical workflow where required.
05
Represented deleted or completed healthcare resources through lifecycle states rather than destructive deletion where appropriate.
design decisions
somewhere mid-build
08 / RETAKES
WHAT WENT WRONG
Naturally, not everything cooperates.
09 / FINAL SHOT
THE OUTCOME
ProblemBuildOutcome
01
Delivered configurable digital care-plan functionality within the TCC360 platform.
02
Implemented threshold, goal and questionnaire-management workflows.
03
Built reusable frontend and backend components for extending care plans.
04
Applied healthcare interoperability standards within a real software architecture.
05
Explored AI-assisted functionality within a clinically governed application.
10 / PRODUCTION NOTES
TECH STACK
The tools behind the scenes.
ReactTypeScriptFHIRAzureLlama 3.3GROQ
FADE OUT.
USER closes the file.
One project down. A few more stories left.
DIVAKAR DESSAI
Pick another?