Save-and-resume clinical questionnaire feature

Problem

Patients and clinicians could not save a partly completed clinical questionnaire and return to it; the questionnaire is a knowledge-graph structure held in a large front-end state store with no clean persistence model behind it.

Solution

The team normalised legacy tables, introduced appointment templates and ordered template steps, and added a filled-form table storing form content as JSON keyed by appointment, step and form category, delivered as non-destructive migrations against staging. Backend save and fetch endpoints on Express running in AWS Lambda validate appointments and steps and upsert rather than duplicate. On the front end, a reusable save button and helpers serialise and restore Redux state, with new actions and a deep-merge reducer so selecting another condition merges into restored answers instead of clearing the form.

Key features

• Relational schema for appointments, templates, steps and saved forms
• Non-destructive SQL migrations against staging
• Save endpoint with validation and upsert
• Fetch endpoint with parameter validation
• Reusable save control in the questionnaire
• Redux rehydration with deep-merge of restored and new selections
• Front-end flow and backend architecture diagrams

Tech stack

• AWS API Gateway
• AWS Amplify
• AWS Cognito
• AWS Lambda
• AWS RDS
• AWS SAM
• Discord
• Docker
• Express
• GitHub
• Next.js
• Node.js
• PostgreSQL
• React
• Redux
• Sentry
• Stripe
• TypeScript
• ViTest
• axios
• eraser.io
• node-postgres
• pgAdmin
• serverless-http