Bachelor's degree in Computer Science, Information Technology, or a related field., Extensive experience in healthcare integration architecture and systems integration., Proficiency in integration protocols such as HL7, FHIR, and DICOM., Strong understanding of security and compliance standards in healthcare..
Key responsabilities:
Develop and maintain the Integration Architecture Blueprint for the Clinical Information System.
Collaborate with integration teams to define and implement integration strategies and solutions.
Create detailed integration design specifications and data mapping documents.
Conduct security and compliance assessments to ensure adherence to healthcare regulations.
Report This Job
Help us maintain the quality of our job listings. If you find any issues with this job post, please let us know.
Select the reason you're reporting this job:
SMSS Inc. is the best solution company specialized in providing Information Technology and Management Consulting. We provide value for money to our clients by delivering the best quality technical services and solutions at reasonable rates. We also provide the best working environment for our staff and consultants. It is a growing IT services provider having wide array of solutions from Business Strategy Analysis to implementation and execution of Information Technology as well as management aspects of a business entity.
Without mandatory documents, we cannot submit a candidate.
Updated Resume in word format (Mandatory)
Skills Matrix and References (Mandatory)
Expected hourly rate (Mandatory)
Visa Status (Mandatory)
LinkedIn ID (Mandatory)
Job Title:REQ21628 - Senior Healthcare Integration Architect Client: Province of New Brunswick Department: SNB-Strategy, Planning & Solutions Business Days: 540 days ** Closing Date/Time: April 1st, 2025, 10:30 AM EST Office Location: In Fredericton, Remote Contract Duration: Asap until 30-Apr-2027 end date (Possibility for extension and conversion to FT) Standard Hours per day: 7.25 hours work day
Deliverables The successful candidate must deliver the following (including but not limited to) in order to successfully complete the engagement:
Responsible for Integration Architecture Blueprint;
Work with SNB Integration team to define and implement integration strategies and guiding principals related to integration work required to replace multiple existing Clinical Information Systems with a single, consolidated Clinical Information System
Work with SNB 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 SNB 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 cas es 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 (DFD)
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 SNB 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