Platform capabilities
What each area does, what users do there, and what evidence is produced.
| Area | Function | What it does | Outputs |
|---|---|---|---|
| Access and workspace | Login gate | Protects platform pages and APIs behind authenticated access, with demo access enabled for training. | Authenticated session and protected workspace access. |
| Access and workspace | Tenant context | Displays the active tenant and constrains workspace data to tenant context where Supabase is configured. | Tenant context response and organization/membership evidence. |
| Conversion | Ontario MHA PDS template download | Provides the controlled data collection template with required Ontario MHA PDS fields and local guidance. | Excel workbook template and template download audit evidence. |
| Conversion | Demo source data | Provides a safe sample workbook for training conversion and validation without PHI. | Demo source workbook suitable for conversion practice. |
| Conversion | FHIR Bundle generation | Converts source rows into FHIR R4 Bundles with Patient, Organization, Location, EpisodeOfCare, Encounter, Appointment, and SDOH Observation resources. | FHIR Bundle JSON, conversion summary, import issues, and validation report. |
| Mappings | Mapping workbench | Shows source-to-FHIR mapping rules for PDS fields, FHIR paths, conformance notes, and review status. | Mapping evidence workbook with status, rule, FHIR path, and review notes. |
| Terminology | Terminology catalogue | Displays local terminology references, code table concepts, and governance metadata. | Terminology export, self-check result, local package/import evidence. |
| Validation | Bundle validation workbench | Validates FHIR Bundles against local requirements, downloaded package references, optional HL7 CLI/HAPI validation, and terminology checks. | Validation report, OperationOutcome-style diagnostics, issue counts, and remediation evidence. |
| Interface engine | Source intake | Accepts one canonical source row, validates it, generates a FHIR Bundle, and queues or submits it through the feed. | Submission job, Bundle identifier, resource count, queue status, and OperationOutcome diagnostics. |
| Interface engine | Queue and transport status | Tracks queued, validating, invalid, submitting, accepted, failed, and retrying submission jobs. | Feed activity table, job details, retry evidence, and mock/dry-run/live status. |
| Learning | Learning paths | Provides guided courses for roles, FHIR R4, MHA PDS data sets, terminology, validation, and submission operations. | Course pages, downloadable learning material, scenarios, rubrics, glossary, job aids, and capstone evidence. |
| Evidence | Exports and audit log | Exports conversion, mappings, terminology, validation, readiness, and audit evidence for implementation governance. | Excel/JSON/PDF evidence packages and audit activity records. |
| Settings | Standards and readiness settings | Shows package status, validator configuration, template self-checks, local requirements state, and readiness export. | Readiness workbook, settings evidence, package metadata, and validation configuration status. |
How to use the platform
Core workflow from sign-in through readiness evidence and production preparation.
| Phase | Step | Action | Evidence |
|---|---|---|---|
| 1. Sign in | Open the platform | Go to https://fhirbridge.ca and sign in. For training, use demo/demo. | Authenticated workspace access. |
| 2. Start with readiness | Run and interpret readiness | Open Readiness, review the current gates, and export the readiness workbook. For the seeded demo, distinguish demo-ready mechanics from blocked production gates. | Readiness workbook and documented gate decisions. |
| 3. Prepare source data | Download template and demo data | Use Download template and Download demo data from Overview. | Template and demo workbook downloads. |
| 4. Convert data | Upload source workbook | Use the conversion upload panel, select the demo/source workbook, and run Convert to FHIR. | Conversion job, two Bundle records, resource inventory, and downloaded Bundle JSON. |
| 5. Review mappings | Open Mappings | Review PDS fields, source fields, FHIR targets, mapping rules, status, and export workbook. | Mapping workbook export and owner decisions. |
| 6. Review terminology | Open Terminology | Search the local catalogue, review code table concepts, run self-check, and export terminology evidence. | Terminology export and warning triage notes. |
| 7. Validate FHIR | Open Validation | Review the persisted conversion findings, separate blockers from warnings/information, and export validation evidence. Use manual Bundle validation when testing a separate payload. | Validation report and issue log. |
| 8. Test interface-engine workflow | Open Live Feed | Test the Excel source and mock endpoint, submit one synthetic Bundle immediately, queue another, process next, and review feed activity. | Bundle identifier, queue status, HTTP/mock status, OperationOutcome diagnostics. |
| 9. Complete learning | Open Learn | Choose FHIR, PDS data set, terminology, validation, submission, or role learning paths. | Downloaded course material and completed capstone evidence. |
| 10. Export evidence | Build readiness package | Export mappings, terminology, validation, audit log, conversions, readiness, and course evidence. | Named evidence package with reviewers and dates. |
| 11. Prepare production transport | Review settings and transport mode | Confirm validation package, endpoint, dry-run/live mode, token governance, and Ontario Health onboarding requirements. | Transport checklist and readiness sign-off. |
Implementation and go-live
Production-oriented workstreams and final readiness gates.
| Phase | Owner | Acceptance | Evidence |
|---|---|---|---|
| 1. Confirm sponsorship and tenant setup | Executive sponsor, implementation lead, administrator | Tenant record exists, users are assigned to roles, demo-only access is disabled for customer production use, and RLS evidence is captured. | Tenant setup record, role matrix, access approval, and RLS test notes. |
| 2. Pin the authorized standards package | FHIR lead, data standards owner | Settings show the intended version, local package metadata is recorded, and the team knows which official materials cannot be redistributed publicly. | Package/version register, Settings export, and checksum or source-path notes where available. |
| 3. Complete source-system inventory | Hospital data lead, integration lead | Every required field has a named source, accountable owner, extraction method, and known data-quality limitation. | Source inventory workbook and unresolved gap log. |
| 4. Complete template readiness | Data analyst, quality lead | Template contains the full required field set and a populated test row with no structural errors. | Template workbook, self-check export, and sample-row review notes. |
| 5. Approve mappings | Clinical owner, FHIR lead, data owner | Mandatory fields are approved or explicitly deferred with owner/date, and unresolved mappings are not accepted for production. | Mapping export with approved/review statuses and sign-off notes. |
| 6. Build terminology crosswalks | Terminology lead, clinical owner | Terminology self-check passes for configured local catalogues, and every warning has an owner and disposition. | Terminology export, crosswalk file, and warning triage log. |
| 7. Run a demo conversion | Implementation analyst, QA lead | Expected row count becomes expected Bundle count, import issues are explained, and generated resources can be traced to source fields. | Conversion summary, Bundle JSON, import issue report, and traceability notes. |
| 8. Validate and triage findings | FHIR lead, QA lead | No unresolved fatal/error items remain for the production candidate extract; warnings are accepted or remediated. | Validation report, issue log, and remediation decisions. |
| 9. Test interface-engine workflow | Integration lead, operations lead | Jobs move through queued, validating, submitting, and accepted/mock-accepted states with traceable identifiers. | Feed activity export, job ID, Bundle ID, OperationOutcome, and retry/attempt history. |
| 10. Complete privacy and security readiness | Privacy officer, security lead, administrator | No production PHI is loaded until access, retention, audit, and operations controls are accepted. | Security checklist, privacy sign-off, audit export, and access review. |
| 11. Prepare Ontario Health transport go/no-go | Executive sponsor, integration lead, FHIR lead | A signed go/no-go decision exists before live transmission is enabled. | Transport checklist, dry-run evidence, endpoint/token governance notes, and go/no-go record. |
| 12. Run hypercare and evidence review | Operations lead, quality lead | Daily review is in place for the first production period and unresolved production defects have owners and due dates. | Hypercare tracker, daily queue review, issue register, and release notes. |
| Gate | Owner | Requirement | Evidence |
|---|---|---|---|
| 1. Authorized standards confirmed | FHIR lead and standards owner | The Ontario MHA PDS data dictionary, implementation guide, package, and terminology references are version-pinned for the release. | Standards register, package metadata, Settings export, and validation configuration record. |
| 2. Tenant and access controls approved | Security lead, privacy officer, administrator | Production tenant, memberships, RLS policies, role checks, export protection, and audit logging are verified. | RLS tests, role matrix, audit export, and access review sign-off. |
| 3. Data quality blockers resolved | Data owner and quality lead | Mandatory fields, dates, identifiers, terminology crosswalks, and timeline consistency pass for the production candidate extract. | Data quality remediation tracker, source preflight report, and final validation report. |
| 4. Mappings approved | Clinical owner, data owner, FHIR lead | Source-to-FHIR mappings for required and conditional fields are reviewed, approved, or formally deferred. | Mapping workbook export, approval status, and decision notes. |
| 5. Terminology governance complete | Terminology lead and clinical owner | Local source codes are inventoried, mapped, approved, and retained with a package-aligned terminology snapshot. | Terminology catalogue export, crosswalk, self-check result, and approval log. |
| 6. Validation evidence accepted | QA lead and FHIR lead | Source preflight, conversion traceability, local requirement validation, structural validation, package validation, and terminology validation are retained. | Validation evidence package, OperationOutcome diagnostics, and issue disposition log. |
| 7. Interface-engine dry run accepted | Integration lead and operations lead | Live Feed can queue, process, and record mock/dry-run jobs with traceable Bundle IDs, attempts, statuses, and diagnostics. | Feed job export, attempt history, dry-run response, and support notes. |
| 8. Transport and credentials approved | Integration lead and security lead | Endpoint, token ownership, rotation, timeout, retry, support contacts, and live-mode enablement procedure are approved. | Transport checklist, credential owner register, and endpoint approval notes. |
| 9. Operations and hypercare ready | Operations lead and support lead | Daily queue review, incident triage, retry/replay procedure, escalation path, and release notes are prepared. | Hypercare plan, support roster, incident playbook, and queue review schedule. |
| 10. Final go/no-go recorded | Executive sponsor | Business, clinical, data, privacy, security, FHIR, integration, and operations owners record final readiness decision. | Go/no-go record, owner sign-offs, final evidence pack, and launch decision. |