Our Solution

Bronson designed and delivered the registry as a structured, two-phase Azure database development program coordinated with Know History and SCRJ. The work was organized across nine streams:

1. Azure Platform Architecture

Bronson architected the registry on Microsoft Azure, using interconnected tables to hold personal details, sterilization event data, medical provider information, witness information, consent records, and file assessment outcomes. The platform was selected to meet SCRJ’s security, access control, and reporting requirements.

2. Personal, Contact, and Demographic Data Schema

Bronson built the schema covering legal and alternate names, legally appointed personal representatives, addresses, emergency contacts, education, Indigenous identity with supporting documentation, gender, preferred communication language, and client intake tracking fields.

3. Event, Medical Provider, and Witness Data Schema

Bronson built the event-specific schema covering date of birth, date and age at sterilization, health care provider name and title, location and location type, sterilization type, type of medical consent provided, reason given, surrounding circumstances such as occurrence during labour, delivery, or another medical procedure, residence at the time, witness information, and document uploads.

4. Consent Management Engine

Bronson built a consent management engine supporting all required consent types, with database-enforced rules ensuring that downstream data use and sharing reflects only what each survivor has individually authorized. The engine logs consent changes chronologically and supports workflows for survivors who revoke consent and request data removal.

5. File Assessment and Quality Assurance Workflow

Bronson built the assessment and quality assurance workflow, tracking person type, file status, assessment completion status, and QA review completion, with automated Survivor ID issuance triggered only when all three required conditions are simultaneously met.

6. Role-Based Access Control

Bronson implemented the three-tier permission model: an upload-and-edit role for data entry staff, a read-only role for reviewers and quality assurance personnel, and a reporting role for administrators. The interim system delivered the data entry tier; the completed version introduced all three.

7. Search, Reporting, and Document Storage

Bronson built keyword and wildcard search across name, person ID, phone number, and email address. Reports deliver survivor and applicant contact information in downloadable CSV format, with additional filterable views supporting research, communications, and administrative functions. Document storage accepts JPEG, PNG, PDF, TXT, and DOC/DOCX formats within defined size limits.

8. Epiq Healing Support Fund Integration

Bronson built the integration with Epiq, transmitting only the data each survivor has consented to share: Survivor IDs for all eligible survivors to confirm eligibility, and name, date of birth, and contact details for those who consent to additional information sharing, supporting claim validation and ongoing data reconciliation. CSV-based sharing was scoped for the interim launch, with SRSS automation under review for the completed system.

9. Phased Launch and Partner Coordination

Bronson coordinated delivery across both phases with Know History and SCRJ. The interim solution launched November 1, 2024. The completed registry launched January 31, 2025. Bronson supported Know History on training, testing, and feature sequencing across the two phases.

Key Deliverables

• Azure Registry Database Architecture – The Azure platform design supporting interconnected tables, role-based access, document storage, search, reporting, and integration with the healing support fund administrator.
• Personal, Contact, and Demographic Data Schema – Complete schema covering name, contact, address, emergency contact, education, Indigenous identity with documentation, gender, language, and intake tracking.
• Event, Medical Provider, and Witness Data Schema – Complete schema covering sterilization date and age, provider and location details, sterilization type and reason, surrounding circumstances, residence, witness information, and document uploads.
• Consent Management Engine – Database-enforced consent rules covering all required consent types, with chronological change logging and structured workflows for revocation and data removal requests.
• File Assessment and Quality Assurance Workflow – Structured workflow tracking person type, file status, assessment completion, and QA confirmation, with automated Survivor ID issuance once all conditions are satisfied.
• Role-Based Access Control – Three permission tiers supporting data entry, read-only review, and reporting, phased across the interim and completed registry releases.
• Search, Reporting, and Document Storage Capability – Keyword and wildcard search, filterable CSV reporting, and document storage supporting five accepted file formats.
• Epiq Healing Support Fund Integration – Consent-scoped data transmission to the third-party claims administrator, covering Survivor ID eligibility confirmation and additional consented data for claim processing and reconciliation.

The Impact

Bronson delivered a registry purpose-built for SCRJ’s membership work, providing the technical foundation needed to register and assess survivor files with appropriate care, precision, and control. The engagement produced:

• A custom Azure registry tailored to SCRJ’s specific intake, assessment, and fund coordination requirements, rather than an adapted off-the-shelf platform.
• Database-enforced consent management ensuring that every downstream use of survivor data, whether for fund administration, internal research, or collaborative research, reflects each survivor’s individual authorizations precisely.
• Chronological consent change logging with structured revocation and removal workflows, giving survivors meaningful and ongoing control over their information.
• A structured file assessment and quality assurance workflow that protects the integrity of eligibility determinations and removes reliance on manual user discipline.
• Role-based access controls limiting data visibility and editing rights to appropriate personnel, in line with SCRJ’s privacy requirements.
• A clean, consent-respecting integration with Epiq that supports eligibility confirmation and claim processing without exceeding the bounds of what survivors have agreed to share.
• A two-phase delivery that allowed SCRJ to begin registering members in November 2024, with the full registry operational by the end of January 2025.

The registry Bronson built gives SCRJ a secure, consent-enforced, and operationally reliable foundation for its membership work. As the organization continues processing files and coordinating with the healing support fund, the system supports every step of that process while keeping survivor dignity and data control at the centre of every interaction.