Test Lead

Location: Onsite as needed basis

Public Sector Experience: must have

# of submissions/supplier: 1

Province/State

Ontario

City

Toronto

Country

Canada

Office Location

525 University Avenue

Assignment Type

Hybrid

Job Title

Sr. Test Lead for FHIR validations

Description

The Agency requires a Senior Test Lead to support the Enterprise Pub/Sub Applications Team. The resource will lead validation of The Agency application and workflow changes that integrate with the Enterprise Pub/Sub service, which is based heavily on FHIR Subscription and SubscriptionTopic. Testing will cover the transition from scheduled polling to event-driven delivery, including publishers, subscriptions, notifications, queues, downstream applications, and clinical workflows. This role spans test strategy, estimation, planning, traceability, automation, test data and environment coordination, execution, defect management, reporting, and release readiness. The resource will perform and lead API automation testing using Postman, NextGen API testing tools, and ngrok-hosted endpoints; validate FHIR, REST, HL7 v2, and NextGen Connect integrations; test React single-page applications; and coordinate end-to-end testing across healthcare applications, Ontario digital health assets, and eReferral workflows.

Required Skills

• Senior test guidance experience for complex healthcare integration or enterprise application programs, including test strategy, planning, estimation, risk-based coverage, traceability, defect management, reporting, exit criteria, and release recommendations.
• Strong API automation experience testing publish-and-subscribe and asynchronous workflows using Postman, NextGen API testing tools, and ngrok, including callbacks, authentication, correlation, idempotency, retries, duplicate events, error handling, and replay.
• Hands-on FHIR and REST testing experience, including FHIR Subscription, SubscriptionTopic, notification Bundles, filters, lifecycle and status changes, resource validation, positive and negative scenarios, and end-to-end API verification.
• Hands-on HL7 v2 and NextGen Connect testing experience, including message structure, transformations, routing, acknowledgements, error paths, interface validation, and end-to-end integration with FHIR and application services.
• Experience testing SMART on FHIR React single-page applications and healthcare workflows involving Ontario digital health assets, provincial integration services, and eReferral applications, including functional, integration, regression, accessibility, and browser testing, experience with Smart on fhir sandboxes such as MELD, EPIC launchpad, etc.

Responsibilities

• Develop and maintain the overall test strategy, master test plan, estimates, scope, test levels, environments, data needs, entry and exit criteria, and reporting approach for Enterprise Pub/Sub application changes.
• Review product, workflow, interface, and technical requirements; identify quality risks and coverage gaps; and maintain traceability from requirements through test scenarios, defects, and release evidence.
• Design, automate, execute, and maintain API tests for publishers, subscription management, notification delivery, event retrieval, queue-based processing, downstream actions, and failure-recovery workflows.
• Use Postman, NextGen API testing tools, and ngrok-hosted endpoints to validate REST APIs, external callbacks, rest-hook delivery, request and response payloads, headers, authentication, timeouts, and error handling.
• Validate FHIR Subscription, SubscriptionTopic, notification Bundles, filters, lifecycle and status transitions, resource references, search and event retrieval, conformance, and positive and negative API scenarios.
• Test HL7 v2 interfaces and NextGen Connect channels, including message construction, parsing, transformation, routing, acknowledgements, invalid messages, interface errors, recovery, and integration with FHIR and application workflows.
• Test React single-page applications across supported browsers and user workflows, including functional behaviour, API integration, state handling, error messaging, accessibility, security-related behaviour, and regression coverage.
• Coordinate end-to-end testing across healthcare applications, Ontario digital health assets, eReferral workflows, publishers, Enterprise Pub/Sub, subscribers, and downstream systems.
• Validate asynchronous reliability and operational scenarios, including event correlation, ordering where required, concurrency, idempotency, retries, duplicate delivery, dead-letter handling, replay, reconciliation, outage recovery, and monitoring.
• Coordinate test environments, endpoint configuration, connectivity, certificates, test accounts, test data, privacy-safe data handling, stubs, simulators, and dependencies across participating teams and vendors.
• Lead defect triage, root-cause collaboration, retesting, regression selection, quality metrics, daily status reporting, risk escalation, and evidence-based assessment of residual risk.
• Prepare test completion reports and release recommendations, support business acceptance and production validation, confirm operational readiness, and provide testing knowledge transfer to The Agency teams.

Desired Skills

• Experience testing FHIR R4 or R4B resources and APIs, including Subscription, SubscriptionTopic, event notification Bundles, validation profiles, terminology, and conformance requirements.
• Experience with Ontario digital health services, healthcare assets, EMR or HIS integration, clinical workflows, eReferral applications, and multi-organization testing.
• Experience with NextGen Connect administration and API capabilities, Postman collections, NextGen API testing tools, ngrok, service virtualization, stubs, and test-data utilities.
• Experience integrating automated API and user-interface tests into build and deployment pipelines, with versioned test assets, repeatable execution, reporting, and regression gates.
• Experience testing cloud-based event services, queues, observability, security controls, performance, resilience, failure recovery, and production support scenarios.

