...
| Role | Description |
|---|---|
| Change Control Board | The Interoperability Change Control Board (CCB) are accountable for and will manage the interoperability roadmap and evolution of the specifications, deciding on the priorities and content for upcoming releases, and managing the backlog. The CCB will consist of Interoperability management, subject matter experts and representatives from the Operational and Strategic Governance bodies. |
| IO Team | This Infoway IO Team is responsible for developing and publishing the interoperability specifications in collaboration with it’s partners, for recommendation and approval. They will plan/ host testing events (e.g., Projectathons) and will also provide leadership and subject matter expertise representation on the CCB. |
| Jurisdictional Partners | Jurisdictional Partners (i.e., Canadian jurisdictions participating in the interoperability specifications advancements) will provide input into the process through collaboration with the Infoway IO Team, sharing their priorities, providing feedback during the comment disposition process, participation in testing events and sharing lessons learned from their implementation experience(s). |
| Public Stakeholders | Public Stakeholders (e.g., vendors, PCHO's, etc.) will provide input into the process through the comment disposition process, Infoway-hosted webinar / information gathering sessions, participation in testing events (e.g., Projectathons) and by sharing lessons learned from their implementation experience, where applicable. |
| Operational Governance | The Operational Governance body will participate in the ongoing development and alignment of the pan-Canadian work with jurisdictional priority areas and provide recommendations on the evolution of the interoperability specifications. |
| Strategic Governance | The Strategic Governance body will participate in the ongoing development and alignment of the pan-Canadian work with jurisdictional priority areas and provide strategic direction on the evolution of the interoperability specifications. |
IO Specification Publication Process Example
The following table provides an example scenario of a specification flowing through the Interoperability Publication Process from the initial Draft through to its' Final release.
...
Trial Implementation: Second TI release.
Note v2.0.0 TI may co-exist with v1.1.0 TI, depending on market adoption of v1.1.0 TI.
Input from governance, jurisdictions and other stakeholders (e.g., implementers, PCHO's), the backlog & roadmap will inform future releases.
At such time where no further changes are required, the TI release will be deemed ready to transition to the Final version. Until such time, the cycle of Draft - Trial Implementation releases will continue.
...