Senior Clinical IAM & SSO Architect – Healthcare

Job Description: Senior Clinical IAM & SSO Architect – Healthcare
Client: Service New Brunswick (SNB)
Program: Symbio – Provincial Clinical Information Solution (CIS)
Position: Senior Clinical IAM & SSO Architect – Healthcare
Technical Classification: Technical Specialist 2 (TS2)
Contract Start Date: December 7, 2026, or earlier if possible
Contract End Date: December 6, 2028
Contract Duration: 2 years, with two optional 1-year renewals
Work Location: Remote, with travel to New Brunswick at least once per quarter
Work Schedule: Monday–Friday, 8:15 AM–4:30 PM Atlantic Standard Time (AST)
Reporting To: Director of Symbio Solution Strategy, CIS Project
Language: English required; French is an asset
1. Position Overview
Service New Brunswick (SNB) is seeking a Senior Clinical IAM and Context Specialist (TS2) to support the design, assessment, and implementation of Identity and Access Management (IAM), authentication, clinical application integration, and contextual workflow capabilities for New Brunswick's provincial Clinical Information Solution (CIS).
The province is transitioning from multiple standalone clinical systems to a single provincial CIS. The successful candidate will assess current-state identity and access capabilities, identify technical gaps, develop target-state architecture recommendations, and support the integration of clinical applications and identity services across the provincial healthcare environment.
The specialist will help establish a secure, consistent, and efficient clinical access experience, including Single Sign-On (SSO), tap-and-go technologies, session continuity, contextual application launch, patient-context synchronization, clinician mobility, and integration with connected clinical systems.
This position requires a combination of enterprise architecture, hands-on technical implementation, clinical workflow knowledge, identity integration, troubleshooting, and stakeholder collaboration. The specialist will work closely with SNB enterprise architecture and IAM teams, CIS vendors, cybersecurity teams, clinical leaders, application owners, infrastructure teams, and operational support groups across Horizon and Vitalité.
The successful candidate will also mentor New Brunswick program personnel, facilitate knowledge transfer, and support the transition of implemented capabilities into sustainable operational support.
2. Key Responsibilities
A. Architecture Assessment and Strategy

• Assess current-state and future-state identity integration, authentication, application modernization, and clinical access architectures.
  
• Develop architectural recommendations aligned with provincial standards, enterprise architecture direction, and clinical workflow requirements.
  
• Identify technical dependencies, architectural constraints, integration challenges, and implementation risks.
  
• Evaluate opportunities to improve and consolidate access to the provincial CIS and connected clinical applications.
  

B. Clinical Authentication and Access Architecture

• Assess and design authentication and access solutions, including:
  
  • Single Sign-On (SSO).
    
  • Tap-and-go and badge-based authentication technologies.
    
  • Multi-factor authentication (MFA).
    
  • Federation and remote access solutions.
    
  • Shared workstation environments.
    
  • Clinical session management and session continuity.
    
  • Clinician mobility and session roaming.
    
• Ensure authentication and access approaches support clinical efficiency and appropriate security controls.
  

C. Contextual Launch and Clinical Workflow Integration

• Assess and validate clinician access workflows across clinical applications.
  
• Support launch-in-context capabilities and contextual application launching.
  
• Evaluate synchronization and sharing of patient context between multiple applications.
  
• Assess workflow-aware application access, clinical application interoperability, and user workflow optimization.
  
• Support continuity of clinical access as clinicians move between workstations and care settings.
  

D. Technical Solution Design and Proof of Concept

• Develop detailed technical solution designs and implementation recommendations.
  
• Participate directly in configuration, identity integration, testing, troubleshooting, proof-of-concept activities, and pilot implementations.
  
• Validate authentication, identity integration, contextual launch, and clinical application access approaches.
  
• Document solution options, technical findings, test results, and recommendations.
  

E. Clinical Device Access Architecture

• Collaborate with endpoint, infrastructure, and clinical technology teams to assess clinical device usage models.
  
• Define appropriate authentication, application access, session management, and mobility requirements for different device categories.
  
• Assess access requirements for shared workstations, clinical endpoints, and mobile clinical environments.
  

F. Clinical Application Portfolio Assessment and Readiness

• Assess clinical application portfolios to determine authentication and identity integration requirements.
  
• Identify SSO candidates, launch-in-context candidates, integration dependencies, and modernization opportunities.
  
• Evaluate legacy authentication constraints and application readiness for CIS deployment.
  
• Align application access and integration readiness activities with implementation schedules and deployment priorities.
  

G. Identity and Application Integration

• Design and validate integrations among the CIS, connected clinical applications, IAM platforms, directory services, provisioning solutions, endpoint technologies, and related systems.
  
• Assess and address legacy authentication constraints and multi-domain identity requirements.
  
• Evaluate LDAP integration, identity federation, modern authentication protocols, and API integration patterns.
  
