Enterprise catalogue
FHIRBridge capability system
A HealthTrustIQ-branded catalogue of the platform functions required to move from fragmented healthcare source data to FHIR R4 readiness, validation evidence, and controlled submission operations.
Bundle validation evidence ready
Framework alignment
FHIRBridge is organized around healthcare interoperability, privacy, security, evidence, and operations readiness.
Ontario MHA PDSHL7 FHIR R4Implementation GuidesTerminology Value SetsPHIPA ReadinessSupabase RLSAudit EvidenceQA HAPI TransportSOC 2 ReadinessWCAG/AODA
QA verified — 2026-07-28
Demonstrable end-to-end workflow
Verified on fhirbridge.ca using synthetic data, Supabase-backed demo evidence, and mock/dry-run transport.
2 source rows2 valid Bundles16 FHIR resources0 fatal/error blockers2 mock submissions accepted0 failed submissions
Readiness Intelligence
Assess maturity across governance, source data, mappings, terminology, validation, security, and operations.
Source Data Workbench
Profile Excel, CSV, SQL/API-ready extracts, identifiers, mandatory fields, timeline consistency, and source quality.
Mapping Studio
Govern source-to-PDS-to-FHIR mappings with status, evidence, version notes, and review ownership.
FHIR R4 Factory
Generate traceable Bundles for local validation, QA transport, evidence review, and remediation cycles.
Validation Centre
Translate technical findings into human-readable blockers, warnings, owner actions, and retained evidence.
Interface Operations
Queue, process, test QA HAPI transport, separate dry-run/live modes, and monitor submission activity.
Terminology Catalogue
Maintain local code tables, crosswalks, reference data, value-set decisions, and refresh evidence.
Security and Evidence
Support tenant-aware controls, audit exports, production gates, and implementation evidence packs.
Access and workspace
Functions and outputs in this product area.
| Function | Status | What it does | User actions | Outputs | Production notes |
|---|---|---|---|---|---|
| Login gate | Demo-ready | Protects platform pages and APIs behind authenticated access, with demo access enabled for training. | Sign in with demo/demo for training or Supabase authentication for production tenants. | Authenticated session and protected workspace access. | Production should use Supabase Auth, MFA policy, tenant membership, and role-based access. |
| Tenant context | Beta | Displays the active tenant and constrains workspace data to tenant context where Supabase is configured. | Review active tenant in the header and bootstrap/configure tenant records before production use. | Tenant context response and organization/membership evidence. | RLS policies and tenant isolation tests are required before multi-tenant production onboarding. |
Conversion
Functions and outputs in this product area.
| Function | Status | What it does | User actions | Outputs | Production notes |
|---|---|---|---|---|---|
| Ontario MHA PDS template download | Demo-ready | Provides the controlled data collection template with required Ontario MHA PDS fields and local guidance. | Download the template, preserve column names, and populate source rows with de-identified or approved data. | Excel workbook template and template download audit evidence. | Confirm mandatory/conditional fields against the authorized Ontario Health/CAMH data dictionary release. |
| Demo source data | Demo-ready | Provides a safe sample workbook for training conversion and validation without PHI. | Download demo data and upload it on the Overview conversion panel. | Demo source workbook suitable for conversion practice. | Replace demo data with governed extracts only after privacy and tenant controls are approved. |
| FHIR Bundle generation | Demo-ready | Converts source rows into FHIR R4 Bundles with Patient, Organization, Location, EpisodeOfCare, Encounter, Appointment, and SDOH Observation resources. | Upload source workbook/CSV, run Convert to FHIR, inspect generated Bundle output, and download bundles. | FHIR Bundle JSON, conversion summary, import issues, and validation report. | Generated FHIR must be validated against the authorized Ontario MHA package before submission. |
Mappings
Functions and outputs in this product area.
| Function | Status | What it does | User actions | Outputs | Production notes |
|---|---|---|---|---|---|
| Mapping workbench | Beta | Shows source-to-FHIR mapping rules for PDS fields, FHIR paths, conformance notes, and review status. | Review mappings, select fields, update mapping status, and export the mapping workbook. | Mapping evidence workbook with status, rule, FHIR path, and review notes. | Clinical/data owners should approve mappings before production extracts are accepted. |
Terminology
Functions and outputs in this product area.
| Function | Status | What it does | User actions | Outputs | Production notes |
|---|---|---|---|---|---|
| Terminology catalogue | Beta | Displays local terminology references, code table concepts, and governance metadata. | Search terminology, filter concepts, run self-check, download local copy/package when configured, and export catalogue. | Terminology export, self-check result, local package/import evidence. | Terminology should be versioned and tied to the exact package/data dictionary used for validation. |
Validation
Functions and outputs in this product area.
| Function | Status | What it does | User actions | Outputs | Production notes |
|---|---|---|---|---|---|
| Bundle validation workbench | Beta | Validates FHIR Bundles against local requirements, downloaded package references, optional HL7 CLI/HAPI validation, and terminology checks. | Paste/upload Bundle JSON, run validation, review severity, download validation report, and triage issues. | Validation report, OperationOutcome-style diagnostics, issue counts, and remediation evidence. | Local validation is readiness evidence, not an Ontario Health acceptance response. |
Interface engine
Functions and outputs in this product area.
| Function | Status | What it does | User actions | Outputs | Production notes |
|---|---|---|---|---|---|
| Source intake | Demo-ready | Accepts one canonical source row, validates it, generates a FHIR Bundle, and queues or submits it through the feed. | Open Live Feed, edit canonical source JSON, choose queue/submit, and process next job. | Submission job, Bundle identifier, resource count, queue status, and OperationOutcome diagnostics. | Live Ontario Health transport requires configured endpoint, token governance, dry-run sign-off, and onboarding approval. |
| Queue and transport status | Demo-ready | Tracks queued, validating, invalid, submitting, accepted, failed, and retrying submission jobs. | Refresh feed activity, process next job, and review attempts, HTTP status, and remote/mock ID. | Feed activity table, job details, retry evidence, and mock/dry-run/live status. | Operations should define retry policy, incident response, monitoring, and daily queue review. |
Learning
Functions and outputs in this product area.
| Function | Status | What it does | User actions | Outputs | Production notes |
|---|---|---|---|---|---|
| Learning paths | Available | Provides guided courses for roles, FHIR R4, MHA PDS data sets, terminology, validation, and submission operations. | Open Learn, choose a learning path, complete lessons/labs, and download course material. | Course pages, downloadable learning material, scenarios, rubrics, glossary, job aids, and capstone evidence. | Training artifacts should be reviewed and branded before formal customer enablement. |
Evidence
Functions and outputs in this product area.
| Function | Status | What it does | User actions | Outputs | Production notes |
|---|---|---|---|---|---|
| Exports and audit log | Demo-ready | Exports conversion, mappings, terminology, validation, readiness, and audit evidence for implementation governance. | Use Export buttons across platform pages and retain files in the implementation record. | Excel/JSON/PDF evidence packages and audit activity records. | Retention, PHI minimization, and evidence-review owners must be defined before production use. |
Settings
Functions and outputs in this product area.
| Function | Status | What it does | User actions | Outputs | Production notes |
|---|---|---|---|---|---|
| Standards and readiness settings | Beta | Shows package status, validator configuration, template self-checks, local requirements state, and readiness export. | Review settings, run template self-check, import standards from configured package/path, and export readiness. | Readiness workbook, settings evidence, package metadata, and validation configuration status. | Authorized package URL/path, auth header, package checksum, and version pinning are required for controlled validation. |