Table of Contents
Interoperability (IO) Specification Publication Model
The Interoperability Specification Publication Model describes the lifecycle of the interoperability specifications (e.g., PS-CA, CA:FeX). Specifications will be identified according to semantic versioning, using a three-part version number and release type tag (e.g., v0.1.0 DFT, v1.1.1 TI, etc.,). The tag will identify the Specification Publication Type (i.e., maturity level) as either Draft (DFT), Trial Implementation (TI) or Final (Final).
The following table provides a summary view of the IO Specification Publication Model. There are three Specification Publication Types: Draft, Trial Implementation and Final, which represent the level of maturity for the specification. Within each Specification Publication Type, there are two attributes that further define the maturity level: Implementation Readiness and Prototyping / Validation Readiness. Definitions for each Specification Publication Type and Attribute can be found in the sections below.
The IO Specification Publication Model may also be accessed in PDF format here.
Specification Publication Types | |||
---|---|---|---|
Publication Attributes | Draft | Trial Implementation | Final |
Implementation Readiness | In Development | Limited Roll-Out | Production |
Prototyping / Validation Readiness | Beta Testing / Beta Projectathon | Projectathon / Conformance | Connectathon / Certification |
IO Specification Publication Types
When this designation is assigned, the specification is currently in development and may be in the midst of an internal and/or public review period. These specifications will generally benefit from lessons learned through development and pilots.
When this designation is assigned, the specification is considered to be a draft for trial use / trial implementation in production systems. It has been cycled through public open review and comment dispositioning has been completed. In some cases, features and capabilities or known issues may be documented in the backlog for inclusion in a future trial implementation release.
When this designation is assigned, the specification is considered to have addressed all stakeholder comments received in reviews of prior releases. Projectathon testing has been successfully completed, with all known issues resolved. And, all documentation is complete, providing implementers the ability to use the specification for compliance and certification of their products. |
IO Specification Attribute Definitions
|
IO Specification Publication Versioning
The interoperability specifications will follow semantic versioning, using a three-part version number and release type tag (e.g., v0.1.0 DFT, v1.1.1 TI, etc.,).
Major:
Minor:
Patch:
Release Tag:
|
IO Specification Publication Process Flow
Click on the image to view in full size.
IO Specification Publication Process Roles
Role | Description |
---|---|
Change Control Board | The Interoperability Change Control Board (CCB) will be 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. |