Demo credentials
Use demo / demo. Use only the downloadable synthetic workbook.
End-to-end workflow
Follow these steps in order when onboarding a team, running a demo, or preparing production readiness evidence.
| Phase | Step | Action | Expected result | Evidence |
|---|---|---|---|---|
| 1. Sign in | Open the platform | Go to https://fhirbridge.ca and sign in. For training, use demo/demo. | The Overview dashboard opens and the left navigation is visible. | 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. | Conversion/storage gates are ready; mappings need review; external validator, official package, and production access gates remain visibly incomplete. | Readiness workbook and documented gate decisions. |
| 3. Prepare source data | Download template and demo data | Use Download template and Download demo data from Overview. | You have the controlled workbook structure and a practice data set. | 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. | The supplied demo workbook converts 2 rows into 2 Bundles and 16 FHIR resources with zero rejected rows and zero fatal/error blockers. | 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. | Mappings are understood and review status is visible. | 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 gaps and local crosswalk needs are visible. | 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. | The seeded demo shows no fatal/error blockers; terminology-snapshot and missing external-validator findings remain visible and must not be described as Ontario Health acceptance. | 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. | Both jobs reach accepted mock status with HTTP 201 semantics, while transport remains visibly labelled mock and dry-run. | 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. | Learners can follow labs, scenarios, glossary, job aids, rubrics, and capstone deliverables. | Downloaded course material and completed capstone evidence. |
| 10. Export evidence | Build readiness package | Export mappings, terminology, validation, audit log, conversions, readiness, and course evidence. | The implementation team has readable workbooks containing job, Bundle, resource, issue, package, gate, and audit 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. | The team records a no-go until the authorized package, external validator, production authentication controls, approved endpoint, and credentials are complete. | Transport checklist and readiness sign-off. |
Demo completion checklist
Complete these checks before presenting the workflow.
| Check | Pass condition | If it does not pass |
|---|---|---|
| Authentication | Overview opens after demo/demo sign-in. | Refresh the login page and confirm demo access is enabled. |
| Conversion | 2 rows produce 2 Bundles and 16 resources. | Download a fresh demo workbook and preserve its headers. |
| Validation | Fatal/error blockers remain zero; warnings are visible. | Open the issue evidence and correct source, mapping, terminology, or validator configuration. |
| Interface engine | Immediate and queued jobs reach accepted mock status. | Confirm mock transport and dry-run mode, then retest source and endpoint. |
| Evidence | Readiness, validation, and conversion workbooks download with populated sheets. | Rerun conversion, refresh the page, and export again. |