• Support healthcare interoperability and integration across clinical applications and enterprise platforms.
  

H. Deployment Support and Issue Resolution

• Provide technical guidance during CIS testing, proof-of-concept activities, pilots, and deployment waves.
  
• Investigate and resolve authentication, session management, identity integration, and clinical application access issues.
  
• Coordinate with vendors, application teams, and operational support groups to troubleshoot technical issues.
  
• Support deployment planning, architecture reviews, solution recommendations, testing, and go-live activities.
  

I. Operational Readiness and Transition

• Define operational support models and procedures for clinical access and identity integration capabilities.
  
• Prepare architecture and integration documentation, operational runbooks, and support guidance.
  
• Support operational readiness planning and handover to ongoing support teams.
  
• Conduct knowledge-transfer sessions and mentor program personnel to build sustainable internal capabilities.
  

J. Stakeholder Engagement and Knowledge Transfer

• Work collaboratively with enterprise architecture, IAM, cybersecurity, clinical, application, infrastructure, vendor, and operational teams.
  
• Lead workshops, facilitate technical decisions, and present complex IAM and clinical access topics to stakeholders at different organizational levels.
  
• Communicate architecture decisions, technical dependencies, risks, and implementation recommendations.
  
• Mentor New Brunswick program pers
  

Requirements

3. Mandatory Requirements (M1–M9)
Candidates must clearly demonstrate compliance with every mandatory requirement. Submissions that do not adequately establish the required qualifications and experience may be disqualified.

ID
Mandatory requirement
Minimum qualification
M1
A bachelor's-level university degree in Computer Science, Business Administration, Health Informatics, or a similar discipline. An equivalent combination of education and experience may be considered.
Required
M2
Demonstrated experience designing or assessing application access, authentication, identity integration, or clinical workflow solutions within large, complex healthcare or enterprise environments.
3+ years
M3
Experience in a hospital or clinical environment, including understanding how application access, authentication methods, contextual launch, session management, and clinical workflows impact patient care and clinician efficiency.
3+ years
M4
Experience developing solution architectures and conducting technical assessments involving multiple applications, integration platforms, identity services, and end-user technologies.
5+ years
M5
Experience working with application owners, clinical stakeholders, technical teams, and vendors to assess workflow requirements and align technology solutions with operational needs.
3+ years
M6
Experience supporting large-scale system implementations through architecture reviews, solution recommendations, deployment planning, testing, and go-live support activities.
5+ years
Mandatory submission guidance: For M1–M6, the candidate's submission must provide sufficient detail to validate the relevant education and experience. Include the client or organization, project and role, start and end dates in month/year format, duration, responsibilities, relevant achievements, and resume page references. The conflict-of-interest restriction and submission limits must also be observed.
4. Scored Requirements and Desirable Skills (S1–S10)
Candidates should demonstrate the following experience in their resumes and candidate response matrix. Higher scores may be awarded for experience exceeding the stated minimums and for demonstrable hands-on implementation and troubleshooting.
S1. Clinical Authentication and Access Architecture — 5+ Years
Demonstrated experience designing or assessing clinical authentication and access solutions, including:

• Single Sign-On (SSO).
  
• Tap-and-go technologies.
  
• Multi-factor authentication (MFA).
  
• Clinical session management.
  
• Shared workstation environments.
  
• Remote access solutions.
  

S2. Contextual Launch and Clinical Workflow Integration — 5+ Years
Demonstrated experience assessing or implementing:

• Launch in Context.
  
• Maintaining synchronized context between multiple applications.
  
• Context sharing.
  
• Workflow-aware application access.
  
• Clinical application interoperability.
  
• User workflow optimization.
  

S3. Clinical Application Portfolio Assessment — 3+ Years
Experience assessing application portfolios to determine:

• Authentication requirements.
  
• Integration requirements.
  
• Modernization opportunities.
  
• SSO candidates.
  
• Launch-in-context candidates.
  
• Clinical workflow dependencies.
  

S4. Identity and Integration Architecture — 5+ Years
Experience designing or evaluating:

• Active Directory and Microsoft Entra ID integrations.
  
• Identity federation.
  
• Provisioning approaches.
  
• Application integrations.
  
• API integration patterns.
  
• Healthcare interoperability environments.
  

S5. Healthcare Technology Modernization — 5+ Years
Experience evaluating or implementing modernization initiatives involving:

• Legacy application remediation.
  
• Authentication modernization.
  
• Consolidated access experiences.
  
• Clinical mobility solutions.
  
• Cloud-hosted clinical solutions.
  

S6. Risk, Dependency and Constraint Management — 5+ Years
Experience identifying and managing:

• Technical dependencies.
  
• Architectural constraints.
  
• Clinical workflow risks.
  
• Integration risks.
  
• Authentication risks.
  

S7. Operational Transition and Knowledge Transfer — 5+ Years
Experience transitioning architecture and integration guidance into operational support models through: