Full Stack Developer - Senior, for OCRE Project

Assignment: RQ00811 - Software Developer - Full Stack - Senior

Requisition: RQ00811

Job Title: Full Stack Developer - Senior, for OCRE Project

Client: Ontario Health

Start Date: 2026-11-23

End Date: 2027-05-20

Department: Digital Excellence in Health

Office Location: 525 University Avenue, Toronto

Business Days: 124.00

Location: Onsite as needed basis

Public Sector Experience: must have

Must Haves:

• Java, Spring Boot, REST API, and HAPI FHIR development experience, including hands-on processing of FHIR R4 and DSTU2 resources in production-grade services.
• NextGen Connect (Mirth) and HL7 v2 integration experience, including transformation, validation, routing, acknowledgements, error handling, Java-service integration, and practical experience with the Ontario HRM Standard.
• ReactJS full-stack development experience and hands-on knowledge of FHIR Subscriptions and Ontario Health Enterprise Pub/Sub, including translating physician-level preferences into subscription filter criteria.
• Secure application and container delivery experience using OAuth 2.0, mTLS, Docker, automated testing, configuration management, audit logging, and production troubleshooting.

Description

• The Agency requires a Senior Fullstack Developer contract resource to support the Ontario Clinical Report Exchange (OCRE) project. The resource will help design and build a Java Spring Boot server that replaces the legacy Hospital Report Manager (HRM) solution and supports the secure exchange of hospital clinical reports with electronic medical record systems. The role spans the OCRE integration, backend, and user-interface layers. NextGen Connect (Mirth) will process inbound HL7 v2 messages and send the resulting content to Java services, while HAPI FHIR will be used to process FHIR R4 and DSTU2 resources. The resource will also integrate with Ontario Health Enterprise Pub/Sub and develop a ReactJS application that enables EMR users to create physician-specific OCRE FHIR Subscriptions by translating user preferences into Pub/Sub filter criteria. The solution must use OAuth 2.0 and mutual TLS (mTLS) and be packaged for containerized deployment using Docker.

Required Experience:

• Senior-level hands-on experience developing Java and Spring Boot services and REST APIs, including use of the HAPI FHIR library to process FHIR R4 and DSTU2 resources.
• Hands-on experience with NextGen Connect (Mirth), HL7 v2 message processing, transformation, validation, routing, acknowledgements, and integration with Java services.
• Experience in Ontario HRM Standard and hospital clinical report exchange workflows.
• Strong ReactJS development experience building production user interfaces and integrating them with Java/Spring Boot services and FHIR APIs.
• Experience with FHIR Subscriptions and event-driven integrations, including translating physician-level user preferences into filter criteria for the FHIR R4B or R5 Subscriptions with OAuth 2.0 and mTLS for secure service-to-service and application integration.

Responsibilities:

• Design, develop, test, and support the Java Spring Boot server that will replace the legacy HRM solution within OCRE.
• Use HAPI FHIR to parse, validate, transform, create, and process FHIR R4 and DSTU2 resources used by OCRE services and integrations.
• Develop and maintain NextGen Connect (Mirth) channels that receive and process HL7 v2 messages and securely send the resulting content to Java services.
• Implement clinical report processing, routing, acknowledgements, exception handling, and operational controls in accordance with the Ontario HRM Standard.
• Integrate OCRE services with Ontario Health Enterprise Pub/Sub and the applicable FHIR Subscription workflows.
• Develop and support a ReactJS application that allows EMR users to manage OCRE subscription preferences for individual physicians.
• Translate preference selections captured in the user experience into valid FHIR Subscription and Ontario Health Enterprise Pub/Sub filter criteria.
• Implement OAuth 2.0, mTLS, authorization controls, secure configuration, audit logging, and privacy-aware handling of clinical information.
• Package and configure application components as Docker containers and support their deployment, configuration, monitoring, and troubleshooting.
• Create and maintain unit, integration, interface, conformance, regression, and end-to-end tests across HL7 v2, FHIR, Pub/Sub, backend, and ReactJS components.
• Collaborate with architecture, product, UX, security, privacy, QA, operations, and EMR integration stakeholders to refine requirements and deliver production-ready functionality.
• Prepare technical designs, interface specifications, message and resource mappings, configuration documentation, deployment notes, runbooks, and knowledge-transfer materials.

Desired Skills:

• Experience modernizing a hospital clinical report exchange platform, with detailed knowledge of Ontario HRM specifications, routing, acknowledgements, exception handling, and conformance.
• Experience with FHIR Subscription and SubscriptionTopic concepts, subscription filtering, practitioner-based routing, and FHIR profile validation using HAPI FHIR tooling.
• Experience designing accessible ReactJS user experiences for configuration, preference management, or administrative workflows.
• Experience with automated build, test, container scanning, and deployment pipelines for Java, ReactJS, NextGen Connect, and Docker components.
• Experience supporting production healthcare integrations, including observability, reconciliation, incident investigation, replay or recovery procedures, and operational documentation.

Required Skills:

• Java, Spring Boot, REST API, and HAPI FHIR development experience, including hands-on processing of FHIR R4 and DSTU2 resources in production-grade services.
• NextGen Connect (Mirth) and HL7 v2 integration experience, including transformation, validation, routing, acknowledgements, error handling, Java-service integration, and practical experience with the Ontario HRM Standard.
• ReactJS full-stack development experience and hands-on knowledge of FHIR Subscriptions and Ontario Health Enterprise Pub/Sub, including translating physician-level preferences into subscription filter criteria.
• Secure application and container delivery experience using OAuth 2.0, mTLS, Docker, automated testing, configuration management, audit logging, and production troubleshooting.

Rated Criteria: 100 Points

• Java, Spring Boot, REST API, and HAPI FHIR experience, including the design and implementation of production services that process FHIR R4 and DSTU2 resources. 25 points
• NextGen Connect (Mirth), HL7 v2, and Ontario HRM Standard experience, including message transformation, validation, routing, acknowledgements, error handling, and Java-service integration. 25 points
• ReactJS, FHIR R4B Subscriptions, subscription filter criteria. 25 points
• OAuth 2.0, mTLS, Docker, secure application development, automated testing, deployment support, and production troubleshooting experience. 25 points

Deliverables:

• A production-ready Java Spring Boot server that implements the assigned OCRE capabilities and supports replacement of the legacy HRM solution.
• HAPI FHIR components for parsing, validating, transforming, creating, and processing FHIR R4 and DSTU2 resources.
• NextGen Connect (Mirth) channels and configurations for HL7 v2 ingestion, processing, validation, routing, acknowledgement handling, and integration with Java services.
• Ontario HRM Standard mappings, processing rules, conformance artifacts, and exception-handling components required by the assigned workflows.
• Integration components connecting OCRE services with Ontario Health Enterprise Pub/Sub and the applicable FHIR Subscription workflows.
• ReactJS components that allow EMR users to create and manage physician-specific OCRE subscription preferences.
• Preference-to-filter mapping logic that produces valid FHIR Subscription and Ontario Health Enterprise Pub/Sub filter criteria.
• OAuth 2.0, mTLS, secure configuration, audit logging, and Docker packaging required for deployment and operation of the solution.
• Unit, integration, interface, conformance, regression, and end-to-end test assets, together with defect fixes and release validation support.
• Technical designs, API and interface specifications, message and resource mappings, configuration notes, deployment instructions, runbooks, demos, and release-support 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.