Job Description

Our client, provincial Government, is shifting to a digital-first, service-oriented delivery model. This will require interoperability and a secure messaging fabric. To enable this shift, ITSS is deploying an Enterprise Integration Platform and services to standardize, optimize, and modernize its integration architecture. The \'Digital Architecture Vision\' is to enable data to be entered once, in the designated source of truth application, and then to be reused by other enterprise applications directly through the Enterprise Integration
Platform.
Government has selected SmileCDR as its clinical data repository solution. SmileCDR is a FHIR CDR
designed to complete the vision of access and digitization for Government. The Clinical Data Repository (CDR) will provide a set of APIs that enable access to the government\'s clinical data using the FHIR standard.
Conceptually the CDR is intended to store clinical data from Government source systems and provide a
set of APIs that enable the management of and access to that data using the FHIR standard.
Government is moving forward with a piece of work that will allow the continuance of moving data into
the CDR and working towards key data that is on the CDR roadmap. This will assist in building the foundations of the information within the CDR that can be consumed by Clients or assist in issues with current integrations or future integrations.The resource(s) provided by the successful Proponent(s) must have the following experience:
\xef\x82\xb7 A minimum of three (3) to five (5) of years demonstrated experience working with SMILE CDR;
\xef\x82\xb7 Extensive knowledge of FHIR and integration into CDRs;
\xef\x82\xb7 Experience designing and architecting CDR integrations;
\xef\x82\xb7 Experience working with government organizations is an asset; and
\xef\x82\xb7 Experience in being a technical lead in projects is considered to be an asset.The scope of the services may include, but are not limited to:
\xef\x82\xb7 Facilitate requirements sessions to gather business needs/requirements for CDR projects;
\xef\x82\xb7 Analyze the business needs, requirements and data sets;
\xef\x82\xb7 Transform business requirements into an object model and workflow design;
\xef\x82\xb7 Evaluate and build data architecture and data flow;
\xef\x82\xb7 Develop high-level and detailed Data design specifications;
\xef\x82\xb7 Develop frameworks for new CDR requests;
\xef\x82\xb7 Define CDR standards including the recommended use of languages and tools;
\xef\x82\xb7 Specify data modeling and database development technologies and techniques;
\xef\x82\xb7 Provide training and guidance to any new staff within the province;
\xef\x82\xb7 Develop high-level schemas for the CDR application; and
\xef\x82\xb7 Other work relevant to the service category as required.Expected Deliverables

• Kick Off Meeting: The resource will attend the meeting, along with the Government team responsible for this SOW. An in person meeting would be preferable, if possible.
• Current state design and documentation: \xef\x82\xb7Review the current network and application design for any existing application or solution and dealing with teams that might be involved with operational support; and \xef\x82\xb7 Develop updated and new diagrams for the CDR and new integrations. Any current state design document must be in MS Word format and should include detail information regarding the current integration, the data points, and direction of the flow of data, etc. All diagrams provided to the province need to be editable.
• CDR Roadmap: \xef\x82\xb7 Work with business and IT sections to come up with a roadmap for the CDR, that outlines the applications and datasets that should be pulled in.
• CDR Projects: \xef\x82\xb7 Work with external vendors, Health sections, and ITSS on CDR projects that are already in place and ones that are identified during the roadmap
• Develop architecture and the framework for the integration of applications: The development of any architecture documents. The documents will include all networks and applications that would then integrate with the Enterprise Integration Platform. Any framework should include how the data and services interact with the applications, existing and future. This documentation can be a mix of MS Word and Visio formats to layout the architecture and framework for the government to move forward. The information provided will have a Health focus, but also should include architecture and framework that can be replicated to Core Government and Education.
• Bi-weekly Meetings: After the project kick off meeting, there will be a requirement to have bi-weekly meetings to provide project and status information. MS Presentation format is the preferred format for the bi-weekly meetings to provide project and status information. The presentation should include work completed, pending tasks, action items, and the individuals responsible for each task.

SRA Staffing Solutions