Required Competencies

• Senior test guidance experience for complex healthcare integration or enterprise application programs, including strategy, planning, estimation, risk-based coverage, traceability, defect management, reporting, exit criteria, and release recommendations.
• Publish-and-subscribe API automation experience using Postman, NextGen API testing tools, and ngrok, including subscription workflows, callbacks, asynchronous events, authentication, correlation, idempotency, retries, duplicate events, error handling, and replay.
• FHIR, REST, HL7 v2, and NextGen Connect testing experience, including FHIR Subscription and SubscriptionTopic, notification Bundles, filters, lifecycle changes, resource validation, message transformations, routing, acknowledgements, and interface error scenarios.
• React single-page application and end-to-end healthcare workflow testing experience, including Ontario digital health assets, provincial services, eReferral applications, functional and integration testing, regression, accessibility, and release readiness.

Rated Criteria

• Senior test leadership experience for complex healthcare integration or enterprise application programs, including strategy, planning, estimation, risk-based coverage, traceability, defect management, reporting, exit criteria, and release recommendations. 25 points
• Publish-and-subscribe API automation experience using Postman, NextGen API testing tools, and ngrok, including subscription workflows, callbacks, asynchronous events, authentication, correlation, idempotency, retries, duplicate events, error handling, and replay. 25 points
• FHIR, REST, HL7 v2, and NextGen Connect testing experience, including FHIR Subscription and SubscriptionTopic, notification Bundles, filters, lifecycle changes, resource validation, message transformations, routing, acknowledgements, and interface error scenarios. 25 points
• SMART on FHIR React single-page application and end-to-end healthcare workflow testing experience smart on fhir sandboxes like MELD, EPIC launch pad, etc, including Ontario digital health assets, provincial services, eReferral applications, functional and integration testing, regression, accessibility, and release readiness. 25 points

Total: 100 Points

Deliverables

Deliverables

• A comprehensive test strategy and master test plan covering scope, estimates, test levels, risk-based priorities, environments, data, roles, dependencies, entry and exit criteria, reporting, and release evidence.
• A requirements traceability matrix and maintained suite of test scenarios, test cases, data requirements, expected results, execution records, and coverage evidence.
• Automated publish-and-subscribe API test suites covering publishers, subscriptions, notifications, callbacks, event retrieval, queues, downstream actions, negative scenarios, and failure recovery.
• Postman collections, NextGen API testing assets, ngrok endpoint configurations, environment variables, reusable scripts, and execution instructions for repeatable API and callback testing.
• FHIR and REST test assets covering Subscription, SubscriptionTopic, notification Bundles, filters, lifecycle transitions, conformance, resource validation, search, event retrieval, authentication, and error handling.
• HL7 v2 and NextGen Connect test messages, channel and route validation evidence, acknowledgement and error-path results, interface test records, and end-to-end integration coverage.
• React single-page application functional, integration, accessibility, browser, error-handling, and regression test suites with repeatable execution evidence.
• End-to-end test coverage and results across Ontario digital health assets, healthcare applications, eReferral workflows, Enterprise Pub/Sub, and participating downstream systems.
• Defect records, triage outcomes, retest and regression evidence, quality dashboards, coverage metrics, risk assessments, test status reports, and stakeholder communications.
• Test completion reports, release recommendations, business-acceptance support, production validation evidence, operational-readiness inputs, runbooks, and knowledge-transfer materials.

Additional Terms

The term of this Engagement Assignment is for 124 Business Days, with an option to extend for up to an additional 64 days at the Agency’s discretion. The Engagement Assignment may be extended for unused Business Days at the Agency’s discretion.

The resource will comply with the Agency’s policies and procedures.

The resource will be issued an Agency laptop and is expected to provide at least one additional monitor, an external keyboard and a mouse at their own expense. In addition, when the resource is working from their home location they must have a private office space and are not permitted to work in an open communal space. Internet connection must be hard-wired and suitable bandwidth to support the IT requirements of this role. If these conditions cannot be met within their home office space, the resource will transition to full time in office, and the hybrid option will no longer be available.

The Agency systems cannot be accessed from outside the province of Ontario, and Agency assets including laptops and related equipment cannot be removed from the province of Ontario, without prior written approval from the Agency.

Assignment Type: This position is currently listed as "Hybrid". The resource under this request will be required to work onsite as per Hiring Manager sole discretion.

Knowledge Transfer Details

• The resource will ensure full knowledge transfer is provided to the Agency team before end of engagement. Some of this might occur at the end of the engagement but will also be shared as information is obtained/consolidated. Key deliverables will be shared with team.
• The resource must provide all related documentation as part of knowledge transfer protocol. Documents will be reviewed by the appropriate leads and signed off by manager/director.
• The resource will work collaboratively with the Agency team throughout the assignment and ensure key deliverables, milestones, and documentation are shared.
• A walkthrough of any demos, development, etc. will be required before the end of the engagement.