Job Description:

• Work with Client Integration team to define and implement integration strategies and guiding principles related to integration work required to replace multiple existing Clinical Information Systems with a single, consolidated Clinical Information System.
• Work with Client Systems Integration Services team to define a CIS Implementation strategy for CIS Integration solutions.
• High-level architecture diagrams and documents describing how the new system integrates with other systems (e.g., Electronic Health Records (EHR), laboratory systems, pharmacy systems).
• System architecture overview.
• Integration touchpoints and data flow.
• Integration protocols (HL7, FHIR, DICOM, etc.).
• Middleware and platform selection.
• Security and compliance considerations.

Responsible for Integration Design Specifications:

• Detailed specifications for each interface or integration point between the Clinical Information System and other systems.
• Work directly with customers and support teams to define requirements and present solutions.
• Data formats and standards (FHIR, HL7 v2/v3, CDA).
• APIs or web services used for integration.
• Mapping between source and target systems data models.
• Error handling and data validation rules.
• Frequency and timing of data exchange (real-time, batch).
• Ensure alignment with Client Integration team design documentation.

Responsible for Data mapping and Transformation Rules:

• A comprehensive mapping of data elements between the Clinical Information System and other systems, including any necessary transformations.
• Field-by-field mapping document.
• Data transformation logic (e.g., converting data formats, units).
• Handling of missing or incomplete data.
• Data consistency checks.

Responsible for Integration Test Plans:

• A test plan outlining how the integration will be validated, ensuring data flows correctly and all integration points work as expected.
• Test cases for each interface.
• End-to-end test scenarios.
• Testing methodology (unit tests, integration tests, user acceptance tests).
• Success criteria for each test.
• Tools and resources required for testing.
• Documentation around handling failures.

Responsible for Security and Compliance Assessments:

• A review of the integration design to ensure that it meets healthcare industry security standards and regulations.
• Encryption methods for data at rest and in transit.
• Access control policies (who can access what data).
• Compliance with relevant laws and standards.
• Audit trails and logging requirements.
• Data retention and deletion policies.

Responsible for Data Flow Diagrams:

• Visual representations showing how data moves between systems and components.
• Context-level and detailed DFDs for each integration touchpoint.
• Data sources and destinations.
• Data flow paths, including transformations or intermediate systems.

Responsible for System Interaction Diagrams:

• Diagrams that illustrate how different systems (e.g., CIS, EHR, lab system) communicate with each other.
• Sequence diagrams or interaction diagrams showing communication flow.
• API interactions.
• Protocols and message formats used for communication.

Responsible for Implementation Roadmap:

• A timeline and action plan detailing the phases and milestones for the integration project.
• Key milestones for integration (e.g., completion of design, testing phases, go-live)
• Work with Client Integration team on resource allocation.
• Timeline with dependencies.
• Risk assessment and mitigation plan.

Responsible for Change Management and Support Plan:

• A plan to ensure a smooth transition to the new system and ongoing support.
• Technical leadership, setting best practices for integration, testing, and iterative refinement.
• Training plan for staff on new integrations.
• Documentation of new processes and procedures.
• Support and troubleshooting guide.
• Incident response procedures.

Responsible for Documentation of the Integration Environment:

• Detailed documentation about the integration environment, such as configurations, tools, and infrastructure.
• Configuration details of middleware, APIs, and messaging queues.
• Overview of the staging, development, and production environments.
• Network and infrastructure requirements for integration.

Responsible for Performance and Scalability Plan:

• A document addressing the system s performance under load and its scalability as the healthcare organization grows.
• Performance testing criteria (response time, throughput).
• Load balancing and fault tolerance strategies.
• Scalability requirements for handling increased data or system load.

Responsible for Post-Implementation Monitoring and Maintenance Plan:

• Plan for monitoring the integration post-go-live to ensure it operates smoothly and troubleshooting any issues that arise.
• System monitoring tools and metrics.
• Incident management and escalation process.
• Long-term maintenance schedule (e.g., updates, patches).
• Provide technical expertise and support to Client Systems Integration Services team.

Mandate Requirements:

• Our client seeks a resource that demonstrates the following mandatory experience:
• A University degree in Computer Science or Information Technology is preferred but an equivalent combination of education and experience may be considered Yes/ No
• A minimum of seven (7) years of IM/IT experience 7 years.
• A minimum of five (5) or more years of demonstrated experience leading integration architecture in the healthcare sector 5 years.
• A minimum of three (3) or more years of demonstrated combined experience using HL7 v2x and FHIR to integrate healthcare solutions 3 years.
• A minimum of three (3) or more years of demonstrated combined experience using MS BizTalk Server and MS Azure Integration Services 3 years.

Scored Requirements:

• Demonstrated experience leading integration architecture in a healthcare setting.
• Reference engagements that demonstrate experience and describe role and responsibilities 5 years.

Clearly Demonstrate:

• Summary of referenced engagements.
• Duration of referenced engagements.
• Specific healthcare systems involved (vendor and product) .
• Demonstrated experience in Application Integration Design and Implementation in a healthcare setting.
• Demonstrated experience leading technical design and technical requirements gathering sessions.

Project Reference:

• Types of deliverables candidates generated.
• Demonstrated experience with HL7 v2x and/or FHIR in Microsoft BizTalk Server.
• Specific healthcare systems involved (vendor and product).
• Demonstrated experience with HL7 v2x and/or FHIR in Microsoft Azure Integration Services, specifically Azure Logic Apps, Azure Service Bus, Azure Functions and/or Azure API Management.
• Types of systems that were being integrated
• Specific healthcare systems involved (vendor and product)
• The Azure Integration Service product(s) that was leveraged.
• Demonstrated experience in the design and implementation of highly available integration architectures.
• Demonstrated experience in the design and implementation of disaster recovery integration architectures.
• Demonstrated experience with industry leading Clinical Information System vendors (Health Information Systems)
• Specific Clinical Information System(s) and/or vendor(s) worked with.
• Demonstrated experience working within multi-vendor healthcare teams would be considered an asset
• Specific vendors involved.
• Demonstrated experience in implementing/architecting healthcare integration solutions to PaaS and/or SaaS offerings would be an asset
• Specific healthcare systems involved (vendor and product)
• Identify SaaS systems vs on-prem systems vs systems in other cloud environments.
• Demonstrated experience migrating on-prem Microsoft BizTalk Server HL7 v2.x integration solutions to an Azure Integration Services iPaaS environment would be considered an asset
• Specific Azure Integration Services products used.
• Demonstrated experience with integration solutions exchanging data between a hospitals core Clinical Information Systems (Health Information Systems) and ancillary systems or other Clinical Information Systems (Health Information Systems) would be an asset.
• Clinical Information Systems involved (i.e. vendor and product).
• Mechanism used to exchange data (i.e. - HL7, FHIR, SFTP).